NIST 800-171 3.13.12 (SC.L2-3.13.12): Collaborative Devices

Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device.

NIST SP 800-171 Rev. 2, requirement 3.13.12

CMMC Level 2 practice SC.L2-3.13.12Published 2026-11-11

What 3.13.12 means in practice

Cameras, microphones and networked whiteboards cannot be switched on remotely, and they show the people in the room when they are in use, for example with a light. Dedicated video conferencing systems that a participant calls or connects to are excluded.

SPRS points and the CMMC POA&M

CMMC Level 2 practice: SC.L2-3.13.12
SPRS points: 1 point. When it is not met, the DoD Assessment Methodology subtracts 1 from the score of 110.
CMMC POA&M: Allowed. It is worth 1 point, and 32 CFR 170.21(a)(2)(ii) admits requirements worth 1 point. Conditional status also needs a score of at least 88, and the item must be closed within 180 days.

Sources: NIST SP 800-171 DoD Assessment Methodology, version 1.2.1 (June 24, 2020), Annex A; 32 CFR 170.21, Plan of Action and Milestones requirements.

What an assessor checks for 3.13.12

NIST SP 800-171A gives 3 determination statements for 3.13.12, each found satisfied or other than satisfied. Determine if:

3.13.12[a] collaborative computing devices are identified.
3.13.12[b] collaborative computing devices provide indication to users of devices in use.
3.13.12[c] remote activation of collaborative computing devices is prohibited.

NIST SP 800-171A (June 2018), assessment objectives for 3.13.12

Evidence that shows 3.13.12 is met

An inventory of collaborative computing devices.
Settings that block remote activation.
Photos or specifications showing the in-use indicator.

How PolicyCortex gathers the evidence

No PolicyCortex collector reads the evidence for 3.13.12. Your team provides the evidence listed above.

Related pages

Calculator: SPRS score calculator: mark 3.13.12 and the other 109 requirements and see the score.
Sample package: Sample package: an SSP, a POA&M and an evidence chain the product generated from demonstration data.
Family: All 16 System and Communications Protection requirements (3.13).
Previous: 3.13.11: FIPS Cryptography
Next: 3.13.13: Mobile Code
All requirements: All 110 NIST SP 800-171 requirements, by family.

Related records

Guides and articles describe the work. The evidence that work produces is described in three proof pages, the architecture page, and the two pages on authorization.

proof.state: Proof of State. What the environment was, as of a date someone else picks: point-in-time records, content hashed and chained.
proof.change: Proof of Change. Who or what altered the environment, under what authority, with before and after state hashes.
proof.agency: Proof of Agency. What a machine was permitted to do before it acted, what it did, and what would have stopped it.
architecture: Architecture. How the chain is built and where the evidence is stored in each delivery mode.
authorization: Continuous ATO. How an authorizing official's decision is recorded with its package, and how the authorized system is checked against it every hour.
baseline: NIST SP 800-53. The Low, Moderate and High baselines as evidence, with the SSP, SAR and POA&M generated from one record.