[Bug][cyber] DNS sinkhole/wildcard resolver config wrongly blocked while restricting LAN to a single upstream (req_011CcJonk8TZPZEWqHWcckDs)
Type: Cybersecurity safety-filter false positive · Work domain (heuristic): general
Why this is a false positive
This is routine network administration on the user's own managed infrastructure — diagnosing why an egress firewall/geo-filter policy was over-blocking legitimate traffic, planning per-network WAN failover, and configuring local DNS to resolve queries while restricting resolution to a single approved upstream filtering provider. None of this involves offensive techniques, exploitation, or unauthorized access; it is standard defensive configuration of equipment the operator owns and administers. The classifier appears to have keyed on generic networking and DNS terminology rather than any actual cybersecurity-attack content, producing a false positive that blocks ordinary IT 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-06-22T18:56:01.857Z.
Request IDs (lookup-able server-side)
req_011CcJonk8TZPZEWqHWcckDs(2026-06-22T18:56:01.857Z)
In-scope justification
False positive — in-scope, authorized security work; not out of scope. Filed automatically by claudit.
Block message
API Error: Opus 4.7 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_011CcJonk8TZPZEWqHWcckDs
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>
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗