CMMC Level 2 on CUI Vault

When your CUI lives in the CUI Vault enclave, the vast majority of the 110 NIST SP 800-171 requirements underpinning CMMC Level 2 are implemented for you. The remaining requirements are shared: where CUI Vault provides the mechanism, and you complete onsite organization and facility decisions.

Where does your CUI live?
110
Requirements
93
Handled by CUI Vault
17
Shared with you
0
Left entirely to you

What the enclave gives you

Access

Every user gets their own account, protected by multifactor authentication and limited to the access their role needs as defined by your organization. Privileged access stays with NtelSec.

Endpoints stay out of scope

Users work inside the enclave, and CUI never lands on the computers they connect from. Those computers can remain out of your assessment scope.

Data protection

CUI is encrypted in transit and at rest, hosted in U.S. government cloud regions, and leaves the enclave only through approved channels.

Monitoring and audit

Security activity is logged, retained, and monitored continuously, with ongoing vulnerability management.

Account lifecycle

Accounts are created only on your authorization and disabled promptly when someone departs or no longer requires access to CUI.

Resilience and response

Protected backups and an incident response process that supports your own DFARS 252.204-7012 reporting.

Defining responsibility by family

CUI Vault means we implement every assessment objective for CUI held in the enclave; you reference it in your SSP. Shared means we implement some objectives and you implement others. Both parts are needed for a MET determination.

FamilyRequirementsCUI VaultShared
ACAccess Control22184
ATAwareness and Training321
AUAudit and Accountability99—
CMConfiguration Management99—
IAIdentification and Authentication1111—
IRIncident Response3—3
MAMaintenance66—
MPMedia Protection981
PSPersonnel Security2—2
PEPhysical Protection651
RARisk Assessment321
CASecurity Assessment4—4
SCSystem and Communications Protection1616—
SISystem and Information Integrity77—
Total1109317

What stays with you

  • Declare your scope and write your own System Security Plan, documenting CUI Vault as your external service provider and referencing the Customer Responsibility Matrix.
  • Designate a system owner and the people who hold security duties for your use of CUI Vault, and make sure they are trained for those duties.
  • Screen and authorize every user, and decide by need-to-know who may read or change each of your file sites.
  • Tell us within 24 hours when someone leaves, changes roles, or otherwise no longer requires access to CUI Vault.
  • Approve who outside your organization may receive your CUI, and control what is posted publicly.
  • Mark your CUI as each contract requires.
  • Report cyber incidents to DoD within 72 hours of discovery where DFARS 252.204-7012 requires it, and test your incident-handling responsibilities.
  • Assess risk, keep a plan of action, monitor your responsibilities between assessments, and update your SSP at least annually.

When inheritance holds

  • CUI is created, stored, and shared only inside CUI Vault.
  • Your users follow the Rules of Behavior and send CUI only through the approved encrypted channels.
  • Your SSP shows CUI Vault as your external service provider and the computers your users connect from as out of scope.

If you also hold CUI on paper, removable media, or other systems, you implement the affected requirements for that CUI under your own SSP. Your assessor makes the final determination of scope and inheritance.