Skip to main content
Segmentation & Zero Trust

Device Segmentation With Aruba ClearPass: What Does ORDR Add?

Device segmentation on Aruba works best when you know each device. See how ORDR adds device context to ClearPass and Central so your team can build and test access policy.

If you already use Aruba Central and ClearPass for access control and device segmentation, you may be asking a straightforward question: What does ORDR add?

HPE Aruba Networking ClearPass Policy Manager (ClearPass) gives you a way to make and enforce network access decisions. HPE Aruba Networking Central (Central) helps you understand and manage the Aruba network those devices connect to. ORDR adds detailed information about the connected devices themselves, their risk, and the systems they communicate with. Together, those capabilities help you write more informed access policies and put them to work through the infrastructure you already use.

I spent years working with network access control before joining ORDR. One challenge came up again and again: the network could enforce access, but identifying a device’s true attributes and designing a detailed policy for where and how it should connect took too long to investigate, build, and deploy. Here is how I think about the integration and the questions I hear most often.

Does ORDR replace ClearPass?

No. ClearPass remains the system that enforces network access. ORDR gives ClearPass additional device context to use in its decisions and helps teams create policies based on observed device behavior.

A DHCP fingerprint might tell you an endpoint is a Windows computer. ORDR can add a more detailed device profile, operating system information, risk information, and other attributes gathered from its discovery and connected data sources. Those attributes can inform a ClearPass policy alongside the information you already use.

For connected medical, operational, and other devices that cannot be assessed like a managed laptop, that additional context can be especially valuable. You need to know more than whether a device authenticated. You need to know what it is and whether its access makes sense.

What does Aruba Central contribute?

Central provides network context: which switch and port a device uses, how it is connected, and which role or VLAN it has been assigned. ORDR brings that information into the device view alongside its own discovery data and information from ClearPass.

That matters when you are trying to answer a practical question such as, “Where is this device connected right now?” In environments using Aruba user-based tunneling, Central can also provide the assigned VLAN, which may differ from the tunnel VLAN visible through a basic switch query. Seeing the actual assignment helps you assess the device’s access more accurately.

ORDR brings Aruba Central network details and ClearPass access information into the device view.

How do you get from device visibility to a policy?

Start with a group of devices that should have similar access. ORDR lets you review the destinations and ports those devices communicate with, then use those observed flows as a starting point for an access policy.

You can inspect the proposed rules, account for a known destination that has not yet appeared in the traffic data, and review or simulate the policy before sending it to ClearPass. The network and device owners still decide what access is appropriate. ORDR helps them get to a policy they can examine and refine, rather than starting with a blank page.

ORDR IQ can also suggest where to start with a policy, drawing on observed network flows and best-practice guidance. Your team can review those suggestions against the device’s intended use before deciding what to enforce.

This is particularly useful when a broad rule feels risky but a restrictive rule could interrupt a clinical or operational workflow. Observed communication gives the team evidence for a more precise decision.

Can this help if our network is not segmented yet?

Yes. A sensible first step is to understand where devices sit today. ORDR can show how device types and groups are distributed across VLANs, including places where workstations, servers, security equipment, or connected devices share the same network segment.

A breakdown of device groups by VLAN helps teams identify where to investigate access first.

A mixed VLAN does not automatically tell you which rule to deploy. It tells you where to investigate. From there, you can identify a device group, study its communication, and decide whether a new access policy would reduce unnecessary connectivity without disrupting the work that depends on it.

For organizations with multiple sites, this gives security and network teams a common view of where to begin.

What happens when a device becomes risky or needs to be removed?

ORDR can send device attributes to ClearPass for policy decisions and can initiate a quarantine action when your team decides a device should be restricted. ClearPass handles the change of authorization and enforces the resulting access policy on the network. ORDR can also support rules based on conditions such as a device being marked for decommissioning or behaving outside an established baseline.

You can choose which actions need human review and which are appropriate to automate. When a device is ready to return, the block can be removed so ClearPass can reassess its access.

What if we also use other network vendors?

Many organizations have a mix of Aruba and other infrastructure. ORDR can use device and traffic information across that environment and support policy workflows for different enforcement points. The exact integration and policy format depend on the products and versions in use, so I would map that out with your network team rather than assume one configuration fits every site.

The goal is to make use of the enforcement tools you have while keeping device context and policy decisions consistent.

Where should you start with device segmentation?

Pick one device group whose access is hard to explain today. Find out what those devices are, where they connect, and which systems they need to reach. Compare that with the access they currently have. Then review a proposed policy with the people who own the devices and the network before you enforce it.

That exercise gives you a concrete answer to the question behind most segmentation projects: Do we know enough about these devices to give them the access they need, and no more?

If you use Aruba Central, ClearPass, or both, book a policy test session (opens in a new tab) with the ORDR team. We’ll follow one of your device groups from discovery to a tested access policy, on your own data.

Found this useful? Share it.