NIST SP 800-66 Rev 2
Administrative

NIST SP 800-66 Rev 2 164.308(a)(4)(ii)(A): Isolating Health Care Clearinghouse Functions (Required if applicable)

If a clearinghouse is part of a larger organization, isolate ePHI from the larger organization. NIST recommends network segmentation and separate access domains.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 44 controls across 20 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-53 Rev 5 · 5 controls

CIS Controls v8 · 4 controls

  • CIS-12.2 Establish and Maintain a Secure Network Architecture
  • CIS-12.8 Establish and Maintain Dedicated Computing Resources for All Administrative Work
  • CIS-13.4 Perform Traffic Filtering Between Network Segments
  • CIS-3.12 Segment Data Processing and Storage Based on Sensitivity

ISO 27701:2019 · 4 controls

  • 6.10.1 Network security management
  • 6.3.1 Internal organization
  • 6.5.2 Information classification
  • 6.6.2 User access management

SOC 2 · 4 controls

  • SOC2-C1.1 C1.1 Identifying and maintaining confidential information
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary

FedRAMP High · 3 controls

  • AC-4 Information Flow Enforcement
  • AC-4(21) Physical or Logical Separation of Information Flows
  • SC-7 Boundary Protection

FedRAMP Moderate · 3 controls

  • AC-4 Information Flow Enforcement
  • AC-4(21) Physical or Logical Separation of Information Flows
  • SC-7 Boundary Protection

NIST SP 800-171 Rev 3 · 3 controls

AWS Well-Architected Security Pillar · 2 controls

Azure Security Benchmark · 2 controls

  • ASBv3-GS-2 Define and implement enterprise segmentation/separation of duties strategy
  • NS-1 Establish network segmentation boundaries

CMMC 2.0 · 2 controls

NIST SP 800-172 · 2 controls

  • 3.13.4e Physical and Logical Isolation Techniques
  • 3.14.3e Include Systems in Scope of Enhanced Requirements or Segregate into Purpose-Specific Networks

PCI DSS 4.0 · 2 controls

  • 1.4.1 1.4.1 NSCs between trusted and untrusted networks
  • 2.2.3 2.2.3 Primary functions with different security levels managed

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

  • ASD37-22 Network segmentation (Excellent)

Australia Consumer Data Right - Banking (CDR) · 1 control

  • AUCDR-IS-STEP2 Step 2 - Define the boundaries of the CDR data environment

C5 (Germany) · 1 control

  • C5-OPS-24 Separation of Datasets in the Cloud Infrastructure

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

ISO 27001:2022 · 1 control

  • 8.22 Segregation of networks

ISO 27002:2022 · 1 control

  • 8.22 Segregation of networks

NIST Cybersecurity Framework 2.0 · 1 control

  • NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage

NIST SP 800-161 Rev 1 · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Administrative

Query this from an agent

The graph holds this control, the 44 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll NIST SP 800-66 Rev 2 controls