| Last Modified On : | October 15, 2008 4:21 PM PDT |
Rate |
|
Endpoint Access Control: AMT2.5 for NAC, AMT4.0 and AMT 5.0 for NAP
Intel® Active Management Technology (Intel® AMT) helps secure network endpoints by validating their compliance with network policies. Endpoint access control (EAC) feature allows the IT administrators to implement differentiated policy enforcement and configuration based on the security state of the end point. This example examines the case where a system with non-compliant software configuration is attempting to request the access to the network.
Greater connectivity options, including public wireless hotspots, hotels and home networks increase the vulnerability of notebook PCs. Notebook PCs often become vulnerable when disconnected from the network. When the PC is reconnected to the network, there is the potential threat to the business. Rogue desktop systems (non-IT managed, not properly configured or a visitor’s system) plugged into a corporate network could open a security hole, allowing an external visitor or hacker to snoop the network, and could be the source of spreading malware onto the network. This example includes efforts to isolate the non-compliant systems and automate the system remediation to bring them into compliance with network security policies.
802.1x networks have the ability to authenticate systems before allowing them on the network, but have no ability to validate postures to ensure proper virus protection, proper OS patches, and that no unauthorized software is installed. Non-802.1x networks do not have the ability to authenticate the system. Non-compliant systems (those without proper virus protection, OS patches, or unauthorized software) can connect to the network and potentially become the source of distributing malware into the network. Visitors have the ability to connect to the network. Once connected to the network, they can sniff traffic and view mission critical application traffic and/or access data stored on the network.
At every connection or on demand, a client system's profile is securely surveyed in a trusted manner. The "system posture" (including credentials, configuration, and system data) along with Intel® AMT configuration parameters (Firmware Version, TLS enabled, SOL enabled etc.) , is compared to current requirements. For systems not meeting the minimum standards, the Policy Decision Point (PDP) conveys a health assessment for the system and limits or denies network access. If network access is restricted, a User Notification is displayed to convey to the end user that normal network operation will be delayed until remediation is complete. The system is then redirected to a software configuration system or placed in a remediation network for upgrading to minimum standards. Rogue systems plugged into the network are now identified and the access is controlled based on policy. Full authentication and posture checking before allowing network access can greatly reduce the potential for malware to propagate onto the network, allows for the IT admin to maintain all systems in compliance with current policies, and limits rogue or visitor systems from gaining network access.
The following table summarizes the features and functionality utilized in this use case that are provided by Intel AMT or enabled by Intel AMT in third-party software:
|
Feature |
Functionality |
|
Posture information |
Posture is created by Intel® AMT firmware collecting the data from BIOS, system, itself and pass it on to AMT posture plug-in at host OS. |
|
Posture Verification |
Server plug-in to read Intel® AMT posture information, verify AMT signature and return health statement. |
|
Support for Intel® Out-of Band (OOB) NAC (Network Admission Control) and NAP (Network Access Protection) |
Intel® AMT firmware will support the layer 2 NAC and NAP protocol stacks to exchange authentication and posture information to get access to the network when host OS is down. |
In addition, the following functionality is performed by third-party management applications:
Intel AMT enables the acquisition of accurate endpoint state and attributes information for network admission control, via “always-available” communication, regardless of the PC’s power state, the state of the OS, or the absence of management agents. It achieves this goal by means of exchanging the authentication and posture information by the firmware. Accurate identification of machines in a pre-boot environment results in improved automation and enforcement of secure network policies.
This use case enables IT organizations to enforce endpoint access control:
The components required to configure Endpoint Access Control use case are as follows:
The MC application is used to configure the Intel AMT device and manage the events generated by the Intel AMT device. MC will configure the Intel AMT device to enable EAC allowing the firmware to send posture information at every connection or on-demand.
In the following example, a system has been identified by a central management console as non-compliant with corporate minimum standards, and the central console would like to restrict the system access to only remediation network allowing it to be upgraded to minimum standards. The following is the Endpoint Access Control Overview:
The following table provides some high-level instructions on how to enable/disable/gather EAC settings.
|
Action |
System Defense API/Steps |
|
Get the EAC status |
Call GetEACStatus() to get the enabled/disabled state of EAC |
|
Enable EAC |
Call EnableEAC() to enable or disable EAC. |
|
Get Posture |
Call GetPosture() to get the current posture. Note that posture is only available when EAC is enabled. |
|
Get Posture Hash |
Call GetPostureHash() to get the hash of the posture. Note that posture hash is available only when EAC is enabled. |
Note: See the "System Defense Feature and Agent Presence Overview" [PDF], "Intel AMT Posture Validation Server Sample" [PDF], and "Intel® AMT Network Interface Guide" [PDF] documents located in the Intel AMT SDK for further details.
[4] The following assumptions underlie the analysis in this use case:
OR
Note: In the events described above, NAC agents communicate with NAC servers only and NAP agents communicate with NAP servers only.
