In this episode of CMMC Unlocked, host Paul Netopski breaks down one of the most misunderstood phrases in the new CMMC rule set and CyberAB guidance: “significant changes.” Many small defense contractors and their advisors worry that any major IT or organizational change will automatically invalidate a hard‑won Level 2 certification. Paul walks through what the 32 CFR Part 170 preamble, the Level 2 Scoping Guide, and the Level 2 Assessment Guide actually say—and what they don’t.
We unpack the distinction between:
- When “significant architectural or boundary changes” require a new certification assessment, and
- When “significant changes” simply require you to update your CMMC Level 2 self‑assessment and affirmation, in line with your ongoing risk management and change‑management processes.
Drawing on earlier episodes about risk assessments and continuous monitoring, Paul offers practical guidance for small DIB organizations and consultants on how to:
- Define what “significant change” means for your environment using NIST SP 800‑37, 800‑53, and 800‑53A concepts.
- Build change‑management checkpoints that flag potential CMMC impact early.
- Decide when a change triggers a new self‑assessment and SPRS update versus when it’s covered by your annual affirmation.
- Keep your System Security Plan, asset inventory, and CMMC Assessment Scope aligned as your environment evolves.
If you’re worried that a tech refresh, cloud migration, or acquisition will blow up your CMMC status, this episode will help you separate rumor from requirement and integrate “significant change” into a mature, risk‑based compliance program.