Glossary

FedRAMP runs on acronyms, and the CR26 transition added a second vocabulary on top of the first. These are the terms this site uses, in plain language.

Last updated: 2026-11-22.

Audit terms

3PAO β€” Third Party Assessment Organization

An independent organization accredited by A2LA under ISO/IEC 17020 and recognized by FedRAMP to assess cloud service offerings against FedRAMP baselines. It plans and runs the assessment and writes the SAR. It does not grant authorization, and it cannot implement controls, remediate findings, or write the SSP for a system it assesses. Under CR26, FedRAMP is retiring the "3PAO" label in official usage in favor of "recognized independent assessor," but "3PAO" remains the dominant search term.

A2LA β€” American Association for Laboratory Accreditation

The body that accredits 3PAOs under ISO/IEC 17020 plus FedRAMP-specific requirements. A2LA performs an initial assessment and recommends recognition to FedRAMP, then a favorable annual review and a full on-site reassessment every two years. Detailed personnel and team requirements are in A2LA publication R311, Specific Requirements: FedRAMP.

AO β€” Authorizing Official

The official at a sponsoring federal agency who reviews the authorization package (SSP, SAR, POA&M) and decides whether to grant the Authority to Operate.

ATO β€” Authority to Operate

The authorization an AO grants after reviewing the assessment package. Once granted, the FedRAMP PMO lists the service as FedRAMP Certified in the Marketplace, and other agencies can reuse the package to issue their own ATOs.

Baseline

A tailored set of security controls drawn from NIST SP 800-53 Rev 5, with FedRAMP-specific parameters. Low runs to roughly 125 controls, Moderate to roughly 325, High to roughly 421. Counts are approximate and vary by counting method. Under CR26, baselines give way to certification Classes A–D.

C3PAO β€” Certified Third Party Assessment Organization

A CMMC assessor for defense contractors, accredited by The Cyber AB under a different framework (NIST SP 800-171). Not the same as a FedRAMP 3PAO, and the two are not interchangeable. See the comparison on the hub site: 3PAO vs C3PAO.

ConMon β€” Continuous Monitoring

The ongoing oversight of an authorized service: monthly vulnerability scans, POA&M updates, and inventory reporting, plus an annual 3PAO reassessment and annual penetration testing. Governed by the ConMon Playbook v1.0 (November 17, 2025). See the continuous monitoring page.

CSP β€” Cloud Service Provider

The company offering a cloud service for federal use. The CSP builds the system, implements the controls, writes the SSP, fixes findings, and reports monthly once authorized.

CSO β€” Cloud Service Offering

The specific cloud service being assessed and authorized, as distinct from the company providing it.

FedRAMP Ready

A designation earned through a passing Readiness Assessment Report. Available for Moderate and High only, requires no agency partner, and valid for one calendar year. Now shown as "Legacy FedRAMP Ready" in the Marketplace. See the readiness assessment page.

FIPS 140

The federal standard for cryptographic modules. FIPS 140-validated cryptography is a common remediation item in FedRAMP assessments.

ISO/IEC 17020

The international standard for bodies performing inspection, under which A2LA accredits 3PAOs. A 3PAO may only be a Type A or Type C inspection body.

KEV β€” Known Exploited Vulnerabilities catalog

CISA's catalog of vulnerabilities known to be exploited in the wild. KEV-listed vulnerabilities follow the catalog's own due dates rather than the standard severity clocks.

LI-SaaS β€” Low Impact Software as a Service

A tailored low-impact baseline for SaaS offerings, running to about 37 controls, up to roughly 50–60 if PII or mobile applies. Penetration testing is not required for LI-SaaS.

NIST SP 800-53 Rev 5

The National Institute of Standards and Technology's catalog of security and privacy controls, published September 2020, with 1,000+ controls across 20 families. FedRAMP baselines are tailored from it. SP 800-53A Rev 5 covers assessment procedures; SP 800-53B covers the baselines.

POA&M β€” Plan of Action and Milestones

The working record tracking every open finding from the assessment: a unique ID, the affected control, severity, asset, owner, milestones, scheduled completion date, status, and closure evidence. CSPs use the FedRAMP POA&M template and update it monthly. See the remediation page.

RAR β€” Readiness Assessment Report

An optional 3PAO assessment that tests whether a cloud service is ready for a full FedRAMP assessment. A passing RAR earns the FedRAMP Ready designation. Typically $25K–$75K and 1–2 months (compiled industry range). See the readiness assessment page.

SAP β€” Security Assessment Plan

The 3PAO's plan for testing a cloud service's controls: what will be tested, how, and in what order. The SAP opens the full assessment phase; SAP to SAR often runs 8–16 weeks.

SAR β€” Security Assessment Report

The 3PAO's record of what assessment testing found, including a Risk Exposure Table for the findings. The SAR goes to the Authorizing Official with the SSP and POA&M as the authorization package.

SSP β€” System Security Plan

The CSP's description of its system, its authorization boundary, and how each control in the applicable baseline is implemented, plus attachments (policies and procedures per family, incident response, contingency, and configuration management plans, and the system inventory). The assessing 3PAO cannot write it.

Program terms: Rev5 versus 20x and CR26

FedRAMP is mid-transition, so two vocabularies are in use at once. The left column is the traditional path; the right is where the program is going.

Rev5

Shorthand for the traditional FedRAMP path built on NIST SP 800-53 Rev 5, with Low / Moderate / High impact levels, narrative control documentation, and agency sponsorship. FedRAMP stops accepting applications for new Rev5 certifications on June 11, 2027.

FedRAMP 20x

The redesign announced March 24, 2025, built around automation, machine-readable evidence, and Key Security Indicators, aiming for roughly 20Γ— faster authorization. Phase 1 (Low) ran April–September 2025 with 26 submissions; Phase 2 (Moderate) ran November 2025–March 2026 with 13 participants.

CR26 β€” Consolidated Rules for 2026

The rule set released June 25, 2026 that formalizes the 20x redesign: Classes A–D replace impact levels, and machine-readable OSCAL packages become mandatory. Optional from July 4, 2026; mandatory for all stakeholders from January 1, 2027.

Classes A–D

The certification classes replacing Low / Moderate / High from January 2027. Class A is an entry tier leveraging approved alternative frameworks, with independent assessment optional. Class B is roughly Low, Class C roughly Moderate, Class D roughly High. Class A opened August 3, 2026; Classes B and C opened August 31, 2026. Class D is not yet operational; the 20x Class D pilot is estimated for FY27 Q1–Q2. Legacy impact levels appear in parentheses only until December 31, 2026.

KSI β€” Key Security Indicator

A measurable, automatable security outcome used under FedRAMP 20x in place of narrative control documentation. KSIs are validated against machine-readable evidence. Counts vary between sources and change as the rules dataset is updated, so this site publishes no settled KSI number.

OSCAL β€” Open Security Controls Assessment Language

The machine-readable format for security controls and assessment data. RFC-0024 mandates machine-readable (OSCAL) packages for all FedRAMP providers, with requirements effective September 30, 2026. NIST publishes the full 800-53 catalog in OSCAL.

JAB / P-ATO β€” Joint Authorization Board / Provisional Authorization

The JAB (DoD, DHS, and GSA) used to issue Provisional Authorizations that agencies could leverage. The JAB has been retired and replaced by the FedRAMP Board, a governance body rather than a sponsor. Existing JAB-authorized services transitioned without losing status.

FedRAMP Board

The governance body created by the FedRAMP Authorization Act (December 23, 2022), replacing the JAB. It governs the program; it does not sponsor authorizations.

PMO β€” Program Management Office

The FedRAMP Program Management Office at GSA, established June 2012. It runs the program, reviews authorization packages, lists services as FedRAMP Certified, oversees continuous monitoring, and issues program certification directly under 20x Low.

Terms in context help more than definitions alone. The process page shows how these pieces fit together, and the history page on the hub site dates the program's milestones.