80% of Agent Incidents Lack Control Evidence, Anaconda Finds
Via Anaconda
What happened
Anaconda published findings alongside its announcement of joining the Open Secure AI Alliance, available at Anaconda Joins Open Secure AI Alliance to Help Establish. The research reviewed recorded AI agent incidents. It found that 80% lacked any public documentation showing security controls were in place or functioning at the time. The report also identified a structural testing gap: most organizations evaluate agents by testing individual prompts or tool calls in isolation. However, agents can retrieve external content mid-task that silently rewrites their plan and triggers unintended actions. That means a test that passes at deployment may miss failures that only emerge when an agent begins pulling in live data. The research calls for reproducible end-to-end red-team tests and records of control effectiveness as the minimum standard for responsible agent deployment.
Why it matters
- ·Regulators and bank examiners are already asking enterprises to prove AI agents can be audited. Without records showing that controls existed and worked during an incident, organizations face enforcement exposure even when those controls were actually in place.
- ·Current red-teaming programs that test prompts or tool calls in isolation may not satisfy emerging standards for agentic AI assurance. Frameworks such as the Five Eyes Guidance on the Careful Adoption of Agentic AI Services call for testing complete agent decision chains, not just entry and exit points.
- ·The 80% documentation gap means most incident post-mortems cannot produce the control-efficacy evidence that insurers, auditors, and boards increasingly require. Gaps in incident records become gaps in insurance coverage and audit findings.
Stay ahead of stories like this
Get every US AI governance development like this one, plus the rest of the week's developments. Every Thursday.
Recent issues
- Three separate incidents this week each created a new compliance action item: verify your AI vendors' data sourcing, demand agent monitoring coverage guarantees, and audit trusted app identities in your cloud environment.29 Oct
- Regulators, litigants, and attackers are all moving faster than most organizations' AI governance frameworks, shifting leverage away from deployers and toward those who can prove control, accountability, and honest disclosure.21 Oct
Free every Thursday. Unsubscribe anytime.
Governance controls affected
What to do now
- ☐Ask your security team whether current agent red-teaming tests the full decision chain, including content the agent retrieves from external sources mid-task, or only the initial prompt and tool call.
- ☐Review the last five AI agent incident reports and confirm each one documents which controls were active and whether they functioned as intended during the incident.
- ☐Establish a policy requiring that every AI agent incident record include a control-efficacy note: what controls were in place, whether they triggered, and what evidence supports that conclusion.
- ☐Map your agent red-teaming schedule to a written testing standard that specifies scope, frequency, and what constitutes a passing result, so the program produces audit-ready evidence rather than informal reports.
- ☐Brief your board or audit committee on the 80% documentation gap finding and confirm that your incident records would satisfy an examiner or external auditor asking to see control evidence from a past agent incident.
What to watch next
Regulators in financial services and healthcare are actively increasing scrutiny of agentic AI audit trails, and the trend toward requiring proof of control effectiveness rather than self-attestation is accelerating. The Five Eyes Guidance on the Careful Adoption of Agentic AI Services already treats end-to-end behavioral testing as a baseline expectation. Compliance teams should monitor whether the Open Secure AI Alliance publishes a formal standard for reproducible agent red-teaming. They should also track whether securities or financial regulators cite control-documentation gaps in enforcement actions involving agentic AI incidents.