[Bug][cyber] False positive during OS signing key audit and test certificate hardening (req_011CeDa5r5QL2AWzDbVGC99S)
Triage: kind cyber · domain defensive-hardening · flagging model [REDACTED] · 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): defensive-hardening
Why this is a false positive
The session was performing defensive security hardening by auditing build signing keys to identify default test certificates. The safeguard triggered during the inspection of certificate metadata and key signatures. Auditing signing keys and planning the replacement of insecure default credentials is standard defensive configuration 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-08-20T07:02:00.093Z.
Request IDs (lookup-able server-side)
req_011CeDa5r5QL2AWzDbVGC99S(2026-08-20T07:02:00.093Z)
In-scope justification
False positive — in-scope, authorized security work; not out of scope. Filed automatically by claudit.
Block message
API Error: [REDACTED]'s safeguards flagged this message (https://www.anthropic.com/legal/aup). Our intentionally broad safeguards allow us to deliver more capabilities faster, but can sometimes flag legitimate coding, cybersecurity, and biology tasks. Claude Code can't respond to this message with [REDACTED].
Double press esc to edit your last message, or try a different model with /model.
Send feedback with /feedback or learn more: https://support.claude.com/en/articles/15363606
Details: [cyber]
Environment: Claude Code, Linux. · Work domain: defensive-hardening
Related reports (same work session, linked)
Distinct false-positive blocks from the same work session, each its own report:
#88666
---
<sub>🔎 Filed automatically by ClAudit v2.2.3 — a FOSS tool for reporting false-positive Claude Code blocks.</sub>
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗