Security test analysis method for radio and television supervision software system based on risk model

Abstract

The invention discloses a radio and television supervision software system security test analysis method based on a risk model, which comprises the following steps: step 1, analyzing each module of a radio and television supervision software system, and generating an important function set; 2, analyzing and classifying security vulnerabilities of the radio and television supervision software system, dividing threat levels, and meanwhile, providing a corresponding prevention method for the security vulnerabilities to form a risk model; 3, enabling the important function set to correspond to the risk model, and forming a risk tree; 4, generating a test case according to the minimum cut set of the risk tree; 5, assigning a risk quantization number to the risk tree according to the threat level in the risk model, and calculating the risk degree of each module; and step 6, delimiting test key points according to the risk degree of each model, and executing a test case to perform a security test. According to the method, possible security vulnerabilities of the radio and television supervision software system can be systematically analyzed through the risk model, and the security risk of the system in actual operation is effectively reduced.

Description

Technical Field

[0001] The present invention relates to the field of radio and television technology, and in particular to a radio and television regulatory software system security testing and analysis method based on a risk model. Background Art

[0002] With the development of information technology, software systems have been widely used in all walks of life. However, with the increase in software complexity, security issues have become increasingly prominent. Security vulnerabilities in radio and television regulatory software systems mainly refer to defects in system design, implementation or configuration, which attackers can exploit to obtain unauthorized access rights, steal sensitive information or interfere with the normal operation of the system. Common security vulnerabilities include SQL injection, unauthorized access, privilege escalation, sensitive data leakage, etc. These vulnerabilities not only lead to the loss of corporate property and data, but also may endanger user privacy and system stability.

[0003] With increasingly complex software systems, traditional security testing methods are struggling to cope with diverse attack scenarios. Risk modeling, as a method for systematically analyzing and identifying security risks, can help identify potential security issues in the early stages of the software development lifecycle.

[0004] The purpose of the present invention is to provide a radio and television regulatory software system security test analysis method based on a risk model. The present invention can systematically analyze the possible security vulnerabilities of the radio and television regulatory software system through the risk model, and effectively reduce the security risks of the system in actual operation.

[0005] The technical solution of the present invention: a radio and television regulatory software system security test analysis method based on a risk model, comprising the following steps:

[0006] Step 1: Analyze each module of the radio and television supervision software system and generate a set of important functions;

[0007] Step 2: Analyze and classify the security vulnerabilities of the radio and television supervision software system, and divide the threat levels. At the same time, propose corresponding prevention methods for the security vulnerabilities to form a risk model;

[0008] Step 3: Match the important function set with the risk model to form a risk tree;

[0009] Step 4: Generate test cases based on the minimum cut set of the risk tree;

[0010] Step 5: Assign risk quantification numbers to the risk tree according to the threat level in the risk model, and calculate the risk level of each module;

[0011] Step 6: Define the test focus according to the risk level of each model and execute the test cases for security testing.

[0012] In the above-mentioned risk model security test and analysis method for radio and television regulatory software system, in step 2, the risk model is constructed as follows:

[0013] Step 2.1, define the model's goal as the possible security vulnerabilities in the radio and television regulatory software system;

[0014] Step 2.2: Establish a risk classification framework to classify security vulnerabilities into several major categories and describe their risks to the radio and television regulatory software system;

[0015] Step 2.3: Evaluate the potential harm that the security vulnerability may cause to the radio and television regulatory software system and the difficulty of exploiting the vulnerability, and define the threat level for the risk of each security vulnerability;

[0016] Step 2.4: Provide corresponding protective measures or suggestions for each risk to deal with the risk.

[0017] The aforementioned risk model security testing and analysis method for the radio and television regulatory software system, the categories of security vulnerabilities include input verification vulnerabilities, identity authentication vulnerabilities, session management vulnerabilities, permission vulnerabilities, data management vulnerabilities, security configuration errors, file upload vulnerabilities, vulnerabilities that rely on third-party libraries and components, insecure code execution, insecure APIs, incorrect business logic and social engineering attacks.

[0018] The aforementioned risk model of the radio and television regulatory software system security testing and analysis method, the input validation vulnerabilities include SQL injection, cross-site scripting attacks, special character processing errors and character input restriction vulnerabilities, and the risk levels are high risk, medium risk, medium risk and medium risk respectively;

[0019] The authentication vulnerabilities include weak password management, insufficient authentication mechanisms, and improper authentication expiration, with risk levels of high, high, and medium, respectively;

[0020] The session management vulnerabilities include session fixation, insufficient session security, and improper session expiration policy, all of which have a medium risk level;

[0021] The permission vulnerabilities include unauthorized content access, horizontal permission escalation, vertical permission escalation, and incorrect permission settings, all of which have a high risk level;

[0022] The data management vulnerabilities include plain text storage, insecure encryption, data collection errors, data collection delays, improper data processing, data processing delays, unauthorized data access and data tampering, and the risk levels are high risk, medium risk, medium risk, medium risk, higher risk, medium risk, higher risk and higher risk.

[0023] The security configuration errors include non-essential functions or services, unchanged default credentials, unnecessary open ports, incorrect file permission configuration and improper log management, with risk levels of medium risk, high risk, medium risk, high risk and medium risk respectively;

[0024] The file upload vulnerabilities include malicious file upload, improper file size limit, improper file type verification, and insufficient file type whitelist content, all of which have a medium risk level;

[0025] The vulnerabilities of relying on third-party libraries and components include failure to update in time and code injection, with risk levels of medium risk and high risk respectively;

[0026] The unsafe code execution includes remote code execution and command injection, both of which have high risk levels;

[0027] The unsafe APIs include APIs without authentication and insufficient rate limits, with risk levels of high and medium risk respectively;

[0028] The erroneous business logic includes transaction manipulation and repeated order submission, with risk levels of high risk and medium risk respectively;

[0029] The social engineering attacks include phishing and phone scams, with risk levels of medium and low risk respectively.

[0030] The risk model of the radio and television supervision software system security test analysis method, the risk tree defines the failure of the radio and television supervision software system as the top event, the possible failure of all functional modules of the radio and television supervision software system as the intermediate event, the possible failure of the sub-functional module under the functional module is defined as the secondary event, and all possible direct factors that lead to safety failures are defined as bottom events. The bottom event is the possible safety risk of the system, and then the logical connection between the events is represented by a logic diagram.

[0031] The aforementioned risk model is used for the security testing and analysis method of the radio and television regulatory software system. The logic diagram of the risk tree displays the top events of the radio and television regulatory software system based on the bottom events. The basic construction unit of the risk tree diagram is the event. Each basic event is connected to the cause event of the previous level by an AND gate or an OR gate.

[0032] In the aforementioned risk model-based security testing and analysis method for radio and television regulatory software systems, the risk degree is calculated by first allocating weights according to the importance of the sub-function modules within the function module, and then calculating the risk degree based on the threat quantification number and the weight.

[0033] The above-mentioned risk model of the radio and television supervision software system security test analysis method, the risk calculation formula is as follows:

[0034] R Si =Ro Si +Ra Si ; (1)

[0035] Where: R Si is the risk level of the functional module; Ro Si Ra is the risk of the next-level event or gate connection of the functional module; Si The risk level of the connection between the module's next-level event and the gate;

[0036] in,

[0037]

[0038] In the formula: h is the functional module proportional coefficient; λ is the risk quantification coefficient; w is the weight value; m is 1, 2, 3, 4, etc.; r is the bottom event risk quantification number; j and k are the lower boundaries of the cumulative multiplication; si is the risk subscript, and its value is determined by the functional module number; ni is the risk subscript of the next lower event or gate connection of the functional module;

[0039] Combining equations (1) to (6), we get:

[0040]

[0041] Compared with the prior art, the present invention establishes a set of risk models for the radio and television regulatory software system, which can comprehensively analyze the potential security risks of each module. On this basis, the present invention adopts the risk tree analysis method to further decompose and refine the security vulnerabilities of each module, form a minimum cut set, and generate more targeted test cases through these minimum cut sets. At the same time, the present invention divides the security level and risk factor by the minimum cut set, and identifies more potential risk points by refining the existing security risk framework, and proposes a more fine-grained protection plan, so as to improve the overall security of the software system. By constructing a refined risk model and test case design, the present invention provides the industry with a set of highly operational security testing methods, thereby effectively reducing the security risks of the system in actual operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 It is a schematic diagram of the process of the present invention;

[0043] Figure 2 It is a schematic diagram of the risk tree structure of the present invention. DETAILED DESCRIPTION

[0044] The present invention is further described below in conjunction with the accompanying drawings and embodiments, but they are not intended to limit the present invention.

[0045] Example: A security testing and analysis method for a radio and television regulatory software system based on a risk model, such as Figure 1 As shown, the following steps are included:

[0046] Step 1: Analyze each module of the radio and television supervision software system and generate an important function set; In this step, the radio and television supervision software system is first analyzed, and the main functions and sub-function modules under the main functions are listed to form a software function profile, so that each function module of the software can be known at a glance;

[0047] Step 2: Analyze and classify the security vulnerabilities of the radio and television regulatory software system, and divide the threat levels. At the same time, propose corresponding prevention methods for security vulnerabilities to form a risk model; in this step, the risk model can be used in the system design phase, development process, security assessment and penetration testing, and as new risks and vulnerabilities are discovered, the risk model can be updated regularly. Through the risk model, we can fully understand and evaluate the possible security risks in the radio and television regulatory software system, and take appropriate protective measures. Software security vulnerabilities can appear in different forms in different systems, but the buried points of potential vulnerabilities are common, and similar functional modules of different software may have the same type of security vulnerabilities. Building a secure software system requires comprehensive consideration and testing of these common potential problems during the development process. Therefore, the above content can be used to establish a defect risk model through modeling to analyze the security vulnerabilities of the software. The risk model can be constructed according to the following steps:

[0048] 1. Define the goals of the model

[0049] Identify, classify, and assess possible security vulnerabilities in software systems so that developers and security experts can conduct targeted protection and testing.

[0050] 2. Establish a risk classification framework

[0051] Categorize security vulnerabilities into several major categories and describe their risk to the system. These categories can include: insufficient input validation, authentication and session management vulnerabilities, privilege escalation, sensitive data leakage, security misconfiguration, etc.

[0052] 3. Associated Threat Level

[0053] Define a threat level (low, medium, high, or moderate) for each risk, evaluating it based on the harm it can cause to the system and how easy it is to exploit the vulnerability.

[0054] 4. Risk and protection measures mapping

[0055] Provide corresponding protection measures or suggestions for each risk to help system designers and developers effectively deal with these risks.

[0056] The specific structure of the risk model of the radio and television supervision software system in this embodiment includes:

[0057] 1. Input validation vulnerability:

[0058] M1: SQL injection; Description: Bypassing validation and accessing the database through maliciously constructed SQL statements; Threat level: High; Protection measures: 1. Use precompiled statements and parameterized queries. 2. Strictly validate and sanitize user input. 3. Implement database access control and limit permissions.

[0059] M2: Cross-site scripting (XSS); Description: Inject malicious scripts to trick other users into executing them, causing data leakage or session hijacking. Threat level: Medium; Protection measures: 1. Encode all inputs and outputs. 2. Use content security policy (CSP). 3. Regularly review and update security policies to ensure that new vulnerabilities are fixed in a timely manner.

[0060] M3: Special character processing error (improper encoding / escaping); Description: Improper processing of special characters in input may lead to unexpected code execution or data tampering. Threat level: Medium; Protection measures: 1. Strictly encode and escape the input. 2. Use security libraries and frameworks to avoid manual processing of special characters. 3. Perform input validation tests regularly to detect the effectiveness of the processing mechanism.

[0061] M4: Character input restriction vulnerability; Description: Ability to enter characters that cannot be entered by the system restriction or exceed the input length of the system restriction; Threat level: Medium; Protection measures: 1. Strict input validation: Implement comprehensive input validation, enforce character type and length restrictions, and reject any input that exceeds the set boundaries. 2. Input sanitization and escape: Sanitize user input before processing and escape special characters to ensure that no harmful data is injected or data is processed incorrectly. 3. Current limiting and length limitation: Strictly limit the number of characters and use a current limiting mechanism to prevent excessive or malicious input submissions.

[0062] 2. Authentication Vulnerability:

[0063] M5: Weak password management; Description: The system allows weak passwords, or passwords are not stored securely. Threat level: High; Protection measures: 1. Enforce the use of complex password policies. 2. Use strong encryption algorithms to store passwords. 3. Perform regular password security checks and enforce password updates.

[0064] M6: Insufficient authentication mechanism (lack of multi-factor authentication); Description: The system relies on a single authentication method (such as username and password), which is easily cracked or attacked by brute force. It lacks a multi-factor authentication (MFA) mechanism and does not provide a higher level of security protection. Threat level: high; Protection measures: 1. Implement multi-factor authentication (MFA), such as combining passwords and one-time verification codes, fingerprints or other biometric means. 2. Enforce multi-factor authentication for highly sensitive operations (such as payment, account modification). 3. Update authentication methods regularly to ensure that technologies and methods are consistent with current security standards.

[0065] M7: Improper authentication expiration time; Description: If the authentication validity period is too long, it increases the risk of unauthorized use; if it is too short, it may affect the user experience and lead to frequent re-authentication. Threat level: Medium; Protection measures: 1. Set an appropriate authentication validity period and adjust it according to the user role and operation sensitivity. 2. Use a dynamic authentication mechanism to require re-authentication when suspicious activities are detected. 3. Enforce re-authentication after a user has been inactive for a long time to ensure the validity of the authentication. These supplementary measures provide a more complete protection mechanism for authentication and session management, thereby reducing potential security risks.

[0066] 3. Session Management Vulnerability:

[0067] M8: Session fixation; Description: An attacker can access a legitimate user session through a known session ID. Threat level: Medium; Protection measures: 1. Enable the HttpOnly flag to prevent scripts from accessing cookies. 2. Enable the Secure flag to ensure that cookies are only transmitted over HTTPS. 3. Use the SameSite attribute to limit cross-site request forgery (CSRF) attacks.

[0068] M9: Insufficient session security (HttpOnly and Secure flags not set); Description: The session cookie does not have the `HttpOnly` flag set, allowing client scripts to access and steal the session ID. The `Secure` flag is not set, which may cause the session to be intercepted when transmitted in an insecure HTTP channel. Threat Level: Medium; Protection measures: 1. Enable the `HttpOnly` flag to prevent client scripts (such as JavaScript) from accessing cookies. 2. Enable the `Secure` flag to ensure that cookies are only transmitted over HTTPS to prevent man-in-the-middle attacks. 3. Use the `SameSite` attribute to limit the risk of cross-site request forgery (CSRF) attacks.

[0069] M10: Improper session expiration policy; Description: The session expiration time is not set properly. If it is too long, it may increase the risk of session hijacking, and if it is too short, it may affect the user experience. The session does not expire automatically, which may result in the attacker exploiting the session that has not been actively logged out. Threat level: Medium; Protection measures: 1. Set a reasonable session timeout time, and dynamically adjust the expiration time considering user activities. 2. Implement a session idle timeout policy to automatically log out the session when the user has not operated for a period of time. 3. Clear the session data immediately after the user logs out to prevent the reuse of expired sessions.

[0070] 4. Permission vulnerability:

[0071] M11: Unauthorized access to content; Description: The system does not fully verify access requests, resulting in users being able to access unauthorized content. Threat Level: High; Protection Measures: 1. Implement a strict permission control mechanism to ensure that each user can only access the content they are authorized to access. 2. Regularly review permission configuration to ensure accuracy. 3. Use logs to audit permission changes and detect abnormal access behavior in a timely manner.

[0072] M12: Horizontal privilege escalation; Description: Users can access resources of other users at the same level. Threat level: High; Protection measures: 1. Strictly check and control user privileges. 2. Perform contextual verification on user access requests. 3. Regularly conduct privilege penetration testing to detect potential risks.

[0073] M13: Vertical privilege escalation; Description: The attacker escalates to administrator privileges through a vulnerability. Threat level: High; Protection measures: 1. Separate high-privilege operations. 2. Use multi-factor authentication to protect high-privilege accounts. 3. Regularly review and update privilege allocation policies.

[0074] M14: Incorrect permission settings; Description: Improper file or directory permission settings lead to unauthorized access. Threat level: High; Protection measures: 1. Strictly configure file and directory permissions and follow the principle of least privilege. 2. Regularly review permission settings and fix possible over-authorization issues. 3. Implement automated tools to monitor permission changes.

[0075] 5. Data management vulnerabilities:

[0076] M15: Plain text storage; Description: Sensitive information is stored without encryption and is easily stolen. Threat level: High; Protection measures: 1. Use strong encryption algorithms to store sensitive information. 2. Review encryption policies regularly. 3. Use a key management system to ensure key security.

[0077] M16: Insecure encryption; Description: Use outdated or weak encryption algorithms, data can be easily cracked. Threat level: Medium; Protection measures: 1. Use current best practice encryption standards. 2. Update encryption algorithms regularly. 3. Double encrypt critical data.

[0078] M17. Data collection error (incomplete collected data); Description: Errors occurred during data collection, resulting in incomplete collected data, which may affect the accuracy of subsequent data analysis. Errors include partial data loss, data format mismatch, or invalid collected data. Threat level: Medium; Protection measures: 1. Establish a strict data verification mechanism to ensure that the collected data is complete and conforms to the expected format. 2. Implement redundant collection and use multiple data sources to cross-verify data accuracy. 3. Regularly review the data collection process to identify and fix vulnerabilities that may cause incomplete data.

[0079] M18: Data collection delay (lack of real-time performance); Description: The data collection system has a delay in real-time data collection, which results in the inability to transmit and process data in a timely manner, thus affecting overall business decision-making or response time. Threat level: Medium; Protection measures: 1. Optimize the architecture of the data collection system to improve collection and transmission efficiency and reduce delays. 2. Use high-performance network and hardware equipment to ensure that data can be transmitted and processed in a timely manner. 3. Introduce caching and streaming processing technology to process and analyze collected data in real time.

[0080] M19: Improper data processing (data loss or incorrect processing); Description: Data may be lost or processed incorrectly during the processing phase due to algorithm errors, system failures, or configuration problems. This will directly affect the results of data analysis and even cause systemic errors. Threat level: High; Protection measures: 1. Use highly reliable data processing algorithms and conduct sufficient testing and verification. 2. Set up an automated fault recovery mechanism to ensure that data can be quickly restored when problems occur during processing. 3. Regularly back up key data and monitor and audit the processing process.

[0081] M20: Data processing delay (untimely analysis); Description: Data is delayed in processing and analysis, resulting in an inability to respond to business needs in a timely manner, especially in scenarios that require real-time data support. Threat level: Medium; Protection measures: 1. Introduce parallel processing technology or distributed computing architecture to speed up data processing. 2. Use streaming data processing methods to avoid delays caused by batch processing. 3. Regularly evaluate and optimize data processing pipelines to improve overall efficiency.

[0082] M21: Unauthorized access to data (information leakage):

[0083] Description: Unauthorized users or systems may access sensitive data, resulting in information leakage, including customer privacy, business secrets, etc. Threat level: High; Protection measures: 1. Implement strict access control policies and set minimum permissions based on user roles. 2. Use data encryption technology to ensure the security of data during storage and transmission. 3. Regularly audit access logs to promptly detect and prevent abnormal access behavior.

[0084] M22: Data tampering (lack of integrity protection):

[0085] Description: Data may be tampered with during storage or transmission, resulting in the destruction of data integrity and affecting the credibility of the data. Threat level: High; Protection measures: 1. Use digital signatures, hash verification and other technologies to ensure data integrity. 2. Encrypt the data transmission process to prevent man-in-the-middle attacks and data tampering. 3. Establish a real-time monitoring and alarm mechanism to detect and respond to data tampering in a timely manner.

[0086] 6. Security configuration errors:

[0087] M23: Non-essential features or services; Description: Unnecessary features are enabled, increasing the attack surface. Threat level: Medium; Protection measures: 1. Minimize installed and enabled features. 2. Regularly review configurations.

[0088] M24: Default credentials have not been changed; Description: The system uses factory default credentials, which can be easily exploited by attackers. Threat level: High; Protection measures: 1. Change default credentials immediately after deployment and use strong password management policies. 2. Regularly review all system accounts to ensure that no default or weak passwords are used. 3. Implement multi-factor authentication to further protect key accounts.

[0089] M25: Unnecessary open ports; Description: Unnecessary ports are enabled in the system, increasing exposure. Threat level: Medium; Protection measures: 1. Regularly review and close unnecessary ports to limit network access. 2. Use firewall rules to control port access to prevent unauthorized traffic. 3. Enable intrusion detection system (IDS) to monitor abnormal port activity.

[0090] M26: Incorrect file permission configuration; Description: Improper system file permissions may lead to unauthorized access or tampering. Threat level: High; Protection measures: 1. Follow the principle of least privilege and strictly configure file and directory permissions. 2. Regularly review file permissions and fix possible over-authorization issues. 3. Implement automated tools to monitor permission changes to prevent unauthorized adjustments.

[0091] M27: Improper log management; Description: Inadequate or unprotected log records may lead to the leakage of important information or the inability to track problems. Threat level: Medium; Protection measures: 1. Ensure the integrity of log records, and implement access control and encryption for logs. 2. Configure log rotation and archiving strategies to prevent logs from being tampered with or lost. 3. Regularly review log configuration to ensure that key events are fully recorded and can be audited in a timely manner.

[0092] 7. File upload vulnerability:

[0093] M28: Malicious file upload: Description: The attacker uploads a file with malicious code, which may bypass verification or exploit vulnerabilities, leading to server intrusion or system data damage. Threat level: High; Protection measures: 1. Implement strict file upload verification to check file type, size and content. 2. Perform virus scan and security detection on uploaded files to prevent malicious files from being uploaded. 3. Use a sandbox environment to isolate and test uploaded files to reduce direct risks.

[0094] M29: Improper file size limit: Description: Improper size limit during file upload may lead to system resource exhaustion or denial of service (DoS). Threat Level: Medium; Protection measures:; 1. Set reasonable file size limit to prevent oversized files from affecting system performance. 2. Implement segmented upload and verification to ensure that files within the allowed range can be safely transferred. 3. Monitor upload activities to identify upload behaviors with abnormal file sizes.

[0095] M30: Improper file type verification: Description: Failure to correctly verify the file type may result in illegal files or harmful format files being accepted, which may lead to potential risks. Threat Level: Medium; Protection measures: 1. Use strict MIME type verification to ensure that the uploaded file is consistent with the expected type. 2. Double-verify the legitimacy of the file type by checking the file header information and extension. 3. Reject any file type that is not in the whitelist to ensure that only authorized files are accepted.

[0096] M31: Insufficient whitelist content for file types:

[0097] Description: The file type whitelist is not comprehensive, which may result in some legitimate files being blocked or uncontrolled files being uploaded, increasing system risks. Threat level: Medium; Protection measures: 1. Regularly update and expand the file type whitelist to ensure that all safe and necessary file formats are covered. 2. Conduct security reviews on the whitelist to ensure that its content is not abused or bypassed. 3. Implement a dynamic whitelist strategy and adjust rules based on business needs and risk levels.

[0098] 8. Vulnerabilities in reliance on third-party libraries and components:

[0099] M32: Not updated in time; Description: Third-party components with known vulnerabilities are not updated in time. Threat level: Medium; Protection measures: 1. Regularly check and update third-party libraries. 2. Use automated tools to scan for known vulnerabilities.

[0100] M33: Code injection; Description: Inject malicious code into third-party libraries through vulnerabilities. Threat level: High; Protection measures: 1. Verify and restrict the use of third-party libraries. 2. Monitor the security of the code base.

[0101] 9. Unsafe Code Execution:

[0102] M34: Remote Code Execution (RCE); Description: An attacker can remotely execute malicious code. Threat Level: High; Protection Measures: 1. Limit code execution permissions. 2. Use secure programming practices.

[0103] M35: Command injection; Description: Directly execute system commands through unvalidated input. Threat level: High; Protection measures: 1. Strictly validate input. 2. Avoid directly calling system commands.

[0104] 10. Insecure APIs:

[0105] M36: API without authentication; Description: The API endpoint does not perform authentication checks. Threat Level: High; Protection measures: 1. Mandatory authentication and authorization are enabled for all API endpoints.

[0106] M37: Insufficient rate limiting; Description: The API does not set a request rate limit, which may lead to a DDoS attack. Threat level: Medium; Protection measures: 1. Implement rate limiting and traffic control at the API level.

[0107] 11. Incorrect business logic:

[0108] M38: Transaction manipulation; Description: The attacker can modify the transaction amount or bypass the payment steps. Threat level: High; Protection measures: 1. Strictly verify each step in the business process to ensure the integrity of transaction data.

[0109] M39: Repeated order submission; Description: Repeated order submission by manipulating requests. Threat level: Medium; Protection measures: 1. Request deduplication mechanism: Implement a request deduplication mechanism on the server side, such as generating a unique request identifier (such as UUID) for each order submission, and only processing one request identifier within a certain period of time, and duplicate requests will be ignored. 2. Idempotence check: Ensure that the order submission interface is idempotent. Prevent repeated submission of the same order request by checking the order status. For example, a request for an existing or processed order will not create a new order again.

[0110] 12. Social Engineering Attacks:

[0111] M40: Phishing; Description: Tricking users into entering sensitive information. Threat level: Medium; Protection measures: 1. Conduct user education. 2. Use anti-phishing tools and detection technology.

[0112] M41: Telephone fraud; Description: Obtaining sensitive information of users through phone calls. Threat level: Low; Protection measures: 1. Establish a strict identity verification process. 2. Train users to identify such attacks.

[0113] Step 3. Match the important function set with the risk model to form a risk tree. In this step, the risk tree defines the failure of the radio and television supervision software system as a top event, defines the possible failures of all functional modules of the radio and television supervision software system as intermediate events, defines the possible failures of sub-functional modules under the functional modules as secondary events, and defines all possible direct factors that lead to safety failures as bottom events. The bottom event is the possible safety risk of the system, and then a logic diagram is used to represent the logical connection between the events.

[0114] The logic diagram of the risk tree shows the top events of the radio and television supervision software system based on the bottom events. The basic construction unit of the risk tree diagram is the event. Each basic event is connected to the cause event of the upper level by an AND gate or an OR gate. The risk tree diagram construction process is as follows: Figure 2 shown. Figure 2 In the example, m1, m2, and m3 are all risk points. The three are connected by an OR gate. If any of the three occurs, the S1 functional module will fail, which will cause the top-level system to fail. N1 is a secondary event. N1 is connected to m4 and m5 by an AND gate. When both the m4 and m5 risk points occur, the N1 function will fail, which will cause the S2 module to fail.

[0115] Step 4: Generate test cases based on the minimum cut set of the risk tree. In this step, the bottom events of the risk tree form a minimum cut set, and each minimum cut set can form at least one test case.

[0116] Step 5: assign risk quantification numbers to the risk tree according to the threat level in the risk model, and calculate the risk level of each module; in this step, the threat level includes high threat level threat level (risk quantification number is 0.5), higher threat equal threat level (risk quantification number is 0.4), medium threat equal threat level (risk quantification number is 0.3) and lower threat equal threat level (risk quantification number is 0.1).

[0117] The risk degree is calculated by first assigning weights according to the importance of the sub-function modules within the function module (the sum of the weights is 1), and then calculating the risk degree according to the threat quantification number and the weight. The specific calculation is as follows:

[0118] RSi =Ro Si +Ra Si ;

[0119] (N events or gates connected)

[0120] (N events are connected to the gate)

[0121] (bottom event or gate connected);

[0122] (the bottom event is connected to the gate);

[0123]

[0124] Among them, R Si The risk level of the main module (intermediate event); Ro Si The risk of secondary events or gate connections to the main module; Ra Si is the risk of the next sub-event and gate connection of the module; h is the proportional coefficient of the functional module; λ is the proportional coefficient of the risk quantification number; w is the weight value; m is 1, 2, 3, 4...; r is the risk quantification number of the bottom event; j and k are the lower boundaries of the cumulative multiplication; si is the risk subscript, and its value is determined by the functional module number; ni is the risk subscript of the next sub-event or gate connection of the functional module;

[0125] Step 6: Determine the test focus according to the risk level of each model, and execute the test cases for security testing. This step can focus on in-depth testing of modules with high risk levels, and repair and rectify the vulnerabilities found according to the response plan given by the risk model.

[0126] In summary, each module of the radio and television supervision software system can be mapped to the corresponding risk model, so as to clarify the security requirements of each module and the risk types that need to be protected. According to the characteristics of the provincial backbone network transmission OTN system, the present invention designs and constructs an OSNR monitoring platform for optical power attenuation events of working channels and protection channels, realizes the impact degree determination of attenuation events, and provides emergency repair and maintenance solutions based on automated process processing, which improves the efficiency of network operation and maintenance and ensures the safe and high-quality transmission of radio and television, integrated media dedicated lines and other services.

Claims

1. Security testing and analysis method of radio and television regulatory software system based on risk model, Features: The steps include: Step 1: Analyze each module of the radio and television supervision software system and generate a set of important functions; Step 2: Analyze and classify the security vulnerabilities of the radio and television supervision software system, and divide the threat levels. At the same time, propose corresponding prevention methods for the security vulnerabilities to form a risk model; Step 3: Match the important function set with the risk model to form a risk tree; Step 4: Generate test cases based on the minimum cut set of the risk tree; Step 5: Assign risk quantification numbers to the risk tree according to the threat level in the risk model, and calculate the risk level of each module; Step 6: Define the test focus according to the risk level of each model and execute the test cases for security testing.

2. According to the risk model of claim 1, the radio and television supervision software system security testing and analysis method, Features: In step 2, the risk model is constructed as follows: Step 2.1, define the model's goal as the possible security vulnerabilities in the radio and television regulatory software system; Step 2.2: Establish a risk classification framework to classify security vulnerabilities into several major categories and describe their risks to the radio and television regulatory software system; Step 2.3: Evaluate the potential harm that the security vulnerability may cause to the radio and television regulatory software system and the difficulty of exploiting the vulnerability, and define the threat level for the risk of each security vulnerability; Step 2.4: Provide corresponding protective measures or suggestions for each risk to deal with the risk.

3. According to the risk model of claim 2, the radio and television supervision software system security testing and analysis method, Features: The categories of security vulnerabilities include input validation vulnerabilities, authentication vulnerabilities, session management vulnerabilities, permission vulnerabilities, data management vulnerabilities, security configuration errors, file upload vulnerabilities, vulnerabilities in reliance on third-party libraries and components, insecure code execution, insecure APIs, incorrect business logic, and social engineering attacks.

4. The radio and television regulatory software system security testing and analysis method based on the risk model of claim 3, Features: The input validation vulnerabilities include SQL injection, cross-site scripting, special character processing errors, and character input restriction vulnerabilities, with risk levels of high risk, medium risk, medium risk, and medium risk respectively; The authentication vulnerabilities include weak password management, insufficient authentication mechanisms, and improper authentication expiration, with risk levels of high, high, and medium, respectively; The session management vulnerabilities include session fixation, insufficient session security, and improper session expiration policy, all of which have a medium risk level; The permission vulnerabilities include unauthorized content access, horizontal permission escalation, vertical permission escalation, and incorrect permission settings, all of which have a high risk level; The data management vulnerabilities include plain text storage, insecure encryption, data collection errors, data collection delays, improper data processing, data processing delays, unauthorized data access and data tampering, and the risk levels are high risk, medium risk, medium risk, medium risk, higher risk, medium risk, higher risk and higher risk. The security configuration errors include non-essential functions or services, unchanged default credentials, unnecessary open ports, incorrect file permission configuration and improper log management, with risk levels of medium risk, high risk, medium risk, high risk and medium risk respectively; The file upload vulnerabilities include malicious file upload, improper file size limit, improper file type verification, and insufficient file type whitelist content, all of which have a medium risk level; The vulnerabilities of relying on third-party libraries and components include failure to update in time and code injection, with risk levels of medium risk and high risk respectively; The unsafe code execution includes remote code execution and command injection, both of which have a high risk level; The unsafe APIs include APIs without authentication and insufficient rate limits, with risk levels of high and medium risk respectively; The erroneous business logic includes transaction manipulation and repeated order submission, with risk levels of high risk and medium risk respectively; The social engineering attacks include phishing and phone scams, with risk levels of medium and low risk respectively.

5. According to the risk model of claim 1, the radio and television supervision software system security testing and analysis method, Features: The risk tree defines the failure of the radio and television supervision software system as the top event, defines the possible failures of all functional modules of the radio and television supervision software system as intermediate events, defines the possible failures of sub-functional modules under the functional modules as secondary events, and defines all possible direct factors that lead to safety failures as bottom events. The bottom event is the possible safety risk of the system, and then uses a logic diagram to represent the logical connection between the events.

6. The radio and television regulatory software system security testing and analysis method based on the risk model of claim 5, Features: The logic diagram of the risk tree displays the top events of the radio and television supervision software system based on the bottom events. The basic construction unit of the risk tree diagram is the event, and each basic event is connected to the cause event of the upper level by an AND gate or an OR gate.

7. According to the risk model-based security testing and analysis method for radio and television regulatory software system according to claim 5, Features: The risk degree is calculated by first allocating weights according to the importance of the sub-function modules within the function module, and then calculating the risk degree according to the threat quantification number and the weight.

8. The method for calculating the threat level of the radio and television supervision software system according to claim 7, Features: The risk calculation formula is as follows: R Si =Ro Si +Ra Si (1) Where: R Si is the risk level of the functional module; Ro Si Ra is the risk of the next-level event or gate connection of the functional module; Si The risk level of the connection between the module's next-level event and the gate; in, In the formula: h is the functional module proportional coefficient; λ is the risk quantification coefficient; w is the weight value; m is 1, 2, 3, 4, etc.; r is the bottom event risk quantification number; j and k are the lower boundaries of the cumulative multiplication; si is the risk subscript, and its value is determined by the functional module number; ni is the risk subscript of the next lower event or gate connection of the functional module; Combining equations (1) to (6), we get:

Images