Elisity with NeuBird, the AI SRE: was it the policy?
NeuBird reads the Elisity IdentityGraph, policy groups, policy sets and insights, so an investigation can tell when a microsegmentation policy, not the application, blocked the traffic.
< 5 min
Root cause, at 94% accuracy
15+
Sources queried in parallel per investigation
In place
No bulk telemetry stored
< 1 hour
To deploy on the stack you already run
Core Capabilities
From signals to solutions
Resolve
The policy or the app?
When a service suddenly cannot reach a device or another service, NeuBird looks up both assets in the Elisity IdentityGraph, the policy groups they belong to and the policy sets that apply, while it queries application errors and recent changes in parallel. It shows whether a policy change or a reclassified asset blocked the traffic.
- Finds the policy group and policy set that govern each affected asset
- Spots assets whose attributes moved them into a different policy group
- Root cause in under 5 minutes at 94% accuracy, posted where your team works
Prevent
Catch a risky policy change early
NeuBird reviews Elisity insights and policy groups against the services that depend on each asset, and flags a change likely to block production traffic before it does.
- Flags production assets that sit in no policy group
- Surfaces policy insights that touch critical services
- Highlights assets whose classification changed
Operate
Keep segmentation and services in step
NeuBird compares Elisity policy groups with the services and hosts your other tools report, and recommends changes where the two disagree.
- Finds assets grouped inconsistently with the service they belong to
- Links recurring blocked-traffic incidents to the policy behind them
- Remembers every verified fix, with no bulk telemetry stored
Better Together
Elisity + NeuBird
| Capability | Elisity | NeuBird |
|---|---|---|
| Identity-based microsegmentation | ✓ | Reads it in place |
| Asset discovery and classification in the IdentityGraph | ✓ | Uses it as investigation context |
| Correlation with applications, cloud and code changes | Within the network | 15+ sources in parallel |
| Root cause with cited evidence | Policy insights | Under 5 minutes, 94% accuracy |
| Staged fix or rollback | Policy changes in Elisity | Behind configurable human approval gates |
| Memory of past fixes | Policy and asset records | Verified fixes, no bulk telemetry stored |
Ecosystem
Works across your entire stack
Elisity is one piece of the picture. NeuBird queries it in place and correlates it with every other connected tool, and every agent in the center inherits the connection.
Network
- Cisco Catalyst Center
- Juniper Mist
- Palo Alto Panorama
- Infoblox NIOS
Incident management
- PagerDuty
- ServiceNow
Collaboration
- Slack
- Microsoft Teams
Code and change
- GitHub
- Jira
FAQ
Common questions
How does NeuBird connect to Elisity?
You create an API client with OAuth2 client credentials and a read role in Elisity Cloud Control Center, then enter its URL, client ID and client secret in NeuBird. NeuBird requests a short-lived token and queries Elisity at investigation time, with no bulk telemetry stored.
What Elisity data does NeuBird use?
The IdentityGraph (assets and their attributes), policy groups, policy sets and insights, within what the API client’s role allows. The connection is in preview, so the data available may change.
Does NeuBird change anything in Elisity?
No. NeuBird sends only GET requests, so it cannot change policy or assets. Any fix it proposes is staged through the Suggest, Recommend, Act policy dial, set per action, with configurable human approval gates.
Is NeuBird a replacement for Elisity?
No. Elisity keeps segmenting your network by identity. NeuBird is the AI SRE that checks Elisity policy during an investigation, alongside every other tool you connect.
Get Started
Connect Elisity to the center.
Elisity gives you the data. Connect it to NeuBird once, and every agent that touches production inherits it, including the ones you build yourself.
