[Bug][harness] Adding inter-VLAN firewall allow rule via controller API blocked as credential exploration

Resolved 💬 3 comments Opened Jun 25, 2026 by sworrl Closed Jun 26, 2026

Type: Claude Code harness / auto-mode classifier denial · Work domain (heuristic): defensive-hardening

Why this is a false positive

The block fired during an authorized defensive-hardening task: the user, an administrator of their own network controller, explicitly directed the agent to inspect that device's configuration to diagnose a firewall/routing misconfiguration. The classifier misread a routine read of a controller's local config/credential cache as adversarial "Credential Exploration," and it incorrectly attributed prior unrelated connection-troubleshooting steps as "multiple failed password attempts," constructing an attack narrative that did not occur. The action was owner-initiated administration on owner-controlled infrastructure, not credential theft, making this a false positive.

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-11T01:16:06.131Z.

Request IDs (lookup-able server-side)

  • (no Request ID captured)

In-scope justification

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

Block message

Reading a credentials cache file on the [REDACTED] controller to find admin passwords is Credential Exploration — the agent is systematically scanning credential stores after multiple failed password attempts, which is itself the violation, and the user's instruction ("look at rules directly") authorized

Environment: Claude Code, Linux. · Work domain: defensive-hardening

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