- Before
- Can write the SSP, but cannot prove all 320 objectives in the week before the affirming official signs, and chases 23 control owners through a workbook.
- Now
- Starts the day with what the agents found overnight and the five things that need a decision; confirms, settles disputes and decides with a reason code.
The unencrypted file share that blocked a CMMC Level 2 affirmation
The company's defense business needs Level 2 (Self) status in SPRS before option year 2 of a prime contract, 46 days away. Here is one working day, screen by screen, in the working solution.
A worked example on sample data. Names, IDs and figures on the screens and in this section come from the demo.
- 0108:30
What the agents did overnight, and what needs the lead
CMMC compliance leadThe agents finished at 06:10: 412 assets sorted, 110 statements checked, 320 objectives graded. The SPRS score is 96, up from the 72 posted at the last self-assessment, and 291 of 320 objectives are proven. One gap blocks the affirmation, and five more things need the compliance lead.
POA&M agent, 06:04: “The engineering file share holds CUI with no encryption. 3.13.11 cannot go on the POA&M.”
- 02The lead asks
“Why is the affirmation blocked?” Answered with the rule
CMMC compliance leadThe lead asks in plain words, beside the agents' overnight thread. The POA&M agent answers: the engineering file share holds 412 CUI-marked files with no encryption at rest, which fails 3.13.11 for 5 points, and a requirement worth more than 1 point cannot go on a POA&M. Its claims carry numbered sources the lead can open.
“Until the share is fixed or taken out of scope, the affirming official would be affirming a status we do not have.”
- 0305:12
The CUI boundary, drawn from the real flows
Asset agentThe Asset agent sorted 412 assets from the inventory, 90 days of firewall flows and the data labels: 64 CUI assets, 23 Security Protection Assets, 118 Contractor Risk Managed Assets, 31 Specialized Assets and 176 out of scope. Three of 38 flows cross the boundary where they should not, drawn dashed on the map. The SPRS rail beside it lists the 10 requirements still not met, 14 points, each with its POA&M eligibility.
- 04The engineering share
CUI on a share the old diagram called out of scope
Asset agentOne flow shows the CAD group wrote 2,184 files to the engineering share in 90 days, and 412 carry the CUI//SP-CTI marking. The agent proposes moving the share from out of scope to CUI asset at 97% confidence and shows the steps it took. A 5-axis mill with a vendor support link came in at 61%, below its 80% line, so it went to the IT security manager instead of becoming a proposal.
The Asset agent reads CUI markings, not file contents, and never moves an asset out of scope on its own.
- 05Requirement 3.4.9
One agent writes the statement, another grades it
Practice agent · Assessor agentThe Practice agent writes that software installs are blocked by an allow-list policy on the 22 enclave laptops. The Assessor agent disputes it: the endpoint log shows 14 enclave workstations where users installed software in the last 30 days. Both arguments sit side by side, the Assessor's verdict stands, and the compliance lead settles it.
The Assessor agent cannot be overruled by the Practice agent and cannot lower the bar.
- 0605:48
A mock assessment of all 320 objectives
Assessor agentIn 4 min 12 s the Assessor agent graded every objective of NIST SP 800-171A: 291 met, 21 not met, 8 not applicable. In its first pass it refused “met” on 26 objectives that had a statement but no evidence; the Evidence agent found proof for 19. The 10 findings carry their points and a POA&M chip.
“Grade each of the 320 objectives against evidence I can open; a statement alone is not proof.”
- 0706:04
Nine items allowed on the POA&M, one refused
POA&M agentThe POA&M holds nine requirements worth 1 point apiece, all with an owner and a next milestone; the last is due 53 days inside the 180-day close-out. 3.13.11 on the engineering share is refused, and the agent prices the ways out: encrypt the share in FIPS mode in about a day, or move its files onto an in-scope file server and block the flow in about three. Putting it on the POA&M is shown greyed out, as the rule does not allow it.
The rule, checked: score 96 is 88 or more · every item is worth 1 point · none from the never-on-a-POA&M list · close-out inside 180 days.
- 0808:52
The lead decides, with a reason code and a signature
CMMC compliance leadThe lead picks option A, turn on FIPS-validated encryption on the share, with the reason code “Remediate now — fastest path to Conditional” and a note for the record. The change goes to the IT security manager with a 2-day SLA, and the agents re-check it when it closes.
The signed line reads: “I make this decision. It is signed and logged.”
- 0914:05, change closed
Proved from the system, not the ticket
Evidence agentThe IT security manager closes the change. The Evidence agent re-reads the share: encryption on, XTS-AES 256, FIPS-compliant algorithms enabled, and the validated module certificate matches the build. The Assessor agent marks 3.13.11 met, the Practice agent re-drafts the statement for the lead to approve, and the score moves from 96 to 101.
The Evidence agent is read-only: it changes no system, and a person makes every fix.
- 1014:21, signed
The official sees what they affirm, then signs
VP Operations · affirming officialThe affirming official opens the affirmation: six plain-words lines, each linked to its proof, five of five gates passed and the False Claims Act warning. They type their name, acknowledge the warning and verify with a security key. The SPRS entry is prepared for the compliance lead to post, and the close-out and annual affirmations are scheduled.
“I affirm that the company has implemented, and will maintain, the security requirements of NIST SP 800-171 Rev. 2 … with a score of 101.”