9.5. Summary

The following are key points from this chapter:

• Microsoft NAP requires the use of Microsoft Server 2008.

• Microsoft Server 2008 is due to be generally available in February of 2008.

• Microsoft NAP requires the use of Windows Vista or Windows XP Service Pack 3.

• Service Pack 3 is due to be generally available in the first half of 2008.

• This solution can consist of a mix of components from Microsoft and other vendors.

• SHAs and SHVs work together to determine the overall security posture of devices.

• Microsoft will include APIs for SHAs and SHVs to enable third-party vendors to integrate with the solution.

• This solution is only available in client mode.

• This solution can require that authentication take place to provide access to the network.

• Microsoft NAP is designed to protect the corporate LAN from unauthorized and security-deficient devices and users.

• This solution does not address mobile devices as they are mobile and not connected to the corporate network.

• NAQC can provide assessment of devices as they attempt to gain remote access to the corporate network.

• NAQC works by running scripts on devices to determine if they are compliant.

• Microsoft 802.1x can be used by itself to control access from unauthorized users.

Thus far, we have covered the most well-known LAN-based and Mobile NAC solutions. Chapter 10 discusses how NAC-like functionality can exist in products that are not necessarily marketed as being NAC/NAP.