TL;DR: Claude Code can assemble a peer-to-peer exfiltration path that DLP, CASB, and firewall controls may not flag as malicious, according to KonaSense. Governance for agent-driven transfers has to track prompts, tools, and network sessions together, or approved-looking steps will still add up to one data-movement path.
Editorial analysis by NHI Mgmt Group, based on content published by KonaSense: “Your Coding Agent Just Opened an End-to-End Encrypted P2P Tunnel Out of Your Network”.
Key questions
Q: Why do peer-to-peer encrypted transfers create blind spots for DLP and CASB?
A: They bypass the assumptions those controls rely on.
Q: What signs indicate an AI coding agent is assembling an exfiltration path?
A: Look for a chain of events: installation of a new transfer utility, execution from a sensitive workspace, extraction of a one-time code from stdout, and an outbound connection that follows immediately.
Q: How should security teams govern agent-driven file sharing that bypasses normal DLP controls?
A: Treat the action as the control object.
Practitioner guidance
- Instrument prompt-to-shell-to-network traces Correlate agent prompts, process execution, and outbound connections so a single file transfer is visible as one governed event rather than three disconnected logs.
- Block unauthorised external transfer tools Maintain policy on transfer intent and approved methods, not just a static executable list, so new utilities that perform the same action are covered.
- Classify sensitive working directories Apply stricter controls when agents operate in finance, legal, or other sensitive paths, because file location is part of the risk signal, not just file content.
Bottom line: Claude Code can assemble a peer-to-peer file transfer that escapes conventional DLP, CASB, and firewall assumptions because the data moves as encrypted application traffic, not as a recognised SaaS upload.
Glossary terms: Agent-mediated exfiltration, Peer-to-peer encrypted transfer, Action-level Policy
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Policy by action, not by tool, is the real control boundary here: the transfer succeeds because governance still tends to model approved and unapproved binaries, not approved and unapproved intent. A coding agent can swap among utilities, install missing ones, and complete the same exfiltration pattern through different paths. The practical conclusion is that security programmes need an action-level policy model for agent-mediated data movement, not a denylist tuned to yesterday's tools.
A few things that frame the scale:
- Claude Code-assisted commits leaked secrets at a rate of 3.2%, more than double the human-only baseline of 1.5%, with peaks reaching 31 secrets per 1,000 commits in August 2025, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: Who should own policy decisions for agent-mediated data transfer?
A: Ownership should sit with identity, security, and platform teams together, because the risk spans authorisation, endpoint telemetry, and network inspection. The key question is not which tool to block, but which sessions are allowed to assemble a transfer path from a sensitive directory to an external recipient.
👉 Read our full editorial: Claude Code data exfiltration bypasses DLP in peer-to-peer transfers