Voice Over Internet Protocol
Control and monitor the use of Voice over Internet Protocol (VoIP) technologies.
What gets scored, the objectives
SC.L2-3.13.14 is met only when every one of these 2 objectives, from NIST SP 800-171A, is satisfied. A single missed objective makes the whole requirement not met.
- a.use of Voice over Internet Protocol (VoIP) technologies is controlled
- b.use of Voice over Internet Protocol (VoIP) technologies is monitored
How this is assessed
NIST SP 800-171A defines three assessment methods. For SC.L2-3.13.14, whoever assesses it, including your own team in a self assessment, uses these:
System and communications protection policy; procedures addressing VoIP; VoIP usage restrictions; VoIP implementation guidance; system security plan; system design documentation; system audit logs and records; system configuration settings and associated documentation; system monitoring records; other relevant documents or records
System or network administrators; personnel with information security responsibilities; personnel with responsibilities for managing VoIP
Organizational process for authorizing, monitoring, and controlling VoIP; mechanisms supporting or implementing authorizing, monitoring, and controlling VoIP
What it means, in context
VoIP has different requirements, features, functionality, availability, and service limitations when compared with the Plain Old Telephone Service (POTS) (i.e., the standard telephone service). In contrast, other telephone services are based on high-speed, digital communications lines, such as Integrated Services Digital Network (ISDN) and Fiber Distributed Data Interface (FDDI) . The main distinctions between POTS and non-POTS services are speed and bandwidth . To address the threats associated with VoIP, usage restrictions and implementation guidelines are based on the potential for the VoIP technology to cause damage to the system if it is used maliciously. Threats to VoIP are similar to those inherent with any Internet-based application. NIST SP 800-58 provides guidance on Voice Over IP Systems.
Controlling VoIP technologies starts with establishing guidelines and enforcing the appropriate usage that is described in organizational policies. Monitoring should include the users’ activity for anything other than what is permitted and authorized and detection of insecure or unauthorized use of the VoIP technology . Security concerns for VoIP include eavesdropping on calls and using ID spoofing to impersonate trusted individuals. Selecting a solution that can encrypt VoIP traffic is helpful in maintaining the confidentiality and integrity of the voice data. Example You are a system administrator responsible for the VoIP system. You configure VoIP for new users after being notified that they have signed the Acceptable Use Policy for VoIP technology [a]. You verify that the VoIP solution is configured to use encryption and have enabled requirements for passwords on voice mailboxes and on phone extension management. You require phone system administrators to log in using multifactor authentication when managing the system [a]. You add the VoIP software to the list of applications that are patched monthly as needed [a,b]. Finally, you configure the VoIP system to send logs to your log aggregator so that they can be correlated with those from other systems and examined for signs of suspicious activity [b].
What passing evidence looks like
VoIP controlled and monitored where used: the VoIP system named with its protections (TLS or SRTP), or the documented no VoIP posture.
Common ways contractors fail SC.L2-3.13.14
- !Teams and Meet calling counts as VoIP and inherits the platform protections, name that. A separate desk phone system needs its own settings shown.
The step by step walkthrough for Microsoft 365 GCC High, Google Workspace, and on premises setups, plus the exact evidence to capture, lives inside the CMMC Level 2 plan.
Prove SC.L2-3.13.14, and the other 109
The Level 2 workspace walks your team through all 110 requirements at the objective level, drafts your SSP section by section from your own record for your team to read and accept, gives a prime or your own internal auditor a read only seat on the same record, and a credentialed officer reviews every step.
Book a free advisory callNo credit card, and Level 1 and Level 2 are both open, so sign up for the level your contracts call for. Self assessed and self attested: you score yourself in SPRS on a three year cycle and your senior official affirms it every year. As of September 3, 2026 a class deviation directs contracting officers to remove third party assessment from contracts. The program rule still provides for it, so your solicitation sets the track. Your team builds the same evidence either way. DFARS 252.204-7012 is unaffected, and the NIST SP 800-171 Rev 2 baseline is unchanged.
SC.L2-3.13.14 questions, answered
How many points is CMMC requirement SC.L2-3.13.14 worth?+
SC.L2-3.13.14 is worth 1 point in the CMMC Level 2 score under 32 CFR 170.24. If it is not met, you lose 1 from your total of 110.
Can SC.L2-3.13.14 be placed on a POA&M?+
Yes. A gap on SC.L2-3.13.14 can be deferred to a Plan of Action and Milestones, provided your overall score is 88 or better and the item closes within 180 days.
What family does SC.L2-3.13.14 belong to?+
SC.L2-3.13.14 is in the System & Communications Protection (SC) family, one of the 14 families of NIST SP 800-171 that make up CMMC Level 2.
- NIST SP 800-171 Rev. 2 3.13.14