formation about asset interrelationships. There is noted improvement in asset inventories when device records are automatically gen- erated via orchestration tools in cloud platforms. However, issues related to missing or incorrect Network Security inventory records can be exacerbated by the increased volume and more frequent changes to assets in a virtualized environment. In summary, NFV introduces three new challenges relevant to continuous monitoring programs: Isolation. The adoption of network virtualization increases the importance of securing the hypervisor host. Vulnerabilities on the hypervisor may now affect the security framework of all associated network segments and devices. Relationships. The relationship between the device and other layers of architecture must be consistently captured in asset inventories. Uniqueness. Increased volatility in the asset lifecycle makes it much more important to uniquely identify a device and track its security status over time. 9.4.5 ONAP SECURITY The ONAP software platform [4] delivers product and service independent capabilities for the design, creation, and lifecycle management of the network cloud environment for carrier-scale, real-time workloads. It consists of multiple software subsystems covering two major architectural frameworks: (1) a design time environment to define, and program the platform and (2) an execution time environment to execute the logic programmed utilizing closed-loop, policy-driven automation. ONAP performs tasks such as provisioning of resources (VMs), applications, configuration management (of storage, compute, networking), security monitoring, and reporting. Misuse, either intentionally or unintentionally, of the powerful automation that ONAP provides could easily lead to disruption within the SDN and NFV environment. Security of the ONAP platform is critical to the stability and availability of the SDN and NFV environment. There are two main aspects to security in relation to the ONAP platform: security of the plat- form itself and the 