Knowledge is Power
BARE METAL CYBERKnowledge is Power

Sitewide Search

Search Bare Metal Cyber

Search courses, individual lessons, wiki entries, books, podcasts, magazine articles, Daily Cyber News, and Darwin.

NIST SP 800-171 CUI Protection Center

03.13.01 — Boundary Protection

Read the official CUI requirement and assessment content, then use the separately labeled Bare Metal Cyber perspective to connect it to implementation, evidence, and sustained operation.

1Source controls
6Assessment objectives
3Assessment methods

03.13 — System and Communications Protection · NIST SP 800-171 Revision 3

Active
Official NIST requirement content

Security requirement

  1. a.Monitor and control communications at external managed interfaces to the system and key internal managed interfaces within the system.
  2. b.Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.
  3. c.Connect to external systems only through managed interfaces that consist of boundary protection devices arranged in accordance with an organizational security architecture.
Official NIST discussion

Discussion

Managed interfaces include gateways, routers, firewalls, network-based malicious code analysis, virtualization systems, and encrypted tunnels implemented within a security architecture. Subnetworks that are either physically or logically separated from internal networks are referred to as demilitarized zones or DMZs. Restricting or prohibiting interfaces within organizational systems includes restricting external web traffic to designated web servers within managed interfaces, prohibiting external traffic that appears to be spoofing internal addresses, and prohibiting internal traffic that appears to be spoofing external addresses.

Bare Metal Cyber interpretation

Implementation perspective

Treat Boundary Protection as a CUI protection outcome that must be reflected in the system boundary, documented implementation, operational behavior, and assessment evidence. Pay particular attention to secure architecture, boundary protection, communications security, cryptography, and isolation of CUI processing.

  1. Confirm the requirement is in scope for the CUI system components, services, users, and external connections being assessed.
  2. Resolve every organization-defined parameter through an approved governance and tailoring process.
  3. Map each clause of the requirement to an accountable owner, implementation mechanism, and evidence source.
  4. Verify that inherited and shared implementations are supported by current provider evidence and responsibility boundaries.
  5. Collect evidence during normal operation and review changes, exceptions, and deficiencies on a risk-based cadence.

Questions to ask

  • Which CUI assets, data flows, users, and services are protected by this requirement?
  • Which portions are implemented locally, inherited, shared, or not applicable, and what evidence supports that determination?
  • Do the system security plan, deployed configuration, operating process, and assessment evidence tell the same story?
  • What change, incident, or threshold should trigger reassessment?

Evidence and validation

  • network and trust-boundary diagrams
  • firewall and gateway configurations
  • cryptographic configuration and key records
  • segmentation and isolation test results

Common failure patterns

  • diagrams omitting cloud and third-party paths
  • encryption enabled without key governance
  • flat trust zones permitting unnecessary lateral movement
  • boundary rules accumulating without owner review
Official NIST SP 800-171A content

Assessment objectives and methods

Assessment objectives (6)
  1. a.

    communications at external managed interfaces to the system are monitored.

  2. a.

    communications at external managed interfaces to the system are controlled.

  3. a.

    communications at key internal managed interfaces within the system are monitored.

  4. a.

    communications at key internal managed interfaces within the system are controlled.

  5. b.

    subnetworks are implemented for publicly accessible system components that are physically or logically separated from internal networks.

  6. c.

    external system connections are only made through managed interfaces that consist of boundary protection devices arranged in accordance with an organizational security architecture.

Examine

  • system and communications protection policy and procedures
  • procedures for boundary protection
  • list of key internal boundaries within the system
  • boundary protection hardware and software
  • system configuration settings
  • security architecture
  • system audit records
  • system design documentation
  • system security plan
  • other relevant documents or records

Interview

  • personnel with boundary protection responsibilities
  • personnel with information security responsibilities
  • system developers
  • system administrators

Test

  • mechanisms for implementing boundary protection capabilities
Official source-control relationships

Source NIST SP 800-53 controls

These controls are referenced by the official SP 800-171 Rev. 3 OSCAL record. Open the corresponding control pages for complete control text, enhancements, D3FEND mappings, and related learning.

Source controlSC-7Open SP 800-53 control →
Source record

Authoritative sources

Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST. The official publications, the responsible federal agency, and the governing contract or agreement determine applicability, tailoring, assessment depth, and required implementation.