CONTROLLED UNCLASSIFIED INFORMATION GOES IN HERE, AND ONLY IN HERE

CMMC LEVEL 2 · NIST SP 800-171 · GOOGLE CLOUD

A CMMC Level 2 enclave you don't have to engineer yourself.

A secure, monitored desktop for CUI that you deploy into your own Google Cloud account, from your computer today or from Google Cloud Marketplace soon. Your team exchanges CUI with the government through DoD SAFE. The rest of your company stays out of scope.

THE PROBLEM

You won the DoD work. Now you have to protect the CUI that comes with it.

CMMC Level 2 requires you to secure and protect Controlled Unclassified Information (CUI). If CUI flows through your whole company, every laptop, file share and email inbox falls in scope, and that's an enormous IT effort for a small company or lab.

Most small teams only handle CUI on a handful of contracts. The proven way to protect it is an enclave: a small, separate environment where CUI lives, built to the standard, while the rest of the business carries on as before. Building one yourself takes cloud networking, Linux hardening, identity, logging and audit evidence, and few small firms or labs have that expertise on staff.

Hours to build, not months. You deploy it, and the enclave hardens itself.

THE RISK

Signing a score isn't the same as meeting it.

Under CMMC Level 2 (Self), a senior official at your company signs your score in SPRS, the DoD's supplier risk system. It's tempting to sign first and close the gaps later.

That signature is a formal statement to the government. If your score doesn't match reality, you risk losing the contract, being barred from future federal work, and facing False Claims Act penalties.

Smarter Reality CUI Enclave gives you a hardened system with the technical controls already in place, with an evidence kit that checks the running system. It won't finish your compliance for you. It gets you to a score you can back up, faster.

 

THE SOLUTION

The parts an assessor asks about, ready to deploy 

FIPS mode, enforced

Ubuntu Pro FIPS 22.04 on a Google Shielded VM with Secure Boot and a virtual TPM. The build stops if FIPS mode isn't on.

Two-factor sign-in and lockout

User accounts, 2FA and offboarding run through JumpCloud. Unbind a person there and they lose access within minutes.

Default-deny network, both directions

One way in, filtered to the U.S. and your own addresses. Out, only a named allowlist. Known-malicious and sanctioned-country traffic is dropped. Every decision is logged.

Application allowlisting

Only approved programs can run. Anything else is refused and recorded.

Integrity checks and antivirus

File-integrity monitoring catches unexpected changes to the system. Antivirus scans files as they are opened.

Monitoring that reaches a person

43 alert policies by email, with optional Jira tickets: failed sign-ins, deleted or re-permissioned CUI, exfiltration attempts, configuration drift.

Audit logs and backups

A locked 365-day audit log bucket and scheduled VM backups, both in your Google Cloud project.

Built for a FedRAMP Moderate boundary

You deploy it into a Google Cloud Assured Workloads folder you create, which keeps data in the U.S. and limits Google support to adjudicated staff.

 

Deploying the enclave doesn't make you CMMC compliant on its own. Smarter Reality CUI Enclave handles most of the technical controls, and our Responsibility Reference lists exactly what's left for your policies, training and incident response.


QUESTIONS

Straight answers

Can Smarter Reality see our data?

No. The enclave runs entirely in your own Google Cloud project, whether you deploy it from the download today or from Google Cloud Marketplace once it launches. We run nothing once it's deployed and have no access to your enclave or what's in it.

How many people can use it at once?

One desktop session at a time. Teams take turns, which suits groups that do CUI work in bursts. If you need several people working in parallel, tell us when you reach out.

Can my team copy files off the enclave?

The easy routes are switched off: clipboard, drive sharing, SFTP and SCP. Every transfer attempt the enclave can detect raises an alert, and your written policy covers the rest.

How do I get support?

Use the Get Support button below, and include your Google Cloud project ID and what you were doing when the problem started. Support hours are 9:00 a.m. to 5:00 p.m. Central, Monday to Friday, excluding U.S. federal holidays. We don't commit to a response or resolution time.

Talk To Us

Questions about whether the enclave fits your contract? Tell us what you're working on and we'll be in touch.