Phase 2 is suspended, but CMMC and the underlying DFARS security obligations have not disappeared. Contractors should verify current solicitations, assessment designations, SPRS records, and data flows.
OLIR provides mapping content and governance. OSCAL provides the machine-readable structure for using those mappings in gap analysis, evidence reuse, and change-impact workflows.
Every OSCAL validator claims to validate OSCAL. We enumerated all 348 constraint occurrences in the NIST sources, proved or excluded each one, and then ran the comparison against the Java CLI for real.
Only about a third of affected companies registered with the BSI on time. Until the end of July 2026 this can be fixed – after that, it gets expensive.
With the Stand-der-Technik-Bibliothek, IT-Grundschutz leaves the PDF behind: IT-Grundschutz++ ships as an OSCAL catalog – changing how ISMS work is organized.
With RFC-0024 and the Consolidated Rules 2026, FedRAMP makes structured authorization data mandatory. The deadlines are staggered – the direction is unambiguous.
The OSCAL ecosystem is growing fast: viewing and validating are well covered, while authoring and day-to-day workflows remain the biggest gap.
OSCAL turns compliance documents into structured data: eight document models, three formats, and an ecosystem that is becoming the standard for regulation.
Compliance should not be a reporting project at the end. It should be a living system of trust for teams that need structure, speed, and control.
AI-native compliance means importing existing evidence, understanding context, finding gaps, reviewing outputs, and keeping humans in control where judgment matters.