3.13.14
SC.L2-3.13.14 · Level 2

Control and monitor the use of Voice over Internet Protocol (VoIP) technologies

NIST SP 800-171 Rev 2 · §3.13.14

Control and monitor the use of Voice over Internet Protocol (VoIP) technologies

Assessment objectives

3.13.14[a] use of Voice over Internet Protocol (VoIP) technologies is controlled.
Examine
[SELECT FROM: System and communications protection policy; procedures addressing VoIP; VoIP usage restrictions; VoIP implementation guidance; security plan; system design documentation; system configuration settings and associated documentation; system monitoring records; system audit logs and records; other relevant documents or records].
Interview
[SELECT FROM: System or network administrators; personnel with information security responsibilities; personnel with responsibilities for managing VoIP].
Test
[SELECT FROM: Organizational process for authorizing, monitoring, and controlling VoIP; mechanisms supporting or implementing authorizing, monitoring, and controlling VoIP].
3.13.14[b] use of Voice over Internet Protocol (VoIP) technologies is monitored.
Examine
[SELECT FROM: System and communications protection policy; procedures addressing VoIP; VoIP usage restrictions; VoIP implementation guidance; security plan; system design documentation; system configuration settings and associated documentation; system monitoring records; system audit logs and records; other relevant documents or records].
Interview
[SELECT FROM: System or network administrators; personnel with information security responsibilities; personnel with responsibilities for managing VoIP].
Test
[SELECT FROM: Organizational process for authorizing, monitoring, and controlling VoIP; mechanisms supporting or implementing authorizing, monitoring, and controlling VoIP].

What we look for in practice

The following are placeholder notes that should be refined based on practice experience.

What assessors look for in practice. Documented evidence that this control is implemented across all CUI-handling systems within scope. Specific artifacts vary, but expect requests for written procedures, system configurations, and operational records demonstrating the control is active.

Common failure patterns. Typical issues include incomplete documentation, inconsistent implementation across systems, and missing periodic review records. Refine this section as your practice accumulates direct assessment experience.

Strong evidence looks like. Formal policy referencing this control, technical configurations demonstrating enforcement, periodic review logs with sign-off, and procedures for handling exceptions.

Scoring and POA&M context. 1-point control under the DoD Assessment Methodology. Lower scoring impact, but still required for full compliance. POA&M-eligible — deferral up to 180 days is allowed under conditional certification per 32 CFR 170.21.