![]() |
|||||||||||||
Network Admission Control Agentless Host Support
![]() |
|||||||||||||
Contents
Network Admission Control Agentless Host SupportLast Updated: July 22, 2011
The Network Admission Control: Agentless Host Support feature allows for an exhaustive examination of agentless hosts (hosts that are not running the Cisco Trust Agent software). This examination allows customers to build a robust host or examination functionality by integrating any third-party audit mechanisms into the Network Admission Control architecture. This feature also allows for Extensible Authentication Protocol over UDP (EAPoUDP) bypass, which speeds up the posture validation of hosts that are not using Cisco Trust Agent.
Prerequisites for Network Admission Control Agentless Host Support
Information About Network Admission Control Agentless Host Support
Network Admission ControlThe Cisco Network Admission Control functionality enables the credentials of the endpoint device to be checked for compliance with the security policy before the device is granted access to network resources. This checking requires a security application called Cisco Trust Agent (CTA) to be installed on end devices that gather security state information and communicate it to access servers where policy decisions are made and eventually enforced on Cisco network access devices (such as routers and switches). Agentless HostsEnd devices that do not run CTA cannot provide credentials when challenged by network access devices (NADs). Such hosts are termed âagentlessâ or ânonresponsive.â In the Phase l release of Network Admission Control, agentless hosts were supported by either a static configuration using exception lists (an identity profile) or by using âclientlessâ username and password authentication on an ACS. These methods are restrictive and do not convey any specific information about the host while making policy decisions. EAPoUDP BypassYou can use the EAPoUDP Bypass feature to reduce latency of the validation of hosts that are not using CTA. If EAPoUDP bypass is enabled, the NAD does not contact the host to request the antivirus condition (the NAD does not try to establish an EAPoUDP association with the host if the EAPoUDP Bypass option is configured). Instead, the NAD sends a request to the Cisco Secure ACS that includes the IP address, MAC address, service type, and EAPoUDP session ID of the host. The Cisco Secure ACS makes the access control decision and sends the policy to the NAD. If EAPoUDP bypass is enabled, the NAD sends an agentless host request to the Cisco Secure ACS and applies the access policy from the server to the host. If EAPoUDP bypass is enabled and the host uses the Cisco Trust Agent, the NAD also sends a nonresponsive-host request to the Cisco Secure ACS and applies the access policy from the server to the host. Vendor-Specific Attributes for This FeatureThe following new attributes are supported for various RADIUS message exchanges: audit-session-idThe audit-session-id vendor-specific attribute (VSA) is a 32-byte string that uniquely identifies a host session. This identifier is generated by a NAD when the host is detected, and it remains the same until the session is deleted. Session revalidation or reinitialization does not change this identifier. Every time a session is detected, a new identifier is generated. This attribute is included in access requests to the authentication, authorization, and accounting (AAA) server and in web requests to the audit server. The value of this attribute is displayed in show eou command output (using the ip keyword). url-redirect-aclThe url-redirect-acl VSA string specifies the name of the access control list (ACL) for URL redirection. Any ingress HTTP from the host that matches the access list that is specified by this attribute is subjected to redirection to the URL address specified by the url-redirect VSA. The access list specified in this attribute has to be locally configured on the NAD as an âip access-list extendedâ named ACL. This attribute is specified only in RADIUS access-accept messages. The value of the url-redirect-acl attribute is displayed using the show eou command (with the ip keyword). How to Configure Network Admission Control Agentless Host SupportConfiguring a NAD to Bypass EAPoUDP Communication
SUMMARY STEPS
DETAILED STEPS Verifying Agentless Host and EAPoUDP BypassTo verify your configuration for Agentless Host and EOUoUDP Bypass, perform the following steps. The debug and showcommands can be used independently of each other. DETAILED STEPS Configuration Examples for Network Admission Control Agentless Host Support
RADIUS Message Exchange url-redirect-acl VSA ExampleShow Output Displaying the Value of a Newly Defined VSAThe following show eou command output displays EAPoUPD session cache information for a given IP address. The value of the newly defined VSA is also shown.
Router# show eou ip 10.0.0.1
Address : 10.0.0.1
MAC Address : 0001.027c.f364
Interface : FastEthernet1/0/3
AuthType : EAP
Audit Session ID : 000000001C8A6A330000001812000001
PostureToken : Infected
Age(min) : 444
URL Redirect : http://wwwin.cisco.com
URL Redirect ACL : RedirectACL
ACL Name : #ACSACL#-IP-Infected-42835ff7
User Name : NAC-DEV-PC-3:Administrator
Revalidation Period : 30000 Seconds
Status Query Period : 300 Seconds
Current State : AUTHENTICATED
Additional ReferencesMIBsTechnical Assistance
Feature Information for Network Admission Control Agentless Host SupportThe following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R) Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. |
|||||||||||||
|
|