CydraLabsZero trust for AI agents

Extensions

Test, respond and build securely on the same control plane

Securing agents in production also means testing them before release, responding when one misbehaves and controlling what they are built from.

RoadmapJoin the pilot

The problem

What Extensions resolves

  • Untested behaviour

    Agents ship without evidence of how they behave under prompt injection, tool poisoning or excessive agency.

  • Slow agent investigations

    Responders struggle to reconstruct what an agent did, for whom, and what it could reach.

  • Unvetted building blocks

    MCP servers, tools, skills and plugins are added to agents without review.

Where it acts

Where Cydra controls an agent action

Extensions use the same identity, policy, approval and evidence services as the core products; their own actions go through CydraGateway.

Action-control workflow: receive, authenticate, resolve, context, policy, inspect, decide, approve, execute with scoped credentials, evidence.1Receive2Authenticate3Resolve4Context5Policy6Inspect7Decide8Approve9Execute10EvidencePolicy errors fail closed · Deny outranks approval outranks allow · Every outcome produces an evidence record
The ten-step action-control workflow shared by every product.
Step-by-step explanation

Capabilities

Extensions capability tour

  1. Discover

    • CydraRedTeam campaigns

      Roadmap

      Scenario-based campaigns against agents, MCP servers and tool chains.

    • CydraDevSec supply chain

      Roadmap

      Provenance and review status of the MCP servers, tools, skills and plugins agents are built from.

  2. Decide

    • Recommended policies

      Roadmap

      CydraRedTeam findings become recommended CydraGateway policies.

  3. Enforce

    • CydraSOC containment

      Roadmap

      Guided containment using the kill switch, tool blocking and credential revocation, with approval.

  4. Investigate

    • CydraSOC investigation

      Roadmap

      Agent incident investigation from decisions, delegated identity, blast radius and evidence.

  5. Prove

    • Evidence for every step

      Available

      Each extension action is recorded in the evidence chain.

Prerequisites

Extensions build on the core platform.

  • CydraShield inventory and Security Graph for context
  • CydraGateway for policy and approval of every extension action
  • CydraGovern to map results to controls (optional)

Available today

Incident responders can already use blast-radius analysis, the action timeline, the kill switch and verifiable evidence from the core platform.

Agent incident response

Extensions

The extensions

  • CydraRedTeam

    Roadmap

    Test how agents behave under attack before they ship

    Adversarial testing of agents, MCP servers and tool chains. Findings map to the Security Graph, feed the Agent Risk Score and become recommended gateway policies.

    • Example: run a prompt-injection campaign against a support agent before release and review the policies it recommends
    View CydraRedTeam

  • CydraSOC

    Roadmap

    Investigate and contain agent incidents

    Agent incident investigation and containment, starting from the decision timeline, the delegated identity and the blast radius in the Security Graph.

    • Example: an agent sends customer data to an unexpected destination; reconstruct the timeline and request approval to suspend it

  • CydraDevSec

    Roadmap

    Secure the agent and MCP software supply chain

    Provenance and review of the components agents are built from, with checks in the pipeline before an agent or MCP server reaches production.

    • Example: an unreviewed MCP server is added to a repository; open a review task before it can be deployed

Coverage

Integrations and deployment

Every item carries its current status.

Integrations

  • Agents and MCP servers connected through CydraGateway

    CydraRedTeam targets

    Roadmap

  • Microsoft Sentinel, Splunk, Google Security Operations

    CydraSOC

    Roadmap

  • GitHub, GitLab and Jenkins

    CydraDevSec

    Roadmap

Deployment

  • CydraLabs-managed SaaS

    Hosted and operated by CydraLabs.

    Pilot programme

  • Customer cloud or private VPC

    Deployed into your own cloud account with the CydraLabs reference deployment.

    Pilot programme

  • On-premises or sovereign deployment

    Planned for environments that cannot use cloud services.

    Roadmap
Full capability list with status

  • Scenario-based red-team campaigns

    Campaigns that test agents, MCP servers and tool chains for prompt injection, tool and MCP poisoning, memory poisoning, excessive agency and privilege escalation.

    Roadmap

  • Findings mapped to the Security Graph

    Each finding is attached to the agent, tool or MCP server it affects and feeds the Agent Risk Score.

    Roadmap

  • Recommended gateway policies

    Findings become recommended CydraGateway policies to review and publish.

    Roadmap

  • Agent incident investigation

    Investigate an agent incident from its decisions, delegated identity, blast radius and evidence.

    Roadmap

  • Guided containment

    Contain an incident through the existing kill switch, tool blocking and credential revocation, with approval and evidence.

    Roadmap

  • Agent and MCP supply-chain inventory

    Provenance and review status of the MCP servers, tools, skills and plugins agents are built from.

    Roadmap

  • Pre-deployment checks

    Pipeline checks before an agent or MCP server reaches production.

    Roadmap
Available
Implemented, tested and demonstrable in the current proof-of-concept build.
Beta
Implemented and demonstrable, with documented limitations.
Preview
Interface or mock implementation behind a real contract; live integration not yet enabled.
Roadmap
Not built in this phase. Shared platform foundations are in place.

Trust

Security, privacy and trust

  • Every extension action is subject to the same identity, policy, approval and evidence controls as any other agent.
  • Tenant isolation with PostgreSQL row-level security for the application role.
  • Payloads stored as hashes plus redacted previews by default; no secrets in logs.
  • TLS in transit; encrypted storage in the AWS reference deployment.
  • No third-party certifications or attestations yet. See the Trust Centre for current assurance status.
Visit the Trust Centre

Proof

What we can show today

  • Roadmap status

    CydraRedTeam, CydraSOC and CydraDevSec are on the roadmap. They are not built in the current phase.

  • Design-partner outcomes

    Pilot outcomes and case studies will be published when design partners agree. We do not publish customer names, logos or results before then.

Help shape the extensions

Join the pilot to work with us on red-team, incident-response and supply-chain workflows as they are built.

Join the pilotAssess your agent risk