Working noteAwaiting revisionVersion 0.1
Policy Enforcement in Secure Enclaves
A short working note for the second Rabat session: policy meaning, enforcement placement, evidence, and failure handling.
Published 24 July 2026Updated 29 August 2026
Purpose and status
This note framed PESAEAS Morocco #2 in Rabat. It remains a working basis for review, not an implementation standard or a claim that one enclave technology solves containment.
The central question is how a declared policy becomes an enforceable boundary whose decisions can be inspected independently of the autonomous workload.
Starting propositions
The session used five propositions to frame a credible enforcement path.
- A decision identifies the subject, requested action, target, relevant context, and resulting effect.
- Policy defines defaults, precedence, limits, exceptions, and behaviour when required context is unavailable.
- Every relevant transition passes through an enforcement point the workload cannot alter or bypass.
- Application, operating-system, network, hardware-backed, and operational controls have distinct responsibilities.
- Evidence connects workload identity and policy version to the decision and the action that occurred.
Questions for Rabat
The session was framed around the following unresolved questions.
- What fields belong in a minimal, interoperable policy decision record?
- Which controls belong above the operating system, and which must not remain there alone?
- What exactly should attestation prove to an external reviewer?
- How can emergency changes remain auditable without delaying incident response?