- Inventory collaborative devices and applications — room systems, softphones, webcams, collaboration platforms — and configure remote-activation restrictions in their management consoles.
- Document any exception, such as remote-support activation of a room system, as a defined and deliberate one rather than a discovered surprise.
03.13.12OFFICIAL TITLEPENDING NIST SME REVIEW
03.13.12 — Collaborative Computing Devices and Applications
03.13 System and Communications Protection · NIST SP 800-171 Rev. 3
Independent summary of the official requirement
Requires prohibiting the remote activation of collaborative computing devices and applications, with organization-defined exceptions where remote activation is to be allowed, and providing an explicit indication of use to users physically present at the devices.
Rev. 3 requirement text is multi-part and parameterized with organization-defined values, so this site summarizes rather than reproduces it. The summary is independent — read the official publication for the binding wording.
NIST SP 800-171 Rev. 3 — Protecting CUI in Nonfederal Systems ↗NIST SP 800-171A Rev. 3 — Assessing Security Requirements for CUI ↗Independent interpretation
What this requirement is after
Cameras and microphones in conference rooms and collaboration tools must not be switchable-on from afar without the people in the room knowing. Remote activation is prohibited outside defined exceptions, and anything in use announces it — the light is on because someone present must be able to tell.
Across revisions
Rev. 3 extends the Rev. 2 requirement from devices to devices and applications and adds a defined-exceptions parameter for remote activation.
Mapped practices
Brilliant at the Basics practices that support this requirement
No practice maps to this requirement — deliberately.
The campaign’s twenty practices are a priority list, not a control catalog, and none of them works this requirement’s substance directly. It still applies to you if it is in your contract’s scope: address it through your own implementation and the related artifacts below, and treat the absence of a mapping here as honesty, not permission to skip it.
Doing the work
Implementation considerations and evidence
- Configuration showing remote activation disabled or restricted for collaborative devices and applications
- The documented exception list, if any exists
Artifacts
Templates and worksheets with a mapped relationship
No artifact in the library names this requirement yet. The library index groups everything by category and practice.
The other revision
Where this came from in Rev. 2
Provenance
Sources and review status
| Primary sources | NIST SP 800-171 Rev. 3 — Protecting CUI in Nonfederal Systems · NIST SP 800-171A Rev. 3 — Assessing Security Requirements for CUI |
|---|---|
| Review status | Pending NIST SME review |
| Content version | 1.0 |
| Updated |