[Bug][cyber] Safety block halts defensive triage of aggregated MITRE ATT&CK technique counts from auth logs (req_011CcGwVhvhSJx9reWFcUij2)

Open 💬 2 comments Opened Jun 25, 2026 by sworrl

Type: Cybersecurity safety-filter false positive · Work domain (heuristic): general

Why this is a false positive

The flagged message contained only defensive security telemetry — an aggregated count of authentication events mapped to MITRE ATT&CK technique names (e.g. credential-reuse and policy-modification categories) — which is standard blue-team log review and detection-engineering output, not instructions to carry out an attack. The classifier appears to be matching on the presence of offensive-technique terminology in the data itself, rather than on any request to perform, enable, or evade those techniques. As a result, routine analysis of one's own environment's security logs is being blocked despite containing no actionable harmful content.

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-21T19:15:36.910Z.

Request IDs (lookup-able server-side)

  • req_011CcGwVhvhSJx9reWFcUij2 (2026-06-21T19:15:36.910Z)

In-scope justification

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

Block message

API Error: Opus 4.8 has safety measures that 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]

Please double press esc to edit your last message or start a new session for Claude Code to assist with a different task.

Send feedback with /feedback or learn more: https://support.claude.com/en/articles/15363606

Request ID: req_011CcGwVhvhSJx9reWFcUij2

Environment: Claude Code, Linux. · Work domain: general

---
<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 2 comments on GitHub. Read the full discussion on GitHub ↗