Skip to main content

Filed under

Compliance

  1. Compliance · 8 min read ·

    The Policy Is the Part That Moves

    A proved gate is only as good as the policy it enforces, and the policy is the part that changes while the agent is running. What OSCAL and the agent-authorization drafts both assume, and what breaks.

  2. AI Agents · 7 min read ·

    You Can't Prove the Agent. Prove the Gate.

    Formal verification for AI-agent security. You can't prove a probabilistic model does the right thing — but the deterministic gate in front of it is small enough to prove outright. Dafny proofs, a Rego twin, and differential testing, following the method AWS used for Cedar.

  3. Compliance · 7 min read ·

    The Firewall Stays Put. The Agent Improvises.

    Rewriting security controls for probabilistic agents. Static control catalogs assume systems that do what they're told; AI agents don't — so here's how to express agent guardrails (tool allowlists, secret-egress denial, audit) as machine-checkable OSCAL component definitions.

  4. Compliance · 8 min read ·

    Exploring Claude CLI Context and Compliance with My Standards Repository

    A CLAUDE.md is a prompt, not a loader. What a standards repository can and cannot enforce, and where the real enforcement has to live.

  5. Compliance · 10 min read ·

    Vulnerability Management at Scale with Open Source Tools

    Build enterprise vulnerability management with open source: scanning, remediation tracking, and compliance using OpenVAS, Trivy, and Airflow.