Skip to content

Isolation

What is Isolation?

A security technique that separates systems, processes, or data from each other to prevent unauthorized access and contain the impact of breaches.

Information Security

Terms that appear alongside isolation

Each of these is named in at least one of the same controls as isolation. The number is how many controls name both.

Frameworks that govern isolation

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

What the standards actually require on isolation

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

Australian Information Security Manual7 controls

When using a software-based isolation mechanism to share a physical server's hardware, the underlying operating system is hardened.

ISM-1605 · When using a software-based isolation mechanism to share a physical server's hardware, the →
NIST SP 800-53 Rev 53 controls

Security Function Isolation. Isolate security functions from nonsecurity functions

NIST800-SC-3 · Security Function Isolation. Isolate security functions from nonsecurity functions →
FedRAMP High2 controls

Employ boundary protection mechanisms to separate FedRAMP-defined components supporting FedRAMP-defined missions; HIGH only.

SC-7(21) · Isolation of System Components →
MITRE D3FEND2 controls

Apply D3FEND ISOLATE tactic to create logical or physical barriers in a system to reduce attack opportunities and impact. D3-EI Execution Isolation (D3-HBPI Hardware-based Process Isolation + D3-SCF System Call Filtering + D3-IBCA IO Channel Authentication + D...

MITRE-D3FEND-Isolate-Tactic-Execution-Network-Isolation-Sandboxing-Microsegmentation-DNS-Filtering · MITRE D3FEND Isolate Tactic + Execution + Network Isolation + Sandboxing + Microsegmentation + DNS Filtering →
NIST SP 800-1902 controls

Avoid co tenanting workloads of dramatically different sensitivity on the same node or namespace. Use node selectors, taints, and dedicated node pools to separate regulated workloads from general purpose applications.

SP800-190-3.11 · Mixed Sensitivity Workload Isolation →
NIST SP 800-82 Rev 32 controls

Isolate Safety Instrumented Systems (SIS) from the Basic Process Control System (BPCS) and other networks using physical or logical separation to preserve the integrity of safety functions.

OT-ARCH-4 · Safety Instrumented System Isolation →

Questions people ask about isolation

What is Isolation?
A security technique that separates systems, processes, or data from each other to prevent unauthorized access and contain the impact of breaches.
Why is Isolation important for compliance?
Isolation is a key concept in Information Security. Understanding isolation helps organizations meet regulatory requirements, reduce risk, and demonstrate due diligence during audits. Our compliance platform maps 686 frameworks with 311K cross-framework control mappings.
Which compliance frameworks address Isolation?
Isolation appears in the requirement text of Australian Information Security Manual, NIST SP 800-53 Rev 5, FedRAMP High, MITRE D3FEND, NIST SP 800-190. Across these standards we have identified 18 controls that name it directly, each linked to the control text on the compliance platform.
Where can I learn more about Isolation?
Explore our compliance framework pages to see how isolation 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 686 frameworks.

See how Isolation applies across compliance frameworks

Our platform maps 686 frameworks with 311K 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.