A software development data encryption protection method and system

Abstract

The application discloses a software development data encryption protection method and system, and relates to the technical field of data processing.The method comprises the following steps: login protection, data collection, data encryption protection, classification of software development data into ordinary development data and sensitive development data, encryption evaluation, security evaluation of key one and key two by using an encryption security score algorithm, encryption timeliness evaluation, key replacement sorting, sorting of all unqualified key one and key two, replacement according to the order, and data storage.The method has the effects of classifying and encrypting ordinary and sensitive development data, optimizing calculation resources by using differentiated encryption strength, improving encryption efficiency, dynamically adjusting the key rotation strategy by comprehensively considering the length, complexity, use time and security events of the key in combination with the encryption security score algorithm and the timeliness evaluation algorithm, ensuring the orderly and efficient key management, and reducing the security risk of software development data.

Description

A method and system for encrypting and protecting software development data Technical Field

[0001] This invention relates to the field of data processing technology, specifically to a method and system for encrypting and protecting software development data. Background Technology

[0002] Software development is a systematic engineering process that includes requirements gathering, requirements analysis, design, implementation, and testing. Software is generally implemented using a programming language and typically employs software development tools. The general process of software design involves designing the software's functions and implementation algorithms and methods, designing the overall software structure and modules, programming and debugging, program integration and testing, and writing and submitting the program. Because software development carries the risk of modification and copying, developers need to implement encryption measures to protect software development data from theft or damage.

[0003] Because software development generates a large amount of data, the same encryption protection measures are usually applied to each type of data. This consumes a lot of computer resources when encrypting and protecting the data, reducing the efficiency of software development data encryption. Furthermore, currently, only the key expiration time is usually considered, ignoring other factors that may affect key security. This makes the key rotation strategy inaccurate, which can easily lead to security vulnerabilities or encryption failures, increasing the security risks of software development data. Summary of the Invention

[0004] The purpose of this invention is to provide a method and system for encrypting and protecting software development data, which solves the problems mentioned in the background art.

[0005] To achieve the above objectives, the present invention provides a method for encrypting and protecting software development data, comprising the following steps:

[0006] Login protection is implemented by building a software management platform. Users can upload software development data by logging into the software management platform, and access permissions can be set for users through the permission setting unit. Users can log in to the software management platform with the set account and password.

[0007] Data acquisition involves obtaining software development data from the software management platform and performing format standardization, data filling, data segmentation, and data encoding on the software development data to ensure that the software development data meets encryption protection requirements.

[0008] Data encryption protection involves classifying software development data into ordinary development data and sensitive development data. A symmetric encryption algorithm and a key management unit are used to encrypt ordinary development data using key one and sensitive development data using key two.

[0009] Encryption assessment: The encryption security scoring algorithm is used to assess the security of key one and key two, and the symmetric encryption algorithm is judged as qualified based on the security assessment results. If it is not qualified, key one and key two are replaced through the key management unit.

[0010] Encryption timeliness assessment: After the security assessment of Key 1 and Key 2 is qualified, they are put into use. Then, the timeliness assessment algorithm evaluates the timeliness of Key 1 and Key 2 based on time factors and security event factors, and determines whether the timeliness of Key 1 and Key 2 is qualified based on the results. If they are not qualified, Key 1 and Key 2 are replaced through the key management unit. The security event factors in the timeliness assessment algorithm will affect the data in the encryption security scoring algorithm.

[0011] Before replacing unqualified Key 1 and Key 2, the key management unit sorts all unqualified Key 1 and Key 2 using a replacement priority algorithm and replaces them in order to ensure that important software development data is protected first.

[0012] Data storage involves storing encrypted general development data and sensitive development data. When users access the stored general development data and sensitive development data, they must verify their identity and access permissions through the permission settings unit to ensure that only authorized users can access it. After successful verification, the system decrypts key one and key two before access to the general development data and sensitive development data is granted.

[0013] Optionally, the encryption security scoring algorithm process in the encryption evaluation step is as follows:

[0014]

[0015] Where S AES,i It is the security score of key i;

[0016] L AES,i It is the length of key i;

[0017] α is the key length influence coefficient, with a value ranging from 0 to 1;

[0018] C AES,i It is the complexity score of key i;

[0019] C AES,max It is the maximum complexity score;

[0020] β is the key length influence coefficient, with a value ranging from 0 to 1;

[0021] N i It is the number of encryption rounds for key i;

[0022] log is a logarithmic function;

[0023] The complexity score C of key i AES,i The evaluation process is as follows:

[0024]

[0025] Where T att,i This is the time required to crack key i;

[0026] T enc,i It is the time required for each round of encryption operations for key i;

[0027] T enc,max This is the maximum time required for an encryption operation;

[0028] The value of i ranges from 1 to 2. When i is 1, S AES,1 This is the security score for key one. When i is 2, S AES,2 This is the security score for key two. By evaluating the security of key one and key two and quantifying the results, we can intuitively understand the encryption quality of the symmetric encryption algorithm and set a security score S for key one. AES,1 The security threshold is Y1, and the security score of key two is S. AES,2 The second security threshold is Y2, when the security score of key one is S. AES,1 When the security threshold Y1 is less than 1, it indicates that key one's security is unqualified. When the security score of key two is S... AES,2 When the security threshold is less than 2, it means that the security of key 2 is not up to standard. When the security of both key 1 and key 2 is not up to standard, they should be replaced through the key management unit.

[0029] Optionally, the timeliness assessment algorithm process is as follows:

[0030]

[0031] Where F i It is the timeliness score of key i;

[0032] H exp,i This is the usage time of key i, in days;

[0033] H max,i This is the maximum usage time of key i;

[0034] θ is the key usage time impact coefficient, with a value ranging from 0 to 1;

[0035] Indicates the score for security incidents;

[0036] Qi This represents the number of security events involving key i, indicating the number of attack events that key i suffered during its use.

[0037] Q max It is the maximum number of security incidents;

[0038] γ is the impact coefficient of a security incident, with a value ranging from 0 to 1;

[0039] When i is 1, F1 is the timeliness score of key one; when i is 2, F2 is the timeliness score of key two. Timeliness thresholds Z1 and Z2 are set for F1 and F2 respectively. When the timeliness score F1 of key one is less than the timeliness threshold Z1, it means that the timeliness of key one is unqualified. When the timeliness score F2 of key two is less than the timeliness threshold Z2, it means that the timeliness of key two is unqualified. When the timeliness of key one and key two is unqualified, they are replaced through the key management unit.

[0040] Optionally, the security event score in the timeliness assessment algorithm A higher value indicates a more severe attack, meaning the compromised software development data is more important to external attackers, thus contributing to the security incident score. Set the danger threshold to Y3, and score the safety event. When the value is greater than Y3, it indicates that the strength of the external attack exceeds the preset value, and the strength of the software development data needs to be strengthened. At this time, the security thresholds Y1 and Y2 in the encryption security scoring algorithm will be updated. The update process is as follows:

[0041]

[0042] Where NY1 is the new safety threshold one;

[0043] NY2 is the new safety threshold two;

[0044] When external attacks are too frequent, increasing the security thresholds Y1 and Y2 in the encryption security scoring algorithm can improve the security score of the key, thereby increasing the overall strength of the key and reducing the risk of data leakage.

[0045] Optionally, the priority replacement algorithm process is as follows:

[0046]

[0047] Where C i It is the priority score of key i;

[0048] Indicates the access frequency of key i;

[0049] Di It represents the number of times key i has been accessed;

[0050] W i It is the influence coefficient of key i, and its value ranges from 0 to 1;

[0051] G i It represents the amount of data associated with key i, indicating the size of the data protected by key i;

[0052] G max It is the maximum amount of related data;

[0053] Priority score C of key i i This indicates the urgency of replacing the invalid key one and key two, with key i's priority score C. i The larger the value, the higher the priority of the current key replacement. The key management unit scores C according to the priority of key i. i The unqualified keys 1 and 2 are replaced sequentially from high to low to reduce the risk of leakage of important software development data.

[0054] Optionally, in the data acquisition step, a data scanning tool is used to classify the software development data, and the classified data is then manually reviewed.

[0055] To achieve the above objectives, this method also provides a software development data encryption and protection system, including a software management module, a system login module, a data acquisition module, a data classification module, a data encryption module, a key management module, and a data storage module;

[0056] The software management module includes a software management platform for transmitting and storing software development data. The system login module is used to set access permissions for users and provide a login interface. The data acquisition module is used to collect software development data, and includes a preprocessing unit for processing the software development data to improve its quality. The data classification module is used to classify the software development data into ordinary development data and sensitive development data. The data encryption module is used to encrypt both ordinary and sensitive development data.

[0057] Optionally, the system login module includes an identity authentication unit and a permission setting unit. The identity authentication unit is used to provide facial recognition and SMS authentication when a user logs in, to prevent the user's account password from being stolen.

[0058] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0059] I. This invention classifies software development data into ordinary development data and sensitive development data. Using a symmetric encryption algorithm and a key management unit, ordinary development data is encrypted using key one, and sensitive development data is encrypted using key two. Since ordinary and sensitive development data have different importance, the encryption strength of ordinary and sensitive development data is different. By using differentiated encryption methods, the computer resource consumption during encryption and decryption can be significantly reduced, system performance can be optimized, and the encryption efficiency of software development data can be improved.

[0060] Second, this invention employs an encryption security scoring algorithm that incorporates factors such as key length, complexity, and number of encryption rounds. A timeliness evaluation algorithm then assesses the timeliness of keys one and two. This timeliness evaluation algorithm considers not only the key's usage time but also security event factors, quantifying the security strength of each key and comprehensively evaluating its security. This allows administrators to understand key strength, making key management more orderly and efficient. The timeliness evaluation algorithm, combined with the encryption security scoring algorithm, can dynamically adjust the key rotation strategy and set different key management strategies for data with varying sensitivities. This avoids considering only the key's time factor, making key evaluation more comprehensive, improving the accuracy of the key rotation strategy, and reducing the security risks to software development data. Attached Figure Description

[0061] Figure 1 is a flowchart of the software development data encryption and protection method of the present invention;

[0062] Figure 2 is a block diagram of the software development data encryption and protection system of the present invention. Detailed Implementation

[0063] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0064] Example 1:

[0065] Please refer to Figures 1 and 2. This embodiment provides a method for encrypting and protecting software development data as follows:

[0066] A software management platform is built, where users can upload software development data by logging in, set access permissions for users through the permission setting unit, and log in to the software management platform with the set account and password.

[0067] Obtain software development data from the software management platform, and perform format standardization, data filling, data segmentation, and data encoding on the software development data to ensure that the software development data meets the requirements for encryption protection;

[0068] Software development data is classified into ordinary development data and sensitive development data. A symmetric encryption algorithm and a key management unit are used to encrypt ordinary development data with key one and sensitive development data with key two.

[0069] Specifically, data scanning tools are used to classify software development data. These tools include DLP tools and GitGuardian tools. After classification, the data is then manually reviewed to avoid misclassification.

[0070] Specifically, ordinary development data, such as temporary files and development logs, needs a certain level of protection, but due to their low importance and sensitivity, they can be encrypted with a lower strength. Sensitive development data, such as user information, source code, and commercial keys, requires a higher strength of encryption.

[0071] The encryption security scoring algorithm is used to evaluate the security of key one and key two, and the encryption of the symmetric encryption algorithm is judged as qualified based on the security evaluation results. If it is not qualified, key one and key two are replaced through the key management unit.

[0072] Encryption timeliness assessment: After the security assessment of key one and key two is qualified, they are put into use. Then, the timeliness of key one and key two is evaluated by the timeliness assessment algorithm, and it is determined whether the timeliness of key one and key two is qualified based on the result. If they are not qualified, key one and key two are replaced through the key management unit.

[0073] Before replacing the unqualified Key 1 and Key 2, the key management unit sorts all the unqualified Key 1 and Key 2 using a replacement priority algorithm and replaces them in order to ensure that important software development data is protected first.

[0074] Encrypted general development data and sensitive development data are stored. When users access the stored general development data and sensitive development data, they need to verify their identity and access permissions through the permission setting unit to ensure that only authorized users can access it. After the verification is successful, the system decrypts key one and key two before they can access the general development data and sensitive development data.

[0075] More specifically, in this embodiment, a software management platform is first constructed. Software developers upload software development data to the platform, enabling data sharing and collaborative development, thereby improving software development efficiency. An access control unit sets access permissions for users, ensuring that each person only accesses data relevant to their responsibilities, preventing software development data leakage. Next, software development data is retrieved from the platform and processed through format standardization, data filling, data segmentation, and data encoding to ensure successful encryption and improve encryption quality. The data is then categorized into ordinary and sensitive development data. A symmetric encryption algorithm and a key management unit are used to encrypt ordinary development data using key one and sensitive development data using key two. Since ordinary and sensitive development data have different importance, their encryption strengths differ. This differentiated encryption method significantly reduces computational resource consumption during encryption and decryption, optimizes system performance, and improves the efficiency of software development data encryption.

[0076] In the process of using the encryption security scoring algorithm to evaluate the security of Key 1 and Key 2, the evaluation criteria are different. The encryption security scoring algorithm quantifies the strength of each key by incorporating factors such as key length, complexity, and number of encryption rounds. This allows administrators to understand the key strength and determine whether to replace the key based on the results, making key management more orderly and efficient. Then, the timeliness evaluation algorithm is used to evaluate the timeliness of Key 1 and Key 2. The timeliness evaluation algorithm not only considers the key's usage time but also incorporates security event factors. In conjunction with the encryption security scoring algorithm, it can dynamically adjust the key rotation strategy, avoiding judgment based solely on the key's expiration time, reducing potential security risks, and improving the encryption protection effect of software development data. Finally, a replacement priority algorithm is used to sort all unqualified Key 1 and Key 2 and replace the keys in order. This makes reasonable use of computer resources, ensures that the security of critical software development data is given priority protection, and improves the overall efficiency and security of encryption protection.

[0077] Furthermore, in the encryption assessment step, the encryption security scoring algorithm process is as follows:

[0078]

[0079] Where S AES,i It is the security score of key i;

[0080] L AES,i It is the length of key i;

[0081] α is the key length influence coefficient, with a value ranging from 0 to 1;

[0082] C AES,i It is the complexity score of key i;

[0083] C AES,max It is the maximum complexity score;

[0084] β is the key length influence coefficient, with a value ranging from 0 to 1;

[0085] N i It is the number of encryption rounds for key i;

[0086] log is a logarithmic function;

[0087] By introducing the logarithmic function, an important characteristic of which is its ability to reflect small changes more precisely, the logarithmic function can more sensitively reflect the actual impact of changes on the key security score when the number of encryption rounds of the key changes, ensuring a more accurate key security assessment.

[0088] The complexity score C of key i AES,i The evaluation process is as follows:

[0089]

[0090] Where T att,i This is the time required to crack key i;

[0091] T enc,i It is the time required for each round of encryption operations for key i;

[0092] T enc,max This is the maximum time required for an encryption operation;

[0093] Key length is usually measured in bits. To standardize the key length into a more easily understood number, since 1 byte equals 8 bits, it is easier to convert the key length into bytes, making it easier for administrators to understand. For example, the key length of AES-128 is 128 bits, which is 16 bytes when divided by 8. The key length of AES-256 is 256 bits, which is 32 bytes when divided by 8. The denominator of 8 is used to convert the key length from bits to bytes, making the evaluation of keys more consistent and comparable.

[0094] Specifically, the value of i ranges from 1 to 2. When i is 1, S AES,1 This is the security score for key one. When i is 2, S AES,2 This is the security score for key two, and sets the security score S for key one. AES,1 The security threshold is Y1, and the security score of key two is S. AES,2The second security threshold is Y2. Since key one encrypts ordinary development data and key two encrypts sensitive development data, the strength of key two must be greater than that of key one. Therefore, the second security threshold Y2 is set to be greater than the first security threshold Y1. When the security score of key one is S... AES,1 When the security threshold Y1 is less than 1, it indicates that key one's security is unqualified. When the security score of key two is S... AES,2 When the security threshold is less than Y2, it means that the security of key 2 is unqualified. When the security of key 1 and key 2 is unqualified, they are replaced through the key management unit. By performing security assessments on key 1 and key 2, quantifying the results, and setting different thresholds for them, the encryption quality of the symmetric encryption algorithm can be intuitively understood.

[0095] Furthermore, the timeliness assessment algorithm process is as follows:

[0096]

[0097] Where F i It is the timeliness score of key i;

[0098] H exp,i This is the usage time of key i, in days;

[0099] H max,i This is the maximum usage time of key i;

[0100] θ is the key usage time impact coefficient, with a value ranging from 0 to 1;

[0101] Indicates the score for security incidents;

[0102] Q i This represents the number of security events involving key i, indicating the number of attack events that key i suffered during its use.

[0103] Q max It is the maximum number of security incidents;

[0104] γ is the impact coefficient of a security incident, with a value ranging from 0 to 1;

[0105] Specifically, the risk of key leakage increases with the duration of key use. A timeliness assessment algorithm quantifies the timeliness of keys, providing a clear understanding of the risk associated with key usage. When i is 1, F1 is the timeliness score of key one; when i is 2, F2 is the timeliness score of key two. Timeliness thresholds Z1 and Z2 are set for F1 and F2 respectively. If the timeliness score F1 of key one is less than the timeliness threshold Z1, key one is considered unqualified. If the timeliness score F2 of key two is less than the timeliness threshold Z2, key two is considered unqualified. Both key one and key two are replaced through the key management unit when their timeliness is deemed unqualified.

[0106] Furthermore, the security incident score in the timeliness assessment algorithm A higher value indicates a more severe attack, meaning the compromised software development data is more important to external attackers, thus contributing to the security incident score. Set the danger threshold to Y3, and score the safety event. When the value is greater than Y3, it indicates that the strength of the external attack exceeds the preset value, and the strength of the software development data needs to be strengthened. At this time, the security thresholds Y1 and Y2 in the encryption security scoring algorithm will be updated. The update process is as follows:

[0107]

[0108] Where NY1 is the new safety threshold one;

[0109] NY2 is the new safety threshold two;

[0110] Specifically, when external attacks are too frequent, increasing the security thresholds Y1 and Y2 in the encryption security scoring algorithm can improve the security score of the key, thereby increasing the overall strength of the key and reducing the risk of data leakage. Even if the key is used for ordinary development data, the data security risk increases due to the excessive number of attacks on the data, making data leakage more likely. In this case, increasing the security thresholds Y1 and Y2 allows for dynamic adjustment of the key strength according to the actual situation, improving the flexibility of protecting software development data.

[0111] Furthermore, the process of changing the priority algorithm is as follows:

[0112]

[0113] Where C i It is the priority score of key i;

[0114] This indicates the access frequency of key i. Data that is accessed frequently needs to be protected first because it is at higher risk of being exposed.

[0115] D i It represents the number of times key i has been accessed;

[0116] W i It is the influence coefficient of key i, and its value ranges from 0 to 1;

[0117] G i It represents the amount of data associated with key i, indicating the size of the data protected by key i;

[0118] G max It is the maximum amount of related data;

[0119] Specifically, the priority score C of key i i This indicates the urgency of replacing the invalid key one and key two, with key i's priority score C. i The larger the value, the higher the priority of the current key replacement. The key management unit scores C according to the priority of key i. i The method replaces unqualified keys one and two in descending order of quality, making reasonable use of computer resources, reducing the risk of leakage of important software development data, ensuring that the security of critical software development data is given priority, and improving the efficiency and security of software development data encryption protection. In practical applications, there are usually multiple sets of software development data, but this method provides consistent encryption protection measures for each set of software development data.

[0120] Example 2:

[0121] Based on the above embodiments, please refer to Figure 2. The present invention provides a software development data encryption protection system, including a software management module, a system login module, a data acquisition module, a data classification module, a data encryption module, a key management module, and a data storage module.

[0122] The system login module includes an identity authentication unit and a permission setting unit. The identity authentication unit is used to provide facial recognition and SMS authentication when users log in to prevent user account passwords from being stolen. The permission setting unit is used to set different access permissions for users to ensure that each person only accesses data related to their responsibilities and to prevent software development data leakage.

[0123] The software management module includes a software management platform for transmitting and storing software development data; a system login module for setting user access permissions and providing a login interface; a data acquisition module for collecting software development data, including a preprocessing unit for processing the data to improve its quality; a data classification module for classifying software development data into ordinary and sensitive data; and a data encryption module for encrypting both ordinary and sensitive data.

[0124] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A method for encrypting and protecting software development data, characterized in that, It includes the following steps: Step S1: Login protection. Build a software management platform. Users upload software development data by logging in to the software management platform. The access rights are set for users through the access rights setting unit. Users log in to the software management platform with the set account password. Step S2: Data collection. Obtain software development data from the software management platform. Step S3: Data encryption protection. Classify the software development data into ordinary development data and sensitive development data. Through the symmetric encryption algorithm and the key management unit, use Key One to encrypt the ordinary development data and Key Two to encrypt the sensitive development data respectively. Step S4: Encryption evaluation. Use the encryption security scoring algorithm to conduct a security evaluation on Key One and Key Two, and judge whether the encryption of the symmetric encryption algorithm is qualified according to the security evaluation result. When it is unqualified, replace Key One and Key Two through the key management unit. In the encryption evaluation step, the process of the encryption security scoring algorithm is as follows: ;where S AES,i It is the security score of key i; L AES,i α is the length of key i; α is the key length influence coefficient, ranging from 0 to 1; C AES,i It is the complexity score of key i; C AES,max This is the maximum complexity score; β is the key length influence coefficient, ranging from 0 to 1; N i The key is the number of encryption rounds for key i; log is the logarithmic function; the complexity score for key i is C. AES,i The evaluation process is as follows: ;where T att,i This is the time required to crack key i; T enc,i It is the time required for each round of encryption operations for key i; T enc,max This represents the maximum time required for the encryption operation; the value of i ranges from 1 to 2. When i is 1, S... AES,1 This is the security score for key one. When i is 2, S AES,2 This is the security score for key two, and sets the security score S for key one. AES,1 The security threshold is Y1, and the security score of key two is S. AES,2 The second security threshold is Y2, when the security score of key one is S. AES,1 When the security threshold Y1 is less than 1, it indicates that key one's security is unqualified. When the security score of key two is S... AES,2 When the security threshold is less than Y2, it indicates that the security of key 2 is unqualified. When the security of both key 1 and key 2 is unqualified, they are replaced through the key management unit. Step S5: Encryption timeliness assessment. After key 1 and key 2 pass the security assessment, they are put into use. Then, the timeliness of key 1 and key 2 is evaluated by the timeliness assessment algorithm based on time factors and security event factors to obtain the timeliness score F of key i. i The system determines whether the timeliness of Key 1 and Key 2 is acceptable based on the results. If they are unacceptable, Key 1 and Key 2 are replaced by the key management unit. Security event factors in the timeliness assessment algorithm affect the data in the encryption security scoring algorithm. Step S6: Key replacement sorting. Before replacing unacceptable Key 1 and Key 2, the key management unit sorts all unacceptable Key 1 and Key 2 using a replacement priority algorithm and replaces them sequentially to ensure that important software development data is protected first. The replacement priority algorithm process is as follows: C i It is the priority score of key i; D represents the access frequency of key i; i W is the number of times key i has been accessed; i It is the influence coefficient of key i, with a value ranging from 0 to 1; G i It is the amount of data associated with key i, representing the size of the data protected by key i; G max It represents the maximum amount of associated data; the priority score C of key i. i The priority score C of key i indicates the urgency of replacing invalid key one and key two. i The larger the value, the higher the priority of the current key replacement. The key management unit scores C according to the priority of key i. i Replace the unqualified key 1 and key 2 in descending order of quality to reduce the risk of leakage of important software development data; Step S7: Data storage, store the encrypted ordinary development data and sensitive development data.

2. The software development data encryption and protection method according to claim 1, characterized in that: The process of the timeliness evaluation algorithm is as follows: ;where F i It is the timeliness score of key i; H exp,i H represents the usage time of key i, in days; max,i This is the maximum usage time of key i; θ is the key usage time impact coefficient, and its value range is from 0 to 1; Indicates the score for security incidents; Q i Q represents the number of security events involving key i, indicating the number of attack events that key i suffered during its use; max It is the maximum number of security incidents; γ is the security event impact coefficient, and its value range is from 0 to 1; When i is 1, F1 is the timeliness score of Key One. When i is 2, F2 is the timeliness score of Key Two. Set the timeliness threshold one Z1 and the timeliness threshold two Z2 for F1 and F2 respectively. When the timeliness score F1 of Key One < the timeliness threshold one Z1, it means that the timeliness of Key One is unqualified. When the timeliness score F2 of Key Two < the timeliness threshold two Z2, it means that the timeliness of Key Two is unqualified. When the timeliness of Key One and Key Two is unqualified, both are replaced through the key management unit.

3. The software development data encryption and protection method according to claim 2, characterized in that: The security event score in the timeliness evaluation algorithm A higher value indicates a more severe attack, meaning the compromised software development data is more important to external attackers, thus contributing to the security incident score. Set the danger threshold to Y3, and score the safety event. When the value is greater than Y3, it indicates that the strength of the external attack exceeds the preset value, and the strength of the software development data needs to be strengthened. At this time, the security thresholds Y1 and Y2 in the encryption security scoring algorithm will be updated. The update process is as follows: ; ; where NY1 is the new security threshold one; NY2 is the new security threshold two; when external attacks are frequent, by increasing the security threshold one Y1 and security threshold two Y2 in the encryption security scoring algorithm, the security score of the key is improved, the overall strength of the key is increased, and the risk of data leakage is reduced.

4. The software development data encryption and protection method according to claim 1, characterized in that: The following steps are also included in the data collection: After obtaining the software development data on the software management platform, perform format standardization, data filling, data segmentation and data encoding processing on the software development data to ensure that the software development data meets the encryption protection requirements.

5. The software development data encryption and protection method according to claim 4, characterized in that: In the data collection step, use a data scanning tool to classify the software development data, and then conduct manual review after classification.

6. An encryption protection system used in the software development data encryption protection method according to claim 1, characterized in that: It includes a software management module, a system login module, a data collection module, a data classification module, a data encryption module, a key management module and a data storage module; the software management module includes a software management platform, which is used to transmit and store software development data. The system login module is used to set access rights for users and provide a login interface. The data collection module is used to collect software development data. The data collection module includes a preprocessing unit, which is used to process the software development data to improve the quality of the software development data. The data classification module is used to classify the software development data into ordinary development data and sensitive development data. The data encryption module is used to encrypt the ordinary development data and sensitive development data.

7. The encryption protection system according to claim 6, characterized in that: The system login module includes an identity authentication unit and an access rights setting unit. The identity authentication unit is used to provide face authentication and SMS authentication when users log in to prevent the theft of user account passwords.

Images