Control statement
- a.Prohibit remote activation of collaborative computing devices and applications with the following exceptions: [Organization-defined: exceptions where remote activation is to be allowed] ; and
- b.Provide an explicit indication of use to users physically present at the devices.
Discussion
Collaborative computing devices and applications include remote meeting devices and applications, networked white boards, cameras, and microphones. The explicit indication of use includes signals to users when collaborative computing devices and applications are activated.
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 Collaborative Computing Devices and Applications 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
- SC-15a.remote activation of collaborative computing devices and applications is prohibited except [Organization-defined: exceptions where remote activation is to be allowed];
- SC-15b.an explicit indication of use is provided to users physically present at the devices.
Examine
- System and communications protection policy
- procedures addressing collaborative computing
- access control policy and procedures
- system design documentation
- system configuration settings and associated documentation
- system audit records
- system security plan
- other relevant documents or records
Interview
- System/network administrators
- organizational personnel with information security responsibilities
- system developer
- organizational personnel with responsibilities for managing collaborative computing devices
Test
- Mechanisms supporting and/or implementing the management of remote activation of collaborative computing devices
- mechanisms providing an indication of use of collaborative computing devices
Related controls
These relationships come from the official OSCAL catalog. They indicate useful dependencies or context, not automatic inheritance or equivalence.
Related NIST SP 800-171 requirements
These Rev. 3 requirements cite this base control or one of its enhancements as a source. The relationship does not by itself determine contractual applicability or complete implementation.
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-15(1) — Physical or Logical Disconnect
Provide [Organization-defined: sc-15.01_odp] disconnect of collaborative computing devices in a manner that supports ease of use.
Official discussion
Failing to disconnect from collaborative computing devices can result in subsequent compromises of organizational information. Providing easy methods to disconnect from such devices after a collaborative computing session ensures that participants carry out the disconnect activity without having to go through complex and tedious procedures. Disconnect from collaborative computing devices can be manual or automatic.
Organization-defined parameters (1)
Assessment objectives and methods
the [Organization-defined: sc-15.01_odp] disconnect of collaborative computing devices is/are provided in a manner that supports ease of use.
Examine
- System and communications protection policy
- procedures addressing collaborative computing
- access control policy and procedures
- system design documentation
- system configuration settings and associated documentation
- system audit records
- system security plan
- other relevant documents or records
Interview
- System/network administrators
- organizational personnel with information security responsibilities
- system developer
- organizational personnel with responsibilities for managing collaborative computing devices
Test
- Mechanisms supporting and/or implementing the physical disconnect of collaborative computing devices
SC-15(2) — Blocking Inbound and Outbound Communications Traffic
This enhancement is marked withdrawn in the official OSCAL catalog. Related-control metadata below may identify where its intent was incorporated.
SC-15(3) — Disabling and Removal in Secure Work Areas
Disable or remove collaborative computing devices and applications from [Organization-defined: systems or system components] in [Organization-defined: secure work areas].
Official discussion
Failing to disable or remove collaborative computing devices and applications from systems or system components can result in compromises of information, including eavesdropping on conversations. A Sensitive Compartmented Information Facility (SCIF) is an example of a secure work area.
Organization-defined parameters (2)
Assessment objectives and methods
collaborative computing devices and applications are disabled or removed from [Organization-defined: systems or system components] in [Organization-defined: secure work areas].
Examine
- System and communications protection policy
- procedures addressing collaborative computing
- access control policy and procedures
- system design documentation
- system configuration settings and associated documentation
- system audit records
- list of secure work areas
- systems or system components in secured work areas where collaborative computing devices are to be disabled or removed
- system security plan
- other relevant documents or records
Interview
- System/network administrators
- organizational personnel with information security responsibilities
- organizational personnel with responsibilities for managing collaborative computing devices
Test
- Mechanisms supporting and/or implementing the capability to disable collaborative computing devices
SC-15(4) — Explicitly Indicate Current Participants
Provide an explicit indication of current participants in [Organization-defined: online meetings and teleconferences].
Official discussion
Explicitly indicating current participants prevents unauthorized individuals from participating in collaborative computing sessions without the explicit knowledge of other participants.
Organization-defined parameters (1)
Assessment objectives and methods
an explicit indication of current participants in [Organization-defined: online meetings and teleconferences] is provided.
Examine
- System and communications protection policy
- procedures addressing collaborative computing
- access control policy and procedures
- system design documentation
- system configuration settings and associated documentation
- system audit records
- list of types of meetings and teleconferences requiring explicit indication of current participants
- system security plan
- other relevant documents or records
Interview
- System/network administrators
- organizational personnel with information security responsibilities
- organizational personnel with responsibilities for managing collaborative computing devices
Test
- Mechanisms supporting and/or implementing the capability to indicate participants on collaborative computing 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.