IoT device cybersecurity compliance testing systems, equipment and methods
The automated assessment of the IoT device cybersecurity compliance testing system solves the problems of low efficiency and poor consistency in IoT device cybersecurity compliance assessment, and achieves efficient and accurate compliance testing and risk assessment.
Patent Information
- Application Number
- CN202611298801.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-26
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, the network security compliance assessment of IoT devices relies on manual verification, which is inefficient and inconsistent, making it difficult to meet the needs of batch testing. Furthermore, the test results lack systematic organization and correlation analysis, affecting the objectivity and repeatability of the compliance assessment.
We provide a cybersecurity compliance testing system for IoT devices, including modules for data collection, testing execution, result processing, and report output. Through automated testing and in-depth analysis, it generates structured datasets and outputs compliance testing reports, supporting historical difference comparisons and cross-clause correlation analysis.
It enables automated assessment of cybersecurity compliance of IoT devices, improves detection efficiency, reduces reliance on manual methods, ensures the objectivity and consistency of detection results, and has risk assessment capabilities, thereby enhancing the availability of the detection system.
Smart Images

Figure CN123122916A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of IoT device security technology, specifically to IoT device network security compliance testing systems, testing equipment, and IoT device network security compliance testing methods. Background Technology
[0002] With the rapid popularization of Internet of Things (IoT) technology, consumer IoT devices such as smart homes, wearable devices, smart speakers, and network cameras are widely entering homes and public places. However, many IoT devices lack basic network security protections, and have security vulnerabilities such as weak default passwords, unencrypted communication channels, and lack of firmware update mechanisms. These vulnerabilities are easily exploited by malicious attackers, leading to security incidents such as data breaches and botnets.
[0003] The EN 303645 standard published by ETSI (European Telecommunications Standards Institute) specifies 13 categories of cybersecurity baseline requirements for consumer IoT devices. These requirements cover core provisions such as prohibiting universal default passwords, vulnerability disclosure mechanisms, software update management, storage of sensitive security parameters, communication security, minimizing the attack surface, software integrity protection, and personal data protection. It has become an authorized standard of RED (Radio Equipment Directive) and has been adopted by many countries and regions, including the UK and Singapore.
[0004] However, common EN 303645 compliance assessments primarily rely on manual verification by safety testers. Due to the numerous and interrelated clauses in the standard, manual verification is inefficient and time-consuming, making it difficult to meet the needs of batch equipment compliance assessments. Furthermore, differences in understanding of the clauses among different testers lead to inconsistent test results, and the output test reports suffer from inconsistent formats, affecting the objectivity and repeatability of compliance assessments and making it difficult to directly meet the standard format requirements of regulatory agencies and third-party certification bodies.
[0005] Furthermore, there is currently a lack of systematic organization and correlation analysis methods for test results after compliance assessment, making it difficult to establish correlations between multiple non-compliant items and trace their common root causes, resulting in weak readability of test results. Summary of the Invention
[0006] In view of this, this application provides an IoT device network security compliance testing system, testing equipment, and IoT device network security compliance testing method, which can improve testing efficiency, reduce reliance on manual labor, and ensure the objectivity, comprehensiveness, and consistency of testing results.
[0007] To address the aforementioned technical problems, this application adopts the following technical solution: A network security compliance testing system for IoT devices is provided, comprising a data acquisition module, a testing execution module, a result processing module, and a report output module connected sequentially. The data acquisition module acquires configuration information of the IoT device under test through an external testing interface and transmits the configuration information to the testing execution module. The configuration information includes firmware information, configuration parameters, and network interface data. The testing execution module performs item-by-item testing on the configuration information based on the clauses of the EN 303645 standard, generating test results. The result processing module performs historical difference comparison, cross-clause correlation analysis, and risk level assessment on the test results, generating a structured dataset. The report output module integrates the structured dataset into a compliance testing report in a preset format and outputs it.
[0008] In one specific embodiment, the detection execution module includes a clause mapping unit, which is connected to the data acquisition module and the result processing module. The clause mapping unit is used to map the clause requirements of the EN 303645 standard clauses into executable detection rules, automatically match the detection strategy according to the configuration information of the IoT device under test, detect the configuration information according to the detection rules and the detection strategy, generate the detection results, and transmit them to the result processing module.
[0009] In one specific implementation, the result processing module includes a vulnerability association analysis unit, which connects the clause mapping unit and the report output module. The clause requirements also include semantic relationships between clauses, and the structured dataset includes a vulnerability association graph. The vulnerability association analysis unit is used to obtain the semantic relationships between clauses from the clause mapping unit, perform cross-clause association analysis on non-compliant items in the detection results based on the semantic relationships between clauses, generate the vulnerability association graph, and output it.
[0010] In one specific implementation, the semantic association between the clauses includes at least one of the following: common security attribute association, attack chain dependency association, and remediation measure sharing association.
[0011] In one specific embodiment, the result processing module further includes a difference comparison unit, which is connected to the clause mapping unit and the report output module. The structured dataset includes status change annotations. The difference comparison unit is used to obtain the detection results and configuration information from the clause mapping unit, obtain the compliance detection report of the previous detection on the tested IoT device using the firmware information, perform historical difference comparison between the detection results and the compliance detection report of the previous detection on the tested IoT device, generate the status change annotations, and output them. The status change annotations include newly added non-compliant items, fixed items, persistent items, and persistence duration.
[0012] In one specific implementation, the result processing module further includes a risk assessment unit, which is connected to the vulnerability association analysis unit, the difference comparison unit, and the report output module. The structured dataset includes a risk assessment report. The risk assessment unit is used to assess the risk level of non-compliant items in the detection results based on the node connectivity and the duration of existence in the vulnerability association graph, using a weighted scoring model, and generates and outputs the risk assessment report. The scoring dimensions of the risk level assessment include the basic score of the severity of the clause, the node connectivity, and the duration of existence.
[0013] In one specific implementation, the result processing module further includes a management report unit, which is connected to the risk assessment unit and the report output module. The structured dataset includes a compliance summary report. The management report unit is used to summarize and review the risk assessment report, generate the compliance summary report using the risk assessment report, and output it. The compliance summary report includes at least one of the following: a statistical chart of compliance rate for EN 303645 clauses, a list of non-compliance items ranked by risk level, operational guidance for rectifying high-risk non-compliance items, and a rectification timeline.
[0014] In one specific embodiment, the IoT device network security compliance testing system further includes a historical testing database, which is connected to the difference comparison unit and the report output module. The historical testing database is used to store the compliance testing report output by the report output module. The historical testing database is indexed by the firmware information of the IoT device under test and the timestamp of the compliance testing report.
[0015] In one specific embodiment, the detection execution module further includes a compliance rule base unit, which is connected to the clause mapping unit; the compliance rule base unit is used to store the clause requirements, which include detection judgment rules, compliance benchmark values, and historical version rules.
[0016] In one specific implementation, the detection and judgment rules include provisions prohibiting general default passwords, vulnerability disclosure mechanisms, software update management, sensitive security parameter storage, communication security, attack surface minimization, software integrity, personal data protection, system availability resilience, and telemetry data security.
[0017] To solve the above-mentioned technical problems, another technical solution adopted in this application is to provide a testing device, which includes an IoT device network security compliance testing system as described in any of the above specific embodiments.
[0018] To address the aforementioned technical problems, another technical solution adopted in this application is: providing a method for network security compliance testing of IoT devices, implemented using the IoT device network security compliance testing system as described in any of the specific embodiments above. The method includes: acquiring configuration information of the IoT device under test through an external testing interface, the configuration information including firmware information, configuration parameters, and network interface data; performing item-by-item testing on the configuration information based on the clauses of the EN303645 standard, generating test results; performing historical difference comparison, cross-clause correlation analysis, and risk level assessment on the test results, generating a structured dataset; and integrating the structured dataset into a compliance testing report in a preset format and outputting it.
[0019] The beneficial effects of this application include: by integrating data acquisition, automatic detection, in-depth analysis, and report generation modules, it can efficiently and automatically assess the cybersecurity compliance of IoT devices, realizing an automated detection process, significantly improving detection efficiency, reducing the reliance on manual intervention in the entire detection process, and ensuring the objectivity and consistency of detection results; at the same time, it can also enable the detection process to have a certain risk assessment capability through historical difference comparison and cross-clause correlation analysis, greatly improving the usability of the IoT device cybersecurity compliance detection system. Attached Figure Description
[0020] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the implementation will be briefly introduced below. Obviously, the drawings described below are some implementations of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.
[0021] Figure 1 This is a first structural schematic block diagram of an embodiment of the IoT device network security compliance testing system of this application;
[0022] Figure 2This is a second structural schematic block diagram of an embodiment of the IoT device network security compliance testing system of this application;
[0023] Figure 3 This is a flowchart illustrating an embodiment of the IoT device network security compliance testing method of this application;
[0024] Figure 4 This is a schematic block diagram of the structure of an embodiment of the testing equipment of this application;
[0025] Figure 5 This is a schematic diagram of a vulnerability association map according to an embodiment of this application.
[0026] Figure label:
[0027] 100. IoT device under test; 200. External test interface; 300. Data acquisition module; 400. Detection execution module; 401. Clause mapping unit; 402. Compliance rule base unit; 500. Result processing module; 501. Vulnerability correlation analysis unit; 502. Difference comparison unit; 503. Risk assessment unit; 504. Management report unit; 600. Historical detection database; 700. Report output module; 80. IoT device network security compliance detection system; 90. Detection equipment. Detailed Implementation
[0028] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of the invention. However, those skilled in the art will understand that the invention can be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods are omitted so as not to obscure the description of this application with unnecessary detail.
[0029] It should be understood that, when used in this specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or modules, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, modules and / or a collection thereof.
[0030] It should also be understood that the terminology used in this application specification is for the purpose of describing particular embodiments only and is not intended to limit the application. As used in this application specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise. The terms “first” and “second” are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as “first” or “second” may explicitly or implicitly include at least one of that feature. In the description of this application, “a plurality” means at least two, such as two, three, etc., unless otherwise explicitly specified.
[0031] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.
[0032] Many specific details are set forth in the following description in order to provide a full understanding of this application. However, this application may also be implemented in other ways different from those described herein. Those skilled in the art can make similar extensions without departing from the spirit of this application. Therefore, this application is not limited to the specific embodiments disclosed below.
[0033] With the rapid popularization of Internet of Things (IoT) technology, consumer IoT devices such as smart homes, wearable devices, smart speakers, and network cameras are widely entering homes and public places. However, many IoT devices lack basic network security protections, and have security vulnerabilities such as weak default passwords, unencrypted communication channels, and lack of firmware update mechanisms. These vulnerabilities are easily exploited by malicious attackers, leading to security incidents such as data breaches and botnets.
[0034] The EN 303645 standard published by ETSI (European Telecommunications Standards Institute) specifies 13 categories of cybersecurity baseline requirements for consumer IoT devices. These requirements cover core provisions such as prohibiting universal default passwords, vulnerability disclosure mechanisms, software update management, storage of sensitive security parameters, communication security, minimizing the attack surface, software integrity protection, and personal data protection. It has become an authorized standard of RED (Radio Equipment Directive) and has been adopted by many countries and regions, including the UK and Singapore.
[0035] However, common EN 303645 compliance assessments primarily rely on manual verification by safety testers. Due to the numerous and interrelated clauses in the standard, manual verification is inefficient and time-consuming, making it difficult to meet the needs of batch equipment compliance assessments. Furthermore, differences in understanding of the clauses among different testers lead to inconsistent test results, and the output test reports suffer from inconsistent formats, affecting the objectivity and repeatability of compliance assessments and making it difficult to directly meet the standard format requirements of regulatory agencies and third-party certification bodies.
[0036] Furthermore, there is currently a lack of systematic organization and correlation analysis methods for test results after compliance assessment, making it difficult to establish correlations between multiple non-compliant items and trace their common root causes, resulting in weak readability of test results.
[0037] In order to improve the above technical problems, the inventors of this application, after long-term research, have proposed at least the following embodiments.
[0038] Please see Figure 1 , Figure 1 This is a first structural schematic block diagram of an embodiment of the IoT device network security compliance testing system of this application. It should be noted that if substantially the same result is achieved, this embodiment is not necessarily identical. Figure 1 The structure shown is for illustrative purposes only. This application provides a network security compliance testing system 80 for IoT devices, used to detect the configuration and behavior of IoT devices to identify potential security vulnerabilities and non-compliance items. Specifically, the IoT device network security compliance testing system 80 may include a data acquisition module 300, a detection execution module 400, a result processing module 500, and a report output module 700 connected in sequence.
[0039] The Internet of Things (IoT) device cybersecurity compliance testing system 80 can refer to an automated or semi-automated system specifically designed to assess whether IoT devices comply with a specific cybersecurity standard. In the specific implementation of this application, the specific cybersecurity standard is the EN 303645 standard.
[0040] EN 303645 is a standard published by the European Telecommunications Standards Institute (ETSI) that sets baseline requirements for cybersecurity in consumer IoT devices. EN 303645 contains a series of specific security requirements to guide the design, development, and deployment of IoT devices, thereby enhancing their cybersecurity capabilities.
[0041] The data acquisition module 300 is used to acquire the configuration information of the IoT device under test 100 through the external test interface 200 and transmit the configuration information to the detection execution module 400. The data acquisition module 300 may refer to the module in the IoT device network security compliance detection system 80 responsible for acquiring the necessary detection data from the IoT device under test 100.
[0042] The external test interface 200 is used to read the device configuration information. Specifically, it can refer to the physical or logical connection point for data exchange between the data acquisition module 300 and the IoT device under test 100.
[0043] For example, the external test interface 200 can be a wired or wireless connection such as USB, Ethernet, or Wi-Fi. The external test interface 200 can be a physical interface, such as UART, JTAG, USB, or Ethernet port, or a logical interface, such as a protocol interface like RESTful API, SNMP, MQTT, or CoAP. For instance, the external test interface 200 can obtain the startup logs and system configuration of the IoT device under test 100 via a serial port connection. As another example, the external test interface 200 can obtain the network configuration and list of running services of the IoT device under test 100 via an SSH connection.
[0044] The IoT device under test 100 can refer to IoT devices that need to undergo cybersecurity compliance testing, such as smart home devices, wearable devices, and industrial sensors.
[0045] In this specific embodiment, the configuration information may include firmware information, configuration parameters, and network interface data.
[0046] Configuration information refers to the key settings and status data of the IoT device under test (IoT device 100). Firmware information specifically includes the system version, application version, signature, and update history of the IoT device 100. Configuration parameters may include the function settings, authentication policies, network service configurations, and encryption configurations of the IoT device 100. Network interface data may include the network connection status, traffic characteristics, open services, and API information of the IoT device 100.
[0047] The detection execution module 400 is used to perform item-by-item detection on the configuration information based on the clauses of the EN 303645 standard, thereby generating detection results. The detection execution module 400 may refer to the module in the IoT device network security compliance detection system 80 that analyzes and judges the configuration information according to the preset clauses of the EN 303645 standard.
[0048] The test execution module 400 can convert the clauses of the EN 303645 standard into executable test logic, and check each configuration and behavior of the device under test one by one and output the test results. From the test results, it can be determined whether the device under test meets the safety requirements.
[0049] For example, the detection execution module 400 may contain a series of predefined detection scripts or programs, each script or program corresponding to one or a set of clauses of the EN 303645 standard. These detection scripts or programs are manually written and maintained, and perform logical judgments on the input configuration information according to the requirements of the standard clauses, thereby generating preliminary detection results.
[0050] For example, regarding the "prohibition of common default passwords" clause, the detection execution module 400 can check whether common default username and password combinations exist in the configuration information. As another example, regarding the "communication security" clause, the detection execution module 400 can check whether unencrypted communication protocols or weak encryption algorithms are used in the network interface data.
[0051] The test result can refer to the raw judgment data on the compliance status of the IoT device under test generated by the test execution module 400 after it has checked the configuration information item by item according to the clauses of EN 303645 standard. The test result usually indicates whether the device is compliant under specific clauses.
[0052] The results processing module 500 is used to perform historical difference comparisons, cross-clause correlation analysis, and risk level assessments on the test results, generating a structured dataset. The results processing module 500 can refer to the module in the IoT device network security compliance testing system 80 that performs in-depth processing and analysis on the raw test results output by the testing execution module 400. Through various analysis methods, the results processing module 500 can transform discrete test results into a structured dataset with higher value and readability.
[0053] Historical difference comparison refers to comparing the current detection results with the previous detection results of the IoT device under test 100 to identify changes in the security status of the IoT device under test 100. This allows for determination of whether new non-compliance items have been added to the current detection results, whether vulnerabilities in previous detection results have been patched, and so on. For example, during historical difference comparison, the result processing module 500 can receive the current detection results and compare them item by item with the previous detection results stored in the local file system to identify which clauses have changed in compliance status.
[0054] Cross-clause correlation analysis refers to identifying logical or technical connections between different clauses of the EN 303645 standard to uncover common security issues or root causes behind multiple non-compliance items. For example, if the "Storage of Sensitive Security Parameters" clause is non-compliant, and the "Software Integrity" clause is also non-compliant, the results processing module 500 can determine that there may be deeper security vulnerabilities.
[0055] Risk level assessment refers to the process of evaluating and classifying the risk of non-compliance items based on factors such as the severity, potential impact, and duration of non-compliance items in the test results. For example, when conducting risk level assessment, the results processing module 500 can assign a risk level to each non-compliance item based on a preset risk assessment matrix, combined with the severity, potential impact, and duration of the non-compliance item.
[0056] A structured dataset refers to a collection of detection data that, after processing by the results organization module 500, possesses a clear logical structure and interrelationships. Specifically, a structured dataset can include historical differences obtained from historical difference comparisons, correlation analysis results obtained from cross-clause correlation analysis, and risk assessment information obtained from risk level assessment. These historical differences, correlation analysis results, and risk assessment information can be used for subsequent report generation and in-depth analysis. For example, a structured dataset can be a set of tables in a relational database or a data structure in a NoSQL database (a non-relational database), used to store and represent detection results and their related information.
[0057] The report output module 700 is used to integrate the structured dataset into a compliance testing report in a preset format and output it. The report output module 700 can refer to the module in the IoT device network security compliance testing system 80 that is responsible for generating a compliance testing report in a specific format using the structured dataset and presenting it to the user. The report output module 700 ensures that the final output compliance testing report is complete in content, has a consistent format, and meets the requirements of regulatory agencies or certification bodies.
[0058] For example, the report output module 700 can include multiple preset report templates in PDF, Word, and HTML formats. Information from the structured dataset, including detection results, historical discrepancies, correlation analysis findings, and risk levels, can be populated into the selected report template. For instance, detection results can be organized into a table, and risk level assessment results can be summarized in a risk overview section.
[0059] The compliance testing report, generated by the report output module 700, is a document detailing the cybersecurity compliance status of the tested IoT device 100. The compliance testing report typically includes testing results, risk assessments, and remedial recommendations, and adheres to pre-defined format requirements.
[0060] The IoT device cybersecurity compliance testing system 80 provided in this specific embodiment integrates data acquisition, automatic detection, in-depth analysis, and report generation modules. This enables efficient and automated assessment of the cybersecurity compliance of IoT devices, achieving an automated testing process. This significantly improves testing efficiency and effectively reduces reliance on manual intervention, ensuring the objectivity and consistency of the test results. Furthermore, the IoT device cybersecurity compliance testing system 80 can also incorporate risk assessment capabilities through historical difference comparisons and cross-clause correlation analysis, greatly enhancing its usability.
[0061] Please see Figure 2 , Figure 2 This is a schematic block diagram of the second structure of an embodiment of the IoT device network security compliance testing system of this application. In a specific embodiment of this application, the testing execution module 400 may specifically include a clause mapping unit 401, which is connected to the data acquisition module 300 and the result processing module 500. It should be noted that if there are substantially the same result, this embodiment does not necessarily use it as the standard. Figure 2 The structures shown are limited.
[0062] The clause mapping unit 401 is used to map the clause requirements of the EN 303645 standard clauses into executable testing rules, and automatically match the testing strategy according to the configuration information of the IoT device under test 100. Then, it tests the configuration information according to the testing rules and testing strategy, generates the testing results, and transmits them to the result processing module 500.
[0063] Optionally, the clause mapping unit 401 can be implemented based on a rule engine. The clause mapping unit 401 can maintain a predefined clause-rule mapping table that defines the mapping relationship between clauses of the EN 303645 standard and detection rules. In the clause-rule mapping table, each clause can correspond to one or more sets of specific executable detection rules. Detection rules can include interface scanning, parameter extraction, behavior analysis, etc. When an EN 303645 standard clause is received, the rule engine can obtain the corresponding detection rule according to the clause-rule mapping table.
[0064] Optionally, the clause mapping unit 401 can also employ machine learning or NLP (Natural Language Processing) techniques to perform semantic analysis on the clauses of the EN 303645 standard, automatically extract key information, and generate executable detection rules. Specifically, it can train a model to identify keywords, conditions, and expected behaviors in the clauses of the EN 303645 standard and convert them into structured detection scripts or query statements.
[0065] Optionally, the clause mapping unit 401 can also determine the device type of the IoT device under test 100 based on firmware information and configuration parameters, and then obtain an appropriate detection strategy based on the device type. The detection strategy may include standard clauses that the IoT device under test 100 must detect. By matching an appropriate detection strategy, standard clauses that are irrelevant to the IoT device under test 100 can be skipped, and only relevant standard clauses included in the detection strategy can be detected, thereby reducing the probability of false positives and improving detection efficiency.
[0066] Specifically, the clause mapping unit 401 can maintain a device type-detection strategy mapping table. When receiving firmware information or configuration parameters of the IoT device under test 100, the clause mapping unit 401 can query the device type-detection strategy mapping table and obtain the most suitable detection strategy for the IoT device under test 100 based on the firmware information or configuration parameters of the IoT device under test 100.
[0067] The device types can include pure software-based App devices, Bluetooth-connected devices, Wi-Fi-connected devices, and multi-interface composite devices.
[0068] Optionally, the clause mapping unit 401 can be connected to the data acquisition module 300 and the result processing module 500 via an internal bus, data interface, or network interface to achieve data transmission. The clause mapping unit 401 can interact with the data acquisition module 300 and the result processing module 500 via API calls, message queues, or shared memory.
[0069] In this specific embodiment, by introducing a clause mapping unit 401 into the detection execution module 400, the transformation from abstract EN 303645 standard clauses to specific automated detection logic is realized. Furthermore, the clause mapping unit 401 can match appropriate detection strategies based on configuration information, making the detection process more targeted and flexible. Through the collaboration of detection rules and detection strategies, the clause mapping unit 401 can efficiently and accurately assess the compliance status of the IoT device 100 under test, providing a high-quality, structured data foundation for subsequent result processing and report generation.
[0070] like Figure 2 As shown in a specific embodiment of this application, the result processing module 500 may specifically include a vulnerability association analysis unit 501, which connects the clause mapping unit 401 and the report output module 700. The clause requirements also include semantic relationships between clauses, and the structured dataset includes a vulnerability association graph.
[0071] The vulnerability association analysis unit 501 is used to obtain the semantic association between clauses from the clause mapping unit 401, perform cross-clause association analysis on non-compliant items in the detection results based on the semantic association between clauses, generate a vulnerability association map and output it.
[0072] The vulnerability correlation analysis unit 501 can perform cross-clause correlation analysis on non-compliant items in the detection results based on rule matching. For example, if non-compliant items in clause A and clause B both involve the common security attribute of "weak passwords," they can be correlated. Alternatively, it can be based on graph algorithms, using graph traversal, shortest path, or community discovery algorithms to identify potential correlation patterns.
[0073] For example, the vulnerability association analysis unit 501 could be a rule engine-based analyzer with pre-defined association rules for several non-compliant items. When a non-compliant item in the detection results meets specific conditions, association analysis can be triggered. Alternatively, the vulnerability association analysis unit 501 could be a processing module based on graph database or knowledge graph technology, using terms and non-compliant items as nodes and semantic associations as edges, to perform graph traversal and pattern matching.
[0074] A vulnerability association graph is a data structure that graphically represents non-compliance items and their interrelationships. It can intuitively show the dependencies, commonalities, or causal relationships between non-compliance items, and help readers quickly understand the root causes and scope of impact of non-compliance issues.
[0075] Vulnerability association graphs can be data models in graph databases such as Neo4j, where nodes represent non-compliant items and / or clauses, and edges represent relationships. Vulnerability association graphs can also be data structures in JSON or XML format, using nesting or referencing to represent the relationships between nodes and edges, and can be rendered on the front end using visualization tools for readers to view.
[0076] Specifically, the vulnerability association analysis unit 501 can use graph theory to construct a vulnerability association graph. The vulnerability association analysis unit 501 can treat each non-compliant item as a node and construct directed edges based on relationships such as root cause association, attack chain dependency, and shared remediation measures.
[0077] For example, the two non-compliance items "not disabling the general default password" and "communication data not encrypted" may together lead to the tested IoT device 100 being remotely controlled. Therefore, after correlation analysis of these two non-compliance items, they can be merged into a high-priority risk in the report for rectification guidance. This will help technical personnel to solve the most security problems with the least amount of resources when fixing non-compliance items in the future.
[0078] Semantic relationships between clauses refer to the inherent logical, functional, or security connections between different clauses in the EN 303645 standard. These connections form the basis for cross-clause correlation analysis and can guide the Vulnerability Correlation Analysis Unit 501 in identifying deep connections between non-compliance items. Semantic relationships between clauses can be pre-defined and maintained manually by security experts and stored in a database or configuration file connected to the server. For example, semantic relationships between clauses can be labeled using tags, keywords, or relationship types. Alternatively, Natural Language Processing (NLP) technology can be used to analyze the standard clause text and automatically extract or suggest potential semantic relationships between clauses.
[0079] In this specific implementation, by introducing a vulnerability correlation analysis unit 501, cross-clause correlation analysis is performed on non-compliant items in the detection results using preset semantic relationships between clauses. This integrates the originally isolated detection results into a vulnerability correlation graph with internal logic. This improves upon the fragmented nature of traditional detection results and the difficulty in identifying deep-seated root causes. It allows readers to examine the cybersecurity status of IoT devices from a global perspective, not only discovering non-compliance in individual clauses but also identifying common root causes, potential attack paths, and interdependencies leading to multiple non-compliance items. This graph-based presentation significantly enhances the depth, readability, and systematic nature of the detection results, greatly simplifying the process for security personnel to understand complex security issues. This enables more efficient development of targeted remediation plans and improves the overall security protection level of IoT devices.
[0080] In a specific embodiment of this application, the semantic relationship between clauses may specifically include at least one of the following: common security attribute relationship, attack chain dependency relationship, and remediation measure sharing relationship.
[0081] Common security attribute association refers to the sharing of the same security protection goals or concerns among different standard clauses. For example, multiple standard clauses may all aim to protect the confidentiality, integrity, or availability of data. Common security attribute association can be achieved by assigning a corresponding security attribute label to each EN 303645 clause through a predefined security attribute labeling system, thereby identifying clauses with the same label. Alternatively, common security attribute association can be achieved through ontology modeling, constructing a security domain knowledge graph, associating clauses with security attribute concepts, and thus discovering common attributes.
[0082] Attack chain dependencies refer to the possibility that one non-compliance item can facilitate the exploitation of another non-compliance item or become a preliminary step in the attack path. This relationship simulates the combined attack path taken by an attacker from the initial entry point to the final target. Attack chain dependencies can be identified through threat modeling methods, analyzing how different non-compliance items might be exploited and constructing a graph of potential attack scenarios to recognize dependencies within the attack chain. Alternatively, security incident response experience bases can be used to summarize patterns of vulnerability combination and exploitation in historical attack events, abstracting these patterns into attack chain dependency rules for identification.
[0083] Shared remediation measures refer to situations where multiple non-compliance items can be resolved using the same or similar remediation measures. Identifying such relationships helps to concentrate resources and improve remediation efficiency. Shared remediation measures can be identified by maintaining a remediation measures knowledge base, mapping common security vulnerability remediation solutions to clauses of the EN 303645 standard, thereby discovering remediation measures that can be shared. Alternatively, data mining of historical remediation records can be used to analyze which non-compliance items are frequently remediated together in practice, thus inferring shared remediation measures.
[0084] See Figure 5 , Figure 5 This is a schematic diagram of a vulnerability association map according to an embodiment of this application. Figure 5 The vulnerability association graph shown uses the clauses of the EN 303645 standard as nodes and the three types of semantic associations between the clauses as directed edges.
[0085] In the three types of semantic relationships, the blue solid line in the diagram represents a shared security attribute relationship, indicating that multiple clauses point to the same lack of a security mechanism. For example, clauses 5.1 and 5.4 both pertain to deficiencies in authentication credential management. The red solid line in the diagram represents an attack chain dependency relationship, indicating that non-compliance with one standard clause can exacerbate the risk of another. For example, the red arc from clauses 5.1 to 5.5 to 5.8 can constitute an attack path of "default password → plaintext communication → personal data leakage." The green dashed line in the diagram represents a shared remediation measure relationship, indicating that multiple clauses can be simultaneously remediated through the same security hardening operation. For example, deploying a certificate management system can simultaneously remediate clauses 5.5 and 5.7.
[0086] By analyzing the connectivity of nodes in a vulnerability association graph, priority remediation targets can be identified, for example, in Figure 5 Among them, clauses 5.1 and 5.5 have the highest connectivity, and prioritizing the rectification of clauses 5.1 and 5.5 can achieve the greatest compliance benefits with the least investment.
[0087] By introducing three specific semantic association dimensions—common security attribute association, attack chain dependency association, and remediation measure shared association—the logical depth and accuracy of vulnerability association analysis can be enhanced. This allows the vulnerability association graph to reflect a structured knowledge system that reflects the essential connections between security vulnerabilities. This not only improves the objectivity and repeatability of compliance assessments but also significantly enhances the readability of detection results, providing more precise logical support for subsequent risk assessments and remediation planning.
[0088] See Figure 2 In a specific embodiment of this application, the result processing module 500 further includes a difference comparison unit 502, which connects the difference comparison unit 502 with the clause mapping unit 401 and the report output module 700. The structured dataset includes state change annotations.
[0089] Optionally, the difference comparison unit 502 can be connected to the clause mapping unit 401 and the report output module 700 via an internal data interface or API. This connection can be a data stream transfer or a function call between modules. The difference comparison unit 502 can obtain the detection results and configuration information from the clause mapping unit 401 through shared memory, a message queue mechanism, or by calling a specific data access interface provided by the clause mapping unit 401.
[0090] The difference comparison unit 502 is used to obtain the test results and configuration information from the clause mapping unit 401, obtain the compliance test report of the last test of the IoT device under test 100 using the firmware information, compare the test results with the compliance test report of the last test of the IoT device under test 100, generate a status change label and output it.
[0091] For example, the difference comparison unit 502 can be implemented as a standalone microservice or a software component integrated into the result processing module 500, responsible for executing data comparison algorithms and logic. Alternatively, it can be a set of specific functionalities integrated into the result processing module 500. Specifically, the difference comparison unit 502 can perform comparisons based on a rule engine, that is, by pre-setting a series of comparison rules to identify the differences between the current detection result and the previous compliance detection report. As another example, the difference comparison unit 502 can perform comparisons based on data structure difference algorithms, such as by comparing the tree structure of the detection report in JSON or XML format to discover changes in the nodes within the structure.
[0092] After receiving the data, the difference comparison unit 502 can first parse the firmware information in the configuration information, such as extracting the device model and firmware version number. Then, the difference comparison unit 502 can use this firmware information as a query key to initiate a query request to a dedicated historical detection database 600.
[0093] Since IoT devices may have multiple versions or batches, firmware information such as firmware version number and device model can uniquely identify a specific version of the device or its software status. Therefore, firmware information can play an indexing role in the process of obtaining historical compliance test reports, thereby ensuring that the difference comparison unit 502 can accurately retrieve the historical compliance test report corresponding to the current IoT device 100 under test, avoiding the problem of confusion between historical compliance test reports of different versions of IoT devices 100 under test.
[0094] For example, the difference comparison unit 502 can obtain historical compliance test reports by querying a dedicated historical test database 600, which uses firmware information as the main index field, or by retrieving them through a file system that uses firmware information to name directories or files.
[0095] For example, the historical testing database 600 can be a NoSQL database such as MongoDB or a relational database such as PostgreSQL. The historical testing database 600 can store historical compliance testing reports for all tested IoT devices 100, indexed by firmware information and testing timestamps. For example, a query statement could be "SELECT * FROM historical_reports WHERE device_model = 'IoT_Gateway_V1.0' AND firmware_version = 'FW_20231026' ORDER BY timestamp DESC LIMIT 1".
[0096] Optionally, the historical discrepancy comparison process can employ various algorithms. For example, it can compare the compliance status of each clause of the EN303645 standard item by item. Alternatively, it can perform an in-depth comparison of the structured data in the entire historical compliance monitoring report. The granularity of historical discrepancy comparison can be refined to specific configuration parameter values or security attributes, thereby detecting subtle changes.
[0097] The status change labels include newly added non-compliant items, fixed items, items that persist, and duration of persistence.
[0098] State change annotations are a key component of structured datasets, clearly and systematically recording changes in the security compliance status of the tested IoT device 100 at different testing times. State change annotations not only indicate which compliance items have changed, but also specify the nature of the changes, such as whether they are newly added non-compliance items, remedied items, or persistent non-compliance items. For example, state change annotations can be represented in various data formats, such as JSON objects, XML documents, or database table structures, to facilitate subsequent analysis, querying, and report generation.
[0099] After completing the historical discrepancy comparison, the discrepancy comparison unit 502 can generate status change labels based on the comparison results. For example, if a clause was compliant in the previous inspection but is non-compliant this time, it is marked as "New Non-compliant Item". If it was non-compliant in the previous inspection but compliant this time, it is marked as "Resolved Item". If it is non-compliant in both inspections, it is marked as "Persistent Item". Optionally, these status change labels can be generated in a structured form and output to the report output module 700, so that they can be directly integrated into the final compliance inspection report, providing users with intuitive change information.
[0100] Specifically, newly added non-compliance items refer to items that do not meet the requirements of EN 303645 standard for the first time in this test results, indicating that the tested IoT device 100 has new security risks or configuration errors.
[0101] "Rectified items" refers to items that were marked as non-compliant in the previous inspection but have been shown to meet the standard requirements in the current inspection results. This demonstrates the effectiveness of the safety rectification measures implemented after the previous round of inspections.
[0102] A persistent item is an item that has been found to be non-compliant in both the current and at least the previous inspection. This usually means that there are deep-seated security issues that are difficult to resolve or that remedial measures have not been fully implemented.
[0103] Duration of persistence refers to the length of time or number of rounds a non-compliance item persists across multiple compliance checks. A longer duration of persistence generally indicates a more persistent or delayed non-compliance item, and its risk level should be correspondingly higher. For example, duration of persistence can be simply determined by counting the number of times a non-compliance item appears repeatedly in several consecutive compliance check reports.
[0104] For example, for each clause of the EN 303645 standard, if it is shown as "non-compliant" in the current inspection result but "compliant" in a historical compliance inspection report, a "new non-compliant item" label is generated; if it is currently "compliant" but historically "non-compliant," a "resolved item" label is generated; if both are "non-compliant," a "persistent item" label is generated. These status change labels can be stored in a structured dataset in a structured data format, such as a JSON array containing fields like type, clause ID, and description, and are ultimately integrated into the final compliance inspection report through the report output module 700. For example, a dedicated "Status Change Overview" section can be created in the compliance inspection report to display these labels.
[0105] In this specific implementation, firmware information is precisely matched with historical compliance testing reports, and a deep comparison is performed between the current testing results and historical compliance testing reports. This generates clear status change annotations, allowing readers to intuitively understand whether the security status of the tested IoT device 100 is improving, deteriorating, or stagnating. It enables dynamic and continuous tracking and evolution analysis of the security compliance status of IoT devices, thereby timely identifying newly introduced security risks, verifying the effectiveness of security remediation measures, and identifying long-standing, deep-seated security vulnerabilities. This not only significantly improves the depth and accuracy of compliance testing but also provides clear remediation priorities and decision-making basis for the security operation and maintenance of IoT devices. It transforms compliance assessment from a single point-in-time check into continuous security monitoring, greatly enhancing the practical value of the testing results and its support for security management.
[0106] like Figure 2 As shown in a specific embodiment of this application, the result processing module 500 further includes a risk assessment unit 503, which is connected to a vulnerability correlation analysis unit 501, a difference comparison unit 502, and a report output module 700. The structured dataset includes a risk assessment report.
[0107] Risk assessment unit 503 is used to assess the risk level of non-compliant items in the detection results based on the node connectivity and duration of the vulnerability association graph using a weighted scoring model, and generate and output a risk assessment report.
[0108] For example, the risk assessment unit 503 can be a standalone software module deployed on a server, or it can be a service component in the result processing module 500. The risk assessment unit 503 can connect with the vulnerability correlation analysis unit 501, the difference comparison unit 502, and the report output module 700 through internal data interfaces or APIs.
[0109] Node connectivity refers to the degree of connection between each non-compliant item node and the vulnerability association graph generated by the vulnerability association analysis unit 501, calculated by the risk assessment unit 503. Node connectivity reflects the closeness of the association between a non-compliant item and other non-compliant items. For example, if a non-compliant item is associated with multiple other non-compliant items, its node connectivity is high, indicating that it may have a wider impact or be in a critical position in the attack chain. Methods for calculating node connectivity may include, but are not limited to, calculating the degree centrality, betweenness centrality, or eigenvector centrality of nodes.
[0110] Risk level assessment can refer to the risk assessment unit 503 using a pre-defined mathematical model or rule set to comprehensively consider multiple risk dimensions, calculate a comprehensive risk score for each non-compliance item, and classify it into different risk levels based on the score. The weighted scoring model can assign different weights to different risk dimensions to reflect their importance in the overall risk assessment. For example, risk levels can include high, medium, and low.
[0111] A risk assessment report is a report compiled by risk assessment unit 503 according to a preset format, which includes the assessed risk level, risk score, and related assessment basis.
[0112] The risk level assessment includes a base score for the severity of the clause, the connectivity of nodes, and the duration of existence. The values for each dimension are as follows: base score for the severity of the clause: 0-20 points; number of connected nodes: 0-10 points; duration of existence: 0-10 points; and the total risk score after weighted summation of the three values ranges from 0 to 15 points.
[0113] The severity score for a clause can be a baseline score pre-set based on the inherent risks of the clause itself in the EN 303645 standard or industry experience. For example, a clause prohibiting universal default passwords, being one of the most common, fatal, and easily exploited vulnerabilities in IoT security, could have a high severity score.
[0114] The score for the number of connected nodes in the vulnerability association graph is assigned based on the connectivity of non-compliant items within the graph. Specifically, the more connected nodes a non-compliant item has, the higher its score.
[0115] The persistence score in the status change label is assigned based on the number of times the non-compliance item has persisted in historical inspections. The more times the non-compliance item has persisted, the higher its score.
[0116] These scoring dimensions can be used individually or in combination. When used in combination, the final risk score can be calculated using methods such as weighted summation.
[0117] As a specific implementation method, the risk assessment unit 503 can be implemented as an independent service based on a microservice architecture. The risk assessment unit 503 can interact with the vulnerability association analysis unit 501, the difference comparison unit 502 and the report output module 700 through a RESTful API.
[0118] After the detection execution module 400 completes the detection of the configuration information and generates the detection results, the vulnerability association analysis unit 501 in the result processing module 500 will generate a vulnerability association map, and the difference comparison unit 502 will generate state change annotations. Subsequently, the risk assessment unit 503 will obtain the vulnerability association map and annotation data from the vulnerability association analysis unit 501 and the difference comparison unit 502.
[0119] For a non-compliant item such as "Prohibiting General Default Passwords," the base score for its severity can be set at 10 points out of a maximum score of 20. If this non-compliant item is associated with five other non-compliant items in the vulnerability association graph, including "Communication Security" and "Sensitive Security Parameter Storage," its connected node count score can be calculated as 5 points. If this non-compliant item has been marked as "Persistent Item" in the past two detections, indicating a persistence round count of 3, its persistence round count score can be calculated as 3 points.
[0120] Risk assessment unit 503 can adopt a weighted summation model, which is set as follows:
[0121] Total risk score = (Base score for clause severity * 0.5) + (Score for number of connected nodes * 0.3) + (Score for number of rounds of persistence * 0.2)
[0122] According to this weighted summation model, the total risk score for the non-compliance item "prohibiting general default passwords" is (10*0.5)+(5*0.3)+(3*0.2)=5+1.5+0.6=7.1 points.
[0123] Furthermore, in the preset risk level assessment criteria, the total risk score ranges from 0 to 15 points, with scores of 0 to 5 indicating low risk, 5.1 to 9 indicating medium risk, 9.1 to 12 indicating high risk, and 12.1 to 15 indicating severe risk. Based on the calculated score of 7.1, this non-compliance item can be assessed as medium risk.
[0124] Finally, the risk assessment unit 503 generates a structured risk assessment report, which includes a detailed risk score, risk level, and data on the scoring dimensions that lead to each non-compliance item, and outputs it to the report output module 700 to generate the final compliance inspection report.
[0125] The IoT device network security compliance testing system 80 provided in this specific embodiment combines the node connectivity of the vulnerability association graph and the duration of historical state change annotations. It not only considers the severity of a single vulnerability but also delves deeper into the mutual influence and long-term risks between vulnerabilities. It can perform refined and intelligent risk level assessment of non-compliant items in the IoT device network security compliance testing results, clearly assessing which non-compliant items have the highest potential harm and the most urgent remediation needs. This optimizes resource allocation during the maintenance of the tested IoT device 100, improves the efficiency and pertinence of security remediation, and provides a more comprehensive and dynamic risk view for the security compliance of the tested IoT device 100, significantly improving its overall security protection level.
[0126] See Figure 2 In a specific embodiment of this application, the result processing module 500 further includes a management report unit 504, which is connected to the risk assessment unit 503 and the report output module 700. The structured dataset includes a compliance summary report.
[0127] The management reporting unit 504 is used to summarize and review risk assessment reports, generate and output compliance summary reports using the risk assessment reports.
[0128] Specifically, the management reporting unit 504 can be an independent software module running on the server of the results processing module 500; or it can be an independent microservice that interacts with the risk assessment unit 503 and the report output module 700 through an application programming interface (API). This ensures that the management reporting unit 504 can receive detailed risk data from the risk assessment unit 503 and transmit the processed compliance summary report to the report output module 700 for final formatting and output.
[0129] The steps of summarizing and reviewing risk assessment reports aim to aggregate, filter, classify, and verify the detailed risk assessment reports generated by risk assessment unit 503. This extracts key information and ensures the accuracy and consistency of the data, laying the foundation for generating a high-level compliance summary report. For example, data aggregation algorithms can be used to statistically analyze the risk levels of multiple non-compliance items, calculating the average, maximum, and minimum risk levels for each non-compliance item. Alternatively, pre-defined business rules or expert systems can be used to perform logical verification and consistency checks on the data in the risk assessment reports.
[0130] The compliance summary report can be a specific form of a structured dataset. The compliance summary report can transform the risk assessment information processed and summarized by the management reporting unit 504 into a compliance summary report that is relevant to management and has decision-making guidance. It is presented in a high-level and easy-to-understand way, thereby reflecting the overall compliance status and management recommendations of the tested IoT device 100.
[0131] Specifically, compliance summary reports can be stored in structured data formats such as JSON and XML, or as specific table structures in a database, or generated in document formats such as PDF and HTML. For example, the process of generating a compliance summary report can utilize template engine technology to populate predefined compliance summary report templates with processed data, automatically generating the report. Alternatively, data visualization tools can be used to convert data into charts, graphs, and other formats, which can then be integrated into the compliance summary report.
[0132] The compliance summary report may include at least one of the following: a statistical chart of compliance rate for clause EN 303645, a list of non-compliance items ranked by risk level, operational guidelines for rectifying high-risk non-compliance items, and a rectification timeline.
[0133] The EN 303645 compliance rate chart visually displays the degree of compliance of the tested IoT device 100 with each clause of the EN 303645 standard, i.e., the EN 303645 compliance rate. The EN 303645 compliance rate can be presented as a percentage or in rank format, and the EN 303645 compliance rate chart can use various chart formats such as bar charts, pie charts, and radar charts.
[0134] The risk-level ranking list of non-compliance items lists all non-compliance items and arranges them in descending order of their risk level, thus highlighting the most critical non-compliance issues that require priority attention and resolution. The risk-level ranking list of non-compliance items can be presented in tabular form.
[0135] The high-risk non-compliance item rectification operation guide provides specific and actionable remediation suggestions and steps for identified high-risk non-compliance items, helping technical personnel effectively resolve non-compliance issues. This high-risk non-compliance item rectification operation guide can be a knowledge database or an expert system.
[0136] A rectification timeline is a plan that sets an expected completion schedule for the rectification of non-compliance items, which helps in the management and progress tracking of rectification projects. A rectification timeline can be a Gantt chart or a timeline.
[0137] As a specific implementation, the result processing module 500 in the IoT device network security compliance testing system 80 can be configured with a management reporting unit 504. This management reporting unit 504 can be an independent microservice deployed on a cloud server and communicate with the risk assessment unit 503 and the report output module 700 through a RESTful API interface.
[0138] Once the risk assessment unit 503 completes the risk level assessment of the IoT devices and generates a risk assessment report containing all non-compliance items, their risk levels, and scoring dimensions, the report will be sent to the management reporting unit 504 in JSON format via an API interface. Upon receiving the JSON-formatted risk assessment report, the management reporting unit 504 will initiate a data processing flow.
[0139] First, the management reporting unit 504 performs data validation to ensure the completeness and correct format of the report content. Next, the management reporting unit 504 aggregates the data, which can calculate the number and percentage of non-compliant devices under the "Prohibition of General Default Passwords" clause of the EN 303645 standard, as well as the average risk score for the "Software Update Management" clause.
[0140] After the summary review is completed, the management reporting unit 504 calls a preset report generation template. This template can be a Python-based Jinja2 template, which defines the structure and content layout of the compliance summary report. The management reporting unit 504 populates the processed statistical data and risk information into the Jinja2 template, automatically generating a bar chart as a compliance rate chart for EN 303645 clauses. This bar chart displays the compliance rate of each clause, such as the compliance rate of the "Prohibition of General Default Passwords" clause being 85% and the compliance rate of the "Communication Security" clause being 92%.
[0141] The management reporting unit 504 also generates a table listing all non-compliance items and sorting them in descending order of risk level. This table serves as a list of non-compliance items ordered by risk level. For example, in this table, the first item could be "Default administrator password not changed (high risk)", followed by "Firmware update mechanism has a signature bypass vulnerability (high risk)".
[0142] The management reporting unit 504 also generates rectification instructions for high-risk non-compliance items. For example, for the high-risk item "Default administrator password not changed," the management reporting unit 504 can automatically match and generate corresponding instructions from the knowledge database. For instance, it might generate: "It is recommended to immediately change the default administrator password through the device management interface and enable a complex password policy. Steps: 1. Log in to the device web interface; 2. Go to 'Security Settings'; 3. Change the 'Administrator Password'; 4. Save the settings."
[0143] Management Report Unit 504 also generates a timeline as a remediation timeline, thereby setting a suggested completion time for the aforementioned high-risk items. For example, the timeline could be marked with "Default administrator password change: Recommended to be completed within 24 hours".
[0144] Finally, the management reporting unit 504 sends the generated compliance summary report in PDF or HTML format to the report output module 700 via the API interface. The report output module 700 then integrates the report into the final compliance inspection report and outputs it.
[0145] In the IoT device network security compliance testing system 80 provided in this specific embodiment, by introducing a management report unit 504, the risk assessment report can be summarized and reviewed in depth. The scattered and technical risk data can be refined into a compliance summary report for management. This not only improves the readability and practicality of the test results, but also elevates the security compliance assessment of IoT devices from the simple problem discovery stage to the level of a comprehensive management platform that assists in decision-making and guides rectification. This greatly enhances the efficiency and effectiveness of IoT device security governance.
[0146] Specifically, the EN 303645 compliance rate chart provides managers with a visual view of the overall security posture of the equipment, enabling them to quickly identify compliance weaknesses and optimize resource allocation. The risk-level ranking of non-compliance items clarifies the priority of remediation work, ensuring that high-risk issues are addressed promptly and effectively. The remediation guidelines for high-risk non-compliance items transform complex security issues into actionable steps, significantly reducing the difficulty and time cost for technical personnel. The provision of a remediation timeline allows security compliance work to be integrated into a standardized project management process, ensuring the orderly progress and timely completion of remediation tasks.
[0147] like Figure 1 , Figure 2 As shown in a specific embodiment of this application, the IoT device network security compliance testing system 80 further includes a historical testing database 600, which is connected to a difference comparison unit 502 and a report output module 700. The historical testing database 600 is used to store compliance testing reports output by the report output module 700.
[0148] The historical testing database 600 is indexed by the firmware information of the tested IoT device 100 and the timestamp of the compliance testing report.
[0149] It should be noted that the difference comparison unit 502 maintains a database of historical test results for the tested IoT device 100, storing the test conclusions of each test item using the device's unique identifier and test timestamp as indexes. After each new test is completed, the difference comparison unit 502 can automatically extract the previous test record for item-by-item comparison, marking status change information, providing quantitative evidence for manufacturers to track rectification progress and demonstrate continuous safety improvements to regulatory agencies.
[0150] The Historical Testing Database 600 is a storage system specifically designed for persistent storage of historical testing data and reports. It can be implemented using relational databases such as MySQL and PostgreSQL or non-relational databases such as MongoDB and Cassandra. It aims to provide long-term, structured storage space for compliance testing reports, ensuring the integrity and traceability of historical data.
[0151] The historical detection database 600, the difference comparison unit 502, and the report output module 700 can exchange data via API calls, Kafka or RabbitMQ message queue mechanisms, or direct data access through shared storage paths or database connection pools. This ensures that the difference comparison unit 502 can retrieve historical compliance detection reports from the historical detection database 600 for comparison, while the report output module 700 can write newly generated compliance detection reports into the historical detection database 600 for archiving.
[0152] The historical testing database 600 is used to store compliance testing reports output by the report output module 700. Specifically, reports can be stored in a specific table within the historical testing database 600 in the form of structured data such as JSON or XML, or unstructured documents such as PDF or HTML. Alternatively, compliance testing reports can be stored as files, with their path and metadata stored in the historical testing database 600. Through different storage methods, compliance testing reports generated for each test can be persistently saved.
[0153] Furthermore, the historical testing database 600 can be indexed by the firmware information and compliance testing report timestamps of the IoT device 100 under test. This means that composite or independent indexes can be created for the firmware information and timestamp fields in the historical testing database 600, for example, by defining a PRIMARY KEY or UNIQUE INDEX in a relational database.
[0154] Specifically, firmware information can include unique identifiers such as device model and version number; the timestamp records the specific date and time the report was generated or stored. This indexing mechanism aims to improve the efficiency and accuracy of retrieving historical compliance testing reports, supporting the rapid location of specific historical testing records for specific devices.
[0155] As a specific implementation, the historical inspection database 600 can be constructed using a PostgreSQL relational database. After the report output module 700 generates a compliance inspection report, it can insert the structured content of the report into the `compliance_reports` table of the historical inspection database 600 via a JDBC (Java Database Connectivity) interface. This table can have pre-created composite indexes. For example, indexes can be created on the `firmware_info` and `timestamp` fields to accelerate queries. The structured content can include metadata such as the compliance inspection report body in JSON format, firmware information, and timestamps.
[0156] When the difference comparison unit 502 needs to obtain historical compliance test reports of the IoT device under test 100, it can send an SQL query request to the historical test database 600, such as `SELECT * FROM compliance_reportsWHERE firmware_info = 'IoT_Device_A_v1.2' ORDER BY timestamp DESC`. At this time, the historical test database 600 can use the preset index to quickly locate and return all historical compliance test reports of the IoT device under test 100 for comparison and analysis by the difference comparison unit 502.
[0157] In the IoT device network security compliance testing system 80 provided in this specific embodiment, the compliance testing report generated by the report output module 700 can be persistently stored and traceable, enabling the difference comparison unit 502 to quickly and accurately obtain the historical compliance testing reports of a specific IoT device 100 at different time points. This solves the problem of the lack of systematic storage and efficient retrieval mechanism for historical testing data in traditional solutions. It not only improves the efficiency of compliance assessment but also enhances the objectivity and repeatability of historical difference comparison, greatly improving the effective traceability and management capability of the entire life cycle compliance evolution process of the IoT device 100 under test, and providing solid data support and management foundation for the network security compliance of IoT devices.
[0158] See Figure 2 In a specific embodiment of this application, the detection execution module 400 may further include a compliance rule base unit 402, which is connected to the clause mapping unit 401.
[0159] The compliance rule base unit 402 is used to store clause requirements, which include detection and judgment rules, compliance benchmarks, and historical version rules.
[0160] The Compliance Rule Base Unit 402 is a logical or physical storage module specifically designed for storing and managing the rules and data required for compliance testing. Specifically, the Compliance Rule Base Unit 402 can be an independent database system, such as a relational database like MySQL or PostgreSQL, or a non-relational database like MongoDB, capable of structured storage of various rule data. Alternatively, the Compliance Rule Base Unit 402 can be implemented through a set of configuration files in formats such as XML, JSON, and YAML within a file system, or through in-memory data structures, and can be accessed and managed through a specific application programming interface (API).
[0161] The clause requirements can refer to data that the IoT device cybersecurity compliance testing system 80 can understand and execute, derived from the specific provisions and details of the EN 303645 standard regarding IoT device cybersecurity compliance. For example, these clause requirements can be represented as structured data records, each containing fields such as a unique identifier for a standard clause, a detailed description, testing methods, and judgment criteria. Alternatively, these clause requirements can adopt an object-oriented model, abstracting each standard clause into an object that can contain its attributes and behaviors. The clause requirements can serve as the basis for compliance testing, guiding the testing execution module 400 in making judgments.
[0162] The detection and judgment rules transform the abstract clauses of the EN 303645 standard into executable logical judgment conditions and algorithms for the IoT device cybersecurity compliance testing system 80. Specifically, these rules can be predefined scripts or code snippets, such as Python scripts or Java methods, used to parse the configuration information of the IoT device under test 100 and perform logical judgments according to the clause requirements. Alternatively, the detection and judgment rules can be rule sets based on rule engines such as Drools or OpenL, allowing judgment conditions and actions to be defined using declarative languages. These rules transform manual judgment into machine judgment, achieving standardization and automation of the testing process and improving the consistency of IoT device cybersecurity compliance testing.
[0163] Compliance benchmarks can refer to quantitative indicators or thresholds used during compliance testing to measure whether the configuration information of the tested IoT device 100 meets standard requirements. Compliance benchmarks can be stored in the compliance rule base unit 402, existing in the form of numerical values, strings, or Boolean values. For example, compliance benchmarks may include minimum password length, allowed encryption algorithm types, port open status, etc. Alternatively, compliance benchmarks can be dynamically calculated parameters, adjusted based on the configuration information, risk level, and other contextual information of the tested IoT device 100. Compliance benchmarks provide clear quantitative standards for IoT device network security compliance testing, further avoiding subjective human judgment and thus improving the objectivity and accuracy of IoT device network security compliance testing.
[0164] Historical version rules refer to the detection rules and benchmark values corresponding to different versions or revisions of the EN 303645 standard. Historical version rules can be marked and managed using the EN 303645 standard version number or timestamp. When detecting devices with specific firmware versions or production batches, the IoT device network security compliance detection system 80 can automatically load the corresponding historical rules. For example, the rule base can contain multiple rule sets, each corresponding to a standard version, and which rule set to activate can be selected through configuration. Historical version rules can address compatibility issues brought about by standard updates and support targeted detection of devices with different time periods or version requirements, thereby ensuring the continuous effectiveness of IoT device network security compliance detection.
[0165] As a specific implementation, the compliance rule base unit 402 can be a PostgreSQL-based relational database containing multiple tables. The compliance rule base unit 402 can have a `rules_definitions` table to store detection and judgment rules. Each record contains a rule ID, the corresponding standard clause ID, the rule name, the path or content of the detection script, and the severity of the rule clause. For example, the rule ID could be "R001", the standard clause ID could be "EN303645-5.1", the rule name could be "prohibit general default passwords", the path of the detection script could be a Python script or an SQL query, and the content of the detection script could be "check if there are items in the weak password list in the configuration parameters".
[0166] Optionally, the compliance rule base unit 402 may have a `baseline_values` table to store compliance baseline values, where each record contains a baseline ID, an associated rule ID, a parameter name, a specific value, and the applicable device type of the IoT device 100 under test.
[0167] In addition, a `rule_versions` table can be used to store historical version rules, where each record contains a version ID, associated rule ID, effective date, and status. When the clause mapping unit 401 receives the configuration information of the IoT device 100 under test provided by the data acquisition module 300, i.e., firmware version "FW_V1.0" and device type "IoT_Camera", the clause mapping unit 401 first queries the `rule_versions` table and determines the rule version that should be activated as "V1.0" according to the standard version corresponding to "FW_V1.0". Subsequently, the clause mapping unit 401 obtains the detection judgment rule related to the EN 303645 standard clause from the `rules_definitions` table, i.e., R001 "prohibit general default password", and obtains the compliance baseline value related to R001 and "IoT_Camera" from the `baseline_values` table, such as "min_password_length" being 8. The clause mapping unit 401 then executes a detection script, which compares the password length extracted from the configuration information with the baseline value 8 to generate a detection result.
[0168] In the IoT device network security compliance testing system 80 provided in this specific embodiment, by setting up a compliance rule base unit 402, the clause mapping unit 401 can directly obtain clause requirements dynamically from the compliance rule base unit 402, enabling the entire testing execution module 400 to perform compliance testing more efficiently and accurately. Moreover, the compliance rule base unit 402 is kept updated, enabling the IoT device network security compliance testing to effectively cope with standard updates and the differentiated requirements of different versions of standards on the judgment benchmark value, thereby improving the adaptability and scalability of the entire IoT device network security compliance testing system 80.
[0169] See Figure 2 In one specific embodiment of this application, the detection and judgment rules include provisions prohibiting general default passwords, vulnerability disclosure mechanisms, software update management, sensitive security parameter storage, communication security, attack surface minimization, software integrity, personal data protection, system availability resilience, and telemetry data security.
[0170] The prohibition of generic default passwords aims to detect whether the tested IoT device 100 is using an easily guessed or publicly known default password. Default passwords are usually preset at the factory and can become a serious security risk if not changed.
[0171] Specifically, the IoT device network security compliance testing system 80 can maintain a list of hash values or plaintext containing common default passwords and weak passwords. It can detect passwords by comparing them with the password hash values in the configuration information of the IoT device under test 100 or by attempting to authenticate using these passwords. For example, the IoT device network security compliance testing system 80 can also determine whether the password used by the IoT device under test 100 complies with security standards by analyzing the password complexity requirements in its configuration. Password complexity requirements may include whether the inclusion of uppercase and lowercase letters, numbers, and special characters is mandatory, as well as minimum password length.
[0172] The vulnerability disclosure mechanism clause is designed to ensure that manufacturers or suppliers of the IoT devices under test have clear and accessible vulnerability reporting and response processes so that security researchers or users can securely report discovered vulnerabilities to manufacturers or suppliers.
[0173] Specifically, the IoT device cybersecurity compliance testing system 80 can check whether the firmware information or related documents of the IoT device 100 under test contain links or descriptions pointing to official vulnerability reporting channels such as security email addresses or vulnerability reporting platform URLs (Uniform Resource Locators). Furthermore, the IoT device cybersecurity compliance testing system 80 can also simulate user behavior, attempting to access the official website of the IoT device 100 manufacturer under test, searching for its publicly available vulnerability disclosure policies or security contact information, and assessing their completeness and operability.
[0174] The software update management terms are used to ensure that the IoT device under test 100 has a secure software update mechanism, and to ensure that the IoT device under test 100 can receive, verify and install firmware updates in a timely manner to fix known vulnerabilities and improve security.
[0175] Specifically, the IoT device network security compliance testing system 80 can analyze the configuration parameters of the IoT device 100 under test to check whether it supports OTA (Over-The-Air) updates, update package signature verification mechanisms, rollback mechanisms, etc. Furthermore, the IoT device network security compliance testing system 80 can also query the current firmware version of the IoT device 100 under test and compare it with the latest security firmware version released by its manufacturer. It can also check whether the IoT device 100 under test is configured with automatic update or update notification functions.
[0176] The Sensitive Security Parameter Storage Clause is used to ensure that sensitive security parameters such as encryption keys, certificates, and user credentials stored internally by the IoT device under test 100 are adequately protected to prevent unauthorized access or disclosure.
[0177] Specifically, the IoT device network security compliance testing system 80 can analyze the firmware image of the IoT device 100 under test, identify sensitive data storage areas, and check whether it uses technologies such as encrypted storage, HSM (Hardware Security Module) protection, or secure boot. Furthermore, the IoT device network security compliance testing system 80 can also check the policies regarding key management and certificate chain verification in the configuration information of the IoT device 100 under test, such as whether hard-coded keys are prohibited or whether the use of secure storage media is mandatory.
[0178] The communication security clause is used to ensure that the IoT device under test 100 uses encryption and authentication mechanisms when communicating with external systems, which can prevent communication data from being eavesdropped, tampered with or forged.
[0179] Specifically, the IoT device network security compliance testing system 80 can analyze network interface data to detect whether the tested IoT device 100 uses encryption protocols such as TLS / SSL and DTLS for communication by default, and verify the validity of its certificate chain. Furthermore, the IoT device network security compliance testing system 80 can check the communication protocols, firewall rules, etc., in the configuration information of the tested IoT device 100, and can also strictly control inbound / outbound traffic.
[0180] The attack surface minimization clause is used to ensure that the tested IoT device only opens the necessary services and ports and disables unnecessary functions, thereby reducing potential attack entry points.
[0181] Specifically, the IoT device network security compliance testing system 80 can scan the network interfaces of the IoT device 100 under test, identify all open ports and services, and compare them with a preset security baseline, thereby identifying unnecessary open items. Optionally, the IoT device network security compliance testing system 80 can also analyze the configuration information of the IoT device 100 under test to check whether debug interfaces, unused protocol stacks, or default-enabled test functions are disabled.
[0182] Software integrity clauses can be used to ensure that the firmware, applications, and other software running on the tested IoT device 100 are not tampered with throughout their lifecycle and remain in their original, trustworthy state. The IoT device cybersecurity compliance testing system 80 can also check the firmware's digital signature or hash value and compare it with the official signature or hash value provided by the manufacturer to verify the firmware's integrity.
[0183] Furthermore, the IoT device network security compliance testing system 80 can also analyze the security mechanisms during the startup process of the IoT device 100 under test, such as determining whether it supports Secure Boot, to ensure that only signed code can be executed.
[0184] The Personal Data Protection Clause is used to ensure that the IoT device under test 100 follows privacy protection principles, such as data minimization, anonymization, and user consent, when collecting, processing, storing, and transmitting personal data.
[0185] Optionally, the IoT device network security compliance testing system 80 can analyze the data collection strategy in the configuration information of the IoT device 100 under test, such as whether the user is clearly informed of the purpose and scope of data collection, and can also provide the user with the option to opt out or delete data.
[0186] Optionally, the IoT device network security compliance testing system 80 can also check whether the telemetry data transmitted by the device contains personally identifiable information and assess the effectiveness of its anonymization or pseudonymization processing.
[0187] The system availability resilience clause is used to ensure that the IoT device under test 100 has a certain degree of resistance to attacks and recovery capabilities, so that it can maintain basic functions or quickly resume normal operation even when attacked.
[0188] Optionally, the IoT device network security compliance testing system 80 can check the configuration information of the IoT device 100 under test regarding resource limits, rate limits, and anomaly handling mechanisms to prevent denial-of-service (DoS) attacks.
[0189] Optionally, the IoT device network security compliance testing system 80 can also evaluate the fault recovery mechanism of the IoT device 100 under test, such as whether it supports functions such as watchdog timer, automatic restart, configuration backup and recovery.
[0190] The telemetry data security clause is used to ensure that the confidentiality, integrity and availability of telemetry data are guaranteed when the IoT device under test 100 collects and transmits telemetry data such as device status and usage.
[0191] Optionally, the IoT device network security compliance testing system 80 can analyze the protocol and encryption method of telemetry data transmission to ensure that the telemetry data is encrypted and protected during transmission and to verify the identity of the recipient.
[0192] Optionally, the IoT device network security compliance testing system 80 can also check the granularity, frequency and storage strategy of telemetry data collection in the configuration information of the IoT device under test 100 to ensure that the telemetry data collection complies with the principle of minimization and to perform access control on the stored telemetry data.
[0193] As a specific implementation method, the IoT device network security compliance detection system 80 can store the specific implementation logic of the above ten types of detection and judgment rules in the compliance rule base unit 402 of the detection execution module 400.
[0194] For example, for a clause prohibiting generic default passwords, the compliance rule base unit 402 may contain a predefined list of weak password hashes and a password complexity evaluation algorithm. When the data acquisition module 300 obtains the configuration information of the IoT device under test 100, which includes the management password hash of the IoT device under test 100, the clause mapping unit 401 can identify that a clause prohibiting generic default passwords needs to be applied for detection.
[0195] At this time, the clause mapping unit 401 can retrieve the corresponding weak password hash value list and password complexity evaluation algorithm from the compliance rule base unit 402, and automatically match the detection strategy according to the specific configuration of the IoT device 100 under test, such as whether it supports SSH login and how its authentication is configured.
[0196] The detection execution module 400 then uses these rules and strategies to compare the obtained password hash value with the weak password list and evaluate the password complexity. If the password hash value matches any hash value in the weak password list, or if the password complexity does not meet the preset security baselines such as a length of less than 8 characters or the absence of numbers and special characters, it is determined to be non-compliant.
[0197] For example, regarding software update management terms, the compliance rule base unit 402 can store specifications for the secure firmware update process, including the algorithm for update package signature verification, the firmware version number verification logic, and checkpoints for the rollback mechanism. When the detection execution module 400 needs to evaluate the software update capability of the IoT device under test 100, the terms mapping unit 401 can obtain the corresponding signature verification rules and version comparison logic from the compliance rule base unit 402 based on the firmware information of the IoT device under test 100.
[0198] The detection execution module 400 can attempt to simulate the update process or analyze parameters in the configuration information of the IoT device under test 100, such as the update server address, update frequency, and signature certificate path, and verify whether they meet security requirements. For example, the detection system can check whether the IoT device under test 100 is configured with mandatory firmware signature verification and whether its firmware version is the latest secure version, thereby ensuring that the IoT device under test 100 can securely and timely receive and install updates.
[0199] In the IoT device network security compliance testing system 80 provided in this specific embodiment, by explicitly prohibiting ten categories of clauses such as general default passwords, vulnerability disclosure mechanisms, and software update management, the IoT device network security compliance testing system 80 can accurately invoke corresponding detection logic and strategies based on the firmware information, configuration parameters, and network interface data of the tested IoT device 100. This allows for more targeted and in-depth compliance comparisons, significantly improving the comprehensiveness and accuracy of the detection and ensuring effective coverage of the multi-dimensional security attributes of IoT devices. High-quality detection results also provide a solid foundation for the subsequent results processing module 500 to perform historical difference comparisons, cross-clause correlation analysis, and risk level assessments, thereby improving the objectivity and accuracy of the overall compliance assessment.
[0200] This application also provides a detection device 90 in its specific embodiments; please refer to [link to details]. Figure 4 , Figure 4 This is a schematic block diagram of the structure of an embodiment of the testing equipment of this application. It should be noted that if substantially the same result is obtained, this embodiment is not necessarily identical. Figure 4 The structure shown is for illustrative purposes only. The testing device 90 includes an IoT device cybersecurity compliance testing system 80 as described in any of the specific embodiments above.
[0201] Testing equipment 90 can refer to a physical device with specific functions used for testing, analyzing, evaluating, or monitoring a target object. It typically integrates necessary hardware components, software logic, and a user interface to achieve its preset testing tasks. This testing equipment 90 can be a standalone, portable hardware unit, such as a handheld tester or a test workstation integrated into a dedicated chassis. Such devices usually have their own power supply, processor, storage, and input / output interfaces, enabling them to independently complete testing tasks.
[0202] Alternatively, the testing device 90 can also be an embedded system, with its hardware and software tightly integrated into another larger device or system as a functional module. For example, the testing device 90 can be a module integrated into a production line test fixture, or a dedicated testing node deployed at the network edge.
[0203] The IoT device cybersecurity compliance testing system 80 can be a set of logical functions used to automatically assess the cybersecurity compliance of IoT devices in accordance with the provisions of the EN303645 standard. The IoT device cybersecurity compliance testing system 80 may include core functional modules such as a data acquisition module 300, a testing execution module 400, a result processing module 500, and a report output module 700.
[0204] In the testing equipment 90, the IoT device cybersecurity compliance testing system 80 can exist in the form of software program, firmware, or application-specific integrated circuit (ASIC), running on the processor of the testing equipment 90, and interacting with the IoT device under test 100 through the physical interface of the testing equipment 90. The functional logic of the IoT device cybersecurity compliance testing system 80 can be implemented through programming and can be updated and configured as needed.
[0205] In one specific implementation, the testing device 90 can be a dedicated embedded hardware platform. This platform can be equipped with a high-performance microprocessor, such as an ARM-based processor, and sufficient memory and storage space to run the IoT device cybersecurity compliance testing system 80. The housing of the testing device 90 can be made of robust and durable engineering plastics or metal to adapt to different field environments.
[0206] In terms of interfaces, the testing device 90 can integrate multiple external test interfaces 200, such as multiple RJ45 Ethernet ports, for connecting to the network interface of the IoT device under test 100, supporting PoE power supply. It may also include multiple USB ports for connecting to the debugging interface of the IoT device under test 100 or for firmware transfer. It may also include one or more serial communication ports for low-level communication with specific IoT devices. It may also include a Wi-Fi / Bluetooth module for wireless connection to the IoT device under test 100 or as its own management interface. It may also include an HDMI or DisplayPort interface for connecting to an external display to show testing progress and results. Furthermore, it may include a touchscreen display as a human-machine interface, facilitating user configuration of testing tasks, viewing real-time status, and browsing testing reports.
[0207] The IoT device network security compliance testing system 80 can run as an application on a pre-installed operating system, or be burned into the non-volatile memory of the testing device 90 as firmware. The data acquisition module 300 of the IoT device network security compliance testing system 80 can call the underlying network driver, USB driver, and serial port driver of the testing device 90 to acquire the configuration information of the IoT device under test 100. The testing execution module 400 can utilize the powerful processing capabilities of the testing device 90 to quickly execute the testing rules of the EN 303645 standard clauses. The result processing module 500 and the report output module 700 can utilize the storage and display functions of the testing device 90 to complete data processing and report generation and display.
[0208] Optionally, the testing device 90 may also have a built-in rechargeable battery to support portable operation in the absence of an external power source.
[0209] In this specific embodiment, the testing device 90, as an integrated hardware platform, provides a stable operating environment and rich physical interfaces for complex software testing logic. This enables the data acquisition module 300 to interact directly and reliably with the IoT device under test 100, ensuring the accuracy and completeness of configuration information acquisition. This integrated design significantly improves the portability and standardization of the compliance testing process, allowing the testing system to be quickly deployed as an independent, plug-and-play unit in production lines, testing laboratories, or on-site without complex external configurations or dependencies. This greatly improves the efficiency and flexibility of IoT device compliance assessment. Furthermore, the deep integration of hardware and software enhances the stability and reliability of the testing system, reduces testing errors caused by environmental factors or external device compatibility issues, and ensures the objectivity and repeatability of the test results.
[0210] This application also provides a method for detecting network security compliance of IoT devices, implemented using the IoT device network security compliance detection system described in any of the above embodiments. Please refer to... Figure 3 , Figure 3 This is a flowchart illustrating an embodiment of the IoT device network security compliance testing method of this application. It should be noted that if substantially the same result is obtained, this embodiment is not necessarily identical. Figure 3 The sequence of processes shown is limited. This method for testing the cybersecurity compliance of IoT devices may include:
[0211] S100: Obtain the configuration information of the IoT device under test through an external test interface.
[0212] The configuration information includes firmware information, configuration parameters, and network interface data.
[0213] The execution subject of this specific embodiment can be a computing service device with data processing, network communication and program execution functions, or an electronic device capable of realizing the above functions, such as the detection device of the above specific embodiment.
[0214] S200: Based on the clauses of EN 303645 standard, the configuration information is checked item by item, and the test results are generated.
[0215] By comparing the collected configuration information of the IoT device under test with the requirements of the EN 303645 standard, and independently evaluating each specific clause of the standard, it is possible to determine whether the IoT device under test complies with the requirements of each clause of the standard.
[0216] S300: Perform historical difference comparison, cross-clause correlation analysis, and risk level assessment on the test results to generate a structured dataset.
[0217] By deeply processing and analyzing the original test results, including historical difference comparisons that can track changes in equipment security status, cross-clause correlation analysis that can reveal potential deep security risks, and risk level assessment that quantifies the severity of non-compliance items, a more insightful compliance assessment can be provided.
[0218] S400: Integrates structured datasets into a compliance inspection report in a preset format and outputs it.
[0219] By integrating structured datasets and using preset formats, the reports are standardized and readable, enabling all analysis results to be presented to users or regulatory agencies in a clear and standardized manner.
[0220] In this specific implementation, firmware information, configuration parameters, and network interface data of the IoT device under test are obtained through an external testing interface, ensuring the comprehensiveness and accuracy of the test source data and providing a reliable data foundation for subsequent compliance analysis. Configuration information is tested item by item based on the clauses of the EN 303645 standard. By transforming the standard requirements into executable testing logic, the biases in the understanding of the clauses by different testers are eliminated, ensuring the consistency and objectivity of the test results. Historical difference comparison, cross-clause correlation analysis, and risk level assessment of the test results are performed. This step, through in-depth processing of the original test results, transforms discrete test items into a structured dataset. This not only identifies individual vulnerabilities but also uncovers deeper security risks through correlation analysis and assesses the persistence of risks in conjunction with historical data, thereby improving the depth and readability of the test report. A unified report output standard ensures that the output results directly meet the format requirements of regulatory agencies and third-party certification bodies, achieving standardization and normalization of compliance assessment work.
[0221] The following is an example:
[0222] There is a need to perform network security compliance testing on a smart camera. First, the data acquisition module connects to the smart camera's Ethernet interface and uses the SSH protocol to obtain its configuration file ` / etc / config / network`, user account information ` / etc / passwd` and ` / etc / shadow`, and obtains the firmware version information by reading ` / proc / version`. Then, this configuration information is transmitted to the testing execution module.
[0223] The clause mapping unit in the detection execution module retrieves the corresponding detection and judgment rules from the compliance rule base unit according to clauses of the EN 303645 standard, such as the "Prohibition of General Default Password Clause" and the "Communication Security Clause". For the "Prohibition of General Default Password Clause", the IoT device network security compliance detection system checks whether weak password combinations such as "admin:password" exist in the ` / etc / passwd` file. For the "Communication Security Clause", the IoT device network security compliance detection system checks whether unencrypted Telnet or HTTP services are configured in ` / etc / config / network`. After the detection is completed, the detection execution module generates preliminary detection results, such as the discovery of default weak password accounts and open Telnet services. These detection results are then sent by the detection execution module to the result processing module.
[0224] The difference comparison unit in the results processing module retrieves the previous test report of the smart camera from the historical test database and compares it with the current results. It finds that "default weak password" is a newly added non-compliant item, while "open Telnet service" is a persistent item.
[0225] The vulnerability correlation analysis unit can identify attack chain dependencies between default weak passwords and open Telnet services based on preset attack chain dependency relationships. This means that attackers can log in to the Telnet service using default weak passwords, thereby controlling the device, and generating a corresponding vulnerability correlation graph. The "default weak password" is the starting point of the attack chain and connects multiple potential risk points.
[0226] The risk assessment unit can use a weighted scoring model to classify "default weak password" as "high risk" based on the connectivity in the vulnerability association graph and the characteristic of "default weak password" as a new non-compliant item.
[0227] The management reporting unit can summarize these test results to generate a compliance summary report, which includes statistical charts of the compliance rate for EN303645 clauses, a list of high-risk non-compliance items, and remedial action guidelines and suggested remediation timelines for high-risk items. The remedial action guidelines include immediately changing the default password and disabling the Telnet service.
[0228] Finally, the report output module integrates this structured dataset, including the compliance summary report, into a compliance inspection report in a preset format and outputs it. At the same time, it stores the compliance inspection report in the historical inspection database for comparison of differences in subsequent inspections.
[0229] In this application, the terms "embodiment" and "implementation" mean that a specific feature or characteristic described in connection with an embodiment can be included in at least one embodiment of this application. The appearance of these phrases in various places in the specification does not necessarily refer to the same embodiment, nor are they independent or alternative embodiments mutually exclusive with other embodiments. Those skilled in the art will understand, explicitly and implicitly, that the embodiments described in this application can be combined with other embodiments. Furthermore, it should be understood that the features, elements, or characteristics described in the various embodiments of this application can be arbitrarily combined to form another embodiment that does not depart from the spirit and scope of the technical solution of this application, provided there is no contradiction between them.
[0230] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit it. Although this application has been described in detail with reference to the above preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions to the technical solutions of this application should not depart from the spirit and scope of the technical solutions of this application.
Claims
1. A network security compliance testing system for Internet of Things (IoT) devices, characterized in that, It includes a data acquisition module (300), a detection execution module (400), a result processing module (500), and a report output module (700) connected in sequence. The data acquisition module (300) is used to acquire the configuration information of the IoT device under test (100) through the external test interface (200) and transmit the configuration information to the detection execution module (400). The configuration information includes firmware information, configuration parameters and network interface data. The detection execution module (400) is used to perform item-by-item detection on the configuration information based on the clauses of EN 303645 standard and generate detection results; The result processing module (500) is used to perform historical difference comparison, cross-clause correlation analysis and risk level assessment on the detection results to generate a structured dataset; The report output module (700) is used to integrate the structured dataset into a compliance inspection report in a preset format and output it.
2. The IoT device network security compliance detection system according to claim 1, characterized in that, The detection execution module (400) includes a clause mapping unit (401), which is connected to the data acquisition module (300) and the result processing module (500). The clause mapping unit (401) is used to map the clause requirements of the EN 303645 standard clauses into executable detection rules, and automatically match the detection strategy according to the configuration information of the IoT device under test (100), and then detect the configuration information according to the detection rules and the detection strategy, generate the detection result and transmit it to the result processing module (500).
3. The IoT device network security compliance detection system according to claim 2, characterized in that, The result processing module (500) includes a vulnerability association analysis unit (501), which connects the clause mapping unit (401) and the report output module (700). The clause requirements also include semantic relationships between clauses, and the structured dataset includes a vulnerability association graph. The vulnerability association analysis unit (501) is used to obtain the semantic association between the clauses from the clause mapping unit (401), perform cross-clause association analysis on the non-compliant items in the detection results according to the semantic association between the clauses, generate the vulnerability association map and output it.
4. The IoT device network security compliance detection system according to claim 3, characterized in that, The semantic relationships between the clauses include at least one of the following: shared security attribute relationships, attack chain dependency relationships, and shared remediation measures relationships.
5. The IoT device network security compliance detection system according to claim 3, characterized in that, The result processing module (500) further includes a difference comparison unit (502), which is connected to the clause mapping unit (401) and the report output module (700). The structured dataset includes status change annotations. The difference comparison unit (502) is used to obtain the detection result and the configuration information from the clause mapping unit (401), obtain the compliance detection report of the last detection of the IoT device under test (100) using the firmware information, perform historical difference comparison between the detection result and the compliance detection report of the last detection of the IoT device under test (100), generate the status change label and output it. The status change label includes newly added non-compliant items, fixed items, items that persist, and duration of persistence.
6. The IoT device network security compliance detection system according to claim 5, characterized in that, The result processing module (500) also includes a risk assessment unit (503), which is connected to the vulnerability association analysis unit (501), the difference comparison unit (502), and the report output module (700). The structured dataset includes a risk assessment report. The risk assessment unit (503) is used to assess the risk level of non-compliant items in the detection results based on the node connectivity in the vulnerability association graph and the duration of existence, using a weighted scoring model, and to generate and output the risk assessment report. The risk level assessment includes the following scoring dimensions: the severity score of the clause, the connectivity of the node, and the duration of existence.
7. The IoT device network security compliance detection system according to claim 6, characterized in that, The result processing module (500) further includes a management report unit (504), which is connected to the risk assessment unit (503) and the report output module (700). The structured dataset includes a compliance summary report. The management reporting unit (504) is used to summarize and review the risk assessment report, generate the compliance summary report using the risk assessment report, and output it. The compliance summary report includes at least one of the following: a statistical chart of compliance rate for clause EN 303645, a list of non-compliance items ranked by risk level, operational guidance for rectifying high-risk non-compliance items, and a rectification timeline.
8. The IoT device network security compliance detection system according to claim 5, characterized in that, It also includes a historical testing database (600), which is connected to the difference comparison unit (502) and the report output module (700). The historical testing database (600) is used to store the compliance testing report output by the report output module (700). The historical testing database (600) is indexed by the firmware information of the IoT device under test (100) and the timestamp of the compliance testing report.
9. The IoT device network security compliance detection system according to claim 2, characterized in that, The detection execution module (400) further includes a compliance rule base unit (402), which is connected to the clause mapping unit (401). The compliance rule base unit (402) is used to store the clause requirements, which include detection judgment rules, compliance benchmark values and historical version rules.
10. The IoT device network security compliance detection system according to claim 9, characterized in that, The detection and judgment rules include provisions prohibiting general default passwords, vulnerability disclosure mechanisms, software update management, sensitive security parameter storage, communication security, attack surface minimization, software integrity, personal data protection, system availability resilience, and telemetry data security.
11. A testing device, characterized in that, The testing equipment (90) includes the Internet of Things device network security compliance testing system (80) as described in any one of claims 1 to 10.
12. A method for network security compliance testing of Internet of Things (IoT) devices, characterized in that, Implemented using the IoT device network security compliance testing system (80) as described in any one of claims 1 to 10, the IoT device network security compliance testing method includes: The configuration information of the IoT device under test is obtained through an external test interface. The configuration information includes firmware information, configuration parameters, and network interface data. The configuration information is checked item by item based on the clauses of EN 303645 standard, and the test results are generated. The test results are compared with historical differences, cross-clause correlation analysis and risk level assessment are performed to generate a structured dataset; The structured dataset is integrated into a compliance inspection report in a preset format and then output.
Citation Information
Patent Citations
Animal casting machine
GB303645A
