Blog
Practical guides on hook DLP, Cursor and Claude Code controls, and how security teams inventory shadow AI coding tools — written for engineers and CISOs evaluating real controls.
deep-dive
Oct 12, 2026Why blanket AI bans fail: a four-layer defense across pre-execution hook DLP, governed gateways, customer-key encryption, and multi-cadence alerting.
Read →guide
Oct 10, 2026Why monitoring file-read tools misses agent execution loops: how coding agents use shell pipelines and shadow scripts like load_dotenv() — and how AD-004 detects them.
Read →deep-dive
Oct 8, 2026How autonomous file reads break GDPR data sovereignty, SOC 2 least privilege, audit trails, and sector mandates — with the checklist auditors look for.
Read →comparison
Oct 7, 2026A fair comparison for evaluation queries: tool-level hook redaction, OS/endpoint AI DLP agents, and network AIDR/CASB-style controls — what each sees and misses.
Read →deep-dive
Oct 7, 2026Inventory Cursor, Claude Code, Copilot, and Gemini across engineering — then map evidence for SOC 2 programs and Canadian privacy notes (PIPEDA / Law 25) without invented claims.
Read →guide
Oct 7, 2026A practical how-to: stop secrets in env files and shell output from leaving the workstation when developers use ChatGPT, Cursor, or Claude Code.
Read →guide
Oct 7, 2026Cursor can still read .env files, see terminal output, and send context to the model even when Privacy Mode is on — ignore files are not redaction.
Read →comparison
Sep 21, 2026Why application-owned LLM calls belong in OpenTelemetry, while developer coding assistants require native lifecycle hooks, patch hunks, and terminal context.
Read →deep-dive
Aug 26, 2026Why statistical baselines, bounded evidence, and explainable detectors outperform fuzzy LLM classifiers when auditing enterprise AI coding workflows.
Read →