Control statement
Employ the following out-of-band channels for the physical delivery or electronic transmission of [Organization-defined: information, system components, or devices] to [Organization-defined: individuals or systems]: [Organization-defined: out-of-band channels].
Discussion
Out-of-band channels include local, non-network accesses to systems; network paths physically separate from network paths used for operational traffic; or non-electronic paths, such as the U.S. Postal Service. The use of out-of-band channels is contrasted with the use of in-band channels (i.e., the same channels) that carry routine operational traffic. Out-of-band channels do not have the same vulnerability or exposure as in-band channels. Therefore, the confidentiality, integrity, or availability compromises of in-band channels will not compromise or adversely affect the out-of-band channels. Organizations may employ out-of-band channels in the delivery or transmission of organizational items, including authenticators and credentials; cryptographic key management information; system and data backups; configuration management changes for hardware, firmware, or software; security updates; maintenance information; and malicious code protection updates. For example, cryptographic keys for encrypted files are delivered using a different channel than the file.
Organization-defined parameters
These values must be resolved through the organization’s tailoring and governance process. Bracketed parameter references in the control text identify where a decision is required.
From control text to operational evidence
Use Out-of-band Channels as a testable risk decision. Translate the official statement into accountable people, repeatable processes, configured technology, and evidence that demonstrates the outcome over time. In this family, pay particular attention to secure architecture, boundary protection, communications protection, cryptography, and system isolation.
Implementation workflow
- Define the control boundary, responsible owner, inherited portions, and systems or processes in scope.
- Resolve each organization-defined parameter before declaring the control implemented.
- Document how the implementation satisfies every clause of the official control statement.
- Collect evidence as a normal byproduct of operation rather than only before an assessment.
- Review exceptions, changes, and monitoring results on a risk-based cadence.
Evidence examples
- network and trust-boundary diagrams
- firewall and gateway configurations
- cryptographic configuration and key records
- segmentation and isolation test results
Common failure patterns
- diagrams omit cloud and third-party paths
- encryption enabled without key governance
- flat trust zones allow unnecessary lateral movement
- boundary rules accumulate without owner review
Questions practitioners should ask
- What risk decision is this control intended to support in this system?
- Which parts are implemented locally, inherited, shared, or not applicable—and what evidence supports that decision?
- Do the documented narrative, deployed configuration, operating process, and collected evidence agree?
- What event or threshold requires the implementation to be reviewed or changed?
Assessment objectives and methods
Show the assessment objective
[Organization-defined: out-of-band channels] are employed for the physical delivery or electronic transmission of [Organization-defined: information, system components, or devices] to [Organization-defined: individuals or systems].
Examine
- System and communications protection policy
- procedures addressing the use of out-of-band channels
- access control policy and procedures
- identification and authentication policy and procedures
- system design documentation
- system architecture
- system configuration settings and associated documentation
- list of out-of-band channels
- types of information, system components, or devices requiring the use of out-of-band channels for physical delivery or electronic transmission to authorized individuals or systems
- physical delivery records
- electronic transmission records
- system audit records
- system security plan
- other relevant documents or records
Interview
- System/network administrators
- organizational personnel with information security responsibilities
- organizational personnel installing, configuring, and/or maintaining the system
- organizational personnel authorizing, installing, configuring, operating, and/or using out-of-band channels
- system developers/integrators
Test
- Organizational processes for the use of out-of-band channels
- mechanisms supporting and/or implementing the use of out-of-band channels
Related controls
These relationships come from the official OSCAL catalog. They indicate useful dependencies or context, not automatic inheritance or equivalence.
Control enhancements
Enhancements add specificity, strength, or scope to the base control. Baseline badges show explicit selections in the official SP 800-53B OSCAL profiles.
SC-37(1) — Ensure Delivery and Transmission
Employ [Organization-defined: controls] to ensure that only [Organization-defined: individuals or systems] receive the following information, system components, or devices: [Organization-defined: information, system components, or devices].
Official discussion
Techniques employed by organizations to ensure that only designated systems or individuals receive certain information, system components, or devices include sending authenticators via an approved courier service but requiring recipients to show some form of government-issued photographic identification as a condition of receipt.
Organization-defined parameters (3)
Assessment objectives and methods
[Organization-defined: controls] are employed to ensure that only [Organization-defined: individuals or systems] receive [Organization-defined: information, system components, or devices].
Examine
- System and communications protection policy
- procedures addressing the use of out-of-band channels
- access control policy and procedures
- identification and authentication policy and procedures
- system design documentation
- system architecture
- system configuration settings and associated documentation
- list of security safeguards to be employed to ensure that designated individuals or systems receive organization-defined information, system components, or devices
- list of security safeguards for delivering designated information, system components, or devices to designated individuals or systems
- list of information, system components, or devices to be delivered to designated individuals or systems
- system audit records
- system security plan
- other relevant documents or records
Interview
- System/network administrators
- organizational personnel with information security responsibilities
- organizational personnel installing, configuring, and/or maintaining the system
- organizational personnel authorizing, installing, configuring, operating, and/or using out-of-band channels
- system developers/integrators
Test
- Organizational processes for the use of out-of-band channels
- mechanisms supporting and/or implementing the use of out-of-band channels
- mechanisms supporting/implementing safeguards to ensure the delivery of designated information, system components, or devices
Authoritative sources
Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST. Official control requirements and interpretations remain with NIST and the responsible authorizing organization.