RYE
Security Compliance · DevSecOps
Overview
Enforce security policies on every AI coding tool. Block secrets, restrict models, authorize devices, and maintain compliance-ready audit trails.
News
DeepSeek Harness's Sandbox Confines Files, Not Network or Processes
DeepSeek Harness ships a fail-closed filesystem sandbox using bwrap, Landlock, Seatbelt, or Windows ACLs, but its own source and documentation state that network access and process visibility are outside what the sandbox governs.
Read more
Report
Encrypted Reasoning Is Still Agent State
Researchers extracted 182 credentials and 367 PII artifacts from encrypted chain-of-thought fields returned by major LLM APIs, including secrets that never appeared in any plaintext prompt or response.
Read more
Report
AI Agent Sandboxes Stop Escapes. They Don't Tell You What Happened Inside.
Docker Sandboxes and microVM isolation keep AI agents away from the host. They do not tell security teams what the agent read, ran, changed, or sent while it was inside.
Read more
Report
The GhostApproval Vulnerability: What It Means for Your AI Coding Toolchain
A symlink bug in major AI coding assistants showed a harder truth: approval prompts only help when they tell the user what will really happen.
Read more
Report
How AI Coding Agents Actually Run on Your Machine
A technical look at how Claude Code, Codex CLI, and other coding assistants store sessions, run tools, ask for approval, and leave teams with fragmented controls.
Read more
Report
How Claude Code's Permission System Actually Works
A close look at Claude Code permission rules, hooks, and approval files, and why those local files are not the same thing as team policy.
Read more
Report
Setting Up a Proxy for AI Agent Traffic
How to route Claude Code, Codex CLI, and other AI coding agents through a local proxy so you can inspect model traffic and enforce policy.
Read more
Report
