Cisco SISE (300-715) – Complete Study Guide
1.0 Architecture and Deployment
Cisco Identity Services Engine (ISE) is deployed using different personas. The Policy
Administration Node (PAN) is responsible for system configuration, policy definition, and GUI
access. The Policy Service Node (PSN) handles authentication, authorization, and accounting
(AAA) requests. The Monitoring and Troubleshooting Node (MnT) collects logs, reports, and
troubleshooting data. Deployment models include standalone (used mainly for labs or small
environments), distributed deployments (recommended for production), and high availability
setups with primary and secondary PANs. Scalability is achieved by adding PSNs, while
redundancy is provided through PAN and MnT replication. Cisco ISE can be deployed as a
physical appliance or as a virtual machine on supported hypervisors. Performance depends on
CPU, RAM, disk resources, and the number of endpoints. Zero-Touch Provisioning (ZTP)
allows automatic deployment using DHCP, DNS, and bootstrap configuration files.
2.0 Policy Enforcement
Policy enforcement is the core function of Cisco ISE. Identity stores supported include Active
Directory, LDAP, local user databases, Public Key Infrastructure (PKI), SAML Identity
Providers, and REST-based identity sources. Active Directory is the most common choice and
supports both user and machine authentication. IEEE 802.1X is used for secure network
access control. The authentication flow involves a supplicant (endpoint), an authenticator
(switch or wireless controller), and the authentication server (ISE). Wired access uses IBNS
2.0 with Monitor Mode, Low Impact Mode, and Closed Mode, with Closed Mode being the most
secure. Wireless access relies on 802.1X through a Wireless LAN Controller. MAC
Authentication Bypass (MAB) is used for non-802.1X capable devices such as printers and IP
phones. Cisco TrustSec uses Security Group Tags (SGTs) to enforce role-based access
policies independent of IP addressing. Authentication policies determine identity, while
authorization policies define network access using VLANs, ACLs, downloadable ACLs, or
SGTs.
3.0 Web Authentication and Guest Services
Web Authentication is used when endpoints do not support 802.1X. Users are redirected to a
web portal to authenticate before gaining network access. Cisco ISE supports Central Web
Authentication and Local Web Authentication. Guest Services allow temporary network access
for visitors. Components include the Guest Portal, Sponsor Portal, and Guest Accounts.
Sponsors can create, approve, and manage guest credentials according to defined policies.
4.0 Profiler
The Cisco ISE Profiler service automatically identifies endpoints based on observed network
behavior. Profiling probes include DHCP, RADIUS, SNMP, HTTP, and NetFlow. Change of
Authorization (CoA) allows ISE to dynamically reapply policies without requiring the user to
reconnect. Endpoint Identity Management maintains a consistent identity for each endpoint
across the network.
5.0 BYOD
Bring Your Own Device (BYOD) allows personal devices to securely access the enterprise
network. The BYOD onboarding flow starts with limited access, followed by redirection to a
portal, certificate installation, and full network access. Cisco ISE can function as an internal
Certificate Authority (CA) to issue certificates for EAP-TLS authentication. Block lists and allow
lists control which devices are permitted or denied access.
6.0 Endpoint Compliance
Endpoint Compliance, also known as posture assessment, verifies that devices meet security
requirements before granting access. Compliance checks include antivirus status, firewall
enablement, and operating system patch levels. Cisco Secure Client is commonly used as the
posture agent and can operate in persistent or temporary modes. The posture process
involves the supplicant, authenticator, and authentication server working together.
7.0 Network Access Device Administration
Cisco ISE also provides centralized administration for network devices. RADIUS is used
primarily for network access authentication and operates over UDP. TACACS+ is used for
device administration, operates over TCP, and supports command-level authorization. Using
TACACS+, administrators can control which commands users are allowed to execute on
routers and switches.