Security requirement
- a.Prohibit the remote activation of collaborative computing devices and applications with the following exceptions: [Organization-defined: exceptions].
- b.Provide an explicit indication of use to users physically present at the devices.
Discussion
Collaborative computing devices include white boards, microphones, and cameras. Notebook computers, smartphones, display monitors, and tablets containing cameras and microphones are considered part of collaborative computing devices when conferencing software is in use. Indication of use includes notifying users (e.g., a pop-up menu stating that recording is in progress or that the microphone has been turned on) when collaborative computing devices are activated. Dedicated video conferencing systems, which typically rely on one of the participants calling or connecting to the other party to activate the video conference, are excluded. Solutions to prevent device usage include webcam covers and buttons to disable microphones.
Tailoring decisions required
Resolve these values through the governing organization’s approved tailoring and risk-management process before declaring the requirement implemented.
Implementation perspective
Treat Collaborative Computing Devices and Applications 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.
- Confirm the requirement is in scope for the CUI system components, services, users, and external connections being assessed.
- 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 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
Assessment objectives and methods
Assessment objectives (2)
- a.
the remote activation of collaborative computing devices and applications is prohibited with the following exceptions: [Organization-defined: exceptions].
- b.
an explicit indication of use is provided to users who are physically present at the devices.
Examine
- system and communications protection policy and procedures
- procedures for collaborative computing
- access control policy and procedures
- system configuration settings
- system design documentation
- system audit records
- system security plan
- other relevant documents or records
Interview
- personnel with responsibilities for managing collaborative computing devices
- personnel with information security responsibilities
- system developers
- system administrators
Test
- mechanisms for supporting or implementing the management of remote activation of collaborative computing devices
- mechanisms for providing an indication of use of collaborative computing devices
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.
Authoritative sources
- NIST SP 800-171 Revision 3 official publication ↗
- NIST SP 800-171A 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.