NIST SP 800-171 Rev. 3 3.13.14 — Technology-specific.

What this control requires

Control and monitor the use of Voice over Internet Protocol (VoIP) technologies, including authorization, configuration, and logging, to limit exposure to telephony threats. This control supports the VoIP Usage Management capability within the Situational Awareness (3.13) family.

In plain English

Control and monitor the use of Voice over Internet Protocol (VoIP) technologies, including authorization, configuration, and logging, to limit exposure to telephony threats. In practice, this means you can prove you access management-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.

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.14) and look for objective evidence on the latest two assessment cycles.

How to implement

Logging Monitoring

AWS. Org-trail CloudTrail to a central log archive account, GuardDuty in every region, and Security Hub for cross-source correlation.

Azure. Pipe every diagnostic setting into a central Log Analytics workspace; onboard Microsoft Sentinel for SIEM/SOAR.

GCP. Aggregate audit logs in a dedicated logging project with sink to BigQuery; enable Security Command Center Premium and route findings to Chronicle SIEM.

Operational checklist

• Access. Document the trigger, the owner and the cadence.
• Configuration. Document the trigger, the owner and the cadence.
• Monitor. Document the trigger, the owner and the cadence.
• Technology-Specific.. Document the trigger, the owner and the cadence.
• Scope: management, configuration, authorization.

Evidence to collect

• Identity Scan. IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in.
• Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Technology-specific..

Common pitfalls

• Per-account logging that nobody stitches together at the org level — incidents that cross accounts go undetected for days.

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.

• ISO/IEC 27001:2022 A.8.23 — Web filtering
• NIST SP 800-53 Rev. 5 AU-10(2) — Validate Binding Of Information Producer Identity
• SOC 2 (2017 TSC) CC1.5 — Accountability for Internal Control Responsibilities
• CIS Controls v8 9.2 — Use DNS Filtering Services
• BSI C5:2020 AM-05 — Commitment to Permissible Use, Safe Handling and Return of Assets

Related controls in NIST SP 800-171 Rev. 3

• Requirement 3.13.4 — Information in Shared System Resources
• Requirement 3.3.1 — Event Logging
• Requirement 3.5.5 — Identifier Management
• Requirement 3.1.7 — Least Privilege - Privileged Functions
• Requirement 3.9.1 — Personnel Screening
• Requirement 3.1.16 — Wireless Access

References

• NIST Computer Security Resource Center — NIST SP 800-171 Rev. 3
• Catalogue identifier: Requirement 3.13.14

Topics: identity accesslogging monitoringidentity managementaccess reviewprivileged access