Can you use Google Workspace for CMMC? Yes, with conditions. For CMMC Level 1 (Self), where you hold only Federal Contract Information (FCI), any Google Workspace edition can work if you configure it sensibly. For Controlled Unclassified Information (CUI) and CMMC Level 2 (Self), Google's own guidance points to one setup: the Enterprise Plus edition, the Assured Controls Plus add-on, and only the services covered by Google's FedRAMP High authorization.

The second half of the answer matters just as much. Buying the right licenses does not make you compliant. By Google's own count, 68 of the 110 requirements still need work from you, either inside the Admin console or outside Workspace entirely. This is explanatory content, not legal advice, so check your contract and ask Google for its current documents before you rely on any of it.

The short answer for each path

PathWhat you holdGoogle Workspace answer
CMMC Level 1 (Self)FCI onlyAny edition can work. FAR 52.204-21 lists 15 basic safeguards and sets no cloud authorization requirement.
CMMC Level 2 (Self)CUIThe cloud rule in DFARS 252.204-7012 applies. Google's CMMC guide assumes Enterprise Plus with Assured Controls Plus.
SPRS scoreCUISame 110 requirements and the same cloud rule. Workspace settings you have not configured still count as not met.

Not sure which row is yours? Start with whether you handle CUI. For Level 1, the free Level 1 checklist covers the safeguards one by one.

One caution for every row: a free personal Gmail account is not Google Workspace. It has no Admin console, no organization-wide settings, and it is not the product Google's federal authorization describes. Contract work does not belong there.

What the rules require of a cloud provider

The rule comes from the contract clause, not from CMMC itself. DFARS 252.204-7012 says that if you use an external cloud service provider to store, process, or transmit covered defense information, you must require and ensure two things. First, the provider meets security requirements equivalent to the FedRAMP Moderate baseline. Second, the provider complies with paragraphs (c) through (g) of the clause: cyber incident reporting, malicious software, media preservation, access for forensic analysis, and damage assessment.

The CMMC rule points back to the same clause. The scoping table in 32 CFR 170.19 says a cloud service provider that handles CUI "shall meet the FedRAMP requirements in 48 CFR 252.204-7012."

CMMC Phase 2 and third-party assessments are suspended for now, so the paths in play today are the self-assessed ones. That does not relax any of this. DFARS 252.204-7012 is unchanged and applies wherever CUI is handled.

What Google says about Workspace

Google publishes three documents worth reading before you decide. Here is what they say, in Google's words rather than a reseller's.

Two details deserve a second look. Google's incident commitment is to inform affected customers within 72 hours when their environment is properly configured. Reporting to the DoD is still your job, on your clock. Our post on the 72-hour reporting rule explains that duty. And Google's DFARS page describes data location and Assured Controls as not explicitly required by the clause, while its CMMC page says you must use Assured Controls Plus. The careful reading is to follow the CMMC guidance and get the answer for your account in writing.

What is still yours to do

The implementation guide sorts the 110 requirements of NIST SP 800-171 Rev 2 into three groups. The counts below come from the guide's own lists.

Group in Google's guideRequirementsExamples
You configure it in Workspace47Multifactor authentication (3.5.3), least privilege (3.1.5), audit logging (3.3.1), password rules (3.5.7), mobile devices (3.1.18)
Implemented natively by Google42Data center physical protection (3.10.1), maintenance (3.7.1), FIPS-validated cryptography (3.13.11)
You handle it outside Workspace21Security training (3.2.1), risk assessment (3.11.1), the system security plan (3.12.4), session lock (3.1.10)

Read the middle row carefully. "Native" describes the Workspace service. It says nothing about the laptop someone uses to open a drawing, your office network, or the other software in your scope. An assessor judges your whole environment against the objectives in NIST SP 800-171A, and your system security plan has to say who does what. Our scoping guide shows how to draw that boundary.

Email is where CUI leaks

Inside your own Workspace domain, mail and files stay within the service Google describes. The moment you send CUI to someone outside it, you depend on the other side too. Requirement 3.13.8 calls for cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless other physical safeguards protect it, and Google's guide places that requirement in the group you configure. Decide how outside recipients get CUI, write it down, and test it. If the recipient's mailbox is a consumer account, sending the file was the mistake, however well it was encrypted on the way.

Export-controlled data needs more

If your CUI is also controlled under the International Traffic in Arms Regulations (ITAR), the question changes. Google's ITAR page points Workspace customers to Client-side encryption, properly configured, to meet the end-to-end encryption carve-out in 22 CFR 120.54(a)(5). That is a separate feature with its own setup and key management. Talk to your export compliance contact before any ITAR data goes in.

Add-ons and connected apps

Google's guidance limits you to authorized services. That includes anything bolted on later: AI features, Marketplace apps, backup tools, and browser extensions that read mail or files. Each one is a new place CUI can go. Check it against Google's in-scope list or the vendor's own FedRAMP status before you switch it on.

Google Workspace or Microsoft GCC High?

Neither is required by name. The clause asks for FedRAMP Moderate or equivalent and the (c) through (g) commitments, and you can choose any provider that gives you both in writing. Many primes and consultants know the Microsoft route better, which can make questionnaires easier. Google shops often prefer to stay put rather than move every mailbox. Our comparison of GCC High and commercial Microsoft 365 covers the other side. If only a few people touch CUI, a small enclave on either platform can cost less than upgrading everyone.

What to do this week

  1. Find out which Workspace edition you have and whether Assured Controls Plus is on the account.
  2. Decide what you hold: FCI only, CUI, or export-controlled CUI.
  3. Ask Google or your reseller for the CMMC attestation letter, the Customer Responsibility Matrix, and a quote for the edition and add-on.
  4. List every Workspace service, add-on, and connected app in use. Turn off the ones outside the authorized scope.
  5. Enforce 2-Step Verification for every account and separate administrator accounts from daily ones.
  6. Write down how CUI reaches people outside your domain.
  7. Record all of it in your system security plan, and score the result. The free SPRS calculator shows what each open item costs.

CMMC Map, CMMC compliance software for small defense contractors, walks you through each of these requirements in the free assessment. The paid plan adds a read-only Google Workspace evidence reader that looks at configuration and metadata, never the contents of mail or documents, so you can see which of the settings above are actually switched on.

See which requirements are still yours

The free CMMC Map assessment walks through all 110 requirements and the Level 1 safeguards, so you can see what your cloud provider covers and what you still have to do.

Start free in CMMC Map
Free to assess · Documents $149/mo · No credit card