can be chosen for each flow. This may be using multiple tools from a single vendor or tools from multiple vendors. This determination and traffic flow can be established on demand in real time. In addition, the sizing of each security tool will be determined by the local needs, as compared to the broad set of needs of the entire environment, served by the set of perimeter security controls. This more localized meeting of the security requirements and needs results in a solution that is superior to that provided by a perimeter-based solution. When discussing the design benefits of employing SDN and NFV, it is important to keep in mind that these benefits are available both at initiation (e.g., the initial design or deployment) as well as during the life of the environment. It is easier and faster to evolve the security tools deployed as well as mixing vendors. As previously mentioned, getting away from the traditional solution, enables the optimization of each type of security control. SDN and NFV also enhances the ability to deploy a particular type of tool (e.g., FW) from multiple vendors, and having the specific traffic flows directed to the best tool in that category of security tools. All of these capabilities are accomplished via SDN with its centralized controllers. Centralization ensures that the security functionality distributed across the infrastructure, works in a concerted manner providing the appropriate and needed security. Network Security 9.2.2 PERFORMANCE IMPROVEMENTS From a performance perspective, SDN and NFV can enhance the security of the environment. Patching of virtual machines (VMs) is easier and simpler with SDN and NFV. SDN and NFV enables the patching systems by simply creating a new instance of a function with the patched version of the software and then redirecting the traffic to the new instance(s). The deployment of, as well as the transition to, the new instances is simplified with SDN and NFV. In addition to the patching process being more automated and having essentially no impac