age all the ONAP components via an Operations, Administration, and Management (OA&M) instance of ONAP. It allows the design studio to onboard ONAP components and create recipes, and it allows the policy framework to define ONAP automation. ONAP delivers a single, consistent user experience (UX) based on the user's role and allows role changes to be configured within the single ecosystem. This UX is managed by the ONAP Portal. The ONAP Portal provides access to design, analytics, and operational control/administration func- tions via a common role-based menu or dashboard. The portal architecture provides web-based capabilities including application onboarding and management, centralized access management, dashboards, as well as hosted application widgets. The portal provides an SDK to drive multiple development teams to adhere to consistent user interface (UI) development requirements by taking advantage of built-in capabilities (services/API/UI controls), tools, and technologies. ONAP portal provides common operational services for all ONAP components including activity logging, reporting, common data layer, access control, resiliency, and software lifecycle management. These services provide access management and security enforcement, data backup, restoration, and recovery. They support standardized VNF interfaces and guidelines. The virtual operating environment of the network cloud introduces new security challenges and opportunities. ONAP provides increased security by embedding access controls in each ONAP component, augmented by analytics and policy components specifically designed for the detection and mitigation of security violations. 7.1.3 EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE: NFV MANAGEMENT AND ORCHESTRATION AND ONAP ALIGNMENT The European Telecommunications Standards Institute (ETSI) developed a reference architecture framework and specification in support of NFV management and orchestration (MANO). The main components of the ETSI-NFV architecture are orchestrator, VNF manager, and virtuali