Your SSP says how your Linux servers are set up. Do the servers agree?
Before your consultant writes the Linux sections of your SSP, scan the in-scope servers. Catch mismatches while the plan is still a draft, and keep the results.

The kickoff call with your consultant is going well. The system security plan (SSP) template is on the screen, and the conversation has reached your Linux servers. How is remote access set up? Is root login over SSH turned off? Who can change the audit settings?
Your IT lead answers from memory: "We hardened those last year."
It's an honest answer, and the work was probably done with care. But nobody on the call has looked at those servers since. A year is a long time for a server. Software updates change files. A new install brings its own settings. Someone fixes a problem late at night and never writes it down.
The servers may still be set up exactly as planned. They may also have drifted. Right now, nobody on the call can say which. And the consultant is about to write the answer into a document your company will stand behind at its Cybersecurity Maturity Model Certification (CMMC) assessment.
You can close that gap without adding much to the work you're already doing.
Scoping comes first, and that's right
Most consultants start by working out which systems are in scope: the ones that handle controlled unclassified information (CUI), and the ones connected to them. That has to come first. A scan can tell you how a server is set up. It can't tell you where your data goes.
So if your consultant starts with scoping, let that work finish. Checking every server you own before then only piles up findings on machines that may not matter for the assessment.
Then check the servers, before the writing starts
Once scoping is done, there's a short window. You know which Linux servers are in scope, and nobody has written their part of the SSP yet.
That's the time for a configuration scan. A scan reads each server's security settings and compares them with a published standard, such as a Center for Internet Security (CIS) Benchmark or a Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG). Your consultant then writes the server sections from what the servers report today, not from what someone remembers.
If your consultant already plans a scan, the only question is timing. Ask whether the results will be ready before those sections are drafted.
Why it's better to find a mismatch now
Picture one sentence your consultant might write: "Root login over SSH is disabled on all in-scope Linux servers."
Your IT lead remembers turning it off, so the sentence sounds right. But a later update or a quick fix can change a setting like that without anyone noticing.
The scan settles it. If every server agrees, the sentence now rests on evidence. If one doesn't, your team can fix the server, or write the plan to match what's true, before the sentence goes in.
Now picture finding the same mismatch after the plan is written. Your team still has to work out which servers are affected and fix them. Then someone has to reopen the plan, along with every statement that leaned on the old assumption. The problem was there all along. The scan only changes when you find out about it.
Early findings are still work, and they may arrive sooner than you planned. But they arrive while the plan is still a draft, which is the cheapest time to change it.
The one question to ask your consultant
You don't need a Linux specialist on staff for this. Your consultant can run the scan, or your IT lead can run it and share the results. Before the Linux sections are written, ask:
"Can we scan the in-scope Linux servers against the standard we agreed on, go over the findings together, and use the results when we write those sections of the SSP?"
A consultant who writes from data will welcome the question. From there, your IT lead and the consultant can sort each setting into one of three groups: confirmed, needs fixing, or needs other evidence.
Keep the results yourself
When the engagement ends, keep the scan results, not only the finished SSP or a summary of the findings. A useful record shows which servers were checked, the date of the scan, the standard it used, and what each check found.
That record matters most after the consultant has moved on. The SSP describes how your company meets its security requirements. The scan results show what the servers reported on a given day. If someone later asks why the plan says a setting is turned off, your team can point to a result instead of a memory.
What a scan can't tell you
A scan is good evidence, but it isn't a CMMC assessment. The requirements for CMMC Level 2 are the ones in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, and many of them are about policy, training, and who is responsible for what. A server scan can't see any of that.
Even for settings, a scan reports only on what its rules check, and some results need a person to read them in context. It also describes a single day. It can't promise the servers will stay that way.
So treat the scan as a better starting point for the plan. Keeping your servers in shape, and the assessment itself, are still separate jobs.
What changes
None of this replaces your consultant. It changes what your team knows when the plan gets written. The Linux sections stop being a memory from the kickoff call. They become something your team checked, and can show.