Security requirement
- a.Authorize and control [Organization-defined: organization-defined types of system components] entering and exiting the facility.
- b.Maintain records of the system components.
Discussion
Enforcing authorizations for the entry and exit of system components may require restricting access to delivery areas and isolating the areas from the system and media libraries. This requirement does not enhance a specific requirement in SP 800-171 but can be used to strengthen the protection of CUI associated with critical programs or high value assets.
Tailoring decisions required
Resolve these values through the governing organization’s approved tailoring and risk-management process before declaring the requirement implemented.
Protection strategies supported
These classifications are carried from the official SP 800-172 OSCAL record and help explain the enhanced requirement’s defensive purpose.
Implementation perspective
Treat Delivery and Removal of System Components as an enhanced CUI protection outcome for elevated threat conditions that must be reflected in the system boundary, documented implementation, operational behavior, and assessment evidence. Pay particular attention to physical access, facility protection, visitor accountability, and protection of system components that handle CUI.
- Confirm the federal agency selected this enhanced requirement for the critical program or high-value asset and identify the CUI system components, services, users, and external connections in scope.
- Resolve every organization-defined parameter through an approved governance and tailoring process.
- Map each clause of the requirement to an accountable owner, implementation mechanism, and evidence source.
- Verify that inherited and shared implementations are supported by current provider evidence and responsibility boundaries.
- Collect evidence during normal operation and review changes, exceptions, and deficiencies on a risk-based cadence.
Questions to ask
- Which critical-program or high-value-asset CUI, data flows, users, and services are protected by this enhanced 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
- badge and visitor logs
- physical access reviews
- facility diagrams and sensor records
- environmental and power test results
Common failure patterns
- logical controls undermined by physical access
- tailgating or visitor exceptions normalized
- critical infrastructure omitted from access reviews
- environmental alarms disconnected from response
Assessment objectives and methods
Assessment objectives (5)
- a.
[Organization-defined: types of system components] are authorized when entering the facility.
- a.
[Organization-defined: types of system components] are controlled when entering the facility.
- a.
[Organization-defined: types of system components] are authorized when exiting the facility.
- a.
[Organization-defined: types of system components] are controlled when exiting the facility.
- b.
records of the system components entering and exiting the facility are maintained.
Examine
- Physical and environmental protection policy
- procedures addressing the delivery and removal of system components from the facility
- facility housing the system
- records of items entering and exiting the facility
- system security plan
- other relevant documents or records
Interview
- Personnel with responsibilities for controlling system components entering and exiting the facility
- personnel with information security responsibilities
Test
- Process for authorizing, monitoring, and controlling system-related items entering and exiting the facility
- mechanisms supporting and/or implementing, authorizing, monitoring, and controlling system components entering and exiting the facility
Source NIST SP 800-53 controls
These controls are referenced by the official SP 800-172 Rev. 3 OSCAL record. Open the corresponding control pages for complete control text, enhancements, D3FEND mappings, and related learning.
Authoritative sources
- NIST SP 800-172 Revision 3 official publication ↗
- NIST SP 800-172A Revision 3 official publication ↗
- NIST OSCAL Content release used for this import ↗
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.