Google Workspace, set up for CUI and checked every day.
A separate Google Workspace tenant for the people on your team who handle Controlled Unclassified Information — owned by you, configured with your administrator, and checked for setting changes in CMMCSync so you stay assessment-ready between assessments.
Who it is for
Small defense contractors that need a CUI environment for CMMC Level 2 and would rather keep it in Google Workspace. It fits when:
- Your contracts carry DFARS 252.204-7012, or you expect to receive CUI soon.
- Only part of your staff works with CUI, and the rest should not have to change how they work.
- You want the CUI environment in your own name, administered by your own people.
What you get
A tenant only for CUI work
We stand up a new Google Workspace tenant on a domain of its own and add only the people who handle CUI. Everyone else stays on the mail and files they use today.
Yours, not ours
Your organization owns the tenant. Your own administrator applies each setting while we guide the session, and the standing access CMMCSync keeps afterward is read-only.
Configured to Google’s CMMC guide
The configuration follows the Google Workspace CMMC Level 2 Implementation Guide that Google publishes, control by control.
Checked every day
Each day CMMCSync reads a defined set of the tenant’s security settings and account counts, such as 2-Step Verification enforcement and enrollment for enclave users and admins, and how many super-administrator accounts exist. A change that weakens one of them raises an alert, and CMMCSync proposes a finding that a person on your team accepts or rejects.
The paperwork an assessor asks for
System Security Plan entries for the enclave, a responsibility matrix for our service, and a data-flow diagram.
Security data only
We handle security data only, never CUI. CMMCSync does not read email or Drive content, and for the enclave it stores counts, not lists of users.
Licenses and price: Google Workspace licenses for the enclave are arranged by quote. Contact sales.
Logging and alerts
Collecting the enclave's logs and raising alerts on them is a separate service: Google Security Operations.
Who does what
Runs Google Workspace and publishes its CMMC Level 2 implementation guide. The guide sorts each control into one of three groups: implemented natively by Google Workspace, requiring configuration in Google Workspace, or requiring implementation outside it.
Your administrator
Holds the tenant's administrator accounts, applies the settings during the guided session, decides who joins the enclave, and grants CMMCSync its read-only access. Your team reviews every proposed finding.
CMMCSync
Leads the guided session, prepares the SSP entries, responsibility matrix and data-flow diagram, then reads the defined settings each day, alerts on changes and proposes findings for your review.
CMMCSync is built by HanumanLabs, a Google Cloud partner.
What it is not
- Not a certification. A well-configured enclave is one part of your CMMC Level 2 readiness. Your assessment decides the result.
- Not access to your content. CMMCSync cannot change the tenant and never sees the CUI your people keep in it.
Planning a CUI enclave on Google Workspace?
Tell us who on your team handles CUI and what you use today. We'll scope the tenant with you.
Talk to us