Glossary of Compliance

Compliance Glossary

Our list of curated compliance glossary offers everything you to know about compliance in one place.

Glossary » Generic » CMMC Assessment Scope

CMMC Assessment Scope

Determining the scope of your CMMC assessment is a need for a successful certification process. It sets the groundwork by outlining what you need to evaluate. This approach reduces the assessment’s duration and minimizes the impact of security controls on your workforce.

This is why it is essential to account for every asset, whether within or outside the scope of the assessment, that processes Controlled Unclassified Information (CUI) or is not intended for nCUI processing. Disagreements about assessment scope can lead to certification delays. 

CMMC Self-Assessment

If you’re an Organization Seeking Compliance (OSC) aiming for CMMC Level 1 or a subset of Level 2 OSCs handling non-critical national security information, you can opt for a self-assessment. This means that your organization’s CMMC lead will conduct the assessment internally.

Level 1 Self-Assessment

Level 1 assessments evaluate how the OSC safeguards Federal Contract Information (FCI) using the 17 NIST 800-171 controls that apply to Level 1. To achieve Level 1 compliance, all objectives within these 17 controls must be met.

Level 2 Self-Assessment

Level 2 OSCs must assess against NIST 800-171 (A) and meet all 110 control assessment objectives. Success at this level requires a comprehensive System Security Plan (SSP) that details how policies, procedures, and technologies align with each assessment objective.

Both Level 1 and Level 2 OSCs need to perform self-assessments annually. They must also provide an annual affirmation from a senior company official confirming compliance with all requirements. These self-assessments and affirmations must be registered in the DoD’s Supplier Performance Risk System (SPRS).

Additional reading

Consequences of Non-Compliance: Fines, Failures, and Fallout

TL,DR: Cumulative GDPR fines reached €5.88 billion globally as of 2025, with non-compliance leading to 7 major consequences including regulatory fines, revenue loss, legal action, operational disruptions, and reputational damage Common triggers include outdated policies, unencrypted logs, missing audit trails, unreviewed vendor assessments, disabled MFA, and publicly exposed cloud storage buckets across organizational infrastructure Non-compliance…

10 Security Oversights in Startups [How to Avoid Them]

TL,DR: The 10 common startup security oversights include missing MFA on infrastructure and code repos, lack of access controls, poor vendor verification, no endpoint protection, unencrypted data, missing security policies, no incident response plan, inadequate logging, weak passwords, and no employee training MFA should be enabled on all infrastructure, code repositories, and email systems. Each…

The Complete Guide to Vendor Management 

Vendors are both your biggest enablers and your weakest link. Around 73% of companies face either a security incident or disruption due to third-party vendors. One breach in your supply chain can cripple operations, inject ransomware into your systems, or derail your compliance in a single audit cycle. Most importantly, when vendor oversight is scattered…

Sprinto: Your growth superpower

Use Sprinto to centralize security compliance management – so nothing
gets in the way of your moving up and winning big.