Enterasys Networks 9034385 Features and Value, Inline NAC Layer, End-System and User Tracking

Page 24

Model 1: End-System Detection and Tracking

RADIUS Access‐Accept or Access‐Reject message received from the upstream RADIUS server, is returned without modification to the access edge switch, to permit end‐system access to the network. For MAC authentication, a RADIUS Access‐Accept message is returned to the access edge switch without modification, based on a RADIUS Access‐Accept message received from the upstream RADIUS server or local authorization of MAC authentication requests. The authenticating end‐system is provided access to the network based on the configuration of the access edge switch.

Inline NAC (Layer 2)

For inline NAC utilizing the Layer 2 NAC Controller, an end‐system can be detected in multiple ways. An end‐system can be detected simply by transmitting data traffic not previously seen by the NAC controller. In this case, the traffic is forwarded through the NAC Controller to the traffic destination, and has no impact on the connectivity of the end‐system. In another method, end‐ systems are detected with the authentication of downstream end‐systems via 802.1X, web‐based, and/or MAC authentication on the NAC Controller. These authentication requests may or may not be proxied upstream depending on the NAC configuration.

Inline NAC (Layer 3)

For inline NAC utilizing the Layer 3 NAC Controller, an end‐system is detected simply by transmitting data traffic sourced from an IP address not previously seen by the NAC controller. The traffic is forwarded through the NAC controller to the traffic destination, and has no impact on the connectivity of the end‐system.

Features and Value

There are two key pieces of functionality and value propositions supported by Model 1:

End-System and User Tracking

Model 1 supports the ability to track end‐systems by MAC address, as the device moves from switch port to switch port, and map the device identity to its IP address every time it connects. Furthermore, the associated user can also be mapped to the device and IP address, as long as a username‐based authentication method (802.1X or web‐based authentication) or MAC Registration is implemented with the NAC Gateway, or if end users are configured to login to a Microsoft Windows domain with the NAC Controller using Kerberos snooping functionality.

Using these methods, the Enterasys NAC solution can identify who, what, when, and where devices and users connect to the network. This information is maintained centrally in the NetSight NAC Manager database, providing important historical data that can be used for auditing or troubleshooting purposes. In addition, this information can be easily searched to identify which port a particular user is currently connected to on the network, or which device is currently allocated a particular IP address. This binding (IP address, MAC address, username, location), which is maintained over time for each end‐system, is useful for compliance and auditing purposes, and for planning the subsequent rollout of the next NAC deployment model.

IP-to-ID functionality for Security Information Management (SIM)

This NAC deployment model enables SIM systems such as the Enterasys Dragon Security Command Console (DSCC), to display user‐focused information about assets on the network. Traditionally, SIM systems yield device‐focused information (such as IP address) about detected network threats, through the correlation, normalization, and prioritization of events

2-2 NAC Deployment Models

Page 23 Page 25
Image 24
Page 23 Page 25
Contents Enterasys Page Page Page Contents Design Procedures Use ScenariosDesign Planning Figures TablesPage Intended Audience Related DocumentsGetting Help Support@enterasys.comNAC Solution Overview AuthenticationKey Functionality DetectionAuthorization Deployment ModelsAssessment RemediationModel 2 End-System Authorization Model 3 End-System Authorization with AssessmentModel 1 End-system Detection and Tracking NAC Solution Components NAC ApplianceNAC Gateway Appliance NAC Controller ApplianceNAC Controller is available in two models Appliance Comparison NAC Gateway NAC ControllerDisadvantage Advantage NetSight Management NetSight NAC ManagerSummary Radius ServerAssessment Server Summary Summary Overview Model 1 End-System Detection and Tracking ImplementationOut-of-Band NAC Features and Value Inline NAC LayerEnd-System and User Tracking Model 2 End-System Authorization Required and Optional ComponentsInline NAC Location-Based Authorization Device-Based AuthorizationUser-Based Authorization MAC RegistrationComponent Requirements for Authorization Model 3 End-System Authorization with Assessment Inline NAC Extensive Security Posture Compliance Verification Diverse Security Posture Compliance Verification Component Requirements for Authorization with Assessment Implementation Self-Service Remediation Required and Optional Components Enterasys NAC Deployment Models Value Scenario 1 Intelligent Wired Access Edge Use ScenariosPolicy-Enabled Edge NAC FunctionsRFC 3580 Capable Edge VLAN=ProductionScenario 1 Implementation Scenario 2 Intelligent Wireless Access Edge Thin Wireless EdgeRemediation Web User Laptop Thick Wireless Edge Scenario 2 Implementation Scenario 3 Non-intelligent Access Edge Wired and Wireless Layer 2 Wired LAN Scenario 4 VPN Remote Access Scenario 3 ImplementationVPN Remote Access Enterasys Scenario 4 ImplementationUse Scenario Summaries Summary and Appliance Requirements VPN remote access Design Planning Identify the NAC Deployment ModelSurvey the Network Identify the Intelligent Edge of the NetworkNetwork with Intelligent Edge Evaluate Policy/VLAN and Authentication Configuration Case #1 No authentication method is deployed on the networkCase #2 Authentication methods are deployed on the network Overview of Supported Authentication MethodsSupport of Multiple Authentication Methods End-System CapabilitiesSupport for Multiple End-System Connection Authentication Support on Enterasys Devices Authentication ConsiderationsIdentify the Strategic Point for End-System Authorization Wired LAN Wireless LANThick Wireless Deployments Identify Network Connection MethodsRemote Access WAN Thin Wireless DeploymentsSite-to-Site VPN Remote Access VPN Identify Inline or Out-of-band NAC DeploymentSummary Procedures for Out-of-Band and Inline NAC Identify Required NetSight ApplicationsDefine Network Security Domains NAC Configurations Security DomainNAC Configuration Authorization NAC Configuration for a Security Domain Procedures for Out-of-Band and Inline NAC To the network Procedures for Out-of-Band and Inline NAC Procedures for Out-of-Band and Inline NAC Security Domain Configuration Guidelines for Assessment Identify Required MAC and User Overrides MAC OverridesMAC and User Override Configuration Procedures for Out-of-Band and Inline NAC Procedures for Out-of-Band and Inline NAC User Overrides Assessment Design Procedures Determine the Number of Assessment ServersIdentify Assessment Server Configuration Determine Assessment Server LocationOut-of-Band NAC Design Procedures Identify Network Authentication ConfigurationDetermine the Number of NAC Gateways NAC Gateway Redundancy Determine NAC Gateway Location Identify Backend Radius Server Interaction Determine End-System Mobility RestrictionsVlan Configuration Policy Role ConfigurationDefine NAC Access Policies Failsafe Policy and Accept Policy Configuration Assessment Policy and Quarantine Policy ConfigurationPolicy Role Configuration in NetSight Policy Manager Assessment PolicyService for the Assessing Role Quarantine PolicyInline NAC Design Procedures Determine NAC Controller LocationUnregistered Policy Inline NAC Design Procedures Determine the Number of NAC Controllers Layer 2 NAC Controller Redundancy Define Policy Configuration Additional Considerations NAC Deployment With an Intrusion Detection System IDSNAC Deployment With NetSight ASM Additional Considerations Design Procedures
Top Page Image Contents