Checklist: Implementing a Domain Isolation Policy Design
Updated: October 11, 2012
Applies To: Windows Server 2012
This parent checklist includes cross-reference links to important concepts about the domain isolation policy design. It also contains links to subordinate checklists that will help you complete the tasks that are required to implement this design.
Complete the tasks in this checklist in order. When a reference link takes you to a procedure, return to this topic after you complete the steps in that procedure so that you can proceed with the remaining tasks in this checklist.
The procedures in this section use the Group Policy MMC snap-ins to configure the GPOs, but you can also use Windows PowerShell to configure GPOs. For more information, see Windows Firewall with Advanced Security Administration with Windows PowerShell at http://technet.microsoft.com/library/hh831755.aspx.
For more information about the security algorithms and authentication methods available in each version of Windows, see IPsec Algorithms and Methods Supported in Windows at http://technet.microsoft.com/library/dd125380.aspx.
Checklist: Implementing a domain isolation policy design
Review important concepts and examples for the domain isolation policy design, determine your Windows Firewall with Advanced Security deployment goals, and customize this design to meet the needs of your organization.
Create the GPOs and connection security rules for the isolated domain.
Create the GPOs and connection security rules for the boundary zone.
Create the GPOs and connection security rules for the encryption zone.
Create the GPOs and connection security rules for the isolated server zone.
According to the testing and roll-out schedule in your design plan, add computer accounts to the membership group to deploy rules and settings to your computers.
After you confirm that network traffic is authenticated by IPsec, you can change authentication rules for the isolated domain and encryption zone from request to require mode.