Encased — AI agent security
Containment reference

Encased.ai · Assurance register

Containment certification status

A milestone-by-milestone record of what is documented, built and functionally checked—and what still needs customer-host testing and independent assessment.

No containment certification issued. This is Encased's self-reported status register, not an independent certificate or completed assessment. Encased is not independently SOC 2 audited or ISO 27001 certified.

Current release
Python 0.3.2 review candidate
Domain/IP controls added; the dated 0.3.0 assessment does not assess this changed package. The 0.2.x cooperative SDK remains separate.
Independent assessment
Pending
No signed external report or reviewer endorsement is presented.
Production acceptance
Not established
Customer-host qualification and bounded risk-owner acceptance remain required.

Containment milestones

“Functionally verified” means builder checks of stated paths, not independent assurance. “Built” means the candidate exists, not that the deployed boundary has passed. A skipped probe is never a pass.

  1. CM-01

    Enforcement boundary & threat model

    Documented

    Responsible: Encased engineering

    Evidence & current position

    The containment reference distinguishes hosted decisions, cooperative wrappers and external isolation.

    Still required

    Confirm supported host, integrations and exclusions for each deployment.

  2. CM-02

    Workspace decisions & human review

    Functionally verified

    Responsible: Encased engineering

    Evidence & current position

    Functional journeys exercised allow, block, approval, denial, dashboard telemetry and key revocation through the real REST service.

    Still required

    Independent assessment of tenant isolation, exact-action approvals and uncertain downstream effects.

  3. CM-03

    Cooperative Python SDK

    Functionally verified

    Responsible: Encased engineering

    Evidence & current position

    Supported wrapper paths have functional tests and a connected agent example. Provider-library checks used synthetic responses.

    Still required

    Customer-local real-model qualification. Python hooks are not a hostile-code sandbox.

  4. CM-04

    External network & action gate

    Built · host verification pending

    Responsible: Engineering + host operator

    Evidence & current position

    The 0.3.0 candidate includes a credentialless network-none worker and a host-side typed-action broker.

    Still required

    Qualify alternate network paths and hook removal on the actual reviewed Linux host.

  5. CM-05

    Process limits & stop boundary

    Built · host verification pending

    Responsible: Host operator

    Evidence & current position

    The runner configures resource limits, a read-only filesystem and an independent worker deadline.

    Still required

    Collect cgroup and process evidence for escaped children, resource exhaustion and forced removal. No hosted remote-kill guarantee.

  6. CM-06

    Persistent token & spend gate

    Functionally verified

    Responsible: Engineering + host operator

    Evidence & current position

    Local broker tests cover durable budget reservations, restarts and concurrency in the host-private ledger.

    Still required

    Qualify current provider pricing, input bounds and cancellation or spend overshoot with approved billable tests.

  7. CM-07

    Linux container qualification

    Pending

    Responsible: Lucas or a qualified Linux security engineer

    Evidence & current position

    The nine Docker probes passed on a builder-run Linux host on 10 November 2026. Independent qualification remains pending.

    Still required

    Independently review artifact/image identity and probe assertions, reproduce on the intended host and collect traffic and cgroup evidence. Builder passes are not independent acceptance.

  8. CM-08

    Independent security assessment

    Pending

    Responsible: Independent reviewer

    Evidence & current position

    A ten-domain review checklist is available. No completed external report is presented.

    Still required

    Appoint a qualified independent reviewer and obtain a signed, versioned, scope-specific assessment with findings.

  9. CM-09

    Finding remediation & independent retest

    Pending

    Responsible: Engineering + independent reviewer

    Evidence & current position

    The review process requires findings, owners, fixed revisions and retest evidence. No completed retest is claimed.

    Still required

    Resolve reported findings, independently retest fixes and document treatment of unresolved risks.

  10. CM-10

    Production acceptance & ongoing assurance

    Pending

    Responsible: Customer risk owner + operations

    Evidence & current position

    Production criteria require bounded reviewer conclusions, customer acceptance and operational ownership.

    Still required

    Record acceptance for the exact deployment, monitoring, recovery, retention and change review. No production containment assurance is issued.

What a future assurance record must include

Reviewer identity and independence, report date and reference, exact tested source and image versions, host configuration, scope, limitations, findings and independent retest results. Any public conclusion must be reviewer-approved and limited to that tested deployment. A code release or completed checklist alone does not create certification.

No reviewer, assessment date or completion deadline is assigned here. Customer security audits and their delivery deadlines are separate from independent assessment of Encased's controller. This register does not promise universal bypass prevention, exactly-once effects or a hosted remote emergency-stop channel.