ork of the Future both security and otherwise, as well as the operational processes and procedures that are imple- mented to achieve the desired security level. All these influence the designs, automation schema, and how the cloud platform is deployed and evolved. Each new release of OpenStack supplies additional functionality as well as additional security functionality that needs to be accounted for and incorporated into the security model and frame- work. New technologies and features are continually being introduced that drive additional changes to the AIC security framework roadmap, implementation, and architecture. Examples include con- tainers and micro-segmentation. To accommodate this, the evolution of the AIC security model is achieved in a continuous delivery fashion. This enables the appropriate security functionality to be applied by default at creation of the VM. 9.4.2 AIC SECURITY EVOLUTION The AIC security framework is evolving from a perimeter-based solution to a cloud-based solu- tion. This migration is dictated by the current state of the technology. Some security vendors treat their products as appliances; to take full advantage of VNF functionality, security must be a joint effort-a mix of capabilities provided by the VNF and those provided by our service provider. Consequently, the desired security framework continues to evolve as available security functionality becomes more cloud-based and cloud-centric. This evolution occurring in all of the layers may be observed in Figure 9.7. Figure 9.8 provides a pictorial roadmap of the migration path of the security functionalities used to secure the AIC environment from a primarily perimeter-based solution to a primarily cloud-based solution. Some of the perimeter-based functions have virtual substitutes available while others are still being worked. The ecosystem is evolving to support virtual security appliances and efforts are underway to move security functions such as data leakage prevention, deep packet inspection, vul- nerability scanning, a