Encased.ai · Path to proven containment
Four steps to finish
Encased's hosted platform is live and its isolation candidate is built. Four steps stand between today and tested, reviewed containment — and each is listed here with its honest, current status.
Not yet proven. Python 0.3.2 is an isolation candidate, not production-qualified containment. Locally 73 tests pass and 9 Docker-gated probes, skipped locally, passed 9/9 on a builder-run Linux host on 10 November 2026 — builder evidence is not an independent review.
Step 1 · STEP-1
Linux container qualification
Blocked · no qualified host yet
Step 2 · STEP-2
Independent security review
Quote requested · no review delivered
Step 3 · STEP-3
Remediation and retest
Waiting on step 2
Step 4 · STEP-4
Compliance groundwork
In preparation · follows steps 1–3
Each step in detail
Step 1 · STEP-1
Linux container qualification
Blocked · no qualified host yet
Run the shipped test suite (run-linux-isolation-tests.sh) on a disposable, reviewed Linux Docker host and retain unedited logs. This verifies network isolation, credential absence, resource limits and forced-termination behaviour.
Containment boundaries & limitationsWhere this stands today
Not started: no Linux Docker host has been prepared. The two qualification-script defects were corrected in 0.3.2; reviewed base and worker image digests have not yet been supplied — none can be invented.
Step 2 · STEP-2
Independent security review
Quote requested · no review delivered
An external reviewer — independent of whoever built the controls, with hands-on Linux container isolation experience — completes the ten-domain checklist and issues a signed, version-specific conclusion.
Independent review checklist & findingsWhere this stands today
A quote covering price, scope, exclusions, turnaround and retesting has been requested. No reviewer has been engaged, no report exists, and builder evidence is not an independent conclusion.
Step 3 · STEP-3
Remediation and retest
Waiting on step 2
Close every finding raised by the independent review, then retest the fixed release so the conclusion is version-specific. Retest evidence stays private until the reviewer approves publication.
Certification status & milestonesWhere this stands today
Cannot begin: there are no reviewer findings to remediate until step 2 completes. Existing builder test observations are not findings from an independent reviewer.
Step 4 · STEP-4
Compliance groundwork
In preparation · follows steps 1–3
SOC 2 Type II and ISO/IEC 27001 readiness, an Australian secure-AI self-assessment, an asset register and a formal incident-response plan. These are meaningful once the technical steps above are complete.
Compliance statementWhere this stands today
SOC 2 Type II is in preparation and ISO/IEC 27001 is planned. Encased holds no certification, and the ASD/ACSC alignment remains a self-assessment with named gaps.
The claim gate
Only after steps 1–3 are complete will Encased claim tested, reviewed containment. Until then the isolation layer is described as "in review", not proven.
Step 4 (compliance groundwork) continues alongside and after the technical steps. It can describe readiness; it can never substitute for the Linux evidence, the independent conclusion or the retest.
