Method and device for safety assurance automation
By generating and automatically verifying NF's security requirements and policies, the lack of NF security automation in 5G networks is solved, and the full life cycle security guarantee of NF is achieved, which simplifies management processes and improves security and operational efficiency.
Patent Information
- Application Number
- CN201980097838.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-04-29
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2039-04-29
Smart Images

Figure CN114073039B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure generally relates to the field of network and service development and operation, and more particularly, to a method and apparatus for automating security assurance of a network function (NF) or a management function (MnF) or a service. Background Art
[0002] NF security is a critical issue in 5G networks. Due to the increasing complexity of NFs in 5G networks and the new technologies and development process of NFs, NF vendors and operators may not be able to invest efficiently and effectively in NF security throughout the NF development and operation period. As a result, they are likely to face the risk of service unavailability, loss / theft of critical data, or damage to their intellectual property and reputation.
[0003] The vertical industries introduced in 5G bring diversified security requirements from various industries. In addition, service providers and their supply chains are forced to comply with country-specific security laws and regulations, which cover different security requirements and require different levels of security compliance.
[0004] NF Virtualization (NFV) / Software Defined Network (SDN) enables automatic development, testing, deployment and updating of NFs in 5G, allowing NF operators to quickly release new features to their customers. There are currently many standardized specifications and open source projects that support the automation of 5G network and network slice deployment and updates. However, the existing NF security assurance methods defined by the Third Generation Partnership Project (3GPP) and the Global System for Mobile Communications Association (GSMA) are still based on static security requirements definition and manual verification. Therefore, such NF security assurance methods cannot adapt to NF development and operation in 5G. In addition, 3GPP and GSMA recommend many security testing tools to support NF testing and deployment automation. However, these tools can only promote NF security testing automation. NF security assurance in other NF development and operation stages still requires human intervention, especially relying on security experts to conduct risk analysis, define security requirements, design security solutions, develop test cases, execute test plans, analyze security reports and provide repair plans when necessary. These tasks are difficult, time-consuming and prone to problems.
[0005] Therefore, there is a need to provide more effective solutions to automate NF security assurance during the entire NF development and operation lifecycle. Summary of the invention
[0006] The present disclosure will solve the aforementioned problems by proposing a method and apparatus for safety assurance automation, so as to realize safety assurance automation during the entire development and operation life cycle of NF or MnF or service. Other features and advantages of the embodiments of the present disclosure will also be understood when the following description of specific embodiments is read in conjunction with the accompanying drawings, which illustrate the principles of the embodiments of the present disclosure by way of example.
[0007] In a first aspect of the present disclosure, a method for security assurance automation is provided. The method includes: generating security requirements for NF based on the security profile of NF and the deployment and operation environment; generating security policies and security test specifications for NF based on the security requirements, wherein the security policies define security functions and configurations of the security functions, and the security test specifications define at least one security test; deploying NF and security functions based on the security policies; verifying the security compliance of NF with the security test specifications; and activating NF in response to NF complying with the security policies.
[0008] In some embodiments, generating security requirements may include: determining original security requirements based on the security profile and deployment requirements of the NF; identifying semantically identical security requirements and semantically similar security requirements from the original security requirements; removing redundant semantically identical security requirements; and combining semantically similar security requirements into a combined security requirement, which has the highest degree of security.
[0009] In some embodiments, identifying semantically identical security requirements and semantically similar security requirements from original security requirements may include: calculating the semantic similarity between the original security requirements; identifying security requirements with a semantic similarity greater than a first threshold as semantically identical security requirements; and identifying security requirements with a semantic similarity greater than a second threshold as semantically similar security requirements.
[0010] In some embodiments, combining semantically similar security requirements into a combined security requirement may include: ranking the semantically similar security requirements based on their security levels; selecting the semantically similar security requirement with the highest security level; and removing the remaining semantically similar security requirements.
[0011] In some embodiments, the degree of security of the security requirement may be represented by at least one of a granularity of the security requirement and a security level of the security requirement.
[0012] In some embodiments, generating security requirements may further include: checking whether there are any missing security requirements in the generated security requirements based on a predefined security requirements baseline, the security requirements baseline including default security requirements required by the NF; and in response to the presence of missing security requirements, adding the missing security requirements to the generated security requirements.
[0013] In some embodiments, the security profile may include one or more of: hardware and software technology and architecture information; functionality; and external and internal interfaces.
[0014] In some embodiments, the deployment and operating environment may include one or more of the following: deployment country / region; applied industry; deployment model; operating ecosystem; and additional requirements provided by the NF vendor, network operator or service provider.
[0015] In some embodiments, the deployment mode may indicate that the network function is deployed as one of a physical node, a virtualized node, and a hybrid node. In some embodiments, the operating ecosystem may indicate that the communication network in which the network function will work is one of a public network, a private network, and a hybrid network.
[0016] In some embodiments, generating security requirements and security test specifications may be implemented in an intelligent model.
[0017] In some embodiments, a security test may include a test case, one or more test tools used to execute the test case, a test schedule defining a schedule of the test case, and a test configuration used to configure the one or more test tools.
[0018] In some embodiments, verifying the security compliance of a NF based on a security test specification may include: for each security test in at least one security test in the security test specification: configuring one or more test tools according to a test configuration; executing test cases according to a test schedule to determine whether the security test is passed; and in response to all of at least one security test being passed, determining that the NF complies with security requirements; in response to any of the at least one security test failing, determining that the NF does not comply with security requirements.
[0019] In some embodiments, verifying the security compliance of the NF based on the security test specification may further include: if the NF does not meet the security requirements, generating a security test report that recommends subsequent actions.
[0020] In some embodiments, the method may further include storing security requirements, security policies, and security test specifications.
[0021] In some embodiments, the method may further include: after activating the NF, monitoring the safety status of the NF in operation; and generating a safety monitoring report indicating the monitored safety status and suggesting subsequent actions if the monitored safety status indicates an unsafe state.
[0022] In some embodiments, the security test report and the security monitoring report can be generated based on the security reporting policy for the NF. In one embodiment, the security reporting policy can define the format and content of the security test report and the security monitoring report.
[0023] In some embodiments, the method may further include: updating the security requirements in response to one or more of: changes in the security profile; changes in the deployment and operating environment of the NF; changes in the security status of the NF; and update requests.
[0024] In a second aspect of the present disclosure, a device for safety assurance automation is provided. The device includes at least one processor and at least one memory including computer executable instructions. The at least one memory and the computer executable instructions are configured to, together with the at least one processor, cause the device to at least perform any step of the method according to the first aspect of the present disclosure.
[0025] In a third aspect of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are embodied. When the computer-executable instructions are executed on a computer, the computer is enabled to perform any step of the method described in the first aspect of the present disclosure.
[0026] Based on the various aspects and embodiments of the present disclosure as described above, a new solution can be provided to realize NF security assurance automation during the entire NF development and operation life cycle. BRIEF DESCRIPTION OF THE DRAWINGS
[0027] The above and other aspects, features and benefits of various embodiments of the present disclosure will become more apparent when reading the following detailed description with reference to the accompanying drawings by way of example, in which the same reference numerals or letters are used to designate similar or equivalent elements. The accompanying drawings are shown to facilitate a better understanding of the embodiments of the present disclosure and are not drawn to scale, wherein:
[0028] Figure 1 is a flow chart illustrating a method for NF security assurance automation according to some embodiments of the present disclosure;
[0029] Figure 2 is a flow chart illustrating a process of generating security requirements according to some embodiments of the present disclosure;
[0030] Figure 3 is a schematic diagram illustrating an exemplary implementation of generating security requirements;
[0031] Figure 4 is a schematic diagram showing an exemplary implementation of NF security assurance automation;
[0032] Figure 5is a schematic diagram showing an exemplary network and service automation framework in which the method for NF security assurance automation according to some embodiments of the present disclosure may be implemented;
[0033] Figure 6 It is shown in Figure 5 A schematic diagram of an exemplary workflow for NF security assurance in the network and service automation framework shown in FIG.
[0034] Figure 7 It is shown in Figure 5 A schematic diagram of another exemplary workflow for NF security assurance in the network and service automation framework shown;
[0035] Figure 8 is a schematic block diagram showing an apparatus for NF security automation according to some embodiments of the present disclosure. DETAILED DESCRIPTION
[0036] Hereinafter, the principles of the present disclosure will be described with reference to illustrative embodiments. It should be understood that all of these embodiments are provided only to enable those skilled in the art to better understand and further practice the present invention, and are not intended to limit the scope of the present disclosure. For example, a feature shown or described as part of one embodiment may be used together with another embodiment to produce yet another embodiment. For the sake of clarity, all features of the actual implementation are not described in this specification.
[0037] In the specification, references to "one embodiment", "an embodiment", "an exemplary embodiment", etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment includes the particular feature, structure, or characteristic. In addition, such phrases do not refer to the same embodiment. In addition, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is assumed that a person skilled in the art will be able to effect such feature, structure, or characteristic in conjunction with other embodiments, whether or not these other embodiments are explicitly described.
[0038] For the purpose of illustration, several embodiments of the present disclosure will be described in the context of a 5G network. However, those skilled in the art will appreciate that the concepts and principles of several embodiments of the present disclosure may also be applied to other types of communication networks.
[0039] As used in this application, the term "circuitry" may refer to one or more or all of the following:
[0040] (a) hardware circuit implementation only (such as analog and / or digital circuit implementation only);
[0041] (b) a combination of hardware circuitry and software, such as (where applicable): (i) a combination of analog and / or digital hardware circuitry and software / firmware; and (ii) any portion of a hardware processor with software (including a digital signal processor, software and memory that work together to enable a device such as a mobile phone or server to perform various functions); and
[0042] (c) Hardware circuits and / or processors, such as a microprocessor or portion of a microprocessor, that require software (e.g., firmware) to operate, but may not be present when the software is not required for operation.
[0043] This definition of "circuitry" applies to all uses of this term in this application, including in any claims. As another example, as used in this application, the term "circuitry" also covers an implementation of merely a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its accompanying software and / or firmware. The term "circuitry" also covers (for example and if applicable to the specifically claimed element) a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.
[0044] As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "including" and its variations should be understood as open terms, meaning "including but not limited to". The term "based on" should be understood as "based at least in part on". The terms "one embodiment" and "embodiment" should be understood as "at least one embodiment". The term "another embodiment" should be understood as "at least one other embodiment". Other definitions may be included below, whether explicit or implicit.
[0045] As mentioned above, the current NF security assurance approach is based on static security requirements and requires manual intervention. There is no solution for automating NF security assurance during the entire NF development and operation lifecycle. With the growing demand for NF security requirements in different countries / regions and industries, the emergence of flexible and automated NF security development and update processes and virtualization and programmability technologies, and the openness of future networks, a new approach for automating NF security assurance during NF development and operation is needed.
[0046] According to some exemplary embodiments, the present disclosure provides a solution for enabling NF security automation during the entire NF development and operation lifecycle. The solution can be applied to any type of communication network, for example, a 5G network.
[0047] Figure 1is a flowchart illustrating a method 100 for automating security assurance of a NF according to an embodiment of the present disclosure. Figure 1 The method 100 shown in FIG. 1 may be performed by a computing device or a server, which will be described later.
[0048] like Figure 1 As shown in FIG, a computing device generates security requirements for a NF based on a security profile of the NF and a deployment and operating environment, as shown in block 101. In some embodiments, the security profile of the NF may include information related to characteristics of the NF, such as NF hardware and software technology and architecture information, functions, external and internal interfaces. The NF hardware and software technology and architecture information may indicate the hardware and software technology used for the NF and the architecture of the NF. Functions may specify functions provided by the NF. External and internal interfaces may indicate external and internal interfaces of the NF and their configurations. Based on the security profile of the NF, relevant 3GPP or GSMA specifications or other specifications related to NF security may be determined.
[0049] In some embodiments, the deployment and operation environment of the NF may include information related to the deployment and operation of the NF, such as the deployment country / region, the applied industry, the deployment mode, the operation ecosystem, and additional requirements provided by the NF supplier, network operator or service provider. The deployment country / region may indicate the target country / region to be deployed, so that the security laws and regulations in the deployment country / region may be determined. For example, if the deployment country / region is Europe, the relevant security laws and regulations include at least the General Data Protection Regulation (GDPR). If the deployment country / region is China, the relevant security laws and regulations include at least the China Cybersecurity Law (CSL). The applied industry may indicate the target industry to be applied, so that the industry-specific standards and regulations related to security may be determined. For example, the industry-specific standards may include, but are not limited to, Common Criteria (CC) and International Organization for Standardization (ISO) standards. Optionally, the security compliance level for the relevant laws and regulations and industry-specific standards may be determined. For example, CC EAL+4 or level 4 information security level protection may be determined. Industry-specific regulations may include, for example, the Federal Information Security Management Act (FISMA) in the communications and e-commerce industries, the Payment Card Industry Data Security Standard (PCI-DSS) in the financial industry, and the Health Insurance Portability and Accountability Act (HIPPA) in the healthcare industry. The deployment mode may indicate whether the NF is deployed as a physical node, a virtualized node (e.g., a virtual machine (VM)), or a hybrid node, etc. The operating ecosystem may indicate the communication network in which the NF will work. The communication network may be a public network, a private network, or a hybrid network. Additional requirements provided by the NF vendor, network operator, or service provider may indicate special requirements from the NF vendor, network operator, and / or service provider. In this document, the additional requirements may also be referred to as "organizational policies."
[0050] The following will refer to Figure 2 and Figure 3 Provide a detailed description of the generation security requirements. Figure 2 A flow chart illustrating the process of generating security requirements (as shown in block 101) is shown, and Figure 3 A schematic diagram illustrating an exemplary implementation of generating security requirements is shown. Figure 3In the present invention, the generation of security requirements can be implemented in an intelligent model. The intelligent model can be based on artificial intelligence (AI) or machine learning (ML) technology, for example, natural language processing (NLP) technology. The intelligent model may include a learning phase and a prediction phase. During the learning phase, the intelligent model may learn the internal representation of security requirements by applying AI / ML tools (e.g., natural language processing (NLP)) to security laws and regulations, industry-specific standards and regulations, etc. The learning phase may be online or offline. After the learning phase, the intelligent model may be able to make predictions, i.e., identify semantically identical or semantically similar security requirements.
[0051] like Figure 2 As shown in FIG. 2 , in block 201, the computing device may determine the original security requirements based on the security profile of the NF and the deployment and operation environment. Figure 3 In the exemplary implementation shown in , the security profile of the NF, the deployment country / region, the applied industry, the deployment mode, and the optional organizational policies are input into the intelligent model, and the original security requirements can be determined with the help of the intelligent model based on these inputs.
[0052] Then, in box 203, the computing device can identify semantically identical security requirements and semantically similar security requirements from the original security requirements. In some embodiments, the semantic similarity between the original security requirements can be calculated. In one embodiment, a certain ML tool can be used to calculate the semantic similarity, for example, genSim, simHash, etc. In another embodiment, the semantic similarity between two security requirements can be calculated based on the distance of the internal representation (e.g., paragraph vector) of the security requirements. In this case, the semantic similarity can be expressed as the distance between the paragraph vectors of the security requirements. Furthermore, security requirements whose semantic similarity is greater than a first threshold are identified as semantically identical security requirements, and security requirements whose semantic similarity is greater than a second threshold are identified as semantically similar security requirements. The first threshold may be higher than the second threshold.
[0053] Then, in block 205, the computing device removes redundant security requirements with the same semantics, which can be considered as a deduplication operation. Therefore, only one of the security requirements with the same semantics will be retained in the final security requirements.
[0054] In block 207, the computing device combines semantically similar security requirements into a combined security requirement, and the combined security requirement has the highest degree of security. In some embodiments, the degree of security of the security requirement may be represented by at least one of the granularity of the security requirement and the security level of the security requirement. In some embodiments, the semantically similar security requirements may be ranked based on the degree of security of the semantically similar security requirements. Furthermore, the semantically similar security requirement with the highest degree of security may be selected as the combined security requirement. The remaining semantically similar security requirements may be deleted.
[0055] In some embodiments, the degree of security may be represented by the granularity of the security requirements. For example, one security requirement indicates the use of a national commercial encryption algorithm, while another security requirement indicates the use of a symmetric encryption algorithm. Then, the granularity of the former is coarse, while the granularity of the latter is fine. Therefore, the latter will be selected as the combined security requirement. In some embodiments, the degree of security may be represented by the security level of the security requirements. For example, three security requirements indicate the use of 16-bit, 32-bit, and 64-bit passwords, respectively. In this case, the security level may be represented by the length of the password. Furthermore, the security requirement indicating the use of a 64-bit password has the highest security level, and therefore, the security requirement indicating the use of a 64-bit password is selected as the combined security requirement.
[0056] Through the operations described above, the computing device can obtain final security requirements, which are security requirements that are still retained in the original security requirements after the deduplication operation and the combination operation.
[0057] In addition, in some embodiments, a security requirement baseline may be predefined for the NF. The security requirement baseline may be used to check whether the security requirements generated for the NF are complete. The security requirement baseline may include the default security requirements required by the NF. Figure 3 In the example, the computing device may check whether there are any missing security requirements in the generated security requirements based on the security requirements baseline by comparing the generated security requirements with the security requirements baseline. If there are missing security requirements, the missing security requirements will be added to the generated security requirements, such as Figure 2 As shown in box 209 of .
[0058] Now return to reference Figure 1, as shown in box 103, the computing device generates a security policy and a security test specification for the NF based on the security requirements generated in box 101. In some embodiments, the security policy may define one or more security functions and the configuration of the security function. The configuration of the security function may include one or more configuration rules for the security function. The security test specification may define at least one security test for security compliance verification. In some embodiments, the generation of the security test specification may also be implemented in the intelligent model as described above. In some embodiments, the security test may include a test case, one or more test tools used to execute the test case, a test schedule defining the scheduling of the test case, and a test configuration for configuring one or more test tools.
[0059] Furthermore, in block 105, the computing device may deploy NFs and security functions based on the security policy. As described above, the security policy defines the security functions and the configuration of the security functions. The computing device may deploy and configure the NFs and the security functions for protecting the NFs according to the security policy.
[0060] Then, in block 107, the computing device verifies the security compliance of the NF with the security test specification. In some embodiments, the verification is performed by executing at least one security test defined in the security test specification.
[0061] In some embodiments, during verification, for each security test in at least one security test, the computing device may configure one or more test tools according to the test configuration. Furthermore, the computing device may execute the test case according to the test schedule to determine whether the security test is passed. If all security tests in at least one security test are passed, it is determined that the NF complies with the security policy. If any security test in at least one security test is not passed, it is determined that the NF does not comply with the security policy.
[0062] In addition, in some embodiments, a security test report may be generated. The security test report may indicate whether the NF is security compliant or non-security compliant, and optionally, if the NF does not comply with the security policy, a subsequent action is recommended. For example, the subsequent action may be to terminate the NF, or to update the security configuration for the security function of the NF. In some embodiments, a security test report may be generated based on a security reporting policy for the NF. In one embodiment, the security reporting policy may define the format and content of the security test report, and may be generated based on the security requirements generated in box 101. Further, the security reporting policy may indicate the recipient of the security test report.
[0063] In block 109 , if the NF complies with the safety requirement, the computing device activates the NF and the NF is in a working state.
[0064] Furthermore, in some embodiments, the computing device may store the security requirements, security policies, and security test specifications generated for the NF in, for example, a database for subsequent use, such as deployment of the NF, and verification of security compliance.
[0065] In addition, in some embodiments, after the NF is activated, the computing device may periodically monitor the security status of the NF. In some embodiments, the security status may be monitored by checking the security compliance of the NF based on a security policy. The security status may include a secure state and an unsafe state. Furthermore, the computing device may generate a security monitoring report. In some embodiments, the security monitoring report may indicate the monitored security status, and optionally, if the monitored security status is an unsafe state, a subsequent action is recommended. The subsequent action may be, for example, terminating the NF, or triggering an update of a security requirement. In some embodiments, a security monitoring report may be generated based on a security reporting policy. The security reporting policy may define the format and content of the security monitoring report based on the security requirements generated in box 101. The security reporting policy may also indicate the recipient of the security monitoring report.
[0066] Additionally, in some embodiments, the computing device may generate a migration plan for the NF based on the security requirements generated in block 101 and security reports including a security testing report and a security monitoring report.
[0067] In addition, in some embodiments, the computing device can update the security requirements. For example, if the security profile of the NF changes, or the deployment and operating environment of the NF changes, or the security status of the NF changes, the computing device can update / regenerate the security requirements based on the changed security profile of the NF or the changed deployment and operating environment or the changed security status. Accordingly, the security policy, security test specification, security reporting policy, and migration plan will be updated based on the updated / regenerated security requirements. The update / regeneration process is similar to the following: Figure 1 , 2 and generation of the security requirements shown in 3.
[0068] Although the method described above is described for the security assurance automation of NF, it should be noted that security assurance automation is part of network and service automation, so the above method can be extended to the development and operation of networks and services. Those skilled in the art will understand that the above security assurance automation method can be applied to other functional assurance and non-functional assurance (e.g., execution assurance) of functions (e.g., network functions or management functions) and services to promote end-to-end (E2E) service automation.
[0069] Figure 4 is a schematic diagram showing an exemplary implementation of security assurance automation. Figure 4As shown in , there are five inputs to the generation of security requirements. They are security profile, deployment country / region, applied industry, deployment mode, and optional organizational policy. After the security requirements are generated, a security policy and a security test specification are generated based on the generated security requirements. The security policy may define one or more security functions and the configuration of the security functions. The security test specification may define at least one security test. Each security test may include a test case, one or more test tools for the test case, a test schedule, and a test configuration for the test tool. Furthermore, NF and security functions may be deployed according to the security policy and the NF package, and the NF package includes NF deployment related information, such as a software package and a deployment mode. Furthermore, the security compliance of the NF may be verified by executing the security test in the security test specification, and a security test report may be generated. When the NF is verified to comply with the security policy, the NF is activated to work. While the NF is in the working state, the NF may be continuously monitored for security compliance, and a security monitoring report may be generated.
[0070] From the above description, it can be seen that the method according to the embodiment of the present invention can realize the automation of NF security assurance during the entire NF development and operation life cycle. It helps to simplify the work of NF developers, verifiers and administrators, unify the NF security identification and certification process, and ensure the security of NF even if NF is deployed in different regions for different industries.
[0071] Figure 5 is a schematic diagram showing an exemplary network and service automation framework in which the method for security assurance automation according to some embodiments of the present disclosure can be implemented. The exemplary network and service automation framework can be based on an existing operation and management framework. Figure 5 In the , the operation and management framework is based on the European Telecommunications Standards Institute (ETSI) Zero Touch Network and Service Management (ZSM) architecture. Functional blocks and interfaces related to safety assurance automation are added to the ZSM architecture.
[0072] like Figure 5As shown in , the framework includes at least an intelligence service provider, an orchestration service provider, a control service provider, a policy service provider, a test service provider, an analytics service provider, and a data service provider.
[0073] The security requirement function may be embodied in an intelligent service provider. The security requirement function may provide a service for automatically and dynamically generating and updating security requirements for a specific NF or management function (MnF) deployment as described above. The security requirement function may trigger a policy service provider to generate / update security policies. The security requirement function may also trigger an orchestration service provider to perform deployment of NF or MnF based on security policies.
[0074] The security test specification function can also be embodied in the smart service provider. The security test specification function can provide services for automatically generating and updating security test specifications for specific NF or MnF deployments as described above. The security test specification function can trigger the orchestration service provider to perform security testing for security compliance verification.
[0075] The orchestration service provider can be enhanced by adding the following features: deploying NF or MnF based on security policy, checking whether existing resources can meet security requirements, triggering the deployment of NF or MnF if the check passes, triggering the verification of security compliance of NF or MnF with security test specifications. Alternatively, the above features can be embodied in a new functional block for dedicated security orchestration.
[0076] The control service provider may be enhanced by adding the following features: controlling and managing the deployment of NFs or MnFs, and deploying and configuring NFs or MnFs according to the security policies as described above. Alternatively, the above features may be embodied in a new functional block for dedicated secure deployment management.
[0077] The policy service provider can be enhanced by adding the following features: Generate / update / delete security policies based on security requirements as described above. It also provides features for resolving conflicts between security policies and other policies. Alternatively, the above features can be embodied in a new functional block for dedicated security policy management.
[0078] The testing service provider can be enhanced by adding the following features: Before activating the NF or MnF, the security compliance is verified with the security test specification, as described above. Alternatively, the above features can be embodied in a new functional block for specialized security testing. In this case, the new security testing function can reuse the automatic testing framework for general test cases with additional specific security testing methods. Security testing can include static security testing, dynamic security testing, interactive security testing, software compliance analysis, and penetration testing.
[0079] The data service provider can be enhanced by adding the following features: Support for storage of security data (e.g., security requirements, security policies, security test specifications, etc.) Due to the sensitivity of security data, stricter security access control, isolation, and protection can be considered.
[0080] Next, describe Figure 5 Some new / affected interfaces and their uses in the exemplary network and service automation framework shown in are as follows.
[0081] I1 interface: involves security-related services provided by the policy service provider, and may provide interfaces to the security requirements function, orchestration service provider, control service provider, and test service provider.
[0082] I2 interface: involves security-related services provided by the orchestration service provider and can provide an interface to the intelligent service provider.
[0083] I3 interface: involves security-related services provided by the control service provider and may provide an interface to the orchestration service provider.
[0084] I4 interface: involves security test specification functions and can provide an interface to security requirement functions.
[0085] I5 interface: involves security-related services provided by the test service provider, and may provide interfaces to the intelligent service provider and the orchestration service provider.
[0086] I6 interface: involves security requirement functions and can provide interfaces to analysis service providers and orchestration service providers.
[0087] I7 Interface: relates to security-related services provided by data service providers, and may provide interfaces to security test specification functions, orchestration service providers, control service providers, testing service providers, analysis service providers, and policy service providers.
[0088] Figure 6 It is shown in Figure 5A schematic diagram of an exemplary workflow for NF security assurance in the network and service automation framework shown in FIG. The workflow is described as follows.
[0089] 1. The administrator / user sends a request to the orchestration service provider OrServProv to deploy the target NF or MnF.
[0090] 2. The orchestration service provider OrServProv sends a request to the security requirement function SecReqFun for generating relevant security requirements for the target NF or MnF.
[0091] 3. The security requirement function SecReqFun automatically generates security requirements using AL / ML technology based on the security profile of the NF or MnF as well as the deployment and operation environment.
[0092] 4. The security requirement function SecReqFun requires the policy service provider PolServProv to generate a security policy for the target NF or MnF.
[0093] 5. The policy service provider PolServProv generates security policies based on security requirements.
[0094] 6. The security requirement function SecReqFun requests the security test specification function SecTstSpeFun to generate a security test specification for the target NF or MnF. Alternatively, the generation of the security test specification may be triggered by the orchestration service provider OrServProv or by other management functions.
[0095] 7. The security test specification function SecTstSpeFun generates security test specifications based on security requirements using AL / ML technology, and commands (calls) the data service provider to store the security test specifications in the database.
[0096] 8. The security requirement function SecReqFun generates the security requirements and security test specifications by responding to the orchestration service provider OrServProv.
[0097] 9. The orchestration service provider OrServProv triggers the control service provider ConServProv to deploy the target NF or MnF based on the security policy.
[0098] 10. The control service provider ConServProv obtains the security policy from the policy service provider PolServProv.
[0099] 11. The control service provider ConServProv deploys security functions and configures security measures for the target NF or MnF.
[0100] 12. The control service provider ConServProv responds to the orchestration service provider OrServProv that the target NF or MnF has been deployed.
[0101] 13. The orchestration service provider OrServProv triggers the test service provider TstServProv to verify the security compliance of the target NF or MnF.
[0102] 14. According to the security test specification obtained from the data service provider, the test service provider TstServProv performs security testing based on the security test specification.
[0103] 15. The test service provider TstServProv reports the security test results to the orchestration service provider OrServProv.
[0104] 16. Based on the security test results, if all security tests pass, the orchestration service provider OrServProv triggers the control service provider ConServProv to activate the target NF or MnF. Otherwise, the orchestration service provider OrServProv triggers the reconfiguration of the security function or the termination of the target NF or MnF.
[0105] 17. After the target NF or MnF is activated, the analysis service provider AnaServProv continuously monitors the security status of the target NF or MnF.
[0106] 18. The analysis service provider AnaServProv triggers the security requirement function SecReqFun to update / regenerate / optimize the security requirements in order to achieve operational security assurance for closed-loop automation.
[0107] Figure 7 It is shown in Figure 5 A schematic diagram of another exemplary workflow for NF security assurance in the network and service automation framework shown in FIG. Figure 7 In this paper, the intelligent service provider rather than the orchestration service provider drives the NF or MnF security assurance automation. The workflow is described as follows.
[0108] 1. The administrator / user sends a request to the intelligent service provider IntServProv to deploy a target NF or MnF.
[0109] 2. The intelligent service provider IntServProv sends a request to the security requirement function SecReqFun for generating relevant security requirements for the target NF or MnF.
[0110] 3. The security requirement function SecReqFun automatically generates security requirements using AL / ML technology based on the security profile of the NF or MnF as well as the deployment and operation environment.
[0111] 4. The security requirement function SecReqFun requires the policy service provider PolServProv to generate a security policy for the target NF or MnF.
[0112] 5. The policy service provider PolServProv generates security policies based on security requirements.
[0113] 6. The security requirement function SecReqFun requests the security test specification function SecTstSpeFun to generate a security test specification for the target NF or MnF. Alternatively, the generation of the security test specification may be triggered by the intelligent service provider IntServProv or by other management functions.
[0114] 7. The security test specification function SecTstSpeFun generates security test specifications based on security requirements using AL / ML technology, and instructs the data service provider to store the security test specifications in the database.
[0115] 8. The security requirement function SecReqFun generates the security requirements and security test specifications by responding to the intelligent service provider IntServProv.
[0116] 9. The intelligent service provider IntServProv triggers the orchestration service provider OrServProv to deploy the target NF or MnF based on the security policy.
[0117] 10. The orchestration service provider OrServProv obtains the security policy from the policy service provider PolServProv.
[0118] 11. The orchestration service provider OrServProv triggers the control service provider ConServProv to deploy security functions and configure security measures for the target NF or MnF.
[0119] 12. The orchestration service provider OrServProv responds to the intelligent service provider IntServProv that the target NF or MnF has been deployed.
[0120] 13. The intelligent service provider IntServProv triggers the test service provider TstServProv to verify the security compliance of the target NF or MnF.
[0121] 14. According to the security test specification obtained from the data service provider, the test service provider TstServProv performs security testing based on the security test specification.
[0122] 15. The test service provider TstServProv reports the security test results to the intelligent service provider IntServProv.
[0123] 16. Based on the security test results, if all security tests pass, the intelligent service provider IntServProv triggers the orchestration service provider OrServProv to activate the target NF or MnF. Otherwise, the intelligent service provider IntServProv triggers the reconfiguration of the security function or the termination of the target NF or MnF.
[0124] 17. After the target NF or MnF is activated, the analysis service provider AnaServProv continuously monitors the security status of the target NF or MnF.
[0125] 18. The analysis service provider AnaServProv triggers the security requirement function SecReqFun to update / regenerate / optimize the security requirements in order to achieve operational security assurance for closed-loop automation.
[0126] Reference now Figure 8 , which shows a simplified block diagram of an apparatus 800 according to some embodiments of the present disclosure. The apparatus may be implemented in a communication system such as a 5G system. The apparatus 800 may be operable to perform a reference Figure 1 , 2 , 3 and / or 4, and any other possible processes or methods. It should also be understood that any of the above methods may not be completely performed by the apparatus 800. Some steps of the above methods may be performed by one or more other entities.
[0127] The apparatus 800 may include at least one processor 801 (such as a data processor (DP)) and at least one memory (MEM) 802 coupled to the processor 801. The MEM 802 stores a program (PROG) 803. The PROG 803 may include instructions that, when executed on the associated processor 801, enable the apparatus 800 to operate according to embodiments of the present disclosure, such as performing the above-described methods. The combination of at least one processor 801 and at least one MEM 802 may form a processing unit suitable for implementing various embodiments of the present disclosure.
[0128] Various embodiments of the present disclosure may be implemented by a computer program, circuit, software, firmware, hardware, or a combination thereof that may be executed by the processor 801. The processor 801 may be of any type suitable for the local technical environment, and may include, as non-limiting examples, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor DSP, and a processor based on a multi-core processor architecture.
[0129] The MEM 802 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, by way of non-limiting examples, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory.
[0130] In addition, the present disclosure may also provide a carrier containing the above-mentioned computer program, wherein the carrier is one of an electrical signal, an optical signal, a radio signal or a computer-readable storage medium. The computer-readable storage medium may be, for example, an optical disc or an electronic storage device (such as RAM (random access memory), ROM (read-only memory)), a flash memory, a magnetic tape, a CD-ROM, a DVD, a Blu-ray disc, etc.
[0131] The techniques described herein may be implemented by various means, so that the device for implementing one or more functions of the corresponding device described by the embodiment includes not only prior art means, but also means for implementing one or more functions of the corresponding device described by the embodiment, which may include separate components for each separate function, or components may be configured to perform two or more functions. For example, these techniques may be implemented in hardware (one or more devices), firmware (one or more devices), circuits, software (one or more modules), or a combination thereof. For firmware, circuits, or software, it may be implemented by modules (e.g., processes, functions, etc.) that perform the functions described herein.
[0132] Embodiments of the present invention have been described above with reference to block diagrams and flow charts of methods and apparatus. It should be understood that each block of the block diagrams and flow charts and combinations of the blocks of the block diagrams and flow charts may be implemented by various means including computer program instructions. These computer program instructions may be loaded onto a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine so that the instructions executed on the computer or other programmable data processing device create components for implementing the specified functions in one or more blocks in the flow chart.
[0133] In addition, although some operations are described in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown or in a continuous order, or requiring all operations shown to be performed to achieve the desired result. In some cases, multitasking and parallel processing can be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of the subject matter described herein, but should be interpreted as descriptions of features specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable subcombination.
[0134] It is obvious to those skilled in the art that, with the advancement of technology, the concepts of the present invention can be implemented in various ways. The above embodiments are provided for the purpose of describing rather than limiting the present disclosure, and it will be understood that, as those skilled in the art will readily appreciate, various modifications and variations may be made without departing from the spirit and scope of the present disclosure. Such modifications and variations are considered to fall within the scope of the present disclosure and the appended claims. The scope of protection of the present disclosure is defined by the appended claims.
Claims
1. A method for communication, comprising: generating security requirements for the network function based on the security profile of the network function and the deployment and operating environment; generating a security policy and a security test specification for the network function based on the security requirements, the security policy defining a security function and a configuration of the security function, and the security test specification defining at least one security test; Based on the security policy, deploy the network function and the security function; verifying the security compliance of the network function based on the security test specification; as well as In response to the network function complying with the security policy, activating the network function; The verifying the security compliance of the network function based on the security test specification includes: For each security test in the at least one security test in the security test specification: configuring one or more test tools according to the test configuration; Executing the test case according to the test schedule to determine whether the security test is passed; and In response to all of the at least one security test being passed, determining that the network function complies with the security requirement; In response to any one of the at least one security test being failed, it is determined that the network function does not meet the security requirement.
2. The method according to claim 1, wherein: The deployment and operating environment includes one or more of the following: deployment country / region; applied industry; deployment mode; operating ecosystem; and additional requirements provided by network function suppliers, network operators or service providers.
3. The method according to claim 2, wherein: The deployment mode indicates that the network function is deployed as one of a physical node, a virtualized node, and a hybrid node, And wherein the operating ecosystem indicates that the communication network in which the network function will work is one of a public network, a private network and a hybrid network.
4. The method according to any one of claims 1 to 3, wherein: Generating the security requirements and the security test specifications is implemented in an intelligent model.
5. The method according to any one of claims 1 to 3, wherein: The security test includes a test case, one or more test tools used to execute the test case, a test schedule defining a schedule of the test case, and a test configuration used to configure the one or more test tools.
6. The method according to claim 5, wherein: Verifying the security compliance of the network function based on the security test specification further includes: If the network function does not meet the security requirements, a security test report is generated, and the security test report recommends subsequent actions.
7. The method according to any one of claims 1 to 3, further comprising: After activating the network function, monitoring the security status of the network function in operation; as well as A security monitoring report is generated that indicates the monitored security status and recommends subsequent actions if the monitored security status indicates an unsafe status.
8. The method according to claim 1, further comprising: The security requirements are updated in response to one or more of: a change in the security profile; a change in the deployment and operating environment of the network function; a change in the security state of the network function; and an update request.
9. An apparatus for communication, comprising: at least one processor; as well as at least one memory including computer executable instructions; The at least one memory and the computer executable instructions are configured to, with the at least one processor, cause the apparatus to: generating security requirements for the network function based on the security profile of the network function and the deployment and operating environment; generating a security policy and a security test specification for the network function based on the security requirements, the security policy defining a security function and a configuration of the security function, and the security test specification defining at least one security test; Based on the security policy, deploy the network function and the security function; verifying the security compliance of the network function using the security test specification; as well as In response to the network function complying with the security policy, activating the network function; wherein the at least one memory and the computer executable instructions are further configured to, together with the at least one processor, cause the apparatus to: For each security test in the at least one security test in the security test specification: configuring one or more test tools according to the test configuration; Executing the test case according to the test schedule to determine whether the security test is passed; and In response to all of the at least one security test being passed, determining that the network function complies with the security requirement; In response to any one of the at least one security test being failed, it is determined that the network function does not meet the security requirement.
10. The device according to claim 9, wherein: The deployment and operating environment includes one or more of the following: deployment country / region; applied industry; deployment mode; operating ecosystem; and additional requirements provided by network function suppliers, network operators or service providers.
11. The device according to claim 10, wherein: The deployment mode indicates that the network function is deployed as one of a physical node, a virtualized node, and a hybrid node, And wherein the operating ecosystem indicates that the communication network in which the network function will work is one of a public network, a private network and a hybrid network.
12. The device according to any one of claims 9 to 11, wherein: Generating the security requirements and the security test specifications is implemented in an intelligent model.
13. The device according to any one of claims 9 to 11, wherein: The security test includes a test case, one or more test tools used to execute the test case, a test schedule defining a schedule of the test case, and a test configuration used to configure the one or more test tools.
14. The device according to claim 13, wherein: The at least one memory and the computer executable instructions are configured to, with the at least one processor, further cause the apparatus to: If the network function does not meet the security requirements, a security test report is generated, and the security test report recommends subsequent actions.
15. The device according to any one of claims 9 to 11, wherein: The at least one memory and the computer executable instructions are configured to, with the at least one processor, further cause the apparatus to: After activating the network function, monitoring the security status of the network function in operation; as well as A security monitoring report is generated that indicates the monitored security status and recommends subsequent actions if the monitored security status indicates an unsafe status.
16. The device according to claim 9, wherein: The at least one memory and the computer executable instructions are configured to, with the at least one processor, further cause the apparatus to: The security requirements are updated in response to one or more of: a change in the security profile; a change in the deployment and operating environment of the network function; a change in the security state of the network function; and an update request.
17. A computer-readable storage medium having stored thereon computer-executable instructions, which when executed by a computer cause the computer to perform the method according to any one of claims 1 to 8.
