Gap assessment: find out what is missing before an assessor does

A gap assessment is a dry run against the baseline. You compare the system, control by control, against the level you are targeting, and you write down everything that falls short. Done well, it turns a vague worry about readiness into a priced list of fixes.

Last updated: 2026-11-22.

What it is, in one paragraph

Pick the target level. Low covers about 125 controls, Moderate about 325, High about 421. (Under the new classes, Class B maps roughly to Low, Class C to Moderate, Class D to High.) For each control, the question is the same: is it implemented, is it evidenced, and could you show an assessor the proof? Anything that fails one of those three is a gap. The output is a register: every gap, its control, its severity, an owner, and a fix. That register becomes the remediation plan, and later the seed of the POA&M.

What it covers

A thorough gap assessment looks at the system, the paperwork, and the operations around them. The same eight areas as the self-check show up here, in more depth:

Who runs it

Three options, with one hard rule.

In-house

Your own team

Cheapest and slowest to start. It works when the team already knows NIST SP 800-53 and has done this before. The risk is blind spots: the people who built the system are the least likely to notice what it lacks. A self-run gap assessment still beats no gap assessment.

Advisor

A separate advisory firm

The usual choice for first-timers. Advisory firms do gap assessments, boundary and landing-zone design, SSP authorship, evidence prep, remediation, and sponsorship support. FedRAMP's Marketplace now lists 21 advisors on its Advisors tab, and the wider advisory market includes firms such as stackArmor, 38North Security, MindPoint Group, and Sysorex. See the advisors page on the hub site for the full picture.

Not this

The 3PAO that will assess you

Independence rules bar a 3PAO from advising on, implementing controls for, remediating, or writing the SSP for a system it will assess. A 3PAO's formal readiness product is the Readiness Assessment Report, which is an assessment with a verdict, not advisory work. If an assessor offers to help you fix what it will later grade, that is a red flag, not a convenience.

What it costs

No firm publishes a standalone gap-assessment price, so there is no honest number to quote for one. What the market does publish, in ranges:

Budgeting advice: get quotes from two or three advisors and compare scope, not just price. A cheap gap assessment that skims the documentation is worse than none, because it produces false confidence.

How long it takes

No standard duration is published for a gap assessment, and anyone quoting a fixed number is guessing. It scales with the size of the boundary, the number of controls at your level, and how much documentation already exists. A small, well-documented Low system can be assessed in weeks; a sprawling Moderate system with no SSP takes considerably longer. For calibration, the formal RAR takes 1–2 months, and a gap assessment is lighter work than a RAR.

What you should get out of it

  1. A gap register. Every gap, mapped to its control, with severity and an owner.
  2. A remediation plan. The fixes in priority order, with the long-lead items (crypto replacement, landing-zone work) flagged early.
  3. A realistic budget and timeline. The gap list is what turns the published ranges into a number for your system.
  4. A POA&M seed. Gaps that will still be open at assessment time become POA&M entries. Starting the POA&M during the gap assessment saves rework later.
  5. A go/no-go signal for the RAR. If the gap list is short and the fixes are quick, a RAR is the next step. If it is long, fix first and save the RAR fee.

One trap to avoid. A gap assessment that only checks whether controls exist, without checking whether they are evidenced, misses half the work. Assessors test controls and ask for proof. A control that is implemented but undocumented is a gap, and the gap assessment should say so.

Frequently asked questions

Is a gap assessment the same as a Readiness Assessment Report?

No. A gap assessment is usually informal advisory work: your team or an advisor compares the system against the baseline and lists the gaps. A RAR is a formal assessment by a 3PAO with a verdict, and a passing RAR earns the FedRAMP Ready designation. The gap assessment normally comes first and makes the RAR cheaper by shrinking the surprise.

Can I run a gap assessment myself?

Yes, if your team knows NIST SP 800-53 well. The risk is blind spots, and the most common one is documentation: teams that built the system tend to grade their own paperwork generously. If you go in-house, have someone who did not build the system review the findings.

Do I need a gap assessment if I plan to hire an advisor anyway?

The advisor will run one as the first phase of the engagement. Ask to see the gap register as a deliverable rather than letting it stay in the advisor's head.

Next: FedRAMP Ready