
We recently attended CS5 East, the Cyber AB’s official CMMC conference. Our team spent the two days on the show floor, in back-to-back conversations with defense contractors working through CMMC and NIST 800-171. Let’s take a closer look at two questions that kept coming up in our conversations: how to keep a self-attested score accurate while third-party certification is paused, and what quantum computing means for the data GovCons are required to protect.
Key takeaways
- Pull your current SPRS score and check that it reflects your environment today, not where things stood at your last assessment.
- Make sure each control you’re claiming has evidence behind it. The annual affirmation is a legal statement, so it needs documentation you could put in front of an assessor.
- Start a crypto inventory: map where your sensitive data lives and which systems still rely on RSA or elliptic-curve (public-key) encryption.
- Favor crypto-agile systems going forward so you can move to post-quantum algorithms once NIST’s standards are final.
- Fold quantum readiness into your existing CMMC and NIST 800-171 work, as much of the groundwork is largely the same.
CMMC self-attestation: Keeping your SPRS score defensible
Self-attestation dominated our conversations at the show. In July, the Pentagon paused CMMC Phase 2, the third-party C3PAO certification requirement that was set to start in November. Contractors still score themselves against the 110 requirements in NIST 800-171 and submit that number to SPRS, where a senior official affirms it each year under the same False Claims Act exposure as before.
The score now stands on its own, with no assessor scheduled to catch a mistake. The question we kept hearing: how can we be sure the number we’re submitting is accurate?
We walked GovCons through what makes a score defensible. Keep the following in mind when you’re assessing yourself:
- A SPRS score is a snapshot of your environment at a point in time, so start by reassessing against the environment you run today, not the one you had at your last review.
- Accuracy means claiming only the controls you’ve genuinely implemented, since the fastest way to inflate a score is marking one “met” when it’s halfway there.
- A defensible score adds evidence: for every control you claim, you need the documentation to back it, from your system security plan to the configurations and records that show it’s real.
- Because the affirmation is a legal statement, whoever signs it needs to understand the score and what they’re putting their name to.
- Where you have gaps, a documented plan of action holds up better than an optimistic number.
Quantum readiness: Preparing for post-quantum encryption requirements
The other theme we heard a lot about was related to quantum computing, and specifically what happens to encrypted data once quantum computers can break today’s encryption.
Quantum computing puts public-key encryption at risk, specifically the RSA and elliptic-curve algorithms that protect data in transit and digital signatures. Symmetric encryption like AES is more resistant and can be shored up with longer keys. The public-key exposure is real.
Or, put in simpler terms: the digital locks that keep sensitive data safe as it moves around could one day be picked by a powerful enough quantum computer. The government is already preparing for that day, and contractors will be expected to do the same.
An executive order this summer and the OMB guidance that followed (M-26-15) set a deadline for federal civilian agencies to submit post-quantum migration plans to OMB and the National Cyber Director. Those plans were due this past month. Agencies will now begin checking whether their contractors and vendors are ready. NIST’s post-quantum standards are already published, and a 2030 compliance target already points at covered contractors.
Federal requirements that start with agencies usually reach contractors through procurement. Contractors who start now will be in better shape than those who wait for a clause to show up in a solicitation.
We’re calling this quantum readiness. Preparing for it overlaps with much of the work regulated contractors do for CMMC. You need to know what sensitive data you hold and what’s encrypting it, and your systems have to be able to swap algorithms once the standards are final. Contractors who’ve done their NIST 800-171 work have a head start.
If you left CS5 with questions you didn’t get to ask, or new ones have come up since, reach out to Ntiva for help.
Back to blogAbout the author
Michael Diab is Ntiva's Director of Regulatory & Compliance, where he supports the company's GovCon practice and its CMMC readiness and compliance-as-a-service work for regulated clients. He’s helped take Ntiva through its own CMMC Level 2 certification via an accredited C3PAO and advises defense contractors from firsthand, auditor-tested experience.

.png?width=420&height=210&name=dso%202%20(3).png)



