Passive identification methods allow Aruba devices and ClearPass to classify devices without directly interacting with them. These techniques rely on observing traffic already being sent by the endpoint.
What is it?
When a device connects to the network and requests an IP address using DHCP, it sends certain fields called “Options.”
Option 55: Lists what DHCP parameters the device is asking for.
Option 60 (Vendor Class Identifier): Often contains the device manufacturer or operating system info.
How it's used:
By analyzing these options, Aruba ClearPass can guess the OS of the device — such as Windows 10, macOS, Android, etc.
Why it's useful:
Without any manual input, the network gets an idea of what kind of device is trying to connect.
What is a MAC OUI?
The first 24 bits (first 6 characters) of a device's MAC address identify the manufacturer — called the Organizationally Unique Identifier (OUI).
Example:
00:1A:79 = Apple
3C:5A:B4 = Hewlett Packard
Use case:
Helps ClearPass determine if a device is likely a laptop, printer, phone, etc., based on the vendor.
How it works:
Every operating system (OS) implements the TCP/IP stack a bit differently. Details like:
Time To Live (TTL)
Window size
TCP options (e.g., SACK, Timestamps)
can help fingerprint the OS.
Passive TCP fingerprinting:
Aruba switches or ClearPass Device Insight sensors can observe traffic and infer the OS without active probing.
In active classification, the network initiates interaction with the endpoint to get more precise information.
NMAP is a network scanner that can:
Discover open ports
Detect running services
Perform banner grabbing — reading service versions like “Apache 2.4.58” or “Windows SMB 3.0”
ClearPass OnGuard can be used to perform agent-based scans, checking the device’s behavior and service exposure.
Why use it?
Helps classify unknown or unmanaged devices more accurately (e.g., IoT, BYOD).
For managed devices like switches, printers, or cameras, SNMP can return:
sysDescr — describes the device (e.g., “HP LaserJet 4200”)
sysObjectID — a unique ID for the device model/firmware
ClearPass can poll these devices using SNMP to learn exactly what they are.
OnGuard is a ClearPass module that installs an agent (persistent or dissolvable) on endpoint devices.
It performs security posture checks such as:
Antivirus status
Operating system patch level
Disk encryption (e.g., BitLocker)
Firewall status (enabled/disabled)
Posture results are sent back to ClearPass for policy enforcement.
Once a device is identified and its trustworthiness is assessed, Aruba applies network access policies through dynamic roles.
CPDI is a cloud-hosted AI/ML engine.
It collects passive and active data to classify devices by type:
Learns from global behavior patterns and applies contextual classification.
Every device gets a risk score based on:
Device type and behavior
OnGuard posture results
Known vulnerabilities or suspicious traits
Score ranges:
0–49: Low risk (fully trusted)
50–79: Medium risk (limited access)
80–100: High risk (quarantine, alert)
High-risk devices are often assigned:
An isolated VLAN
Strict ACLs (block access to sensitive systems)
Lower QoS priority
ClearPass maps the endpoint to a user role using one or more conditions:
Device posture
Group membership (from Active Directory)
MAC address
Risk score
Location or time of day
Each role defines:
VLAN assignment
ACLs (what the device can access)
Bandwidth or QoS limits
Enforcement duration (e.g., limited-time access)
Downloadable Enforcement Profiles
These are policy bundles sent from ClearPass to switches, controllers, or gateways.
Automatically apply the correct role-based policy — no need to manually configure every switch.
ClearPass Profiler is a built-in service that passively identifies endpoints by observing:
DHCP options
MAC OUI
TCP/IP fingerprinting
SNMP responses
HTTP headers (for web-based devices)
ClearPass can automatically pull updated fingerprint definitions from Aruba’s cloud intelligence platform, enabling it to recognize:
New IoT device types
Uncommon embedded systems
Updated OS or firmware variants
Fingerprint library updates are periodically synced.
No manual signature tuning is needed.
Enables accurate classification even for zero-touch devices.
This ensures device recognition remains accurate over time, strengthening identity-based policy enforcement without requiring human reconfiguration.
ClearPass OnGuard evaluates endpoint posture using dissolvable or persistent agents. Based on the result, it assigns the appropriate role and access scope.
Antivirus installed and running
Disk encryption (e.g., BitLocker)
Firewall enabled
OS patch level up-to-date
| Posture Result | Assigned Role | Action Taken |
|---|---|---|
| Healthy | corp-user |
Access to full enterprise VLAN + ACLs |
| Warning | restricted-user |
Access to remediation portal only |
| Failed | quarantine |
Placed into VLAN 999, no LAN access |
Enforcement Profile: "Quarantine Profile"
→ VLAN: 999
→ ACL: deny_all
→ CoA: reauth
This approach ensures that only compliant, trusted devices can reach corporate services, while non-compliant ones are automatically isolated.
Change of Authorization (CoA) is a RADIUS protocol extension that allows ClearPass to change an endpoint’s access permissions mid-session, without disconnecting or requiring manual intervention.
Device connects and authenticates (via 802.1X or MAB)
ClearPass assigns an initial role (e.g., unknown)
After additional evaluation (e.g., OnGuard result, device behavior):
ClearPass sends a CoA request to the switch or gateway
Device session is re-evaluated and new role/VLAN/ACL is applied
Upgrade from guest to employee after login via captive portal
Downgrade from corp-user to restricted if risk score increases
Automatically bounce the port for devices violating security posture
Policy Action:
IF Risk Score > 80 THEN
→ Role = "High-Risk"
→ Send CoA to reauthenticate + isolate
show port-access clients detail
| Topic | Purpose |
|---|---|
| Profiler Service Updates | Keeps fingerprint matching accurate and up to date via cloud syncing |
| Posture-Based Role Assignment | Enforces VLAN/ACL/QoS policies based on antivirus/firewall/patch status |
| Change of Authorization (CoA) | Enables real-time dynamic role/VLAN updates based on policy/risk shifts |
How does Aruba ClearPass automatically classify endpoints in a campus network?
ClearPass classifies endpoints by collecting device attributes from multiple network sources and matching them against profiling rules.
ClearPass uses profiling collectors to gather information about connected devices. These attributes may come from DHCP requests, MAC address prefixes, SNMP queries, HTTP user-agent strings, or authentication data. Once collected, ClearPass compares the attributes against predefined profiling rules or fingerprint databases to determine the device type, operating system, and category. This classification allows administrators to enforce network access policies based on device identity, such as granting different access levels to printers, laptops, or IoT devices. Endpoint profiling is a key component of Network Access Control (NAC) because it enables automated enforcement of security policies across both wired and wireless networks.
Demand Score: 86
Exam Relevance Score: 90
Why might some endpoints fail to be classified by the ClearPass Endpoint Profiler?
Endpoints may fail to be classified if ClearPass does not receive enough identifying attributes.
Device profiling depends on attributes collected from the network. If the endpoint uses static IP addressing, does not send DHCP options, or hides identifying information, ClearPass may not receive sufficient data to determine the device type. Misconfigured profiling collectors or missing integrations with network devices can also prevent attribute collection. For example, if RADIUS device profiling or network device configuration is incorrect, the profiler might fail to retrieve attributes such as device name or operating system family. Community discussions frequently highlight cases where profiling fails because the required data sources were not properly configured or the device simply does not expose enough identifiable information.
Demand Score: 83
Exam Relevance Score: 88
What role does DHCP information play in endpoint profiling within ClearPass?
DHCP information provides device attributes that help identify and classify endpoints.
When a device connects to the network, it typically sends DHCP requests containing options such as vendor class identifiers, hostnames, and parameter request lists. ClearPass can analyze these DHCP attributes to identify the device type or operating system. For example, certain DHCP fingerprints correspond to specific device categories such as Windows laptops, printers, or IoT devices. Administrators often integrate DHCP servers with ClearPass to forward these attributes for profiling. Community discussions frequently mention DHCP-based profiling as a key mechanism for improving device classification accuracy in NAC deployments.
Demand Score: 80
Exam Relevance Score: 86
Why is endpoint classification important in campus network security?
Because it allows the network to enforce different access policies based on device identity and risk level.
Not all devices should have the same level of network access. Endpoint classification allows security systems like ClearPass to identify whether a device is a corporate laptop, personal device, printer, or IoT sensor. Once classified, the network can apply appropriate policies such as VLAN assignment, role-based access, or restricted connectivity. For example, a printer might only need access to print servers, while a corporate laptop may require broader network access. By identifying and categorizing devices automatically, organizations reduce security risks and prevent unauthorized or unmanaged devices from accessing sensitive resources.
Demand Score: 78
Exam Relevance Score: 91