Threat degree calculation method for radio and television supervision software system

Abstract

The invention discloses a threat degree calculation method for a radio and television supervision software system, which comprises the following steps of: 1, establishing a risk tree according to a functional module of the radio and television supervision software system, a sub-module of the functional module and security vulnerabilities existing in the sub-module, and connecting the functional module, the sub-module and the security vulnerabilities by adopting a logic diagram; and 2, each security vulnerability in the risk tree is endowed with a risk quantization number, then a weight is allocated according to the importance degree of the sub-module in the function module, a threat degree is calculated according to the threat quantization number and the weight, and the threat degree is used for measuring the degree of the security risk faced by each function module and each sub-module. According to the method, the threat degree calculation result with relatively high accuracy can be obtained, the security risk degree of the radio and television supervision software system can be measured, and the practicability is high.

Description

Technical Field

[0001] The present invention relates to the field of radio and television technology, and in particular to a method for calculating the threat level of a radio and television supervision software system. Background Art

[0002] Security vulnerabilities in radio and television regulatory software systems mainly refer to defects in system design, implementation or configuration. Attackers can exploit these vulnerabilities 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] At present, the threat level of security vulnerabilities is usually determined by set rules. However, the real network environment is more complex and there are many types of security vulnerability events. When the threat level determination rules set in the inherent model are used to determine the threat level of security vulnerability events, the threat level determination results are relatively simple and have low accuracy. Summary of the invention

[0004] The purpose of the present invention is to provide a method for calculating the threat level of a radio and television regulatory software system. The present invention can obtain a threat level calculation result with high accuracy, can measure the security risk level of the radio and television regulatory software system, and has strong practicality.

[0005] The technical solution of the present invention is a method for calculating the threat level of a radio and television supervision software system, comprising the following steps:

[0006] Step 1: Establish a risk tree based on the function modules of the radio and television supervision software system, the submodules of the function modules, and the security vulnerabilities of the submodules, and connect the function modules, submodules, and security vulnerabilities using a logic diagram;

[0007] Step 2: Assign a risk quantification number to each security vulnerability in the risk tree, then assign weights according to the importance of the sub-module within the functional module, and then calculate the threat degree based on the threat quantification number and weight. The threat degree is used to measure the degree of security risk faced by each functional module and sub-module.

[0008] The above-mentioned threat degree calculation method of the radio and television supervision software system, 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-module under the functional module is defined as the secondary event, and all possible direct factors that lead to security failures are defined as bottom events. The bottom event is the possible security vulnerability of the system, and then a logic diagram is used to represent the logical connection between the events.

[0009] The aforementioned threat degree calculation method of the radio and television supervision software system, 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 previous level by an AND gate or an OR gate.

[0010] The threat degree calculation method of the aforementioned radio and television regulatory software system, the risk levels of the security vulnerabilities include high risk, relatively high risk, medium risk and low risk, among which the risk quantification number of high risk is 0.5, the risk quantification number of relatively high risk is 0.4, the risk quantification number of medium risk is 0.3, and the risk quantification number of low risk is 0.1.

[0011] The threat degree calculation method of the aforementioned radio and television supervision software system, the threat degree calculation formula is as follows:

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

[0013] Where: R Si is the threat level of the functional module; Ro Si Ra is the threat level of the next-level event or gate connection of the functional module; Si The threat level of the module's next-level event connected to the door;

[0014] in,

[0015]

[0016] 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;

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

[0018]

[0019] Compared with the prior art, the present invention proposes a new threat degree calculation method for the radio and television supervision software system. The present invention first establishes a risk tree according to the functional modules, submodules of the functional modules and security vulnerabilities existing in the submodules of the radio and television supervision software system, and connects the functional modules, submodules and security vulnerabilities with a logic diagram; then, each security vulnerability in the risk tree is assigned a risk quantification number, and then a weight is assigned according to the importance of the submodule in the functional module, and then the threat degree is calculated according to the threat quantification number and the weight. Thus, the danger degree calculated by the present invention can accurately measure the degree of security risk faced by each functional module and submodule of the radio and television supervision software system. The greater the threat degree, the greater the risk of the module, and the more emphasis needs to be placed on testing, risk repair and prevention. The present invention intuitively knows the modules that need to be focused on in the radio and television supervision software system through the calculation of the threat degree, thereby effectively reducing the security risks of the system in actual operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 It is a schematic diagram of the risk tree structure schematic diagram monitoring platform of the present invention;

[0021] Figure 2 It is a risk tree diagram of the radio and television supervision software system of the present invention. DETAILED DESCRIPTION

[0022] 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.

[0023] Embodiment: A method for calculating the threat level of a radio and television supervision software system comprises the following steps:

[0024] Step 1. Establish a risk tree based on the functional modules of the radio and television supervision software system, the sub-modules of the functional modules, and the security vulnerabilities of the sub-modules, and use a logic diagram to connect the functional modules, sub-modules and security vulnerabilities; 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-modules under the functional modules as secondary events, and defines all possible direct factors that lead to security failures as bottom events. The bottom event is the security vulnerability that may exist in the system, and then a logic diagram is used to represent the logical connection between the events. The logic diagram of the risk tree displays the top event 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, thereby constructing the following Figure 1 Risk tree shown. Figure 1In 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.

[0025] Step 2: Assign a risk quantification number to each security vulnerability in the risk tree, then assign weights according to the importance of the sub-module within the functional module, and then calculate the threat degree based on the threat quantification number and weight. The threat degree is used to measure the degree of security risk faced by each functional module and sub-module.

[0026] In this step, the security vulnerabilities of the radio and television supervision software system include:

[0027] 1. Input validation vulnerability:

[0028] 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.

[0029] 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.

[0030] 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.

[0031] 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.

[0032] 2. Authentication Vulnerability:

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 3. Session Management Vulnerability:

[0037] 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.

[0038] 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.

[0039] 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.

[0040] 4. Permission vulnerability:

[0041] 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.

[0042] 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.

[0043] 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.

[0044] 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.

[0045] 5. Data management vulnerabilities:

[0046] 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.

[0047] 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.

[0048] 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.

[0049] 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.

[0050] 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.

[0051] 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.

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

[0053] 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.

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

[0055] 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.

[0056] 6. Security configuration errors:

[0057] 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.

[0058] 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.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] 7. File upload vulnerability:

[0063] 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.

[0064] 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.

[0065] 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.

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

[0067] 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.

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

[0069] 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.

[0070] 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.

[0071] 9. Unsafe Code Execution:

[0072] 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.

[0073] 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.

[0074] 10. Insecure APIs:

[0075] 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.

[0076] 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.

[0077] 11. Incorrect business logic:

[0078] 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.

[0079] 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.

[0080] 12. Social Engineering Attacks:

[0081] 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.

[0082] 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.

[0083] For the above security vulnerabilities, the risk quantification number for high risk is assigned to 0.5, the risk quantification number for relatively high risk is assigned to 0.4, the risk quantification number for medium risk is assigned to 0.3, and the risk quantification number for low risk is assigned to 0.1.

[0084] In this step, the calculation formula of the threat degree is as follows:

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

[0086] Where: R Si is the threat level of the functional module; Ro Si Ra is the threat level of the next-level event or gate connection of the functional module; Si The threat level of the module's next-level event connected to the door;

[0087] in,

[0088]

[0089] 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 both the lower boundaries of accumulation and 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;

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

[0091]

[0092] Based on the above threat degree calculation method, this embodiment is demonstrated with actual radio and television media resource management software. Radio and television media resource management software usually contains multiple modules, each module for specific functions and business needs. This embodiment analyzes and sorts out the core functional modules and their sub-functions in the radio and television media resource management software, analyzes them with a risk tree, and generates test cases based on the minimum cut set of the risk tree (that is, the bottom events of the risk tree form a minimum cut set, and each minimum cut set can form at least one test case), such as Figure 2 As shown, the following results are obtained:

[0093] 1. Content Management System (CMS), weight: 0.4;

[0094] Sub-functional modules and risk points of the content management system:

[0095] 1. Content input box: weight 0.1;

[0096] SQL injection: threat quantification value 0.4;

[0097] XSS attack: threat quantification value 0.4;

[0098] Special character handling error (improper encoding / escaping): Threat quantification value 0.2;

[0099] 2. Permission setting: weight 0.3;

[0100] Unauthorized content access: Threat quantification value 0.4;

[0101] Vertical privilege escalation: Threat quantification value 0.3;

[0102] 3. Data storage: weight 0.4;

[0103] Plain text storage: threat quantification value 0.3;

[0104] Insecure encryption: Threat quantification value 0.2;

[0105] 4. API interface: weight 0.2;

[0106] API without authentication: Threat Quantification Value 0.3;

[0107] Minimal cut set:

[0108] 1. {Content input box: SQL injection ∪ XSS attack ∪ special character processing error (improper encoding / escaping)}, expressed as: M1∪M2∪M3, the threat level is calculated to be 4;

[0109] 2. {Permission setting: unauthorized content access ∪ vertical permission escalation}, expressed as: M11 ∪ M13, the calculated threat level is 2.1

[0110] 3. {Data storage: plaintext storage ∪ insecure encryption}, expressed as: M15 ∪ M16, the calculated threat level is 2.1;

[0111] 4. {API interface: API without authentication}, represented by: M36, the calculated threat level is 0.6;

[0112] The calculated threat level of the main module is 8.7;

[0113] Test case generation:

[0114] 1. Test the input validation function of the content input box;

[0115] Verify SQL injection;

[0116] Verify XSS attacks;

[0117] Validate special character input.

[0118] 2. Test permission settings.

[0119] Verify privilege escalation;

[0120] Verify unauthorized access to content;

[0121] 3. Test the risk of sensitive data leakage in data storage and verify data encryption and backup mechanisms.

[0122] Verify plain text transmission and encryption mechanism for sensitive data;

[0123] Verify data backup mechanism;

[0124] 4. Test the API interface.

[0125] Verify API abuse;

[0126] Coping strategies:

[0127] 1. Insufficient input validation: Use strong input validation and sanitization mechanisms to prevent SQL injection and XSS attacks; set a whitelist of special characters.

[0128] 2. Privilege escalation: Strict authority control and auditing to prevent unauthorized access to content; strictly limit unauthorized access.

[0129] 3. Sensitive data leakage: Use encrypted storage and backup solutions to protect the confidentiality of sensitive data.

[0130] 4. Insecure APIs: Conduct security assessments and harden APIs to prevent abuse.

[0131] 2. Media Asset Management System (MAM)

[0132] Sub-function modules and risk points:

[0133] 1. File upload: weight: 0.2;

[0134] Malicious file upload: threat quantification value 0.4;

[0135] Improper file size limit: Threat quantification value 0.3;

[0136] 2. File type verification: weight 0.3;

[0137] Improper file type verification: Threat quantification value 0.3;

[0138] Insufficient whitelist content for file types: Threat quantification value 0.3;

[0139] 3. File storage: weight 0.3;

[0140] Plain text storage (unencrypted storage): Threat quantification value 0.3

[0141] Improper data handling (data loss or mishandling): Threat quantification value 0.3

[0142] Unauthorized access to data (information leakage): Threat quantification value 0.3

[0143] Data tampering (lack of integrity protection): Threat quantification value 0.3

[0144] Minimal cut set:

[0145] 1. {File upload: malicious file upload ∪ improper file size limit}, expressed as M25 ∪ M26, the calculated threat level is 1.4;

[0146] 2. {File type verification: Improper file format type verification ∩ Insufficient file type whitelist}, expressed as M30 ∩ M31, the calculated threat level is 0.27;

[0147] 3. {File storage: plaintext storage ∪ improper data processing (data loss or incorrect processing) ∪ unauthorized data access (information leakage) ∪ data tampering (lack of integrity protection)}, expressed as M15 ∪ M19 ∪ M21 ∪ M22, the threat level is calculated to be 3.6;

[0148] The threat level of the main module is calculated to be 5.27;

[0149] Test case generation:

[0150] 1. Test the verification function of file upload:

[0151] Verify file upload (malicious file) verification function;

[0152] 2. Verify the file upload file size limit

[0153] Test file type validation:

[0154] Verify the file format type;

[0155] Verify file type whitelist;

[0156] 3. Test file storage:

[0157] Verify plaintext storage;

[0158] Improper handling of validation data (data loss or mishandling);

[0159] Verify that data is not accessed by authorized personnel;

[0160] Verify data tampering;

[0161] Coping strategies:

[0162] 1. Insufficient file upload verification: Strengthen file upload verification, limit file type and size, and scan for malicious files.

[0163] 2. Improper file type verification: Establish a sound file type whitelist to prevent trusted file types from being uploaded.

[0164] 3. File storage data leakage and easy data loss: Use encrypted storage and strict access control measures, and adopt data backup technology;

[0165] Unauthorized access to data: Strengthen data access control to prevent unauthorized access and tampering.

[0166] It can be seen that after calculation, the threat level of the content management system is 8.7, and the threat level of the media asset management system is 5.27. Therefore, the content management system needs to be tested intensively, and the content input box module in the sub-module faces a higher security risk and needs to be tested intensively.

[0167] In summary, the risk level calculated by the present invention can accurately measure the degree of security risk faced by each functional module and submodule of the radio and television supervision software system. The greater the threat level, the greater the risk of the module, and the more attention needs to be paid to testing, risk repair and prevention. The present invention can intuitively know the modules that need to be focused on in the radio and television supervision software system through the calculation of the threat level, thereby effectively reducing the security risks of the system in actual operation.

Claims

1. A method for calculating the threat level of a radio and television supervision software system, characterized in that: The steps include: Step 1: Establish a risk tree based on the function modules of the radio and television supervision software system, the submodules of the function modules, and the security vulnerabilities of the submodules, and connect the function modules, submodules, and security vulnerabilities using a logic diagram; Step 2: Assign a risk quantification number to each security vulnerability in the risk tree, then assign weights according to the importance of the sub-module within the functional module, and then calculate the threat degree based on the threat quantification number and weight. The threat degree is used to measure the degree of security risk faced by each functional module and sub-module.

2. The method for calculating the threat level of the radio and television supervision software system according to claim 1 is characterized in that: 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 sub-modules under the functional module as the secondary event, and all possible direct factors that lead to security failures as the bottom event. The bottom event is the possible security vulnerability in the system, and then a logic diagram is used to represent the logical connection between the events.

3. The method for calculating the threat level of the radio and television supervision software system according to claim 2 is characterized in that: 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.

4. The method for calculating the threat level of the radio and television supervision software system according to claim 1 is characterized in that: The risk levels of the security vulnerabilities include high risk, higher risk, medium risk and low risk, where the risk quantification number of high risk is 0.5, the risk quantification number of higher risk is 0.4, the risk quantification number of medium risk is 0.3, and the risk quantification number of low risk is 0.

1.

5. The method for calculating the threat level of the radio and television supervision software system according to claim 2 is characterized in that: The calculation formula of the threat degree is as follows: R Si =Ro Si +Ra Si (1) Where: R Si is the threat level of the functional module; Ro Si Ra is the threat level of the next-level event or gate connection of the functional module; Si The threat level of the module's next-level event connected to the door; 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