Track CMMC Deadlines Like Support End Dates: 170.15, 170.21 and 170.22
If you run IT for a small defense supplier, the CMMC rules give you a recurring calendar, not a one-time project. Level 1 status means a self-assessment every year. Every assessment triggers an affirmation, and that affi
If you run IT for a small defense supplier, the CMMC rules give you a recurring calendar, not a one-time project. Level 1 status means a self-assessment every year. Every assessment triggers an affirmation, and that affirmation repeats every year. Open plan of action items have a 180-day limit. Treat these like support end dates, tracked in one list with an owner.
This post walks through the timing in 32 CFR Part 170 the way you'd model it in a tracker. It covers the 4 clocks, what triggers each one, and who has to act. It doesn't cover controls or tooling. The goal is to stop the dates from surprising anyone.
The problem
A gap assessment is a good consulting project. It ends with a scored report, a list of gaps and a system security plan. Then the consultant leaves, and the calendar that follows the report has no owner.
That calendar isn't vague. The regulation spells it out.
Clock 1: the yearly Level 1 self-assessment
Under 32 CFR 170.15, a company that holds Level 1 status has to run a self-assessment on an annual basis and submit the results in SPRS, the Defense Department's Supplier Performance Risk System.
Model it as a yearly recurring item, keyed to the date of the last submission.
Clock 2: the Level 2 self-assessment every 3 years
Under section 170.16, a company with Level 2 (Self) status has to repeat the Level 2 self-assessment every 3 years and submit the results in SPRS.
This is the longest interval, which also makes it the easiest to forget. A 3-year item needs a reminder well ahead of the due date, not on it.
Clock 3: the affirmation, after every assessment and every year
Section 170.22 requires an affirmation of continuing compliance after every assessment, including a POA&M closeout assessment, and annually after that. Affirmations go into SPRS.
Two details matter for your tracker.
The trigger is an event plus a yearly repeat. Every assessment creates a new affirmation date.
The person is fixed by the rule. The Affirming Official is defined as the senior level representative from within the company who is responsible for CMMC compliance. Your consultant can't be that person, and neither can a vCIO. Your tracker should name the executive, not the IT contact.
Clock 4: 180 days to close open items
If a Level 2 assessment ends with requirements on a plan of action and milestones, section 170.21 says the closing has to be confirmed by a POA&M closeout assessment within 180 days of the conditional status date. If that doesn't happen in time, the conditional status expires.
This is the clock with the hardest edge. Each open item needs an owner, a funding source and a due date well inside the 180 days.
The clock that can start any day
There's one more timer that isn't on a calendar. DFARS 252.204-7012 requires a contractor to report a cyber incident to the DoD within 72 hours of discovery. A 72-hour window can open on a Saturday. Nobody can hire a consultant that quickly, so an incident plan has to have an owner before anything happens.
What changed in 2026, and what didn't
The Pentagon suspended the third-party assessment phase on July 13, 2026. The self-assessment phase that started on November 10, 2025 still applies, and so does the DFARS clause. None of the 4 clocks above went away.
Put it next to your support end dates
These clocks belong in the same list as your hardware and software lifecycle dates. SQL Server 2017, for example, reaches the end of extended support on October 12, 2027. Plenty of accounting and ERP systems run on SQL Server underneath.
A useful row in that list has 5 fields.
The item, such as the Level 1 self-assessment or SQL Server 2017
The rule or source, such as 32 CFR 170.15 or Microsoft's lifecycle page
The next due date
The named owner
The budget year it lands in
Renewals belong in the same list. Microsoft 365, phone and ERP licenses each renew on their own date, and a cyber insurance application comes back every year with answers that should match last year's.
Gotchas
An affirmation date resets with every new assessment, POA&M closeout included. Don't hard-code a single yearly date.
Don't list the consultant as owner of the affirmation. The rule names a senior person inside the company.
If your budget is set in the fall, the 2027 budget is the last one that can pay for the SQL Server 2017 upgrade before support ends.
A consultant's handover should include the POA&M with owners and dates. Without it, the 180-day clock is running and nobody can see it.
We wrote the longer comparison of who should own this work, consultant or vCIO, for Fort Worth companies here: vCIO vs IT consultant for Fort Worth companies
Disclosure: I'm the Lead vCIO at Uprite Services, a managed IT provider in Texas.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.