EMAIL SUPPORT

dclessons@dclessons.com

LOCATION

US

Authentication & Authorization Policies

Authentication & Authorization Policies

Policy Set Enablement

AN Authorization policy can only be created once Authentication policy are in place. A policy set consist of separate pair of Authentication and Authorization rule for each use cases.

To see Policy Set, Refer below path on ISE.

Policy| Policy Set

On the last, there is default policy, Click in default policy set, to see and verify the authentication and authorization policies.

Below is the process , how policies are evaluated , as in figure Once RADIUS request are being made, and particular Policy Set is invoked , first authentication policy then authorization policy are processed to provide Result.

Authentication Policy Goals

Below are some goals that can be achieved by authentication Policy.

  • To identify if the identity credential is valid or not.
  • It drops incoming request who are not allowed
  • It routes authentication request to correct identity store.
  • Validate the identity
  • Passes successful authentication request to the authorization Policy.

Authentication Policies Overview

Here we will see deep dive concepts about authentication policies. To go to authentication policy use following path:

  • From the ISE GUI, navigate to Work Centers | Network Access | Policy Sets or Policy | Policy Sets
  • A Basic Authentication policy rules are logically organize in following manner.
  • IF conditions THEN ALLOW PROTOCOLS IN AllowedProtocolList
  • AND CHECK THE IDENTITY STORE IN LIST IdentityStore
  • In Authentication Policy, Rules are evaluated from top to bottom, the moment Match is found the evaluation is stopped else it will move to next rule.

Conditions: To understand this lets take an example, picturized below.

Condition checks if the user is Wired MAB or Wireless MAB, if yes then it will allow certain protocols defined. If Authentication success it will send to authorization policy else it will go to explore further options. 

Navigate to Work Centers | Network Access | Policy Elements | Conditions | Smart Conditions

Select the Wired_MAB

Here you can see, Condition Wired_MAB is mapped to different dictionary attributes per network device vendor.

For Cisco, the condition is looking for the RADIUS NAS-Port-Type to be Ethernet and Service-Type to be Call Check. These attributes are notified by RADIUS authentication packet to ISE, which indicates that this is MAB request from Switch.

Each different vendor has different attributes, and in order to see different vendor mapping, click on network device vendor name.

Now to see about Wireless MAB conditions,

 

GENERAL FAQ

Authentication, you attempt to identify who the user or device is; with authorization, you determine what they can do once logged in. In other words, Authentication verifies the identity; Authorization grants network access rights.

Authentication policies ensure only legitimate users or devices can connect. Authorization policies, then, decide what kind of access they receive. Together, they secure the network and make sure users are being granted the proper permissions automatically.

When a RADIUS request is received, ISE processes the authentication policy first. If the user or device clears that check, it then goes to authorization. This takes place from the top down; once a rule matches, evaluation breaks off at that point.

An authentication policy authenticates credentials, determines which identity store (such as Active Directory or the internal database) to use for subsequent processing, and denies any requests that are not allowed. If the authentication is successful, it passes on the request to the authorization policy.

Conditions are the logic tests to determine who to wire and wirelessly. These conditions are based on RADIUS packet attributes, like NAS-Port-Type or Service-Type, which inform ISE what it is looking at with regard to the access request.

ISE interprets the authentication conditions in its own way per vendor. As an example, Cisco devices may be using Ethernet-based attributes, or those could be defined differently by another vendor. This flexibility allows ISE to accommodate heterogeneous vendor environments without disrupting policy logic.


Comment

    You are will be the first.

LEAVE A COMMENT

Please login here to comment.