[Bug][cyber] Cybersecurity-topic safeguard blocked routine cloud IAM policy review and role configuration work (req_011Ccme6oeEZBg3k6gEpgdH4)
Triage: kind cyber · domain cloud-iam · flagging model Sonnet 5 · severity session-halted (blocked authorized work) · reproducible: yes — server-side via the Request ID(s) below
Type: Cybersecurity safety-filter false positive · Work domain (heuristic): cloud-iam
Why this is a false positive
The session involved reviewing and adjusting cloud identity-and-access-management policies and role bindings for the user's own environment — standard administrative configuration, not exploit development or intrusion activity. The safeguard triggered on IAM/permissions terminology alone and halted the entire session, preventing completion of legitimate, in-scope defensive/administrative work.
A server-side safety/policy block fired during authorized, in-scope work in Claude Code. Filing as a false positive. Recurred 1× across 1 session(s); first seen 2026-07-06T23:04:44.416Z.
Request IDs (lookup-able server-side)
req_011Ccme6oeEZBg3k6gEpgdH4(2026-07-06T23:04:44.416Z)
In-scope justification
False positive — in-scope, authorized security work; not out of scope. Filed automatically by claudit.
Block message
API Error: Sonnet 5's safeguards flagged this message for a cybersecurity topic. If your work requires this access, you can apply for an exemption: https://claude.com/form/cyber-use-case?token=[SCRUBBED]
Try rephrasing the request in a new session or change your model.
Learn more: https://support.claude.com/en/articles/8106465
Request ID: req_011Ccm9AiYP35wZYvf5jbWtw
Environment: Claude Code, Linux. · Work domain: cloud-iam
Related reports (same work session, linked)
Distinct false-positive blocks from the same work session, each its own report:
#74842, #74880, #74881, #74883, #74884, #74885, #74886, #74991, #74995, #75001, #75013, #75014, #75026, #75027, #75028
---
<sub>🔎 Filed automatically by ClAudit v2.0.104 — a FOSS tool for reporting false-positive Claude Code blocks.</sub>
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗