Enclave Page Out is the eviction of a memory page from a protected enclave back to normal system memory or storage. In enclave-based computing, the runtime must save enclave state securely so the page can be restored later without exposing its contents to the operating system or other processes.
What Enclave Page Out Does
Enclave page out is the secure eviction of enclave memory to ordinary system memory or storage so the runtime can free protected pages without exposing their contents. The security requirement is not the move itself, but preserving confidentiality and integrity while the page is away from the enclave.
That makes enclave page out a core part of confidential computing behaviour, where the platform must treat enclave contents as sensitive even when they are not resident in protected execution memory. A well-designed implementation must assume the operating system can observe paging events, but not the plaintext state being swapped.
Why Enclave Paging Is Security-Sensitive
Paging in a protected execution model creates a boundary-crossing event. If the save-and-restore path is weak, the enclave can leak code, data, keys, or session material through memory snapshots, replayed pages, or tampered restore state. The risk is highest when the page-out path is handled by components that are not trusted with enclave internals.
Because the operating system commonly manages page placement, enclave paging must be designed so untrusted infrastructure cannot read or silently alter what is being saved. That is why enclave paging is usually paired with memory encryption, integrity protection, and sealed or encrypted page metadata rather than ordinary swap semantics.
How Enclave Page Out Preserves Confidentiality
A secure page-out path typically serialises enclave state in an encrypted form, attaches integrity checks, and uses replay-resistant metadata so the page can be restored exactly as intended. The runtime may also need to preserve versioning or freshness information so an attacker cannot reintroduce an old page image.
In practice, this is a tightly coupled part of the enclave’s trust model, not a generic operating-system paging feature. The enclave must be able to trust that its internal state remains confidential while idle in normal memory, and that restoration only succeeds when the platform and runtime invariants still hold.
Operational Consequences and Restore Behaviour
Page out is not just a storage event, it changes how the enclave behaves under memory pressure, scheduling contention, and fault handling. Excessive paging can increase latency, expose more restore operations to monitoring, and make enclave workloads more sensitive to platform configuration and resource starvation.
When restore fails, the enclave may need to abort, reinitialise, or reconstruct state from a higher-level secret or session boundary. That is why enclave-aware applications often distinguish between transient eviction, recoverable resume, and conditions that should force re-attestation or session renewal.
For deeper background on confidential computing architectures, Confidential Computing Guide covers TEEs, attestation, and encrypted memory models that make page out safe.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 provides the primary governance reference for this term.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | SC-28 — Protection of Information at Rest | Enclave page out protects enclave data while it is stored outside protected execution memory. |
| SC-4 — Information in Shared Resources | The paging path passes sensitive state through resources shared with less trusted system components. | |
| IA-5 — Authenticator Management | Enclave page out can involve protected secrets and cryptographic material that must remain controlled across restore. | |
| Recommendation — Encrypt enclave page images and related state before they leave trusted execution memory. Prevent shared-memory and paging paths from exposing enclave contents to unauthorized code. Rotate and protect enclave-related secrets that would be compromised if paging state is exposed. | ||
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 29, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org