[Bug][aup] Defensive incident-response sweep of web/container infra blocked after IAM breach (req_011Cbwvt243PhEypPNU8DgJW)

Open 💬 1 comment Opened Jun 25, 2026 by sworrl

Type: AUP / Usage-Policy block (false positive) · Work domain (heuristic): cloud-iam

Why this is a false positive

This safeguard fired on a routine cloud IAM incident-response task—reviewing identity and access configuration on infrastructure the operator owns to confirm whether a confirmed account compromise had spread—which is defensive security work explicitly permitted under the Usage Policy. No exploit, attack tooling, or unauthorized-access technique was requested; the activity is read-only auditing of one's own environment in response to an active breach. The block prevents legitimate, time-sensitive remediation and should be treated as a false positive for authorized defensive use.

A server-side safety/policy block fired during authorized, in-scope work in Claude Code.
Filing as a false positive. Recurred across 1
session(s); first seen 2026-06-11T18:16:15.485Z.

Request IDs (lookup-able server-side)

  • req_011Cbwvt243PhEypPNU8DgJW (2026-06-11T18:16:15.485Z)

In-scope justification

False positive — in-scope, authorized security work; not out of scope. Filed automatically by claudit.

Block message

API Error: Claude Code is unable to respond to this request, which appears to violate our Usage Policy (https://www.anthropic.com/legal/aup). This request triggered cyber-related safeguards. To request an adjustment pursuant to our Cyber Verification Program based on how you use Claude, fill out https://claude.com/form/cyber-use-case?token=[SCRUBBED]. To learn more about the program or provide feedback, visit o… Please double press esc to edit your last message or start a new session for Claude

Environment: Claude Code, Linux. · Work domain: cloud-iam

---
<sub>🔎 Filed automatically by ClAudit v2.0.21 — a FOSS tool for reporting false-positive Claude Code blocks.</sub>

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗