FedRAMP readiness self-check

Answer honestly. A generous score here only delays the bad news until an assessor finds the same gaps and charges you to document them.

Sixteen questions across eight readiness areas. Last updated: 2026-11-22.

How this works. Each question has three answers: Yes (done, and you could show evidence), Partially (started or true for some of the system), or No. Yes scores 2, Partially 1, No 0, out of 32. Your answers never leave this page. There is no account, no submission, and nothing is stored.

0 of 16 questions answered.

1. Boundary and scope

Have you drawn the authorization boundary?

Which components, services, and data flows are in scope, and which are out, written down and agreed.

Does the federal environment run on FedRAMP-authorized infrastructure?

For example AWS GovCloud or Azure Government, or a boundary that inherits authorization from an authorized IaaS.

2. FIPS-validated cryptography

Is encryption in transit provided by FIPS 140-validated modules?

Validated, not merely FIPS-compliant or FIPS-capable. The module must appear on the CMVP validated list.

Is encryption at rest provided by FIPS 140-validated modules?

Databases, object storage, disks, and backups, not just the front door.

3. Multi-factor authentication

Is MFA required for all privileged access?

Admin consoles, production access, and infrastructure management. No exceptions for break-glass accounts without compensating controls.

Is MFA required for every user of the federal environment, with no shared accounts?

Every human has their own account and their own second factor. Service accounts are inventoried and justified.

4. Centralized logging

Do audit logs from every in-scope component flow to one central store?

Application, infrastructure, and security logs in one place, with timestamps that can be correlated.

Are logs retained long enough to cover the assessment window, and can you show an assessor the trail?

Retention that survives the months between evidence collection and the assessor's review, plus a way to query and export.

5. Configuration baselines

Is there a written approved configuration for each component type?

Operating systems, databases, network devices, and cloud services each have a documented baseline, not just tribal knowledge.

Are deviations from the baseline recorded with a reason?

When a system differs from the baseline, the difference is written down, approved, and reviewable.

6. Vulnerability management

Do you scan the operating system, databases, and web applications at least monthly?

Monthly scanning across all three is the continuous monitoring expectation. Less frequent scanning is a finding waiting to happen.

Is every finding tracked in a POA&M with an owner and a due date?

A Plan of Action and Milestones entry per weakness, with severity, affected control, milestones, and closure evidence when fixed.

7. Incident response

Is there a written incident response plan naming the people who run it?

Roles, escalation paths, and contacts, current enough that the named people still work there.

Has the plan been tested, not just written?

A tabletop exercise or a real incident handled under the plan, with notes on what was learned.

8. Documentation and the SSP

Is there a System Security Plan covering the full baseline for your level?

Low runs about 125 controls, Moderate about 325, High about 421. The SSP describes how each one is implemented, or marks it honestly as planned.

Are the SSP attachments in place?

Policies and procedures per control family, incident response and contingency plans, the configuration management plan, and a current inventory.

What the score means

Result bands for the 32-point scale.
Score Verdict What to do next
28–32 Ready to talk to an assessor Book a Readiness Assessment Report with a 3PAO. See the FedRAMP Ready guide.
20–27 Close Fix the weak areas first, then consider a RAR. A gap assessment will size the remaining work.
0–19 Not yet Build the foundations before paying for any assessment. Start with the boundary and the SSP.

What this check cannot tell you

Sixteen questions cannot cover a 325-control baseline. This check probes the eight areas where first-time assessments most often stumble, and it trusts your answers. It cannot test your controls, read your evidence, or judge whether a control description would satisfy an assessor. Treat a high score as permission to commission a RAR, not as a prediction that the RAR will pass. And a low score is not a verdict on the product, only on its readiness for this particular audit.

Frequently asked questions

Is this the same as a FedRAMP Readiness Assessment?

No. A formal Readiness Assessment Report is performed by a FedRAMP-recognized 3PAO, typically costs $25K–$75K, takes 1–2 months, and earns the FedRAMP Ready designation for one calendar year. This page is a self-screening tool. Only a RAR can confirm readiness.

Does the self-check send my answers anywhere?

No. It runs entirely in your browser with client-side JavaScript. Answers are never transmitted, stored, or seen by anyone, including this site's operator.

Which level should I be checking against?

These questions apply at every level. The difference is breadth: Low covers about 125 controls, Moderate about 325, High about 421, so the documentation burden grows with the level even though the eight areas stay the same. Under the new Classes A–D, Class B maps roughly to Low, Class C to Moderate, and Class D to High.

Next: the gap assessment