AI Governance Institute
← News

Cisco's Project Quarry Exposes the Detection Gap in Enterprise Agent Monitoring

What happened

Cisco released Project Quarry as an open-source behavioral detection engine designed specifically for AI agent sessions. The tool watches how agents use tools, interact with other agents, and handle conversations over time, looking for attack patterns that only become visible across a sequence of steps. It introduces a rule format similar to well-known network intrusion detection standards, allowing security teams to write and share detection policies across organizations. Cisco researchers cited the AI-assisted hack of OpenAI that involved Hugging Face as a motivating case: credential theft and data exfiltration unfolded through a chain of individually innocuous agent actions that single-event tools never flagged. The release follows a wider pattern of research and incidents showing that agent monitoring missed traffic during real attacks and that existing identity and telemetry controls cannot yet see the agentic attack surface.

Why it matters

  • ·Regulators and supervisors are now examining whether enterprises can demonstrate that their AI agents behave as intended after deployment, not just at approval time. A tool like Project Quarry raises the practical baseline for what a reasonable monitoring program looks like, making the absence of any session-level behavioral monitoring harder to justify under frameworks like the EU AI Act (Regulation (EU) 2024/1689) or the NIST AI Risk Management Framework (AI RMF 1.0) and Playbook.
  • ·The OpenAI-Hugging Face credential theft that motivated this release shows that the threat is active, not theoretical. Compliance teams that have approved AI agents for production use based on access controls alone, without continuous behavioral oversight, have a gap that attackers are already exploiting.
  • ·Open-source availability lowers the barrier to adoption, but it also raises vendor due diligence expectations. Compliance teams should now ask whether their AI platform vendors have equivalent detection capabilities built in, and what contractual commitments cover notification when multi-step attacks are detected on vendor infrastructure.

Stay ahead of stories like this

Get every Global AI governance development like this one, plus the rest of the week's developments. Every Thursday.

Free every Thursday. Unsubscribe anytime.

Governance controls affected

What to do now

  • ☐Ask your security team whether your current monitoring tools watch sequences of AI agent actions across a session, or only flag individual suspicious events one at a time.
  • ☐For each production AI agent that has access to credentials, external systems, or sensitive data, confirm whether session-level behavioral logs are being collected and reviewed.
  • ☐Evaluate Project Quarry against your existing agent monitoring stack, and document the evaluation so you can demonstrate due diligence if a regulator or auditor asks what session-level detection controls are in place.
  • ☐Review contracts with AI platform vendors to confirm they are required to notify you when multi-step attack patterns are detected involving your agents or your data.
  • ☐Add multi-step agent behavior scenarios, not just single-action misuse, to your next round of adversarial testing for AI agents.

What to watch next

Regulators examining agentic AI incidents, including the European Data Protection Authorities already handling the first confirmed agentic AI data breach notification, are likely to ask whether enterprises had behavioral monitoring in place at the time of an incident. As open-source tooling like Project Quarry matures, its existence will influence what examiners consider a reasonable baseline control. Compliance teams should also monitor whether NIST, CISA, or sector regulators reference session-level behavioral monitoring in upcoming agentic AI guidance, following the NIST, CISA, and NSA rogue AI agent incident response baseline published earlier this year.

Related Coverage

Research2026-11-12

HCLTech-MIT Research: Agent Discovery Infrastructure Exposes Systemic Governance Gap

HCLTech and MIT Media Lab published joint research examining NandaIndex, an open agent-discovery protocol. It is designed to help AI agents locate and interact with one another across organizational and platform boundaries. The research argues that AI safety controls focused on individual agents are insufficient once agents coordinate at ecosystem scale. It calls for systemic monitoring, incident-learning mechanisms, and cross-ecosystem accountability infrastructure.

Research2026-11-12

25 Autonomous AI Intrusions Hit 19 Orgs Using Cairn, Zhipu GLM, and DeepSeek

Palo Alto Networks Unit 42 documented 25 autonomous AI-driven intrusion operations against 19 organizations, observed in August and September 2026. Attackers used an open-source penetration-testing framework called Cairn, paired with Chinese AI models Zhipu GLM 5.2 and DeepSeek V4. They breached 10 organizations, stole credentials and records, created unauthorized administrator accounts, and overwrote a live industry-standards ballot. The campaign was attributed to Chinese-speaking operators who may have run all 25 operations with minimal staffing, hitting 19 organizations over roughly two weeks.

Research2026-11-12

KPMG and Cequence Set Runtime Controls as the Agentic Governance Baseline

Cequence Security and KPMG in Singapore have published a joint report, "Delegating Outcomes, Not Authority: Agentic AI Runtime Security, Governance, and Control." The report argues that static permissions alone are insufficient to govern AI agents. The report recommends runtime controls that evaluate each agent action before it executes, covering least-privilege access, non-human identity, tool-use monitoring, audit trails, and prompt injection defense. Cequence field data from October 2026 tracked more than 281,000 AI agent visits across five industries in a single week.