NIST SP 800-171 Rev. 3·Requirement 3.13.12·high·Component: Situational Awareness

What this control requires

This control prohibits the remote activation of collaborative computing devices and applications, with specified exceptions. It requires providing explicit indications to users when these devices are in use, such as notifications when microphones or cameras are activated, to ensure transparency and security during their operation. This control supports the Device Usage Control capability within the Situational Awareness (3.13) family.
— NIST SP 800-171 Rev. 3, Requirement 3.13.12

In plain English

This control prohibits the remote activation of collaborative computing devices and applications, with specified exceptions. In practice, this means you can prove you device remote-level controls on a defined cadence.

Why it matters

DoD contractors and their subcontractors must implement all 100 SP 800-171 requirements to keep CUI handling contracts. Gaps are scored against the SPRS scoring methodology; below a 110-point starting score, each unmet requirement deducts points and a below-threshold score can disqualify a bid.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

A C3PAO conducting a CMMC Level 2 assessment uses NIST SP 800-171A objectives. They expect a System Security Plan (SSP), Plan of Action & Milestones (POA&M) for any gaps, and objective evidence (configurations, ticket records, training records) for every requirement.

Within Situational Awareness, the assessor will trace your implementation back to the catalogue reference (Requirement 3.13.12) and look for objective evidence on the latest two assessment cycles.

How to implement

Endpoint Protection

MDM. Make MDM enrollment a hard gate for device access (Intune compliance + Conditional Access, or Jamf + Okta device trust). Unmanaged devices simply don't get a session token.

EDR. Deploy CrowdStrike / SentinelOne / Defender for Endpoint to every server and laptop; alert on any host that stops sending telemetry for >24h.

Operational checklist

  • Device. Document the trigger, the owner and the cadence.
  • Remote. Document the trigger, the owner and the cadence.
  • Protection. Document the trigger, the owner and the cadence.
  • Security. Document the trigger, the owner and the cadence.
  • Collaborative. Document the trigger, the owner and the cadence.
  • Scope: remote, applications, security, protection, notifications when microphones, ensure transparency.

Evidence to collect

  • User Device Scan. MDM compliance state per user device (Intune / Jamf / Workspace ONE).
  • Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.

Endpoint compliance telemetry (Intune, Jamf) proves managed coverage. Focus: Collaborative Computing Devices and Applications.

Common pitfalls

  • Pilot MDM rollouts that quietly exclude executives or engineers; carving out the highest-risk users is the most common audit failure.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

Related controls in NIST SP 800-171 Rev. 3

References

Topics: endpoint securityendpoint protection