The Defense Compliance ReportCMMC 2.0 & the Defense Industrial Base

CMMC Compliant VoIP: Is Your Phone System in Scope, and What Passes SC.L2-3.13.14

By The Defense Compliance Report Editorial Team · Last verified: November 17, 2026

General information for the defense industrial base, not legal, contractual or compliance advice. Not affiliated with DoD, the Department of War, NIST, The Cyber AB, Microsoft, Zoom, Cisco, Avaya or any government agency. Your contract and your own scoping decisions control what applies to you.

Short answer: No phone system is "CMMC certified." CMMC assesses your company's systems, so a CMMC compliant VoIP setup is one you have scoped, configured and documented. If your phones, voicemail, call recordings, transcripts or fax lines can carry CUI, they belong in your Level 2 scope. Two requirements decide most of the work: SC.L2-3.13.14, which says to control and monitor VoIP, and the cloud rule, which says a hosted phone service that handles CUI must be FedRAMP Moderate authorized or equivalent. Microsoft Teams Phone in GCC High runs through Direct Routing, because Microsoft's calling plans are not offered there. CMMC Phase II is still suspended as of November 17, 2026, but Level 2 (Self) assessments and DFARS 252.204-7012 still apply.

Who this page is for

  • IT managers and MSPs at defense contractors who run a hosted phone system, an on-premises PBX or Microsoft Teams calling and need to know how it fits a Level 2 self-assessment.
  • Companies moving to GCC High or a CUI enclave that have found out their phone plan changes too.
  • Owners replacing an old phone system who want to buy one that won't create a finding.
  • Anyone filling in an SSP who reached SC.L2-3.13.14 and isn't sure what "control and monitor VoIP" means in practice.

If you are still deciding whether you handle CUI at all, start with who needs CMMC certification. This page assumes you hold CUI and have a Level 2 obligation now or soon.

Is your phone system in scope for CMMC?

Scope follows the information. 32 CFR 170.19 calls assets that "process, store, or transmit CUI" CUI Assets, and an asset can be out of scope only if it cannot do any of those things. CUI does not stop being CUI because someone said it out loud. The federal CUI rule defines a document to include "phonic or visual reproductions or oral statements, conversations, or events," and it defines disseminating as transmitting CUI "through any means" (32 CFR 2002.4).

Phone systems also store things. A voicemail, a recorded call, a transcript or an incoming fax can sit in a mailbox or a vendor's cloud for months. Here is how each part of a typical business phone system lines up with the asset categories in 32 CFR 170.19.

Phone system component — Likely asset category if CUI is discussed or stored — Why
Phone system componentLikely asset category if CUI is discussed or storedWhy
Cloud phone service (UCaaS) carrying CUI calls or voicemailCUI Asset, and the provider is a cloud service providerIt transmits and stores CUI, so the FedRAMP Moderate rule applies
Voicemail and voicemail transcriptsCUI AssetA recording or transcript that contains CUI is stored CUI
Call recording and AI call summariesCUI AssetSame as voicemail, and often stored in a separate place with its own retention
Desk phones and conference phones on your networkCUI Asset or Contractor Risk Managed AssetDepends on whether policy allows CUI on calls and how the phones are separated
Softphone apps on laptops and mobile phonesCUI Asset if used for CUI callsThe device runs the client and may cache voicemail
On-premises PBX or session border controllerCUI Asset if CUI calls pass through itIt carries the media and signaling
Fax server, e-fax service or multifunction faxCUI Asset if CUI is faxedFaxed drawings and specs are stored CUI
Call logs and admin portalSecurity Protection Asset or CUI AssetAdmin access controls who can reach recordings and settings
Separate guest or lobby phone line with no CUI usePossibly out of scopeOnly if it cannot carry CUI and is separated from CUI assets

In our view, most contractors can't credibly call a phone system out of scope if staff can speak about CUI on it or leave CUI in voicemail. Out-of-scope assets must be unable to process, store or transmit CUI, and you must be ready to justify that. The realistic choice for most phone systems is between treating them as CUI Assets and treating them as Contractor Risk Managed Assets with a written policy that keeps CUI off calls. The CMMC scoping guide covers those categories in depth.

Contractor Risk Managed or CUI Asset: how to decide

A Contractor Risk Managed Asset is one that "can, but [is] not intended to, process, store, or transmit CUI because of security policy, procedures, and practices in place." That label can fit a phone system if you keep CUI off it in practice. It still has to appear in your asset inventory, SSP and network diagram, and an assessor can run a limited check if your documentation raises questions.

Question — If yes — If no
QuestionIf yesIf no
Do engineers, buyers or program managers discuss drawings, specs or controlled program details by phone?Treat the phone system as a CUI AssetContractor Risk Managed may fit
Do callers leave voicemail about CUI programs?CUI Asset, including voicemail storageKeep checking
Do you record calls or run AI summaries?The recordings and summaries are in scopeKeep checking
Does anyone fax CUI?The fax path is a CUI AssetKeep checking
Can you show a written rule, training and monitoring that keep CUI off the phones?Contractor Risk Managed is defensibleYou can't support the lighter label

What SC.L2-3.13.14 requires

The requirement text in NIST SP 800-171 Rev 2 is one line: "Control and monitor the use of Voice over Internet Protocol (VoIP) technologies." NIST's discussion says usage restrictions and implementation guidelines should be "based on the potential for the VoIP technology to cause damage to the system if it is used maliciously," and that threats to VoIP "are similar to those inherent with any Internet-based application." It points to NIST SP 800-58, Security Considerations for Voice Over IP Systems, for detail.

NIST SP 800-171A turns that line into two assessment objectives.

Objective — Text — What evidence usually shows it
ObjectiveTextWhat evidence usually shows it
3.13.14[a]Use of VoIP technologies is controlledAn approved phone system list, VoIP acceptable use rules, user provisioning records, encryption and admin settings
3.13.14[b]Use of VoIP technologies is monitoredPhone system logs sent to your log tool, alerts for unapproved VoIP apps, periodic reviews

The CMMC Assessment Guide for Level 2, version 2.13 adds plain examples. It says control "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." It names two threats, eavesdropping on calls and caller ID spoofing, and says "Selecting a solution that can encrypt VoIP traffic is helpful."

The guide's example system administrator does six things:

  1. Sets up VoIP for new users only after they sign the VoIP acceptable use policy.
  2. Confirms the VoIP solution is configured to use encryption.
  3. Requires passwords on voice mailboxes and on phone extension management.
  4. Requires multifactor authentication for phone system administrators.
  5. Adds the VoIP software to the monthly patch list.
  6. Sends VoIP logs to the log aggregator so they can be correlated with other systems.

The guide's assessment considerations ask two questions: are approved VoIP technologies defined, and is there monitoring for unapproved VoIP or unapproved use of the allowed solution? If you can answer both with documents and screenshots, you have the core of 3.13.14.

What "unapproved VoIP" looks like

Monitoring for unapproved use means watching for calling tools you didn't approve. Common examples are a personal calling app on a work laptop, a consumer conferencing tool a sales rep installed, or a second phone service someone signed up for with a company card. Your application allowlist, software inventory and firewall or DNS logs are the usual places to catch them. The CMMC asset inventory guide explains how to record what you approve.

The other requirements your phone system touches

SC.L2-3.13.14 is the VoIP requirement by name, but a phone system in scope gets assessed against the rest of Level 2 too. These are the ones most tied to a phone system. Point values come from the scoring method in 32 CFR 170.24.

Requirement — What it means for a phone system — Points if NOT MET
RequirementWhat it means for a phone systemPoints if NOT MET
SC.L2-3.13.14 VoIPApproved system, usage rules, monitoring1
SC.L2-3.13.12 Collaborative devicesConference phone microphones and cameras can't be turned on remotely, and users can see when they are on1
SC.L2-3.13.8 CUI in transitEncrypt calls and voicemail that carry CUI, for example SIP over TLS and SRTP3
SC.L2-3.13.11 FIPS cryptographyThe encryption protecting CUI must be FIPS-validated3 if not FIPS-validated, 5 if none
SC.L2-3.13.1 Boundary protectionPhone traffic crosses a monitored boundary, such as a firewall or session border controller5
SC.L2-3.13.15 Communications authenticityProtect sessions against hijacking and man-in-the-middle attacks5
IA.L2-3.5.3 Multifactor authenticationMFA for phone admins and for users who reach voicemail or recordings over the network5 if none, 3 if only remote and privileged users
AU.L2-3.3.1 System auditingKeep phone system logs5
AU.L2-3.3.2 User accountabilityTie phone actions to named users3
CM.L2-3.4.1 System baseliningInventory and baseline settings for phones, PBX and session border controllers5
SI.L2-3.14.1 Flaw remediationPatch phone firmware, PBX software and softphone apps5
AC.L2-3.1.18 Mobile device connectionControl phones and tablets that run the softphone5
AC.L2-3.1.19 Encrypt CUI on mobileEncrypt CUI that the softphone app caches on mobile devices3

For SC.L2-3.13.12, NIST's discussion names networked white boards, cameras and microphones, and excludes "dedicated video conferencing systems, which rely on one of the participants calling or connecting to the other party to activate the video conference." The Assessment Guide adds that if a device can't show it's in use, manual means such as a paper notice on the entryway can work.

NIST already ties phones to these requirements. Its discussion of 3.3.2 lists "use of Voice over Internet Protocol (VoIP)" among the events to consider logging. Its discussion of 3.4.1 lists "voice and data switches" as network components with security settings. For the encryption rows, see CMMC encryption requirements and CMMC FIPS 140-2 requirements. For MFA, see CMMC MFA requirements.

Where CUI hides in a phone system

Stored data is easier to overlook than live calls. Walk through each place a call leaves something behind.

Where it lands — What it can contain — What to check
Where it landsWhat it can containWhat to check
VoicemailAudio, plus a text transcript if transcription is onWhere it's stored, who can open it, how long you keep it
Voicemail to emailThe same audio and transcript as an email attachmentThe mailbox must be in your CUI scope
Call recordingsFull conversationsStorage location, retention, access, FedRAMP status of the store
AI summaries and transcriptsKey points, action items, names, part numbersWhether the AI feature sits inside the authorized service
Contact center and call queuesRecordings, notes, screen capturesWho in the vendor's support team can reach them
FaxDrawings, specs, purchase ordersFax server storage, email delivery, printer trays
Text messages from the phone appShort notes, photosWhether texting is approved for CUI at all
Call detail recordsNumbers, times, durationsUsually not CUI alone; protect them as audit logs

Microsoft's own documentation shows how this works for Teams. A Cloud Voicemail message is "an email message with an audio file attachment" delivered to the user's Exchange mailbox, and it contains the transcription if transcription is on (Microsoft Learn). Microsoft also documents protected voicemail, which uses sensitivity labels to encrypt voicemail and block forwarding for Exchange Online mailboxes. So if voicemail can contain CUI, the mailbox that holds it must sit inside your CUI boundary. The Microsoft Teams CMMC compliance page covers the rest of the Teams footprint.

Cloud phone systems: the FedRAMP Moderate test

If a hosted phone service stores, processes or transmits CUI, the provider is a cloud service provider under the rule. For a Level 2 (Self) assessment, 32 CFR 170.16(c)(2) allows it only if the offering is FedRAMP Authorized at Moderate or higher on the FedRAMP Marketplace, or meets FedRAMP Moderate equivalency under DoD policy. Your own equipment that connects to the service stays in your scope, and you must document the provider's customer responsibility matrix in your SSP.

DFARS 252.204-7012, paragraph (b)(2)(ii)(D), says the same thing in contract terms. If you use "an external cloud service provider to store, process, or transmit any covered defense information," you must require and ensure that it meets security requirements equivalent to the FedRAMP Moderate baseline and follows the clause's incident reporting rules (DFARS 252.204-7012).

The DoD CIO's December 21, 2023 equivalency memo says FedRAMP Moderate Authorized offerings on the Marketplace "can be leveraged without further assessment." An offering that isn't authorized must show 100 percent compliance with the latest FedRAMP Moderate baseline, assessed by a FedRAMP-recognized third-party assessor, with no open findings from that assessment. Ask early whether a phone vendor can provide that package. Our FedRAMP equivalency guide walks through what to ask for.

Calling and fax offerings on the FedRAMP Marketplace

We searched the FedRAMP Marketplace data on November 17, 2026 for calling, unified communications and fax offerings with a FedRAMP Authorized status. This is not a full list of every option, and it is not a recommendation. Marketplace status can change, so open the listing before you sign.

Offering — Marketplace status and level — Notes
OfferingMarketplace status and levelNotes
Microsoft 365 GCC HighFedRAMP Authorized, HighMicrosoft 365 for government; Microsoft says Teams Phone System here runs through Direct Routing
Microsoft 365 GCCFedRAMP Authorized, ModerateMicrosoft 365 Government Community Cloud and supporting services
Zoom for GovernmentFedRAMP Authorized, ModerateLists Zoom Phone, described as a cloud phone system with PBX features and PSTN connectivity, among its authorized products
Webex for GovernmentFedRAMP Authorized, ModerateLists Webex for Government Calling as a cloud calling service that can replace an on-premises PBX
Avaya Government CloudFedRAMP Authorized, ModerateUnified communications and contact center, including enterprise voice
Enterprise Cloud Fax Government (ECFax)FedRAMP Authorized, HighCloud fax service from Consensus Cloud Solutions
ETHERFAX GovCloudFedRAMP Authorized, HighCloud fax service hosted in AWS GovCloud

Three checks matter more than the vendor's logo:

  1. The exact feature must be inside the authorization. A vendor can have an authorized government platform while a newer feature, add-on or AI tool sits outside it. Ask for the authorization boundary in writing. Our Zoom CMMC compliance page shows why: availability of a product is not proof that it is authorized.
  2. You must be on the government version. A commercial account with the same brand name is a different offering.
  3. Get the customer responsibility matrix. It tells you which settings, such as encryption, retention and admin MFA, are your job. See the CMMC shared responsibility matrix guide.

Microsoft Teams Phone in GCC High: Direct Routing

Contractors that move to Microsoft 365 GCC High for CUI email and files find that calling works differently there. Microsoft's GCC High and DoD service description says PSTN Calling and PSTN Conferencing "are currently not available in GCC High and DoD," and that Phone System and Audio Conferencing "are being delivered via Direct Routing."

Direct Routing connects Teams to the phone network through a session border controller that you or a voice partner run. Microsoft's Direct Routing planning guide lists GCC High and DoD among the environments where it's offered and gives the GCC High SIP address as sip.pstnhub.gov.teams.microsoft.us. Signaling uses SIP over TLS, and for GCC High and DoD only port 5061 may be used. Media uses SRTP.

Teams calling item — Commercial Microsoft 365 — GCC High
Teams calling itemCommercial Microsoft 365GCC High
Microsoft Calling Plans (Microsoft as carrier)AvailableNot available, per Microsoft's service description
Direct Routing (your SBC or a partner's)AvailableThe documented path for Phone System
Audio Conferencing dial-inAvailableDelivered through Direct Routing
Voicemail storageExchange mailboxExchange mailbox in GCC High
Session border controller in your scopeIf you run itYes if you run it; if a partner runs it, treat the partner as a service provider

For scope, the Teams service is covered by the GCC High authorization, but the session border controller and the voice carrier on the other side are not. If you host the SBC, it is part of your boundary and needs hardening, patching, logging and admin MFA like any other CUI asset. If a voice partner hosts it, that partner carries your CUI calls, so ask how it meets the cloud rule or the external service provider rules. Our GCC High cost and licensing page explains the budget side of this. The CMMC external service provider requirements page explains the provider side.

On-premises PBX and SIP trunks

An on-premises phone system doesn't avoid the cloud rule if a cloud piece touches CUI, but it does move most of the work to you. If the PBX sits in your office and carries CUI calls, it is a CUI Asset like a file server.

On-premises item — What an assessor will expect
On-premises itemWhat an assessor will expect
PBX or call managerIn the asset inventory, baselined, patched, admin MFA, logs kept
Phone VLANSeparated from guest networks; documented in the network diagram
SIP trunk to the carrierEncrypted where the carrier supports it; a firewall or SBC at the boundary
IP desk phonesDefault passwords changed, firmware patched, web admin disabled or restricted
Voicemail serverTreated as CUI storage; access limited; retention set
MSP that manages the PBXAn external service provider in your SSP; see CMMC requirements for MSPs

The public phone network beyond your carrier isn't something you control. NIST's discussion of 3.13.14 compares VoIP with plain old telephone service. For calls that must carry CUI to someone outside your company, decide in policy which channels you allow. A simple rule is to keep detailed CUI off outside calls and send it through an approved file sharing service instead; see CMMC compliant file sharing. The CMMC network segmentation guide shows how to separate the voice network.

Fax is part of the phone system

If you fax CUI, the fax machine, fax server or e-fax service is a CUI Asset. A cloud fax service that stores or transmits CUI faces the same FedRAMP Moderate test as any other cloud service. The two fax offerings in the table above are listed at FedRAMP High.

The Center for Development of Security Excellence teaches DoD personnel these fax rules under DoDI 5200.48: the sender makes sure protection is in place at the receiving end, the fax is attended by someone authorized to receive CUI, the machine is in a controlled environment, and an SF 901 cover sheet marks the CUI (CDSE CUI Life Cycle Short #3, January 2024). That guidance is written for government staff, but it is a sensible baseline for a contractor's fax procedure.

The same CDSE guide says hard-wired landlines are permitted for CUI, to avoid wireless transmission of CUI when other options exist, and for telework, that "use of a conventional wired landline or Voice over Internet Protocol (VOIP) is recommended."

Mobile phones and softphones

Softphone apps on cell phones need their own rules. If staff use a softphone for CUI calls, the phone holding that app is a mobile device that connects to your CUI systems. AC.L2-3.1.18 (5 points) and AC.L2-3.1.19 (3 points) then apply, along with your mobile device management. The CMMC mobile device management page covers enrollment, encryption and remote wipe.

Mobile setup — Scope effect — Common control
Mobile setupScope effectCommon control
Company phone with the approved softphone, enrolled in MDMIn scope as a mobile deviceMDM policy, app protection, encryption, remote wipe
Personal phone with the softphone appIn scope if used for CUI calls or voicemailApp protection policy, conditional access, or a ban on CUI calls
Personal phone used only for normal cellular calls about non-CUI topicsUsually outside the phone systemPolicy that CUI isn't discussed on personal devices
Voicemail played on a personal phoneVoicemail data reaches that phoneBlock voicemail access from unmanaged devices

How a VoIP gap affects your SPRS score

A Level 2 self-assessment starts at 110 points and subtracts each NOT MET requirement's value. SC.L2-3.13.14 and SC.L2-3.13.12 are worth 1 point each. Under 32 CFR 170.21, a 1-point requirement can go on a plan of action for a Conditional Level 2 (Self) status, as long as your score is at least 88 (0.8 of 110) and you close it within 180 days.

The bigger risks are the requirements a weak phone setup drags down with it.

Gap — Requirement — Points lost — Can it go on a POA&M for Conditional status?
GapRequirementPoints lostCan it go on a POA&M for Conditional status?
No VoIP policy or monitoringSC.L2-3.13.141Yes
Conference phone mic can be turned on remotely, no indicatorSC.L2-3.13.121Yes
CUI calls or voicemail sent without encryptionSC.L2-3.13.83No
Encryption on, but not FIPS-validatedSC.L2-3.13.113Yes, this is the one 3-point exception
No encryption protecting CUISC.L2-3.13.115No
No MFA on privileged accounts, including phone system adminsIA.L2-3.5.33 if other users have it, 5 if no one doesNo
PBX and SBC missing from the baselineCM.L2-3.4.15No
Phone firmware never patchedSI.L2-3.14.15No

The contract clauses behind the score matter too. DFARS 252.204-7019 requires a current NIST SP 800-171 assessment, not more than 3 years old, posted in SPRS. DFARS 252.204-7020 requires you to give the government access to your facilities, systems and personnel for a Medium or High assessment. DFARS 252.204-7021 and 252.204-7025 carry the CMMC level a solicitation requires. A phone system you scored as MET is part of what those clauses let DoD check.

A cloud phone service that holds CUI but isn't FedRAMP Moderate authorized or equivalent isn't a point deduction you can plan around. It means the service doesn't meet 32 CFR 170.16(c)(2) or DFARS 7012. Move the CUI or move providers. The SPRS score guide explains how the score is posted, and the POA&M 180-day rule explains the closeout clock.

Evidence to keep for SC.L2-3.13.14

Self-assessment or not, your Affirming Official signs off on the score, and DoD can still run government-led assessments during the suspension. Keep evidence you could hand over.

Evidence — What it proves — Objective
EvidenceWhat it provesObjective
VoIP or phone system policy naming the approved systemUse is controlled3.13.14[a]
Signed acceptable use acknowledgmentsUsers agreed to the rules before getting service3.13.14[a]
Screenshot of encryption settings (TLS and SRTP or the vendor's equivalent)Calls are protected in transit3.13.14[a], 3.13.8
Admin MFA setting and admin account listOnly named admins change the system3.13.14[a], 3.5.3
Voicemail PIN and extension management settingsMailboxes and settings are protected3.13.14[a]
Patch records for phones, PBX, SBC and softphone appsThe system is kept current3.13.14[a][b], 3.14.1
Phone system logs flowing into your log toolUse is monitored3.13.14[b], 3.3.1
Report or alert for unapproved calling appsUnauthorized VoIP is detected3.13.14[b]
FedRAMP Marketplace listing and CRM for a hosted serviceThe cloud rule is met170.16(c)(2)
SSP section describing the phone system and its asset categoryThe scope decision is documented3.12.4

If your log tool is a SIEM, the SIEM for CMMC page explains what to forward. The CMMC Level 2 documentation checklist shows where this fits in your SSP.

Step by step: making your phone system CMMC ready

  1. List every calling and fax tool. Include the main phone system, Teams or Zoom calling, conference phones, softphone apps, e-fax and any call recording or AI note tool.
  2. Trace where CUI goes. Ask engineering, purchasing, quality and program staff whether they discuss or receive CUI by phone, voicemail or fax. Add the answers to your CUI data flow diagram.
  3. Pick the asset category. Decide CUI Asset or Contractor Risk Managed Asset for each component and write down why.
  4. Check the cloud rule. For each hosted component that will touch CUI, find its FedRAMP Marketplace listing at Moderate or higher, or get the equivalency body of evidence.
  5. Turn on encryption and admin MFA. Use the vendor's TLS and SRTP settings or equivalent, and confirm the cryptography is FIPS-validated where it protects CUI.
  6. Lock down storage. Set voicemail and recording retention, limit who can open recordings, and turn off transcription or AI summaries that sit outside the authorized service.
  7. Fix conference rooms. Confirm room devices show when the microphone or camera is on and can't be switched on remotely.
  8. Write the VoIP policy. Name the approved system, the rules for CUI on calls, the rules for personal devices and how you monitor.
  9. Send logs and patch. Forward phone system logs to your log tool and add phones, PBX, SBC and softphones to the patch cycle.
  10. Update the SSP and score. Describe the phone system in your SSP, score 3.13.12 and 3.13.14 from your evidence, and add any open item to your POA&M.

Buying a CMMC compliant VoIP system: questions to ask

No vendor can sell you CMMC compliance, because CMMC assesses your systems. A vendor can sell you a service that makes your assessment easier. These questions separate the two.

Ask the vendor — A good answer — A red flag
Ask the vendorA good answerA red flag
Is this exact offering FedRAMP Authorized at Moderate or higher?A Marketplace listing for the government version"We're CMMC compliant" with no listing
Are calling, voicemail, recording and AI features all inside the authorization?A written boundary that names each featureOnly meetings are covered
Can I see your customer responsibility matrix?A CRM mapped to NIST SP 800-171A marketing one-pager
Are signaling and media encrypted, and with FIPS-validated modules?Named protocols and a validation reference"Bank-grade encryption"
Where are voicemail and recordings stored, and for how long?U.S. government cloud regions, configurable retentionUnclear or commercial storage
Who on your staff can reach my recordings?Screened U.S. support with logged accessGeneral global support
Can I export logs to my SIEM?Native export or APILogs only in the vendor portal
How do I get incident notices that meet DFARS 7012?A documented processNo answer

If you're shopping for a GCC High tenant at the same time, the best GCC High providers for CMMC page covers resellers, and CUI enclave providers covers enclaves that bundle calling.

Rev 3 dropped the VoIP requirement, but Rev 2 still binds

NIST SP 800-171 Revision 3, published in May 2024, lists 03.13.14 as "Withdrawn" with the reason "Technology-specific." That does not remove the requirement for CMMC. 32 CFR 170 incorporates NIST SP 800-171 Revision 2, and the DoD CIO page says the department will enforce NIST 800-171 Rev 2 during the suspension. Until DoD changes the rule or your contract says otherwise, SC.L2-3.13.14 stays on your Level 2 list. See NIST 800-171 Rev 2 vs Rev 3 for the full comparison.

What the CMMC suspension changes for your phone system

The suspension changes very little for your phone system. On July 13, 2026 the Department of War suspended the move to CMMC Phase II. The implementing memo says requiring activities may include only CMMC Level 1 (Self) or Level 2 (Self) and may not designate Level 2 (C3PAO) or Level 3 (DIBCAC) (suspension memo, PDF). The DoD CIO CMMC page still says that "All Phase I self-assessment requirements remain firmly in place" and that the suspension "does not eliminate the requirement for companies to protect information in accordance with DFARS clause 252.204-7012." As of November 17, 2026, no restart date has been announced. CMMC phases tracks the status.

Item — Status on November 17, 2026 — Source
ItemStatus on November 17, 2026Source
Level 2 (Self) in new contractsAllowedSuspension memo; Class Deviation 2026-O0025, Revision 3
Level 2 (C3PAO) designationsNot allowed during the suspensionSuspension memo
SC.L2-3.13.14 and the other 109 requirementsStill part of Level 232 CFR 170; NIST SP 800-171 Rev 2
FedRAMP Moderate rule for cloud services with CUIStill in forceDFARS 252.204-7012; 32 CFR 170.16
Government-led assessmentsMay still happenDoD CIO CMMC page

What it costs

Phone system costs vary too much by vendor and seat count for us to publish a reliable range, and we don't quote prices we can't source. These are the drivers that move the number.

Cost driver — Why it matters
Cost driverWhy it matters
Moving from a commercial phone service to a FedRAMP authorized government offeringGovernment editions are separate products with their own pricing and feature lists
Direct Routing for Teams in GCC HighYou pay for a session border controller or a voice partner, plus carrier service
Encryption and FIPS settingsOlder desk phones may not support the encryption you need
Log forwardingYour SIEM or log service may charge by volume
Policy, training and SSP workInternal hours or consultant time
Fax migrationA cloud fax service at FedRAMP Moderate or higher replaces an old fax line or server

For the assessment itself, DoD's final rule estimates $34,277 for a small entity's Level 2 self-assessment and affirmation and $37,196 over three years (CMMC final rule, 89 FR 83092). Those figures assume the requirements are already in place, so fixing a phone system costs extra.

Common mistakes with phones and CMMC

  • Leaving the phone system off the asset inventory. If it isn't in the inventory, SSP and network diagram, you can't defend any scope decision about it.
  • Moving email to GCC High but leaving voicemail-to-email on a commercial service. Voicemail with CUI then lands outside your boundary.
  • Assuming the brand name covers the feature. The government edition, and the specific feature inside it, must be in the authorization.
  • Turning on AI call summaries without checking where they run. Summaries of CUI calls are CUI.
  • Ignoring the session border controller. In GCC High Direct Routing, the SBC carries your calls and needs the same hardening as a server.
  • No monitoring for unapproved calling apps. That leaves 3.13.14[b] NOT MET even if the main system is locked down.
  • Calling the phone system out of scope while staff discuss CUI on it. An out-of-scope label needs proof that the asset can't carry CUI.

Which provider category fits

If you need — Provider category — Start here
If you needProvider categoryStart here
A scope decision and SSP language for phonesReadiness consultant or RPOCMMC consultant
GCC High with Teams calling and Direct RoutingGCC High provider or MSPGCC High CMMC
A managed enclave that includes calling or keeps CUI off phonesCUI enclave providerCUI enclave providers
Ongoing patching, logging and MFA for the PBX and phonesManaged service providerCMMC provider categories

The CMMC provider categories page explains how these differ. Find My CMMC Path is free; we may receive a referral fee from providers, and providers can't pay for placement in a recommendation.

CMMC compliant VoIP: FAQ

Is my phone system in scope for CMMC?

Yes, if it can carry or store CUI. That includes calls where staff discuss CUI, voicemail, recordings, transcripts and faxes. If you can show a written rule, training and monitoring that keep CUI off the phones, you may treat it as a Contractor Risk Managed Asset, which still goes in your inventory and SSP.

Is there such a thing as a CMMC certified VoIP provider?

No. CMMC assesses contractors' systems, not products. What you can check is whether the provider's government offering is FedRAMP Authorized at Moderate or higher on the FedRAMP Marketplace, and whether its customer responsibility matrix covers your settings.

What does SC.L2-3.13.14 require?

It requires you to control and monitor the use of VoIP. NIST SP 800-171A splits that into two objectives: VoIP use is controlled, and VoIP use is monitored. In practice that means an approved system, usage rules, encryption, admin MFA, patching and logs.

How many points is SC.L2-3.13.14 worth?

1 point. It can go on a plan of action for Conditional Level 2 (Self) status if your score is at least 88 and you close it within 180 days.

Can I use Microsoft Teams Phone in GCC High?

Yes, through Direct Routing. Microsoft says PSTN Calling and PSTN Conferencing are not available in GCC High and DoD, and that Phone System and Audio Conferencing are delivered through Direct Routing. The session border controller and voice carrier are outside the GCC High authorization, so scope them separately.

Is Zoom Phone or Webex Calling FedRAMP authorized?

On November 17, 2026 the FedRAMP Marketplace listed Zoom for Government (Moderate) with Zoom Phone among its authorized products, and Webex for Government (Moderate) with Webex for Government Calling among its capabilities. Confirm that the feature you plan to use is inside the authorization and that you're on the government edition.

Do voicemail and call recordings count as CUI?

They can. The federal CUI rule treats phonic reproductions and oral statements as documents. A voicemail or recording that contains CUI is stored CUI, and so is its transcript.

Can I keep using an old on-premises PBX?

Yes, if you can secure it. It becomes a CUI Asset that needs baselining, patching, admin MFA, logging and encryption where CUI passes through it. If the vendor no longer ships security patches, that is a flaw remediation problem.

Does faxing CUI put my fax line in scope?

Yes. The fax machine, fax server or e-fax service that sends or stores CUI is a CUI Asset. A cloud fax service handling CUI must meet the FedRAMP Moderate rule.

NIST Rev 3 withdrew the VoIP requirement. Can I skip it?

No. NIST SP 800-171 Rev 3 withdrew 03.13.14 as technology-specific, but CMMC Level 2 is built on Rev 2, and DoD says it is enforcing Rev 2 during the suspension. SC.L2-3.13.14 still counts.

What we verified

On November 17, 2026 we opened each source linked on this page: the DoD CIO CMMC page, the July 13, 2026 suspension memo, Class Deviation 2026-O0025 Revision 3, 32 CFR 170.16, 170.19, 170.21 and 170.24 on eCFR (current through November 13, 2026), 32 CFR 2002.4, DFARS 252.204-7012, 7019, 7020, 7021 and 7025, NIST SP 800-171 Revision 2, NIST SP 800-171A, NIST SP 800-171 Revision 3, NIST SP 800-58, the CMMC Assessment Guide Level 2 version 2.13, the DoD CIO FedRAMP Moderate equivalency memo, the FedRAMP Marketplace listings in the table, Microsoft's GCC High and DoD service description, Direct Routing planning guide and Cloud Voicemail documentation, the CDSE CUI Life Cycle Short #3 student guide, and the CMMC final rule cost estimates. The DoD CIO site blocked direct download of the Assessment Guide, so we read the same version 2.13 file from a public web archive copy. We did not test any vendor's product, and vendor features and Marketplace status can change.

Sources