Example, read only. A sample company whose own team runs its CMMC program here, reviewed by a credentialed officer and kept current.
SI.L1-3.14.1 · FAR 52.204-21 (b)(1)(xii) · NIST SP 800-171 3.14.1
Flaw Remediation
Identify, report, and correct information and information system flaws in a timely manner
Reviewed by a credentialed officer on June 12, 2026. The officer advises and never signs; this corroborates your own self assessment and certifies nothing. The finding, and the affirmation, stay yours.
Who is accountable for this safeguard
They get the reminder when this evidence goes stale. Carries into next year's cycle.
What it means
When your software or computers have security updates available, install them, and keep a log showing you did.
Why it matters
'I installed updates' without proof isn't enough. A screenshot of update history, a patch log, or an endpoint-management dashboard showing patched devices all work, pick one and be consistent.
The proof on file
- intune-patch-compliance.pngUploaded, checked by Charlie · June 10, 2026Sufficient
Every uploaded file is checked by Charlie the moment it arrives, so a gap is caught on the spot, not at the assessment. Pulls from Microsoft 365 and references to the Policy Center and registers come straight from where they live, so they skip that check.
The narrative on file
Microsoft Defender and Windows Update for Business keep every managed workstation patched and current. Intune reports patch status, and the owner reviews the compliance dashboard weekly to confirm all covered devices are up to date.
You answer in plain English. Charlie drafts the narrative for your System Security Plan, and you confirm it.
What makes it pass
- Patch policy clearly states critical updates within 30 days, others at least monthly
- Recent patch log entries cover every device in scope (no missing devices)
- Per-device update history screenshots show recent install dates (within policy window)
- For Intune path: dashboard shows compliant device count vs total in scope
Assessment objectives, NIST SP 800-171A
The team at Cedar Ridge Machine Works, LLC confirmed this safeguard MET. The evidence above is a living document: refresh rosters, devices, and accounts whenever the business changes and the safeguard stays current. The single signature happens in Attest & file, once all 17 are met.
Next safeguard →Need the exact clicks?Microsoft 365 / Intune, step by step
- 1Go to Intune / Endpoint Manager → Reports → Device compliance or Update compliance
- 2Screenshot the dashboard showing devices patched within policy
- 3Also screenshot the Update rings / policies page showing the patch cadence
Capture: Dashboard screenshot plus update-policy screenshot.
This is one of 17
Answer in plain English, file the proof, confirm it MET.
The team at Cedar Ridge Machine Works, LLC walked all 17 the same way. The platform explains each one in plain English and tells you what proof to grab or pulls it from Microsoft 365, Charlie drafts the paperwork with you, a credentialed officer reviews it, and your team confirms each one MET. The self assessment stays your act. Start free for 30 days, no credit card, or book a free advisory call if you would rather talk it through first.