NIST 800-171 3.13.5Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks
Overview
This control requires organizations to implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. It is part of the System and Communications Protection family and is required for CMMC Level 2 certification. Defense contractors handling CUI must implement this control to protect sensitive information and demonstrate compliance during assessments.
Assessment Objectives
- 1Determine if the organization has defined policies and procedures to implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks
- 2Determine if the organization implements mechanisms to implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks
- 3Verify that the implementation is consistent with organizational policies and NIST 800-171 requirements
Implementation Guidance
Implement this control by establishing documented policies and procedures, deploying appropriate technical controls, and maintaining evidence of ongoing compliance. Regularly review and test the implementation to ensure effectiveness and address any gaps identified during assessments.
Common Audit Gaps
Related DFARS Clauses
Frequently Asked Questions
What is NIST 800-171 control 3.13.5?
NIST 800-171 control 3.13.5 requires organizations to implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. This control is part of the System and Communications Protection family and is required for CMMC Level 2 certification.
How do you implement NIST 800-171 3.13.5?
To implement control 3.13.5, establish documented policies, deploy technical controls to implement subnetworks for publicly accessible system components that are physica, and maintain evidence of compliance. Regular testing and monitoring are essential.
What evidence is needed for NIST 800-171 3.13.5?
Evidence for control 3.13.5 typically includes written policies and procedures, system configuration documentation, audit logs showing enforcement, and records of periodic reviews. Assessors will look for both documentation and technical implementation.
Related Controls
3.13.4|Prevent unauthorized and unintended information transfer via shared system resources
System and Communications Protection
3.13.6|Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception)
System and Communications Protection
3.14.1|Identify, report, and correct system flaws in a timely manner
System and Information Integrity
More in System and Communications Protection
Related Guides
Check your compliance for NIST 800-171 3.13.5
Cabrillo Club automates evidence collection and audit readiness across all 110 NIST 800-171 controls.
Join Free