e deployment models include network topology, location, physical resource availability, and applications targeted for a given loca- tion. For example, some sites will be designed to support VNFs due to their geographic location while other sites will support more generic computing needs due to the network connectivity and cost of the infrastructure. Based on the expected needs, costs, etc., those sites designed to support VNFs will be smaller than those used for more generic computing. In all instances because of the common OpenStack base, there is the capability and flexibility to handle whatever VMs or applica- tions that are needed at that location. Building the Network of the Future The AIC security framework is a composite of core AIC architecture and design decisions, which incorporates principles that ensure and achieve some level of security. For example, the archi- tectural requirement that there be separation between management and bearer traffic helps provide an inherently secure architecture. The implementation and distribution of security functionality and capabilities within and on top of the infrastructure further builds out the security model. The AIC security framework is predominantly based on components outside of the security functionality provided by OpenStack as part of it base functionality. The ultimate goal is to have a security solu- tion that meets and exceeds expected corporate security requirements. AIC connects to many different types of networks. All of these networks have the potential to impact the AIC security framework. The specific security implementation for each AIC model and data flow is based on the functionality and data content provided by AIC in that instance. It is the functionality and data that defines which requirements and security controls apply in each case or flow, all facilitated by service chaining enabled via SDN. Figure 9.7 depicts the areas that impact how, when, and where the security functions that com- prise the AIC security framework are implemented. The