Resource protection method and device

Abstract

The invention relates to the field of resource collection, and particularly provides a resource protection method and device, and the method comprises the following steps: S1, for a collection source, generating resources of a deletion list, and collecting and obtaining the deletion list at the same time; s2, for the resources of which the deletion list cannot be generated by the acquisition source, a safety threshold mode needs to be adopted; s3, a safety threshold mode is adopted for the deletion condition; s4, configuring a security threshold for each resource in the system; and S5, analyzing the data quantity of each day by the system, and updating the safety threshold in real time through an algorithm to meet the actual deletion requirement of each resource in an actual scene. Compared with the prior art, the method and the device have the advantages that stock resources in the system can be protected in the resource collection process, errors can be effectively recognized under the condition that collection files are generated mistakenly, and therefore mistaken updating of the resources is avoided.

Description

Technical Field

[0001] The present invention relates to the field of resource collection, and specifically provides a resource protection method and device. Background Art

[0002] In the prior art, the resource collection logic lacks a security protection mechanism, and there are relatively large security risks in actual application scenarios. Therefore, it is necessary to add this resource collection protection mechanism to ensure the correctness of system resource collection.

[0003] Common resource file errors include:

[0004] (1) The collection file format is incorrect, resulting in parsing failure;

[0005] (2) The collection file generation is recognized, resulting in an empty content;

[0006] (3) The connection to the server where the collection file is generated is abnormal, resulting in collection errors.

[0007] The industry usually directly stores the data after collection into the database, which cannot guarantee the accuracy of the data. At the same time, it cannot provide protection for the existing data in the system, and it is easy to perform a large number of additions and deletions to the data, thus causing a disastrous impact on the subsequent business logic. Summary of the Invention

[0008] The present invention aims at the above-mentioned deficiencies of the prior art and provides a resource protection method with strong practicability.

[0009] A further technical task of the present invention is to provide a resource protection device with reasonable design, safety and applicability.

[0010] The technical solution adopted by the present invention to solve its technical problems is:

[0011] A resource protection method, comprising the following steps:

[0012] S1. For the resources for which the collection source generates a deletion list, it is necessary to simultaneously collect and obtain the deletion list;

[0013] S2. For the resources for which the collection source cannot generate a deletion list, it is necessary to adopt the method of a safety threshold;

[0014] S3. Adopt the method of a safety threshold for the deletion situation;

[0015] S4. A safety threshold can be configured for each type of resource in the system;

[0016] S5. The system analyzes the data quantity of each day, and the safety threshold is updated in real time through an algorithm to meet the actual deletion requirements of each resource in the actual scenario.

[0017] Further, in step S1, during the preprocessing of resources, resource comparison is not required. The collected resource deletion list is deleted from the resource table, and only the resource part existing in the resource deletion table is processed.

[0018] Further, in step S2, the security threshold T = the number of resources deleted / the number of resources before collection. A security threshold is configured for each resource, and the number of each type of resource per day is recorded.

[0019] After resource collection, it is first entered into a temporary table for management. Each type of resource is preprocessed in the temporary table, and the number of resources on the current day is obtained and compared with the previous number of this resource. If the deletion ratio exceeds the security threshold set for this resource in MinIO, this update is cancelled, and relevant personnel are notified via SMS and email.

[0020] Further, in step S3, for the update situation, in the actual production environment, each type of resource will frequently modify some attributes in large quantities. If the resource is only updated rather than added or deleted, using the security threshold protection in this case does not meet the actual business requirements.

[0021] Further, in step S4, in the actual business scenario, each type of resource has different situations for secure deletion, and a deletion security threshold needs to be configured separately for all types of resources.

[0022] A resource protection device needs to collect and obtain the deletion list for resources that generate a deletion list from the collection source; for resources that cannot generate a deletion list from the collection source, a security threshold method is required for the deletion situation.

[0023] A security threshold can be configured for each type of resource in the system. The system analyzes the data quantity for each day and updates the security threshold in real time through an algorithm to meet the actual deletion requirements of each resource in the actual scenario.

[0024] Further, for resources that generate a deletion list from the collection source, it is necessary to collect and obtain the deletion list simultaneously.

[0025] During the preprocessing of resources, resource comparison is not required. The collected resource deletion list is deleted from the resource table, and only the resource part existing in the resource deletion table is processed.

[0026] Further, for resources that cannot generate a deletion list from the collection source, a security threshold method is required. The security threshold T = the number of resources deleted / the number of resources before collection. A security threshold is configured for each resource, and the number of each type of resource per day is recorded.

[0027] After resource collection, it is first entered into a temporary table for management. Each type of resource is preprocessed in the temporary table, and the quantity of resources for the current day is obtained and compared with the quantity of the same resource previously. If the deletion ratio exceeds the security threshold set for the resource in MinIO, this update is cancelled, and relevant personnel are notified via SMS and email.

[0028] Furthermore, for deletion cases, a security threshold approach is adopted. For update cases, in an actual production environment, each type of resource will frequently modify a large number of attributes in bulk. If the resource is only updated rather than newly added or deleted, using a security threshold protection in this case does not meet the actual business requirements.

[0029] Furthermore, a security threshold can be configured for each type of resource in the system. In an actual business scenario, each type of resource has different requirements for secure deletion, and a deletion security threshold needs to be configured separately for all types of resources.

[0030] Compared with the prior art, a resource protection method and device of the present invention have the following prominent beneficial effects:

[0031] This method effectively realizes the protection of the existing resources in the system during the resource collection process. In the case of incorrect generation of collected files, errors can be effectively identified, thus avoiding incorrect updates of resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0033] Attached Figure 1 is a schematic flowchart of a resource protection method. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0034] In order to enable those skilled in the art to better understand the solutions of the present invention, the following will further elaborate on the present invention in combination with specific embodiments. Obviously, the described embodiments are only some embodiments of the present invention, rather than all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present invention.

[0035] The following presents a best embodiment:

[0036] Such as Figure 1As shown in the figure, a resource protection method in this embodiment has the following steps:

[0037] S1. For the resources for which the collection source generates a deletion list, it is necessary to collect and obtain the deletion list simultaneously;

[0038] During the preprocessing of resources, resource comparison is not required. The collected resource deletion list is deleted in the resource table, and only the resource part existing in the resource deletion table is processed.

[0039] S2. For the resources for which the collection source cannot generate a deletion list, a security threshold method needs to be adopted;

[0040] The security threshold T = the number of resources to be deleted / the number of resources before collection. Configure the security threshold for each resource and record the quantity of each type of resource every day;

[0041] After resource collection, it is first entered into a temporary table for management. Each type of resource is preprocessed in the temporary table, and the quantity of resources for the current day is obtained and compared with the quantity of the same resource before. If the deletion ratio exceeds the security threshold set for this resource in MinIO, this update is cancelled, and relevant personnel are notified via SMS and email.

[0042] S3. Adopt the security threshold method for the deletion situation;

[0043] Adopt the security threshold method for the deletion situation. For the update situation, in the actual production environment, each type of resource will frequently modify some attributes in large quantities. If security threshold protection is also implemented for the update situation, it does not meet the actual business scenario.

[0044] S4. The security threshold can be configured for each type of resource in the system;

[0045] In the actual business scenario, the security deletion situation for each type of resource is different, and a deletion security threshold needs to be configured separately for all types of resources.

[0046] S5. The system analyzes the data quantity for each day and updates the security threshold in real time through an algorithm to meet the actual deletion requirements of each resource in the actual scenario.

[0047] Based on the above method, a resource protection device in this embodiment, for the resources for which the collection source generates a deletion list, it is necessary to collect and obtain the deletion list simultaneously; for the resources for which the collection source cannot generate a deletion list, a security threshold method needs to be adopted, and the security threshold method is adopted for the deletion situation;

[0048] For each type of resource in the system, a security threshold can be configured. The system analyzes the daily data volume and updates the security threshold in real time through an algorithm to meet the actual deletion requirements of each resource in the actual scenario.

[0049] Furthermore, for the resources that generate a deletion list from the data acquisition source, it is necessary to collect and obtain the deletion list simultaneously.

[0050] During the preprocessing of resources, there is no need to compare resources. Delete the collected resource deletion list in the resource table and only process the resource part that exists in the resource deletion table.

[0051] Among them, for the resources that cannot generate a deletion list from the data acquisition source, a security threshold method needs to be adopted. The security threshold T = the number of resources to be deleted / the number of resources before acquisition. Configure the security threshold for each resource and record the quantity of each type of resource every day.

[0052] After resource collection, first enter it into a temporary table for management. Preprocess each type of resource in the temporary table, obtain the quantity of resources on the current day, and compare it with the previous quantity of this resource. If the deletion ratio exceeds the security threshold set for this resource in MinIO, cancel this update and notify relevant personnel via SMS or email.

[0053] For the deletion situation, a security threshold method is adopted. For the update situation, in the actual production environment, each type of resource will frequently modify a large number of attributes in batches. If the resource is only updated rather than newly added or deleted, using the security threshold protection in this case does not meet the actual business requirements.

[0054] For each type of resource in the system, a security threshold can be configured. In the actual business scenario, each type of resource has different security deletion situations, and a deletion security threshold needs to be configured separately for all types of resources.

[0055] The above specific implementation manners are only specific cases of the present invention. The patent protection scope of the present invention includes but is not limited to the above specific implementation manners. Any technical solution that conforms to the above specific implementation manners described in the present invention and any appropriate changes or substitutions made by those of ordinary skill in the relevant technical field shall fall within the patent protection scope of the present invention.

[0056] Although the embodiments of the present invention have been shown and described, for those of ordinary skill in the art, it can be understood that various changes, modifications, substitutions, and variations can be made to these embodiments without departing from the principles and spirit of the present invention. The scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. A resource protection method, characterized in that: The steps are as follows: S1. For resources whose collection source generates a deletion list, it is necessary to collect and obtain the deletion list at the same time; S2. For resources whose collection source cannot generate a deletion list, a security threshold method needs to be used; S3, using a safety threshold approach for deletion; S4. Security thresholds can be configured for each resource in the system; S5. The system analyzes the amount of data each day and updates the security threshold in real time through algorithms to meet the actual deletion requirements of various resources in actual scenarios.

2. A resource protection method according to claim 1, characterized in that: In step S1, in the process of preprocessing resources, it is not necessary to perform resource comparison, and the collected resource deletion list is deleted from the resource table, and only the resource part existing in the resource deletion table is processed.

3. A resource protection method according to claim 2, characterized in that: In step S2, the safety threshold T = the number of resources deleted / the number of resources before collection, configure the safety threshold for each resource, and record the number of each resource every day; After resource collection, they are first entered into a temporary table for management. Each resource is preprocessed in the temporary table, and the number of resources for the day is obtained and compared with the previous number of the resource. If the deletion ratio exceeds the safety threshold set for the resource in MinIO, the update is canceled and relevant personnel are notified by SMS or email.

4. A resource protection method according to claim 3, characterized in that: In step S3, for updates, in an actual production environment, each resource will frequently make large-scale modifications to some attributes. If the resource is only updated instead of added or deleted, the security threshold protection is also used in this case, which does not meet the actual business needs.

5. A resource protection method according to claim 4, characterized in that: In step S4, in actual business scenarios, each type of resource has different conditions for safe deletion, and a deletion safety threshold must be configured separately for each type of resource.

6. A resource protection device, characterized in that: For resources whose collection source generates a deletion list, it is necessary to collect and obtain the deletion list at the same time; for resources whose collection source cannot generate a deletion list, it is necessary to use a safety threshold method to handle deletion situations; A security threshold can be configured for each resource in the system. The system analyzes the amount of data each day and updates the security threshold in real time through an algorithm to meet the actual deletion requirements of each resource in actual scenarios.

7. A resource protection device according to claim 6, characterized in that: For resources whose collection source generates a deletion list, you need to collect and obtain the deletion list at the same time; In the process of preprocessing resources, there is no need to perform resource comparison. The collected resource deletion list is deleted in the resource table, and only the resource part existing in the resource deletion table is processed.

8. A resource protection device according to claim 7, characterized in that: For resources whose collection source cannot generate a deletion list, a safety threshold method needs to be used. The safety threshold T = the number of resources deleted / the number of resources before collection. Configure a safety threshold for each resource and record the number of each resource every day. After resource collection, they are first entered into a temporary table for management. Each resource is preprocessed in the temporary table, and the number of resources for the day is obtained and compared with the previous number of the resource. If the deletion ratio exceeds the safety threshold set for the resource in MinIO, the update is canceled and relevant personnel are notified by SMS or email.

9. A resource protection device according to claim 8, characterized in that: For deletion, a security threshold is used. For update, in the actual production environment, each resource will frequently modify some attributes in large quantities. If the resource is only updated instead of added or deleted, the security threshold protection is also used in this case, which does not meet the actual business needs.

10. A resource protection device according to claim 9, characterized in that: A security threshold can be configured for each resource in the system. In actual business scenarios, each resource has different requirements for safe deletion. Therefore, the deletion security threshold must be configured separately for each type of resource.

Images