Bruce Weygandt
All posts

CMMC Level 2, one assessment objective at a time

CMMC, Microsoft 365 GCC High, Microsoft Graph. 2 min read.

Building about 320 capabilities for a client on Microsoft 365 GCC High, and why the extra records were worth it.

CMMC assessors don't grade a practice as a whole. They look at each assessment objective inside it, and a narrative that reads well at the practice level can still leave one of those objectives unanswered. That gap is where findings come from.

For a client running Microsoft 365 GCC High, I built their Level 2 coverage at the objective level: one Solution Capability per assessment objective, about 320 in total, each written against how the client actually configured their environment.

The identifier problem

Partway through, I noticed Microsoft Purview still reports CMMC controls under the legacy v1.02 identifiers. The tool and the assessment were describing the same controls with different numbers. I wrote a 110-row crosswalk from the legacy IDs to the current ones so nobody has to translate in their head during an assessment.

Evidence from where the control lives

Where the platform enforces a practice, I tried to automate the evidence. Maintenance-session MFA (MA.L2-3.7.5) is a good example. Purview tracks that control, but Entra Conditional Access is what enforces it, so the evidence should come from Microsoft Graph.

Conditional Access policy JSON is deeply nested, and regex over nested JSON gets unreadable fast. So the fetcher evaluates each policy and writes a small flat summary next to the raw data. The validator only checks a handful of flags, and an auditor can still see the original policy.

# Evidence source
GET https://graph.microsoft.com/v1.0/identity/conditionalAccess/policies

# Flat summary the fetcher writes for each qualifying policy
"policy_state": "enabled"
"mfa_required": true
"external_network_scoped": true
"session_termination_enabled": true

# Validator (ECMAScript)
"policy_state":\s*"enabled"[\s\S]*?"mfa_required":\s*true[\s\S]*?
"external_network_scoped":\s*true[\s\S]*?"session_termination_enabled":\s*true

# Rule: match count = 1  ->  PASS
One chained validator covers both objectives of MA.L2-3.7.5: MFA for nonlocal maintenance, and terminating those sessions.

Was it worth 320 records?

It's more to maintain than practice-level narratives. But every objective now points to a specific answer and the evidence behind it, and that's what an assessor actually asks for.