# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Dell Powerconnect W--clearpass Hardware Appliances W-clearpass Policy Model

Summary

This is an introduction to Dell Networking W-ClearPass Policy Manager 6.0, explaining the policy model and authentication services architecture. The document covers the services paradigm, authentication methods, policy components, and flow of control for network access management. It is intended for network security administrators and IT architects designing enterprise network access control policies using ClearPass Policy Manager.

📄 Preview 📖 Table of Contents Contents PAGE OF 4

Page 1 Text Content

Dell Networking W-Clear Pass Policy Model 6.0 An Introduction

From the point of view of network device or other entities that need authentication services, Policy Manager appears as RADIUS, TACACS+ or Web Authentication server; however, its rich and extensible policy model allows it to broker security functions across range of existing network infrastructure, identity stores, health/posture services and client technologies within the Enterprise.

Services Paradigm Services are the highest level element in the Policy Manager policy model. They have two purposes: Unique Categorization Rules (per Service) enable Policy Manager to test Access Requests ("Requests") against available Services to provide robust differentiation of requests by access method, location, or other network vendor-specific attributes. NOTE: Policy Manager ships configured with number of basic Service types. You can flesh out these Service types, copy them for use as templates, import other Service types from another implementation (from which you have previously exported them), or develop new Services from scratch.

By wrapping specific set of Policy Components, Service can coordinate the flow of request, from authentication, to role and health evaluation, to determination of enforcement parameters for network access. Figure 1: Dell Networking W-Clear Pass Policy Manager Flow of Control and Table 1: Policy Manager Service Components illustrate and describe the basic Policy Manager flow of control and its underlying architecture.

0511287-01 Mar

Page Summary Contents For Dell Powerconnect W--clearpass Hardware Appliances W-clearpass Policy Model

Page 1 Dell Networking W-Clear Pass Policy Model 6.0 An Introduction From the point of view of network device or other entities that need authentication services, Policy Manager appears as RADIUS, TACACS+ or...
Page 2 Figure 1: Dell Networking W-Clear Pass Policy Manager Flow of Control Table 1: Policy Manager Service Components Component Service: Description component ratio Authentication Method Zero or more per E...
Page 3 Component Service: Description component ratio Some Services (for example, TACACS+) contain internal authentication methods; in such cases, Policy Manager does not make this tab available. Authenticat...
Page 4 Component Service: Description component ratio installed agent, or which cannot respond to Policy Manager interactions. Audit servers typically operate in lieu of authentication methods, authenticatio...

Manual Details

Brand Dell
Pages 4
File Size 184.06 KB
Published July 01, 2026
4 views

Enter the captcha to get the download link:

captcha

Frequently Asked Questions

What services can PolicyManager use to identify and differentiate access requests?

Unique Categorization Rules (per Service) allow PolicyManager to test Access Requests against available Services.

How does a service coordinate the process of assigning network access parameters?

By wrapping specific policy components, a Service can coordinate the flow from authentication through role/health evaluation to determining enforcement parameters.

What types of identity repositories can PolicyManager use for verification?

It supports Microsoft Active Directory, any LDAP compliant directory, RADIUS-based token servers (like RSA), SQL databases, or Static Host Lists.

What is the purpose of an AuditServer in a network access framework?

An AuditServer evaluates the health of clients that do not have an installed agent or cannot respond to PolicyManager interactions.