Skip to content

Enclave

What is Enclave?

A network segment with specific security requirements that is separated from other segments through access controls and monitoring.

Information Security

Frameworks that govern enclave

ISO 27001:2022View framework →NIST SP 800-53 Rev 5View framework →NIST Cybersecurity Framework 2.0View framework →

What the standards actually require on enclave

Requirements naming enclave across 6 standards, quoted from the control text.

NIST SP 800-2071 control

Places a gateway PEP at the boundary of a resource enclave (a group of resources), suitable for legacy applications or on-premises data centers that cannot protect resources individually.

SP800-207-DEP-ENCLAVE · Enclave-Based Deployment →
DISA Security Technical Implementation Guides (STIGs)3 controls

A single SRG or STIG is not all-inclusive for a system: a system may include database, web server, DNS and other components, and compliance with all the SRGs and STIGs applicable to it is required.

disa-security-technical-implementation-guides-stigs::PGM-3 · PGM-3 All applicable SRGs and STIGs apply to a system, and product STIGs take precedence over the SRG →
ITU-T X.805 - Security Architecture for End-to-End Communications2 controls

Security Dimension 3 Non-Repudiation per X.805 Clause 6.3: Non-repudiation stops a person or entity from credibly denying that it carried out a given action on data, by keeping evidence of network-related actions available (for example evidence of an obligatio...

X805-Dim3-Non-Repudiation-Proof-Origin-Delivery-Sender-Receiver-Denial-Prevention · ITU-T X.805 Security Dimension 3 - Non-Repudiation + Proof of Origin + Proof of Delivery + Sender + Receiver Denial Prevention + Digital Signatures + Timestamping + Audit Logs + Forensic Evidence + Court-Admissible Records →
OWASP MASVS2 controls

Per OWASP MASVS v2 MASVS-CRYPTO: correct use of cryptography in mobile apps. Requirements include (a) use industry-vetted cryptographic primitives + libraries + parameter choices appropriate to risk + (b) avoid weak + deprecated algorithms + custom cryptograph...

OWASPMASVS-2 · MASVS-CRYPTO: Cryptography Usage →
CISA Industrial Control Systems (ICS) Security Guidance1 control

Limit damage from perimeter breaches by segmenting networks into logical enclaves and restricting host-to-host communication paths so a compromised system cannot reach other enclaves.

CISA-ICS-7S-4 · Build a Defendable Environment →
ENISA Data Protection Engineering - From Theory to Practice1 control

TEEs (e.g. Intel SGX, ARM TrustZone, AMD SEV) provide a hardware-protected enclave where confidential computation can run with attestation and integrity guarantees, supporting confidential cloud workloads and processing of regulated data.

ENISA-DPE-4.3 · Trusted execution environments (TEEs) →

Questions people ask about enclave

What is Enclave?
A network segment with specific security requirements that is separated from other segments through access controls and monitoring.
Why is Enclave important for compliance?
Enclave is a key concept in Information Security. Understanding enclave helps organizations meet regulatory requirements, reduce risk, and demonstrate due diligence during audits. Our compliance platform maps 1,016 frameworks with 316K cross-framework control mappings.
Which compliance frameworks address Enclave?
Enclave appears in the requirement text of NIST SP 800-207, DISA Security Technical Implementation Guides (STIGs), ITU-T X.805 - Security Architecture for End-to-End Communications, OWASP MASVS, CISA Industrial Control Systems (ICS) Security Guidance. Across these standards we have identified 10 controls that name it directly, each linked to the control text on the compliance platform.
Where can I learn more about Enclave?
Explore our compliance framework pages to see how enclave applies across different standards and regulations. Our implementation guides provide step-by-step guidance, and the compliance platform offers AI-powered analysis of how this concept maps across 1,016 frameworks.

See how Enclave applies across compliance frameworks

Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.

Explore on Platform
Written and maintained by Gerard Blokdyk, The Art of Service.