Introduction

Microsoft for some time has been making security its main priority with the Microsoft Trustworthy Computing initiative. Starting with Microsoft Windows 2003 Server we were introduced to Network Access Quarantine Control. This feature enabled administrators to control remote access to a private network until the remote computer was validated by a script. The components necessary to deploy this solution included Microsoft Windows 2003 remote access servers, the Connection Manager Administration Kit, and Internet Authentication Service.

The most obvious problem with Network Access Quarantine Control was that it worked with only remote computers connecting to the network using Routing and Remote Access Services (RRAS). This solution left a wide gap throughout the network infrastructure for other types of clients to cause issues and management problems for network administrators.

With Microsoft Windows 2008 Server, Windows Vista, and Windows XP Service Pack 3, Microsoft has introduced Network Access Protection (NAP). NAP can control virtual private network (VPN) connections better than Network Access Quarantine Control, but NAP can also enforce policy compliance through the following types of network access or communications:

• Internet Protocol security (IPSec) protected traffic

• IEEE 802.1x authenticated network connections

• Dynamic Host Configuration Protocol (DHCP) address configurations

• Remote access VPN connections

The key word to keep in mind when discussing NAP and its features is compliance. With the introduction of NAP into our network, we can force Windows Server 2008, Windows Vista, and Windows XP Service Pack 3 to comply with standards set forth on our network.