CANDOR AGENT DEFENSE
candoragentdefense.com
AI agent cybersecurity and risk management →For enterprise agent fleets →Discovery engagement & pricing →What has been verified →Framework mappings →Interactive demo →
Candor Agent Defense | runtime security for AI agents

Your AI agents hold credentials and act on real systems.
Candor controls what they may do, and proves what they did.

Every agent action is checked twice before it runs: is this agent who it claims to be, acting within what it was granted, and is the action itself dangerous. High-impact actions wait for a named person. Revoking a compromised supervisor stops every agent under it. Every decision goes into a record that cannot be quietly edited.

Identity and authority

Every agent gets a verifiable identity, a named task and the exact resources it may touch. Authority is short-lived and issued from outside the agent.

A person on high-impact actions

Payments, deletions and other high-impact actions are held until a named person approves them. The agent cannot approve itself.

One step to stop a whole tree

Declare a supervisor compromised and every agent under it loses authority, including requests already in flight. Unrelated agents keep working.

A record you can hand over

Every decision is sealed into a hash-chained ledger. Give an auditor, a regulator or a customer a record that shows it was not edited after the fact.

I build AI agents for other companies

Pass your customer’s security review

Scoped identity, kill switch, containment and a tamper-evident audit trail, with dated evidence.

Enterprise agent fleets

For any organization running agents that hold credentials, call tools or act on business systems. Start with a fixed-price Discovery engagement: we inventory your agents, observe them without acting, and hand you a signed report.

Game studios

For studios shipping AI characters, companions and agentic systems that players will try to jailbreak. Runtime containment mid-session, on a local model, with the same tamper-evident record.

Verified, with dates. Not just promised.
Revocation across a ten-agent delegation tree
Pending and in-flight work blocked after supervisor termination
High-impact actions held for a named operator's approval
Runtime discovery reconciled with the declared inventory
Ledger verification of every decision
The limits we have not closed yet, stated openly
Mapped to NIST AI RMF 1.0 and the OWASP agentic items. Mappings, not certifications.

Each row maps a dated, Candor-reported test to a framework item it gives evidence for. No row claims conformance with a framework, and no framework body has reviewed these results. All tests are Candor’s own, on Candor’s test ranges. Sources: the NIST AI RMF 1.0 subcategories from the NIST AI RMF Playbook, and the OWASP Top 10 for Agentic Applications for 2026, published 9 December 2025. Mapping prepared 6 November 2026.

OWASP agentic items, with dates
OWASP itemLatest testStatus
ASI01 Agent Goal Hijack19 Oct 2026Tested
ASI02 Tool Misuse and Exploitation21 Sep 2026Tested
ASI03 Identity and Privilege Abuse19 Oct 2026Tested. Limit: requester scope across agents not yet evaluated
ASI04 Agentic Supply Chain Vulnerabilities3 Oct 2026Partial. No supply-chain test (model or tool provenance) is listed on the evidence page
ASI05 Unexpected Code Execution3 Oct 2026Tested in the sealed sandbox arm
ASI06 Memory and Context Poisoning19 Oct 2026Tested for retrieved content; persistent memory poisoning not separately tested
ASI07 Insecure Inter-Agent Communication5 Oct 2026Tested. Limit: covert channels between agents not tested
ASI08 Cascading Failures5 Oct 2026Tested at ten-agent tree scale only
ASI09 Human-Agent Trust Exploitation5 Oct 2026Tested on the operator boundary only
ASI10 Rogue Agents19 Oct 2026Tested
NIST AI RMF 1.0 subcategories and the tests that give evidence
SubcategoryWhat it asksCandor tests that give evidence
GOVERN 1.6Inventory of AI systemsDiscovery of undeclared agents (18 Sep); Our own fleet under control (21 Sep)
GOVERN 1.7Decommissioning carried out safelyA revoked agent stays out (19 Oct)
GOVERN 3.2Human roles for oversight definedAuthority check and human hold (21 Sep); Operator authentication (5 Oct)
GOVERN 4.2Risks and impacts documented and sharedReport from the ledger (21 Sep)
MAP 1.1Context and deployment setting documentedDiscovery of undeclared agents (18 Sep)
MAP 3.5Human oversight processesAuthority check and human hold (21 Sep); Operator authentication (5 Oct)
MEASURE 2.3Performance measured under deployment-like conditionsSustained load (15 Sep); Sandbox compatibility (3 Oct)
MEASURE 2.4Functionality and behavior monitored in productionObservation mode (21 Sep)
MEASURE 2.5Valid and reliable before deploymentSustained load (15 Sep)
MEASURE 2.7Security and resilience evaluated, adversarial attackIdentity and credential (21 Sep); No credential, no action (21 Sep); Containment (21 Sep); Sealed platform (21 Sep); Sealed, governed department (3 Oct); Retrieved content cannot redirect an agent (19 Oct)
MEASURE 2.8Transparency and accountability, audit trailsReport from the ledger (21 Sep); Handoff integrity controls (5 Oct)
MANAGE 2.3Respond to and recover from a newly identified riskTree revocation (18 Sep); Probation after restore (21 Sep)
MANAGE 2.4Supersede, disengage or deactivateTree revocation (18 Sep); Containment (21 Sep); Work in flight at revocation (5 Oct); A revoked agent stays out (19 Oct)
MANAGE 4.1Recovery and change management after deploymentProbation after restore (21 Sep); Observation mode (21 Sep); Our own fleet under control (21 Sep)
See it live. Every Tuesday, 4:00 PM Eastern.
15 minutes on Google Meet, the real system, no slides. My own agents on my own system: a demonstration, not a customer result.
Pick a Tuesday →
sales@candortrustandsafety.com
Designed to support agent-runtime safety and evidence controls. Informational only. Not legal advice and not a certification. © 2026 Open Feed Network, Inc.