192.168.190.6 InterfaceAlias : Ethernet 2 SourceAddress : 192.168.190.5 PingSucceeded : True PingReplyDetails (RTT) : 2 ms Chapter 6 24. This shows that PVLAN190-4 can communicate with the VMs that are not isolated. The PVLAN virtual machines should be currently in the following configuration: Virtual Machine PVLAN Mode PVLAN190-1 Promiscuous PVLAN190-2 Isolated PVLAN190-3 Community PVLAN190-4 Community The following diagram shows this configuration: Isolated Promiscuous Community PVLAN190-2 PVLAN190-3 PVLAN190-1 PVLAN190-4 How it works Private VLANs are implemented within the Hyper-V Extensible Switch with the port configuration saved into the Virtual Machine's configuration file. Layer 2 traffic is controlled via the switch as the Hyper-V Extensible Switch understands the configuration of a PVLAN and its port type. The port type controls which devices within a PVLAN can communicate with one another. Network Access Control Lists In this chapter, we will cover the following recipes: Locking down a VM for security access Applying rules to a list of VMs Introduction In Windows Server 2012, Microsoft introduced the Hyper-V Extensible Switch. One of its features was the Port Access Control List (ACL). This does not refer to a protocol port such as the TCP port for HTTP, but rather the logical port inside the Hyper-V Extensible Switch. Windows Server 2012 R2, Microsoft extended this functionality to include the following parameters: Source IP address Destination IP address Protocol Source port Destination port Direction (inbound/outbound) As the configuration of the ACL relates to the VM, it is stored in the VM's configuration file. This ensures that if the VM is migrated to a different host, the ACLs will move with it. System Center 2012 R2 VMM is not capable of managing ACLs for virtual machines, so the only option for managing ACLs is PowerShell. Network Access Control Lists Locking down a VM for security access This recipe will show you how to apply ACLs to VMs to protect them from unauthorized access. Getting rea