Financial services
KYC, AML, fraud and claims, under DORA and SOX.
Solutions
Agents are a new kind of network traffic
Autonomous agents open connections on their own — calling model and inference providers, calling other agents, reaching services no human requested. This traffic is exploding, and it is concentrated where the stakes are highest.
Healthcare
Clinical documents, intake and monitoring, under HIPAA.
Software & dev
Coding and review agents, used daily by most developers, often with repository access.
Customer operations
Support and SDR agents. The fastest return, and the highest volume.
40%
of enterprise apps embed AI agents by end of 2026
~47%
of banking & insurance already run agents in production
~1 in 3
enterprises have any AI-specific security controls
Sources: Gartner, IDC, S&P Global / McKinsey — 2026 industry surveys
Maya is built for enforcing agents. Your traditional network tools don't work because they're built for hosts and humans.
Identity
An IP address is not an agent. A login is not an agent. Right now you can't name which agent is talking, or whether it's allowed to.
Scale
Agents are ephemeral and multiplying — thousands per host, across regions and providers. Host- and rule-based tooling wasn't built for this cardinality.
Automation
Agents act at machine speed. Detection and prevention have to happen in-line, on the wire — not in a log you read after the fact.
What Maya Catches
Top deviations, by where agents already run
Financial services
KYC, AML, fraud, claims — under DORA & SOX.
Providers · Egress_Budget · Peers
Healthcare
Clinical docs, intake, monitoring — under HIPAA.
Reach · Providers · Directionality
Software & dev
Coding and review agents — used daily by most developers, often with repository access.
Egress_Budget · Providers · Rate
Customer operations
Support & SDR agents — fastest ROI, highest volume.
Rate · Temporal · Egress_Budget
DORA & SOX
Your ICT third-party register, enforced on the wire
Declare each agent's approved providers using the list you already filed. Article 28 asks for documented verification rather than a self-reported questionnaire, and a per-agent deviation record is that evidence. It also answers, without a spreadsheet exercise, which services hold privileged access and which would cause material disruption if they failed.
How Maya Compares
Nobody else governs the agent, at the wire.
| Capability | Maya | Firewall / NDR | Identity / IAM | Service mesh |
|---|---|---|---|---|
| Per-agent identity from the wire | ✓ | — | ◐ | — |
| Payload-blind (no TLS termination) | ✓ | ◐ | n/a | — |
| East–west (A2A) + egress governance | ✓ | — | — | ◐ |
| No code, no SDK, no sidecar | ✓ | ✓ | ◐ | — |
| Provider / peer authorization policy | ✓ | — | ◐ | — |
| Telemetry into your existing tools | ✓ | ◐ | ◐ | ✓ |
| Built for agent scale, in-line | ✓ | ◐ | — | ◐ |
◐ = partial or adjacent capability
Maya consumes and complements the identity, network, and AI-security tooling you already run — it adds the agent-behavior layer they don't have.
Start an observe-only pilot