EMAIL SUPPORT

dclessons@dclessons.com

LOCATION

US

ISE Building blocks & Design

ISE Building blocks & Design

ISE Solution Components:

There are three ISE solution components to complete Cisco ISE Design Architecture.

  • Infrastructure Components
  • Policy Components
  • Endpoint Components

Infrastructure Components:

Devices such as Wireless, WLC, Switches, Routers, Firewall, VPN, AD, LDAP etc which uses ISE to create secure access infrastructure. Full ISE functionality on both Cisco and Non-Cisco devices are supported in ISE2.0 version.

Below is feature to functionality mapping that ISE uses.

Below table shows partial mapping of ISE supported devices to ISE features and it also states the minimum OS levels for each devices that to be used with ISE.

In the above table! Stands for Limited support.

Policy Components:

Cisco ISE provides access control management on Wire, Wireless and Context based environment. Policy components can be spanned in following areas.

  • ISE checks and determines that user accessing network are authorized and have policy compliant device.
  • ISE establish user identity, location, access-history, for compliance and reporting
  • ISE assigns policy and service based on user host and user context example assigns user to role, AD group, location, device type.
  • ISE allows authenticated users to access specific segments of network or specific applications, services or both.

Endpoint Components:

Endpoint are those identity that access the network , access the application  and services  and for this they authenticates to ISE using 802.1X, MAB , Easy Connect  or web authentication.

Following are recommended Endpoint components:

802.1X supplicant/agents: A suppliant is built on Windows or Mac OS X and is just software that understand how to communicate via EAPoL (Extensible Authentication protocol over LAN). Supplicant is also available via Cisco AnyConnect or via any other third party suppliant software agents. Some suppliant is in build with certain hardware like IP phone, Video equipment, printers.

Cisco AnyConnect Compliance Module: With the help of this module all windows , Mac OS X , Linus systems provides host posture information to ISE like antivirus installed  status, OS patching , presence of registry keys.

ISE Personas:

ISE can be deployed in two mode:

  • Standalone deployment mode : In this all Personas are on a single ISE appliance or a pair of ISE appliance
  • Distributed deployment mode: Personas are spread out and dedicated to just particular ISE appliances.

ISE has three personas and each personas type ISE node determines that service it provides.

Administration:

  • It allow to perform all administrative operation in standalone or distributed ISE deployment
  • It provides a single pane of glass for management and all system related and policy-based configuration can be done from this Personas
  • In distributed deployment model, it can be single ISE or can be in HA pair of nodes running administration Persona.
  • The ISE node working as administration Personas is called as Policy Administration Node(PAN)

Policy Service:

This Personas type has following features:

  • It provides network access, posture, guest access and client provisioning, web portals and profiling services Policy service Personas can be deployed in more than one node and when it has dedicated ISE node then it is referred as Policy Service Node (PSN)
  • In Distributed environment, PSN can be more than one node and can be geographically separated to each other.

Monitoring:

Monitoring Personas helps in log collector, and store logs from PAN and PSN.

  • This Personas provides advances monitoring and troubleshooting tools and is referred as Monitoring & Troubleshooting node (MnT)
  • ISE allow only to have maximum of two nodes with this personas and both can take primary or secondary role for HA.
  • Both node captures logs and if primary fails secondary automatically becomes primary monitoring node.

Below is the architecture which shows how these personas and node type look logically and here only primary connection are shown.

GENERAL FAQ

As you'll see, the architecture of Cisco ISE is based around 3 pieces: Infrastructure, Policy, and Endpoints. Devices such as switches, routers, firewalls, and controllers are in the category of Infrastructure. Authentication, authorization, and access control are policy components. Endpoints refer to the user devices that are connecting to the network and authenticating with ISE.

ISE leverages policy elements to determine who and what is connecting to the network, including where they’re connecting from and which type of device they are using. In this context, ISE enforces certain policies defining what resources users or devices are allowed to access.

Endpoints, such as the laptops, phones, printers, or IP phones that are attempting to access the network. They are authenticated to ISE by enrolling or using mechanisms such as 802.1X, MAB, Easy Connect, or web authentication. Each endpoint's compliance is confirmed by ISE before access is granted.

A Persona describes the function that a Cisco ISE node fulfills in the deployment. The three profiles are Administration, Policy Service, and Monitoring. Configuration and policy are controlled by Administration, user access and posture checks are performed by Policy Service, and logs and reports are taken care of by Monitoring. Between them, these are the workhorses of ISE's distributed architecture.

There are four major collections of Cisco ISE services that are organized into personas, each with different functions within the Cisco ISE Architecture. These personas include: the Administration persona, Policy Service persona, Monitoring persona, and pxGrid persona. Personas may be collocated on a single node or distributed across multiple nodes.

1. Administration persona: This is the control center, the user interface for licensing and policy configuration. The Administration persona pushes configurations out to other nodes in a distributed deployment and is often referred to as the Admin node.

2. Policy Service persona: This is the engine that processes all Cisco ISE-related network messaging: DHCP, Cisco Discovery Protocol, NetFlow, and RADIUS, among others. Nodes that implement this persona are referred to as Policy Service nodes.

3. Monitoring persona: This is the engine for collecting and correlating logs and report data. It generates reports and alarms for the Cisco ISE system. Nodes that implement this persona are referred to as monitoring nodes.

4. pxGrid persona: This enables the sharing of context-based information from a Cisco ISE session directory to other network systems, such as Cisco Secure Firewall. You can use the pxGrid framework to exchange policy and configuration data between nodes. This data includes sharing tags and policy objects between Cisco ISE and third-party vendors for non-ISE-related information exchanges, such as threat information. Use of the pxGrid service is available with the Advantage and Premier licenses.

 

In a centralized deployment, all personas run on one or two ISE nodes. It’s more basic but meant for small places. In distributed deployment, each persona is deployed on independent dedicated hosts for a more scalable, efficient, and resilient solution.

The initial state of a Cisco ISE node immediately after installation is standalone mode. In this mode, all personas run on a single Cisco ISE node. This deployment model lacks fault tolerance and has limited scalability. It has a maximum of 2000 endpoints, regardless of the physical hardware on which it runs.

 

Yes, it does. From ISE 2.0 onward, full functionality is available for both Cisco and non-Cisco devices, but they must be compliant with the required OS and feature compatibility levels.


Comment

    You are will be the first.

LEAVE A COMMENT

Please login here to comment.