 goals of the security framework for the particular flow and functionality. The bridging of networks, whether they be virtual or physical, must be designed to maintain the security. Given the flexibility provided by the cloud implementation, this must be an integral part of the core AIC design. The layer below network designs captures the introduction of new technologies and functions that are part of AIC and impact the security framework. The list of new technologies and functions is long and each brings its own impact on security. For example, containers bring a new model, which can provide new boundaries and structure for applications. Their role in achieving and pre- serving our security framework cannot be ignored. Similarly, the greater use of software, whether it be the hypervisor, VNFs, or other capabilities bring additional risks and interactions. Controls (e.g., hypervisor separation) and evaluations need to be performed to ensure a proper understanding of possible security issues and impact on the security framework. For example, if when a virtual FW (vFW) fails it allows all traffic to pass, then this would be a significant difference from a standard capability of FW appliances today. The bottom layer in the diagram captures the external processes and the requirements that form the security framework. In addition to the security policy and requirements, there are the strategies, DMZ/Tools/ Control Structure Control Structure Control Structure Control Structure Firewall Firewall Firewall Tools Tools Tools Firewall Firewall Firewall Firewall Firewall Single Physical OpenStack Multiple Virtual OpenStack Multiple Virtual OpenStack Multiple Virtual OpenStack Instance within a Site Instances within a Site Instances within a Site Instances within a Site Firewall Firewall Firewall Network Designs Containers/ Hypervisor Micro Services Separation Other Security Cloud Process/Procedure/ Standards and Orchestration Strategies Designs Tools Requirements Platform FIGURE 9.7 AIC security framework. Building the Netw