Manuals / Enterasys Networks / Household Appliance / Plumbing Product

Enterasys Networks 9034385 manual

Models: 9034385

1 98

Download 98 pages 26.86 Kb

Page 2

Image 2

Page 2

Image 2

Contents

Design Guide Network Access ControlEnterasys Page Enterasys Networks, Inc 50 Minuteman Road Andover, MA Page Chapter 1 Overview ContentsAbout This Guide Chapter 2 NAC Deployment ModelsChapter 4 Design Planning Chapter 5 Design ProceduresChapter 3 Use Scenarios Figures TablesPage Related Documents About This GuideIntended Audience Getting Help Overview NAC Solution OverviewAuthentication Key FunctionalityAssessment AuthorizationDeployment Models RemediationModel 4 End-System Authorization with Assessment and Remediation Model 2 End-System AuthorizationModel 3 End-System Authorization with Assessment Model 1 End-system Detection and TrackingAuthorization with NAC Solution ComponentsAuthorization The NAC ApplianceNAC Gateway Appliance NAC Controller ApplianceThe NAC Controller is available in two models NAC Function Appliance ComparisonTable 1-2 Comparison of Appliance Functionality NAC GatewayNAC Gateway FeaturesTable 1-3 Comparison of Appliance Advantages and Disadvantages NAC ControllerFeatures NetSight ManagementNetSight NAC Manager NAC GatewayAssessment Server SummaryRADIUS Server NetSight ConsoleEnterasys offers two types of NAC appliances Summary 1-12 OverviewImplementation NAC Deployment ModelsModel 1 End-System Detection and Tracking Out-of-Band NACEnd-System and User Tracking Features and ValueInline NAC Layer IP-to-ID functionality for Security Information Management SIMTable 2-1 Component Requirements for Detection and Tracking Model 2 End-System AuthorizationRequired and Optional Components ComponentImplementation Inline NACAuthorization ‐ The NAC Gateway allocates the appropriate network resources to the end‐system based on device identity, user identity, and location. For Enterasys policy‐enabled edge switches, the NAC Gateway formats information in the RADIUS authentication messages that directs the edge switch to dynamically assign a particular policy to the connecting end‐system. For RFC 3580‐ capable edge switches, the NAC Gateway formats information in the RADIUS authentication messages in the form of RFC 3580 VLAN Tunnel attributes that directs the edge switch to dynamically assign a particular VLAN to the connecting end‐system. The NAC Gateway may deny the end‐system access to the network by sending a RADIUS Access‐Reject message to the edge switch or assign the end‐system a set of network resources by specifying a particular policy or VLAN to assign to the authenticated end‐system on the edge switch Out-of-Band NACFeatures and Value Location-Based AuthorizationDevice-Based Authorization User-Based Authorization MAC RegistrationAuthorization Table 2-2 Component Requirements for AuthorizationPost-Connect NAC integration with NetSight Automated Security Manager Required and Optional ComponentsImplementation Model 3 End-System Authorization with AssessmentModel 3 End-System Authorization with Assessment Out-of-Band NACInline NAC Extensive Security Posture Compliance Verification Features and ValueDiverse Security Posture Compliance Verification Authorization with Model 4 End-System Authorization with Assessment and RemediationTable 2-3 Component Requirements for Authorization with Assessment Required and Optional ComponentsImplementation Out-of-Band NACInline NAC Self-Service RemediationFeatures and Value Component Authorization withRequired and Optional Components Assessment andValue Table 2-5 Enterasys NAC Deployment ModelsDeployment Model SummaryScenario 1 Intelligent Wired Access Edge Use ScenariosAuthenticate Policy-Enabled EdgeSwitch Authentication3rd Party Switch RFC 3580 Capable EdgeScenario 1 Intelligent Wired Access Edge VLAN=QuarantineScenario 1 Implementation Scenario 2 Intelligent Wireless Access Edge Thin Wireless EdgeIntelligent Wireless AccessWireless VLAN=QuarantinePoint5 Thick Wireless EdgeAssessment Authentication 3-8 Use Scenarios Scenario 2 ImplementationScenario 2 Intelligent Wireless Access Edge Scenario 3 Non-intelligent Access Edge Wired and Wireless Layer 2 Wireless LAN Layer 3 Wired LANLayer 2 Wired LAN Figure 3-5 Non-intelligent Access Edge Wired and WirelessScenario 4 VPN Remote Access Scenario 3 ImplementationNAC Manager Figure 3-6 VPN Remote AccessScenario 4 Implementation 4 ControllerSummary and Appliance Requirements Table 3-1 Use Scenario SummariesUse Scenario SummarySummary and Appliance Requirements Table 3-1 Use Scenario Summaries continuedUse Scenario SummaryDesign Planning Identify the NAC Deployment ModelSurvey the Network 1. Identify the Intelligent Edge of the NetworkFigure 4-1 Network with Intelligent Edge Policy‐enabled Enterasys devices at the physical edge of the networkFigure 4-2 Network with Non-Intelligent Edge 2. Evaluate Policy/VLAN and Authentication ConfigurationCase #1 No authentication method is deployed on the network Case #2 Authentication methods are deployed on the network Overview of Supported Authentication MethodsSupport for Multiple End-System Connection Support of Multiple Authentication MethodsEnd-System Capabilities MAC AuthenticationAuthentication Support on Enterasys Devices Authentication Considerations3. Identify the Strategic Point for End-System Authorization Thick Wireless Deployments Wired LANWireless LAN 4. Identify Network Connection MethodsSite-to-Site VPN Remote Access WANThin Wireless Deployments Summary Remote Access VPNIdentify Inline or Out-of-band NAC Deployment Wired LAN Wireless LAN Remote Access WAN Site‐to‐Site VPN 1. Identify Required NetSight Applications Design ProceduresProcedures for Out-of-Band and Inline NAC 5-2 Design Procedures 2. Define Network Security DomainsProcedures for Out-of-Band and Inline NAC NAC Configurations Figure 5-1 Security DomainAssessment Figure 5-2 NAC ConfigurationAuthentication Authorization How health results are processed5-6 Design Procedures Figure 5-3 NAC Configuration for a Security DomainProcedures for Out-of-Band and Inline NAC Network Scenario Table 5-1 Security Domain Configuration GuidelinesSecurity Domain Configuration ExamplesNetwork Scenario Table 5-1 Security Domain Configuration Guidelines continuedSecurity Domain Configuration ExamplesNetwork Scenario Table 5-1 Security Domain Configuration Guidelines continuedSecurity Domain Configuration ExamplesNetwork Scenario Table 5-2 Security Domain Configuration Guidelines for AssessmentSecurity Domain Configuration ExamplesNetwork Scenario Security Domain ConfigurationProcedures for Out-of-Band and Inline NAC Examples3. Identify Required MAC and User Overrides MAC OverridesEnterasys NAC Design Guide Figure 5-4 MAC and User Override ConfigurationProcedures for Out-of-Band and Inline NAC Network Scenario Table 5-3 MAC Override Configuration GuidelinesSecurity Domain Configuration ExamplesNetwork Scenario Table 5-3 MAC Override Configuration Guidelines continuedSecurity Domain Configuration ExamplesSecurity Domain Configuration User OverridesTable 5-3 MAC Override Configuration Guidelines continued Network ScenarioAssessment Design Procedures 1. Determine the Number of Assessment Servers3. Identify Assessment Server Configuration 2. Determine Assessment Server LocationOut-of-Band NAC Design Procedures 1. Identify Network Authentication ConfigurationNAC Gateway Model 2. Determine the Number of NAC GatewaysTable 5-4 End-System Limits for NAC Gateways Concurrent End-Systems SupportedFigure 5-5 NAC Gateway Redundancy 3. Determine NAC Gateway Location 4. Identify Backend RADIUS Server Interaction 5. Determine End-System Mobility Restrictions8. Define NAC Access Policies 6. VLAN Configuration7. Policy Role Configuration Failsafe Policy and Accept Policy Configuration Assessment Policy and Quarantine Policy ConfigurationFigure 5-6 Policy Role Configuration in NetSight Policy Manager Assessment PolicyFigure 5-7 Service for the Assessing Role Quarantine Policy1. Determine NAC Controller Location Inline NAC Design ProceduresFigure 5-8 Service for the Quarantine Role Unregistered PolicyHowever, the closer the NAC Controller is placed to the edge of the network, the more NAC Controllers are required on the network, increasing NAC deployment cost and complexity. Conversely, when moving the NAC Controller towards the core of the network, fewer NAC Controllers are required, decreasing NAC deployment cost and complexity, but also decreasing the level of security NAC Controller Model 2. Determine the Number of NAC ControllersTable 5-5 End-System Limits for NAC Controllers Concurrent End-Systems SupportedFigure 5-9 Layer 2 NAC Controller Redundancy Figure 5-10 Layer 3 NAC Controller RedundancyFailsafe Policy and Accept Policy Configuration 4. Define Policy Configuration3. Identify Backend RADIUS Server Interaction Assessment Policy and Quarantine Policy ConfigurationNAC Deployment With NetSight ASM Additional ConsiderationsNAC Deployment With an Intrusion Detection System IDS Unregistered Policy5-34 Design Procedures Additional Considerations