l ONAP API gateway Aggregate Track Ingest Notify Provide Security Order Usage Licenses Capacity Fallout Platforms ASTRA ECOMP Data Collection Security Framework Portal Orchestration Framework Model Inventory Aggregation Active Security Security Agent Collector Design Threat Deploy Resiliency Data Management Monitor Event Mgmt. Metadata Platform Analytics Platform Logging Access Control Run- Time Catalog Install Models File Transfer / ETL Platform Admin Context Manager History Data Movement Report Visualization & Scheduler Software LCM Admin Reporting Analytics Controller IP Address Data & Protocol Framework Framework User Guide Testing Mgmt. Transformation Analytics Analytics Controller Controller Design Time Run-Time Environment Execution Onboard Configure Collect Collect Collect Execute Elements Faults Usage Telemetry Tests Analytics App Security App Applications Containers Controller Stream Agent Active Collector FIGURE 9.12 ONAP platform and interfaces. ONAP is a platform for many types of services. Because of its inherent security, it is also a powerful means to provide security as a service. In many ways, security services are similar to introducing other services. However, security services must be provided via a platform and infra- structure that is inherently secure. The various types of security services can be access control, authentication, authorization, compliance monitoring, logging, threat analysis, management, etc. This is illustrated with the example of managed vFWs. Using a customer web portal, the customer provides the needed information to enable ONAP to determine and orchestrate the FW placement. In addition, the FW capabilities (e.g., rules, layer 7 FW) are instantiated at the appropriate locations within the architecture. If necessary, service chaining of many security controls and technologies including FWs, URL blocking, etc. can also be service chained. As part of an overall security architecture, the log data from the FWs can be captured by DCAE and used by the threat manage- ment appl