Elisity Release 26.9: Wider infrastructure coverage, risk context that drives policy, and a fuller Zero Trust Posture

Elisity Release 26.9 extends policy to Aruba AOS-S, adds plant-floor visibility for Rockwell Automation Stratix, lets Rapid7 InsightVM and Tanium data define Policy Groups, and widens Zero Trust Posture scoring.

Overview

No enterprise network is built from a single catalog. Acquisitions bring their own switching. Refresh cycles leave two generations of hardware side by side. Plant floors run industrial switches chosen by the controls team, not by IT. And on top of the infrastructure sits a second estate: the vulnerability scanners and endpoint management platforms that each know something important about a device and cannot, on their own, control who reaches it.

A microsegmentation program has to work across both. If policy covers only the parts of the network that match one vendor’s reference design, the gaps are exactly where an attacker will move. If the risk data an organization already pays for never reaches the policy model, the people writing policy are working with less information than the people running the scanner.

Release 26.9 widens both, and gives leadership a better way to measure the result. More of the network infrastructure customers already own is now in scope, from Aruba AOS-S access switches to Rockwell Automation Stratix on the plant floor. Rapid7 InsightVM and Tanium data can now define the Policy Groups that policy is written against. And the Zero Trust Posture score now reflects more of the estate, more consistently.

More of the Network You Already Own: Aruba and Stratix

Elisity enforces policy through the infrastructure customers already run: Elisity Virtual Edge programs existing switches out-of-band with identity-based device groupings and policies, and the switch enforces natively. Every platform that model reaches is one more part of the network that can be brought under least-privilege policy without new hardware.

Aruba AOS-S. Elisity now supports policy enforcement on Aruba AOS-S 2530, 2920, 2930, and 3810 switches, with automated onboarding, endpoint discovery, and flow telemetry. Organizations running both Aruba AOS-S and Aruba CX manage them the same way, from the same Cloud Control Center, alongside every other supported platform. For many enterprises, AOS-S is the access layer that has been in the wiring closet for years. It can now take part in identity-based policy as it stands.

Rockwell Automation Stratix. Stratix switches can now be onboarded as visibility nodes. They enrich Elisity IdentityGraph™ with VLAN, interface, and topology data for the devices connected to them; they do not enforce policy or change the switch’s configuration. On a plant floor, that context is what matters. Stratix switches often sit at the line level, and knowing exactly which assets are connected to each line is what makes it possible to write policy, enforced upstream, that keeps one line’s problem from becoming the next line’s outage.

Mixed infrastructure is the normal state of an enterprise network, not a phase it passes through. One policy model across all of it means a switch migration, an acquisition, or a new plant does not reset the microsegmentation program.

Rapid7 InsightVM and Tanium: Risk Context That Drives Policy

Organizations invest heavily in tools that understand their devices. A vulnerability scanner ranks every asset by risk. An endpoint management platform knows what is installed, what is patched, and how each machine is configured. What neither tool does is decide which other systems can reach that device. That decision belongs to the policy model, and it is only as good as the context the policy model can see.

Rapid7 InsightVM. Elisity now supports Rapid7 InsightVM as an Elisity IdentityGraph™ connector, enriching devices with vulnerability context: risk score, vulnerability counts by severity, and exploit and malware-kit exposure. Organizations running more than one InsightVM environment can connect all of them to a single tenant.

Tanium. Elisity now supports Tanium as an Elisity IdentityGraph™ connector, enriching devices with the endpoint attributes Tanium collects. Administrators can also bring in custom attributes from their own Tanium sensor catalog, so the sensors a team has already written become part of each device’s identity.

Both connectors’ data can be used to define Policy Groups, and that is where the value compounds. The scanner knows a device is vulnerable but cannot stop anyone from reaching it; Elisity controls who can reach it. Together, a device with an exploitable vulnerability can be placed in a more tightly governed Policy Group until it is patched, and devices the endpoint platform vouches for can be classified with more confidence. The exposure data a security team already trusts starts driving policy directly, alongside the context correlated from 25+ native integrations. The same identity that describes a device is the identity its policy is written against.

Zero Trust Posture Updates: A Score for the Whole Estate

Leadership asks a simple question after every major breach in the news: how exposed are we? The Zero Trust Posture score answers it from the organization’s own policy, and in 26.9 it answers it for more of the estate.

Device-to-workload policy counts. Zero Trust Posture scores now cover policies between device and workload Policy Groups, so the score reflects the paths from campus and plant devices to cloud applications, not only the paths inside the campus.

A steadier measure. Scores now include offline devices that belong to a Policy Group. Devices go offline and come back throughout the day; a score that rose and fell with them was measuring uptime as much as posture. Including them keeps the score consistent from day to day, which is what makes it useful as a trend a CISO can report.

Posture where policy is managed. Coverage scores now appear on each Device Policy Group, with a drill-down into the details behind them, including the MITRE ATT&CK techniques and exposed ports that remain. The team responsible for a group of devices can see how well it is covered, and what is still exposed, without leaving the place where they manage it.

Coverage That Matches the Network You Actually Run

The through line in 26.9 is coverage. A microsegmentation program does not get to choose the network it protects; it inherits the switching, the plant floor, and the security tools that are already there. Release 26.9 extends identity-based policy to more of that infrastructure, lets the knowledge in those tools drive how devices are grouped and governed, and gives leadership a posture score that reflects the full estate rather than the convenient part of it.

Release 26.9 at a Glance

Frequently Asked Questions About Elisity Release 26.9

Does Elisity support HPE Aruba AOS-S switches?

Yes. Release 26.9 adds policy enforcement on Aruba AOS-S 2530, 2920, 2930, and 3810 switches, with automated onboarding, endpoint discovery, and flow telemetry, managed from the same Cloud Control Center as Aruba CX and every other supported platform.

Does Elisity work with Rockwell Automation Stratix switches?

Yes. Stratix switches are onboarded as visibility nodes that enrich Elisity IdentityGraph™ with VLAN, interface, and topology data for connected devices. They do not enforce policy or change switch configuration; policy for those devices is enforced through supported infrastructure elsewhere in the network.

Can vulnerability data from Rapid7 InsightVM drive microsegmentation policy?

Yes. The Rapid7 InsightVM connector enriches each device with its risk score, vulnerability counts by severity, and exploit and malware-kit exposure, and that data can be used to define Policy Groups. A device with an exploitable vulnerability can be placed in a more tightly governed group until it is patched.

Can Elisity use our Tanium data, including custom sensors?

Yes. The Tanium connector enriches devices with the endpoint attributes Tanium collects, and administrators can bring in custom attributes from their own Tanium sensor catalog. That data can be used to define Policy Groups.

What is the Zero Trust Posture score?

It is a measure of how well an organization’s own policy covers its estate and what remains exposed, built from the policy that is actually in place. In 26.9 it covers device-to-workload policy and offline devices, and each Device Policy Group shows its own coverage with a drill-down into the MITRE ATT&CK techniques and exposed ports that remain.

Does the Zero Trust Posture score cover cloud workloads?

Yes. Scores cover policies between device and workload Policy Groups, so paths from campus and plant devices to cloud applications are part of the measure.

Does Elisity require new hardware to enforce policy?

No. Elisity enforces identity-based policy through the network infrastructure organizations already own, managed from Cloud Control Center. Release 26.9 adds Aruba AOS-S to the supported enforcement platforms.

Availability

Elisity Release 26.9 is available now. Complete details, including API updates and configuration command changes, are in the 26.9.0 release notes. (Customer Login Required)

Next step: Schedule a demo to see how Elisity delivers identity-based microsegmentation on the network infrastructure you already own.