GovRAMP vs FedRAMP: Which Cloud Certification to Pursue First

GovRAMP vs FedRAMP is a choice between two cloud security programs built on the same control catalog but sold into different markets. FedRAMP certifies cloud services for federal agencies. GovRAMP, formerly StateRAMP, verifies cloud services for state and local governments, and some states also recognize it for their own programs. Both draw on NIST SP 800-53 Rev 5, so work done for one carries into the other, but the paths between them are not symmetrical. This article compares the two programs, explains how they connect, and sets out which to pursue first depending on where a provider sells. GovRAMP and FedRAMP Side by Side GovRAMP FedRAMP Who runs it GovRAMP, a nonprofit membership organization (formerly StateRAMP) The FedRAMP program at the U.S. General Services Administration Market State, local, and education governments Federal agencies Control basis NIST SP 800-53 Rev 5, at impact levels based on FIPS 199 NIST SP 800-53 Rev 5 for Rev5 certifications; key security indicators for 20x, under the Consolidated Rules for 2026 Levels of recognition Statuses: Progressing Snapshot, Core, Ready, Provisionally Authorized, Authorized Certification classes A through D under the Consolidated Rules for 2026 Assessment Snapshot and Core are lighter steps; Ready and above require a third-party assessment Third-party assessment, with requirements set by class Ongoing obligations Membership and monthly continuous monitoring for Ready and above Continuous monitoring under the CR26 rules The table shows the main structural difference. GovRAMP offers graduated statuses that let a provider show progress before full authorization, which suits state and local buyers who want evidence early. FedRAMP’s 2026 rules reorganized certification into classes tied to the risk of the service and the agency’s needs. Elevate’s overview of the FedRAMP Consolidated Rules for 2026 explains the class structure. GovRAMP Statuses in Brief The Progressing Snapshot measures a prioritized subset of controls and places the product on GovRAMP’s progressing list. Core sets baseline cybersecurity requirements. Ready requires an independent assessment showing that controls are implemented. Provisionally Authorized and Authorized represent full authorization with ongoing monitoring, and require a government sponsor. Elevate’s GovRAMP audit readiness service covers each step. How GovRAMP and FedRAMP Connect The two programs recognize each other’s work, but mostly in one direction: federal work counts toward state recognition more easily than the reverse. From FedRAMP to GovRAMP: Fast Track GovRAMP’s Fast Track lets providers with existing FedRAMP work submit their federal security package to the GovRAMP program office for an expedited review, instead of repeating a full assessment. GovRAMP membership and GovRAMP continuous monitoring still apply. For a provider that already holds a FedRAMP certification, this is usually the quickest route into state and local markets. From GovRAMP to FedRAMP: Class A FedRAMP’s Consolidated Rules for 2026 created one place where a GovRAMP status counts. A Class A certification requires a prior audit from an approved alternative framework, and GovRAMP at any impact level qualifies, alongside FedRAMP Rev5 and SOC 2 Type 2. Class A is temporary: it cannot be held for more than two years and is intended as a market-entry step for agency pilots. Beyond that, a GovRAMP status does not substitute for the higher FedRAMP classes, so a provider moving into the federal market still needs a FedRAMP assessment. Elevate’s guide to FedRAMP Class A authorization covers that path. Into State Programs: Texas as an Example Some states run their own programs and recognize both. Texas’s TX-RAMP grants its Level 2 certification to services with GovRAMP Core, Ready, Provisionally Authorized, or Authorized status, and recognizes FedRAMP Low, Moderate, and High at the corresponding levels on request. Elevate’s explainer on TX-RAMP [INTERNAL LINK: TX-RAMP article, add URL after publication] covers the details. Starting point Federal market State and local market FedRAMP certification Direct GovRAMP via Fast Track; TX-RAMP via reciprocity request GovRAMP status Counts only as the prior audit for a temporary FedRAMP Class A Direct; TX-RAMP Level 2 for Core and above Neither Full FedRAMP path Full GovRAMP path, or a state’s own program The table summarizes the asymmetry. A FedRAMP certification opens both markets with relatively little extra work. A GovRAMP status opens the state market fully but reaches the federal market only through the temporary Class A step. Which to Pursue First The right order depends on where revenue will come from in the next two years, not on which program is more rigorous. If You Sell Mainly to State and Local Governments Start with GovRAMP. A Progressing Snapshot gets the product listed early, and Core or Ready status gives buyers verified evidence without a government sponsor. Ready status and above also earn TX-RAMP Level 2 through reciprocity, which covers one of the largest state markets with the same work. Pursue Provisionally Authorized or Authorized when a sponsoring agency is ready to back it. If Federal Revenue Is the Goal Within Two Years Start with FedRAMP at the class your target agencies need, then use GovRAMP Fast Track to reach state and local buyers. Doing it in this order avoids building a GovRAMP package that does not carry into the federal market. Elevate’s article on FedRAMP sponsor requirements explains how agency sponsorship works under the 2026 rules. If a Federal Pilot Is Within Reach Now A provider that already holds GovRAMP status or a SOC 2 Type 2 report can use FedRAMP Class A to serve an agency pilot while it works toward a higher class. Plan the move before the two-year limit, because Class A cannot be renewed into a permanent status. If You Sell Only in Texas TX-RAMP can be earned directly through a state assessment or Fast Track based on accepted audit reports. If other states are likely to follow, GovRAMP Ready is often the better investment, since it earns TX-RAMP Level 2 and is recognized beyond Texas. In every scenario, the control work overlaps heavily because both programs draw on NIST SP 800-53 Rev 5. Documenting controls once, in a form both programs can reuse, is what keeps the second certification from becoming a second project. Elevate’s comparison of
TX-RAMP: What Texas Requires From Cloud Providers

TX-RAMP, the Texas Risk and Authorization Management Program, is the security certification Texas requires for cloud services that process the data of state agencies. It is run by the Texas Department of Information Resources (DIR), and since January 1, 2022, state agencies have been required to contract only for cloud computing services that meet TX-RAMP requirements. For any software or cloud company selling to Texas government, TX-RAMP is a condition of the sale. This article explains who must comply, the certification levels, how certification works, including recognition of GovRAMP and FedRAMP, and what it takes to keep certification once granted. Who Must Comply With TX-RAMP TX-RAMP applies to cloud computing services that a Texas state agency uses to process its data, including software as a service, platforms, and infrastructure. The obligation falls on the agency, which cannot contract for a non-certified service, and therefore on the vendor, which needs certification to win or renew the contract. Vendors typically meet the requirement when an agency procurement asks for it; certified products appear on a public list DIR maintains. The program’s current rules are set out in the TX-RAMP Program Manual 4.0, published by DIR in February 2026. Providers that certified under an earlier version of the manual should review their certification and monitoring practices against it. TX-RAMP Certification Levels TX-RAMP has two certification levels, set by the sensitivity of the data the service handles, plus a time-limited provisional status. Status What it covers How it is typically achieved Level 1 Public or non-confidential information, and low impact systems DIR assessment against the Level 1 criteria, or recognition of a corresponding external status Level 2 Confidential or regulated information, in moderate or high impact systems DIR assessment against the Level 2 criteria, or recognition of a corresponding external status Provisional A temporary certification that lets agencies contract while the provider pursues full certification Granted on the basis of available artifacts and access, or of certain external statuses The agency’s categorization of its data decides which level a service needs. Most services that handle personal, health, financial, or other regulated state data need Level 2. Provisional certification does not indicate that a service meets TX-RAMP security requirements; it is a bridge to full certification, not a substitute. Three Ways to Get Certified The program manual describes certification either through a TX-RAMP assessment conducted by DIR or through recognition of an existing GovRAMP or FedRAMP status. In practice, providers use three routes. A DIR Assessment The provider completes the TX-RAMP assessment for the required level, with supporting documentation, and DIR reviews it. This route suits providers without another government cloud certification. Fast Track DIR offers a faster assessment for providers that hold certain accepted third-party audit reports. Reporting on DIR’s certified product list indicates that Fast Track has become the most used route. Providers should confirm with DIR which reports qualify before relying on it. Reciprocity With GovRAMP or FedRAMP TX-RAMP recognizes certain GovRAMP and FedRAMP statuses at the corresponding level. Reciprocity is not automatic: since late 2024, providers must submit a request to DIR to be added to the certified list. External status TX-RAMP result GovRAMP Core, Ready, Provisionally Authorized, or Authorized Level 2 GovRAMP Snapshot Provisional only; DIR does not treat it as a long-term solution FedRAMP Low Level 1 FedRAMP Moderate or High Level 2 FedRAMP LI-SaaS Not accepted The table shows why many providers pursue GovRAMP, formerly StateRAMP, first. One GovRAMP status can satisfy Texas at Level 2 and also supports sales in other states that recognize GovRAMP. The FedRAMP mapping in the table uses the impact levels the TX-RAMP rules refer to. FedRAMP’s Consolidated Rules for 2026 replaced those baselines with certification classes, so providers holding a new FedRAMP class should confirm with DIR how it is recognized. Elevate’s GovRAMP audit readiness service covers the GovRAMP side. How to Prepare for TX-RAMP The route matters more than the paperwork. Five steps help a provider choose the right one and avoid certifying twice. Step 1: Confirm the Level With the Agency Ask the contracting agency how it categorizes the data the service will handle. That categorization decides between Level 1 and Level 2, and certifying at the wrong level wastes time. Step 2: Check What You Already Hold A current GovRAMP or FedRAMP status may already qualify for reciprocity, and an accepted third-party audit report may qualify for Fast Track. Both are faster than a full DIR assessment. If the provider sells to several states, a GovRAMP status may be the better investment than a Texas-only certification. Step 3: Prepare the Security Documentation For a DIR assessment, the provider documents how its controls meet the TX-RAMP criteria for the required level. The criteria draw on the NIST SP 800-53 control catalog, so providers already working toward FedRAMP or GovRAMP can reuse much of their documentation. Elevate’s comparison of ISO 27001 and NIST 800-53 reuse in FedRAMP explains how existing control work carries over. Step 4: Use Provisional Status Deliberately Provisional certification lets an agency contract while full certification is in progress. It is time-limited and does not show that the service meets TX-RAMP requirements, so plan the path to full certification before relying on it. Step 5: Plan for Continuous Monitoring Certification is not a one-time event. TX-RAMP expects ongoing monitoring and reporting through DIR’s systems, with published analyses of Manual 4.0 describing quarterly vulnerability reporting for Level 2 and annual reporting for Level 1. Services certified through GovRAMP or FedRAMP reciprocity generally report their monitoring through that program instead. Elevate’s guide to FedRAMP continuous monitoring evidence describes how recurring evidence is organized. Elevate helps cloud providers prepare for state and federal cloud certifications, including GovRAMP and FedRAMP, through its FedRAMP services and GovRAMP readiness work. To choose the right route into Texas, talk to an Elevate advisor. Conclusion TX-RAMP is the price of entry for cloud services sold to Texas state agencies. It has two levels, set by data sensitivity, a time-limited provisional status, and three practical routes
FIPS 203 (ML-KEM): The Post-Quantum Standard Compliance Teams Need to Know

FIPS 203 is the NIST standard that specifies ML-KEM, the Module-Lattice-Based Key-Encapsulation Mechanism, a post-quantum algorithm for establishing shared secret keys between two systems. NIST published it on August 13, 2024, alongside FIPS 204 and FIPS 205 for digital signatures. ML-KEM is the post-quantum replacement for the key exchange that RSA and elliptic curve Diffie-Hellman provide today, and it sits at the center of the federal transition deadlines now in place. This article explains what FIPS 203 specifies, why it matters to compliance programs as well as to engineers, and how organizations are adopting it. What FIPS 203 and ML-KEM Specify A key-encapsulation mechanism lets two parties agree on a shared secret over an untrusted channel. One party publishes an encapsulation key; the other uses it to produce a ciphertext and a shared secret; the first recovers the same secret from the ciphertext with its decapsulation key. That shared secret then keys symmetric encryption such as AES for the rest of the session. ML-KEM defines three operations, key generation, encapsulation, and decapsulation, and fixes the shared secret at 256 bits. ML-KEM is derived from CRYSTALS-Kyber, one of the algorithms selected through NIST’s multi-year post-quantum standardization process. Its security rests on the difficulty of a lattice problem called module learning with errors, which is not known to be efficiently solvable by quantum computers. The Three Parameter Sets Parameter set NIST security category Encapsulation key size Ciphertext size Typical use ML-KEM-512 1 (comparable to AES-128) 800 bytes 768 bytes Constrained environments where category 1 suffices ML-KEM-768 3 (comparable to AES-192) 1,184 bytes 1,088 bytes The common default for general enterprise use ML-KEM-1024 5 (comparable to AES-256) 1,568 bytes 1,568 bytes Required under CNSA 2.0 for national security systems The table shows the main operational change from classical key exchange: size. An elliptic curve public key is a few dozen bytes; ML-KEM keys and ciphertexts run to more than a kilobyte. That rarely matters for a web session, but it can affect constrained devices, protocols with tight message limits, and network equipment that inspects handshakes. Choosing the parameter set is usually a policy decision rather than an engineering one: national security systems follow CNSA 2.0, and most other programs choose ML-KEM-768 unless a customer or regulator specifies otherwise. How It Relates to the Other Standards FIPS 203 covers key establishment only. FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA) cover digital signatures. In March 2025 NIST also selected HQC, a code-based algorithm built on different mathematics, as a backup key-encapsulation mechanism; it is intended as insurance in case a weakness is ever found in lattice-based schemes, not as a replacement for ML-KEM. Why FIPS 203 Matters to Compliance Programs For most organizations outside government, post-quantum cryptography was an engineering roadmap item until recently. Federal policy has since turned FIPS 203 into a compliance reference point, because the deadlines that now exist are deadlines for key establishment, and ML-KEM is the standardized way to meet them. The Federal Deadlines Point to It Executive Order 14412, signed June 22, 2026, requires agencies to move their high value assets and high impact systems to post-quantum key establishment by December 31, 2030, and to post-quantum digital signatures by December 31, 2031. It also directs the FAR Council to propose a rule requiring covered contractors to comply with NIST’s post-quantum FIPS standards by December 31, 2030. For key establishment, that means FIPS 203. NIST’s final transition report, NIST IR 8547, published October 27, 2026, maps the quantum-vulnerable key establishment schemes in current NIST standards to ML-KEM as their replacement. Validated Modules Are the Practical Constraint Federal programs rarely accept an algorithm on its own; they expect it inside a cryptographic module validated under the NIST Cryptographic Module Validation Program to FIPS 140-3. Validation takes time, and post-quantum modules are newer than the classical modules most products use. Published analyses of Executive Order 14412 report that it also directs NIST to speed up validation of post-quantum modules. Until validated ML-KEM implementations are widely available in the products an organization uses, adoption plans have to account for which modules are validated and which are not. Hybrid Deployment Fits the Rules as Proposed The most common path today is hybrid key exchange, which combines a classical algorithm with ML-KEM so the session stays secure if either one holds. FedRAMP’s RFC-0035, open for comment until November 17, 2026, addresses this directly: under the proposal, adding a non-validated algorithm while a validated module still protects federal customer data, as in a hybrid implementation, would not be treated as a transformative change. That gives cloud providers a defined way to add ML-KEM without dropping the validated cryptography their agency customers rely on. National Security Systems Have Their Own Rule For national security systems, the NSA’s Commercial National Security Algorithm Suite 2.0 sets the requirement, and it specifies ML-KEM-1024. Defense contractors that build or operate those systems follow CNSA 2.0 rather than choosing a parameter set themselves. How Organizations Are Adopting FIPS 203 Most organizations will not implement ML-KEM themselves. They will receive it through the platforms, libraries, browsers, and network equipment they already use, many of which have added hybrid key exchange that includes ML-KEM. The compliance work is knowing where it applies, confirming it is turned on and validated where required, and documenting it. Step 1: Start From the Cryptographic Inventory Adoption decisions depend on knowing where key establishment happens: TLS endpoints, VPNs, service-to-service connections, key management systems, and file transfer. Elevate’s guide to building a cryptographic inventory covers the fields to record. Step 2: Prioritize Long-Lived Data Key establishment that protects data with a long confidentiality requirement is exposed today to collection and later decryption. Those paths should move to hybrid ML-KEM first. Elevate’s explainer on harvest now, decrypt later covers how to identify them. Step 3: Choose the Parameter Set by Policy Use ML-KEM-1024 where CNSA 2.0 applies, and follow customer or regulator requirements elsewhere. Where nothing is specified, ML-KEM-768 is the common choice. Record the decision so assessors can see
Harvest Now, Decrypt Later: What It Is and Which Data Is at Risk Today

Harvest now, decrypt later is an attack strategy in which an adversary collects encrypted data today and stores it until a future quantum computer can break the encryption that protects it. The attacker does not need a quantum computer now. It only needs access to the data now, and patience. That is why the quantum threat is already a present-day problem for any data that must stay confidential for years. The term appears in federal guidance. A 2023 fact sheet from CISA, NSA, and NIST warned that threat actors could be targeting data that needs protection far into the future, using what it called a catch now, break later or harvest now, decrypt later operation. This article explains how the attack works, which data is exposed today, and how organizations should prioritize their response. How Harvest Now, Decrypt Later Works Most encrypted communication today relies on public-key algorithms such as RSA and elliptic curve cryptography to agree on the keys that protect data in transit. A sufficiently powerful quantum computer, which the federal guidance calls a cryptographically relevant quantum computer, could break those algorithms. Once the key exchange is broken, every session recorded under it can be decrypted. The attack therefore has two stages separated by years. In the first, an adversary intercepts encrypted traffic or steals encrypted files, which is possible with today’s tools. In the second, years later, it uses a quantum computer to recover the keys and read the data. Nothing about the first stage looks different from ordinary data theft. The organization may never know that the data was taken, and if it does, it may assume encryption made the loss harmless. Why Key Establishment Is the Weak Point The exposure is concentrated in key establishment, the step where two systems agree on a shared secret. If that step uses a quantum-vulnerable algorithm, recorded traffic becomes readable once the algorithm falls. Digital signatures face a different quantum risk: forgery in the future rather than exposure of past data. This is why federal timelines put key establishment first. Executive Order 14412 requires federal high value assets and high impact systems to use post-quantum key establishment by December 31, 2030, a year before the deadline for digital signatures. Which Data Is at Risk Today Not all encrypted data is equally exposed. The question for each data set is how long it must stay confidential, compared with how long it will take to move its protection to quantum-resistant cryptography and how long until a capable quantum computer exists. A framework often credited to researcher Michele Mosca puts it simply: if the data’s required confidentiality period plus the time needed to migrate is longer than the time until a quantum computer can break current encryption, the data is already at risk. Nobody knows exactly when that machine will exist. The useful part of the test is the first two terms, which an organization can estimate today. Data that must stay secret for a long time, protected by systems that will take years to migrate, is the exposure. The Shelf-Life Test Applied Data type How long it must stay confidential Harvest now, decrypt later exposure Health records For the life of the patient and beyond High Identity and financial account data As long as the person or account exists High Trade secrets, designs, and source code As long as they confer advantage High Controlled unclassified and defense-related information For the duration of the program or contract and often longer High Legal, merger, and negotiation records Years, until the matter is closed or public Medium to high Long-lived keys and certificates For their validity period, and anything they protected Medium to high Short-lived session data and one-time codes Minutes to days Low Information that will soon be public Until publication Low The table shows that most regulated industries hold some high-exposure data. That is why the CISA, NSA, and NIST guidance tells organizations to prioritize high impact systems, industrial control systems, and systems with long-term confidentiality needs. For a hospital, a bank, a defense contractor, or a cloud provider serving federal agencies, the high-exposure categories are often the core of the business. What Is Less Exposed The risk centers on public-key cryptography. Symmetric encryption, such as AES protecting data at rest, is considered far less affected by known quantum attacks, and NIST has said it does not expect to transition away from its symmetric standards as part of the post-quantum migration. The practical caution is that symmetric keys are often exchanged or wrapped using public-key methods. If the key that protects stored data was ever transmitted under a quantum-vulnerable key exchange, the stored data inherits that exposure. How to Reduce Harvest Now, Decrypt Later Exposure The CISA, NSA, and NIST fact sheet recommends four starting actions: build a quantum-readiness roadmap, inventory cryptography, assess risk, and engage technology vendors. Applied to harvest now, decrypt later specifically, those actions translate into five steps. Step 1: Inventory Where Public-Key Cryptography Protects Long-Lived Data Start from the data, not the algorithms. Identify the systems that hold or transmit the high-exposure categories above, then record which protocols and algorithms protect them in transit and how their keys are exchanged. Elevate’s guide to building a cryptographic inventory [INTERNAL LINK: cryptographic inventory article, add URL after publication] covers the fields worth capturing and how to keep the inventory current. Step 2: Prioritize Key Establishment for That Data Once the inventory shows where long-lived data crosses quantum-vulnerable key exchanges, those paths go first. This matches the federal sequence, where key establishment has an earlier deadline than signatures. NIST’s FIPS 203 standard, ML-KEM, is the published post-quantum key establishment mechanism, and hybrid approaches that combine it with a classical algorithm let organizations add quantum resistance without dropping validated cryptography. Step 3: Reduce What Can Be Harvested Data that is not retained or transmitted cannot be harvested. Retention limits, data minimization, and removing unnecessary copies of sensitive data reduce exposure regardless of cryptography. They are also the cheapest controls available, and
FedRAMP VDR and VER Enforcement: Corrective Action Plans, Remediation, and Revocation

A FedRAMP corrective action plan is now the mechanism that decides what happens to Rev5 cloud providers that have not fully implemented the Vulnerability Detection and Response (VDR) rules and the related VER rules. At the FedRAMP Rev5 Community Working Group meeting on November 4, 2026, FedRAMP officials walked through the enforcement sequence: who will be publicly listed as in remediation, when corrective action plans need formal approval, when a red team assessment becomes a condition, and when a certification can be revoked. FedRAMP said a public notice and a support website with the details in writing would follow by the next Tuesday. The message was firm in both directions. FedRAMP said it does not want anyone to fail the transition, and that providers working in good faith without egregious security issues will not lose their certification. It was equally clear that providers who do not engage will. The VDR and VER Enforcement Timeline The VDR and VER rules, part of FedRAMP’s Consolidated Rules for 2026, become required on December 7, 2026. The enforcement sequence described at the meeting runs from December 2026 to March 2027. Date What happens December 7, 2026 VDR and VER requirements take effect. New certification applicants after this date must show them implemented December 17, 2026 Data collection. Providers that are not fully implemented and submit no corrective action plan are listed as in remediation. So are providers whose plan targets completion after February 3, 2027 December 17 to February 3 Corrective action plans are reviewed but not formally approved or disapproved After February 3, 2027 Corrective action plans must be formally approved by FedRAMP; FedRAMP will request updated plans and expects to meet with providers still on one March 7, 2027 End of the grace period. Every provider not fully implemented is listed as in remediation, even with an approved plan After March 7, 2027 Revocation and a one-year ban apply to providers that are not fully implemented and are not operating under an approved corrective action plan The table shows that the plan, not the implementation date alone, decides the outcome. A provider that is behind but has an approved plan and shows progress keeps its certification, although it will be publicly marked as in remediation after March 7 so agencies can see its status without opening its package. A provider without an approved plan by then faces revocation. Plans That Run Past March 7 A provider may propose a target completion date after March 7, 2027. If it does, it must agree to a red team assessment by FedRAMP, coordinated with CISA, to determine whether the slower implementation creates risk for the federal government. A plan that proposes a later date without agreeing to the red team assessment will be denied. FedRAMP said it expects at least monthly meetings with providers still on a corrective action plan after March. What Leads to Revocation After March 7, FedRAMP described four situations that lead to revocation of the FedRAMP certification and a one-year ban: Elevate’s article on FedRAMP vulnerability management and the VDR deadline explains what the VDR and VER rules require. What Fully Implemented Means FedRAMP gave a precise definition, because the whole sequence depends on it. VDR and VER are fully implemented when: FedRAMP noted there are around 60 rules across VDR and VER. A provider that has implemented every MUST but simply ignored a SHOULD is not fully implemented; one that has documented why a SHOULD does not fit its service can be. What the December Data Collection Asks For The data collection, timed around December 17, 2026, will ask each provider for information on every VDR and VER rule, plus sample vulnerability reports. Field What to provide Status Fully implemented, partially implemented, not implemented, or not applicable Short explanation A few sentences on how the rule is implemented, not a full SSP control narrative Reason or risk Why a rule is not followed, where applicable Risk and mitigations For rules not fully implemented: the risk to customers, what the provider is doing to mitigate it, and mitigations customers can apply Target completion When the rule will be fully implemented The table describes what FedRAMP called a mini security decision record, lighter than the full security decision record format. FedRAMP said providers already documenting their implementation in the full format should be able to generate the mini version from that work. Formats and Templates Submissions will be text-based, CSV, JSON, or Markdown, not Excel or Word files, although providers can edit in those tools and save in a text format. The support website is expected to include schemas, templates including a CSV template for teams working by hand, a basic corrective action plan template, validators and a viewer, a list of what to have ready, frequently asked questions, examples, and a discussion forum. FedRAMP cautioned that its examples are generated with AI and only lightly reviewed, and are meant to show the level of detail expected, not a structure to copy. It also reminded providers that ignoring FedRAMP’s emergency communications is itself grounds for administrative action, separate from the VDR and VER enforcement. Write for Your Agency Customers FedRAMP’s advice on detail was pointed: the information is for agency customers, who will decide whether to keep using a service partly on how clearly the provider explains its status. A minimal submission may satisfy FedRAMP but frustrate customers, and in some cases influence whether a contract continues. Other Clarifications From the Meeting The question and answer session settled several practical points. Changes and approvals. Providers should implement VDR and VER through their normal change process: significant change notifications, change requests with documented compensating risk, or emergency changes. A 3PAO does not need to review every change in detail. FedRAMP also repeated that sponsoring agencies no longer exist for continuous monitoring; providers work with their agency customers. Vendors are not an excuse. A provider cannot claim a dependency on a scanning vendor that has not implemented VDR and VER. FedRAMP described VDR
Cryptographic Inventory First: What FedRAMP Cloud Providers Should Do About Post-Quantum Cryptography

A cryptographic inventory, a record of where a cloud service uses encryption, which algorithms and modules it relies on, and which data each protects, is the first step any FedRAMP cloud provider can take toward post-quantum cryptography. Quantum computers cannot break today’s public-key encryption yet. But the federal timeline for replacing it is now set, and no migration can be planned until a provider knows every place its service depends on vulnerable algorithms. Three developments in 2026 changed the picture. Executive Order 14412 set federal deadlines. NIST finalized its transition roadmap, NIST IR 8547. And FedRAMP opened RFC-0035, a proposal on cryptographic module rules that explicitly mentions post-quantum cryptography. This article explains what each one says and does not say, and why the inventory comes before any migration decision. Why Post-Quantum Cryptography Matters to Cloud Providers Now Public-key algorithms such as RSA and elliptic curve cryptography protect key exchange and digital signatures across almost every cloud service. A sufficiently capable quantum computer could break them. The risk that matters today is not that such a machine exists, but that encrypted data captured now could be decrypted later, once one does. Data that must stay confidential for many years is exposed to that risk already. For federal cloud providers the question is also contractual. Agencies now have deadlines for their most sensitive systems, and those systems often run on or connect to commercial cloud services. A provider that cannot tell an agency where its quantum-vulnerable cryptography sits will struggle to answer the questions agencies are starting to ask. The FedRAMP Consolidated Rules for 2026 already require providers to document their cryptographic modules; the post-quantum transition gives that documentation a new purpose. What FedRAMP RFC-0035 Says, and What It Does Not FedRAMP opened RFC-0035, Cryptographic Module Use Rules Updates, on October 14, 2026, with comments due November 17, 2026. It proposes changes to the cryptographic module use (CMU) rules in the Consolidated Rules for 2026, for both FedRAMP 20x and Rev5. FedRAMP states that the changes would not require currently operating cloud services to do anything differently. What It Proposes The RFC makes four changes. It defines a “CMVP-validated module” as a cryptographic module with an active validation under the NIST Cryptographic Module Validation Program, or an update stream of such a module. It relaxes the Class D rule on using validated modules from MUST to SHOULD, matching Class C. It adds a new rule that treats replacing a validated module with a non-validated one as a transformative change for Class B, C, and D certifications. And it moves existing language into the new definition without functional change. Certification class Use of CMVP-validated modules to protect federal customer data (as proposed) Class A MAY Class B MAY Class C SHOULD Class D SHOULD (currently MUST) The table shows that, under the proposal, no certification class would be strictly required by FedRAMP rules to use validated modules. That does not lower the bar for agencies. The documentation rule stays in place: providers must document the cryptographic modules used in each service that protects federal customer data, including whether they are validated, so that agencies can see where and how cryptography is used. What It Explicitly Does Not Do The RFC states plainly that it does not change agency obligations under FIPS 140-3 and does not set post-quantum cryptography requirements. FedRAMP’s reasoning is that agencies decide where they rely on cryptography to protect federal information, and where they do, FIPS 140-3 applies regardless of certification class. In other words, nobody fails a FedRAMP assessment for lacking post-quantum algorithms today, and FIPS 140-3 obligations continue to run through the agency. Where Post-Quantum Fits The RFC mentions post-quantum cryptography in one specific way: the proposed change would let providers integrate emerging cryptographic technologies such as post-quantum algorithms in parts of their offering at the direct request of agency customers. Its notes also clarify how this interacts with the new transformative change rule. Updating a validated module through its update stream is not a transformative change. Replacing a validated algorithm with one the update stream adds, which falls outside the module’s validation, is. But adding a non-validated algorithm while a validated module still protects federal customer data, as in a hybrid implementation, is not. That distinction matters for planning. A hybrid approach, combining a classical validated algorithm with a post-quantum one, appears to be the path the proposal leaves open without triggering a transformative change. Whether that language survives the comment period is not yet known. Elevate’s overview of FedRAMP significant change categories explains how transformative changes are handled today. The Federal Timeline: Executive Order 14412 and NIST IR 8547 RFC-0035 sets no post-quantum requirement, but the rest of the federal government has set dates. Two documents define the timeline cloud providers should plan against. Executive Order 14412 Executive Order 14412, Securing the Nation Against Advanced Cryptographic Attacks, was signed on June 22, 2026. It directs agencies to review their inventories of high value assets and high impact systems, excluding national security systems, and to move them to post-quantum cryptography for key establishment by December 31, 2030 and for digital signatures by December 31, 2031. It also directs the Federal Acquisition Regulatory Council to propose, within 180 days, a rule requiring covered contractors to comply with NIST’s post-quantum FIPS standards by December 31, 2030. That proposed rule is due around December 2026, and its scope, including which contractors count as covered, has not been defined yet. NIST IR 8547 NIST published the final version of NIST IR 8547, Transition to Post-Quantum Cryptography Standards, on October 27, 2026, replacing the November 2024 draft. The report identifies the quantum-vulnerable algorithms in NIST’s current standards and maps the transition to the post-quantum standards NIST published in August 2024: FIPS 203 (ML-KEM) for key establishment, and FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA) for digital signatures. According to published analyses of the final report, NIST will deprecate quantum-vulnerable public-key algorithms after 2030 and disallow them under its standards and guidelines
FedRAMP 20x Class D Pilot: What RFC-0036 Would Require of Cloud Providers

FedRAMP 20x Class D moved from roadmap to proposed rules on October 15, 2026, when FedRAMP opened RFC-0036 with the specific requirements for a Phase 4 pilot of the highest assurance level under 20x. Until now, Class D could be reached only through the Rev5 Agency path. RFC-0036 does not change that yet: it is a proposal for a pilot of at most ten providers, and eligibility requires a CR26-compliant 20x Class C Certification before December 1, 2026. Comments close on November 19. This article explains what the RFC proposes, how it differs from the earlier outline in RFC-0033, who the pilot realistically fits, and what cloud providers should do before the window closes. What RFC-0036 Proposes for FedRAMP 20x Class D How RFC-0036 Fits Into Phase 4 FedRAMP set the approach for Phase 4 in RFC-0033 and said the full pilot requirements would follow as a second request for comment. RFC-0036 is that second request. It proposes two new definitions, updates to six rulesets, and ten new Key Security Indicators, and it covers only cloud-hosted services. Self-hosted and hybrid-hosted services are handled in separate tracks that run in parallel, and their rules do not exist yet. FedRAMP is explicit that none of this is settled. The RFC says additional rules and indicators may be added during or after the pilot and that existing ones are likely to change based on feedback, and RFC-0033 says the final rules from Phase 4 will be folded into the Consolidated Rules for 2027. FedRAMP also says it expects 20x Class D to provide a greater level of assurance than a legacy Rev5 Class D, and that it anticipates few commercial services will invest fully to reach it. That candor is the clearest signal of who this tier is for. Elevate’s explainer on FedRAMP High and Class D covers the Rev5 baseline that Class D means today. The Pilot Timeline and Who Can Join The pilot calendar comes from RFC-0033, and FedRAMP marks every date after the comment period as a target that assumes no unexpected delays. Date What happens Source October 15, 2026 RFC-0036 opens for comment RFC-0036 November 13, 2026 Providers that apply for 20x Class C before this date and intend to join the pilot should notify the FedRAMP Director RFC-0033 November 19, 2026 RFC-0036 comment period closes RFC-0036 December 1, 2026 Deadline to hold a CR26-compliant 20x Class C Certification to be eligible RFC-0033 December 1 to 4, 2026 Application window (target) RFC-0033 December 7 to 18, 2026 Initial discussions with participants (target) RFC-0033 February 17, 2027 Mandatory draft package submission and progress review (target) RFC-0033 March 17, 2027 Final pilot package submission deadline (target) RFC-0033 The table shows two dates that matter for most providers and several that matter only to those already inside the process. The binding date is December 1, and in practice November 13, because a provider that wants to join has to be far enough along with Class C to notify FedRAMP after submitting its application. RFC-0033 also targeted November 18 for final pilot requirements, one day before RFC-0036 closes, so expect the final text to arrive after the comment period. Participation is deliberately narrow. FedRAMP will cap the pilot at 10 participants, limit it to providers that have already shown they can meet 20x requirements, and expect them to engage a FedRAMP Recognized Independent Assessment Service and the FedRAMP PMO. Participants should also expect to engage FedRAMP’s Technical Advisory Group, the FedRAMP Board, and interested agencies. Phase 2 pilot participants are not exempt: they need a full CR26-compliant 20x Class C Certification by December 1 like everyone else. Class C First: The Progressive Path to Class D The most consequential proposed rule is FRC-CLD-PCD. It says a provider seeking a 20x Class D Certification must maintain a 20x Class C Certification without corrective action for at least six months, or receive a special exemption from FedRAMP for an urgent critical need. For the Phase 4 pilot itself, a full non-pilot 20x Class C Certification is required to qualify, but the six months are not. FedRAMP’s reasoning is stated in the rule’s notes: Class D is a very large investment for the program, and traditional High sponsorship often took many years, so the proposal breaks it into stages in which a provider demonstrates progressive assurance. The notes also settle a question for existing holders. No one with a Rev5 Class D is expected to give up that certification, but a Rev5 Class D provider moving to 20x still goes through 20x Class C first, and FedRAMP anticipates most will keep their Rev5 Class D even after earning a 20x Class D. FedRAMP signaled this direction at its Rev5 community meeting earlier this month, where it described Class C first as its intent. RFC-0036 puts proposed rule language behind it. Elevate’s recap of the meeting covers what FedRAMP said then. The Rules and Key Security Indicators in RFC-0036 Rules That Raise the Bar on Automation and Data Sharing The RFC does not reproduce the existing Class D rules, only the new or modified ones, and the pattern across them is data access. Class D providers would verify and validate machine-based resources at least every three days (VDR-TFR-MVX), which matches the current Class C expectation. They would have to make all recent historical vulnerability detection and response activity available in JSON for automated retrieval, updated persistently and at least every seven days (VER-TFR-MRH). That is a change from SHOULD to MUST for Class D. Two further rules push the same direction. The Security Decision Record would have to include historical Key Security Indicator metrics: a 30-day summary, a summary of up to a year where available, and metric data every four hours for up to a year (SDR-CSX-KMT). And providers would have to supply all machine-readable parts of the certification package through a web-compatible API (CDS-CSX-API), which FedRAMP calls a new rule for Class D. The practical reading is that a Class D agency customer would
FedRAMP Updates for Rev5 Providers: What the Latest Community Meeting Changed

The FedRAMP updates from the latest Rev5 community meeting add up to a clear message: the rules are settling, enforcement is arriving on a calendar, and Rev5 providers are being steered toward 20x without being forced there yet. FedRAMP added a new PAIN0 rating to vulnerability evaluation, tightened how public JSON data must be served, shared how long Rev5 reviews are really taking, and spent much of the Q and A explaining why the December 7, 2026 vulnerability dates are not a planning target. This article sorts those updates by what they change for a cloud service provider that holds, or is pursuing, a Rev5 certification. A note on sources: FedRAMP’s spoken guidance and its published rules can differ in wording. Rule identifiers appear where the public changelog confirms them, and anything that comes only from the meeting is attributed to FedRAMP’s speakers. FedRAMP Updates That Change Your Rule Set This Month PAIN0 Adds a Floor to Vulnerability Evaluation FedRAMP’s October 5 release of the Consolidated Rules for 2026 added a PAIN0 rating to the rule that governs how providers estimate potential agency impact (VER-EVA-EPA). It covers situations where it is extremely unlikely that any agency would notice an adverse effect. Before the change, a provider had to choose a rating from N1 through N5, so findings with no meaningful agency effect tended to default to N1, the lowest rating available. FedRAMP’s speakers described two practical uses. The first is any finding that is not a real exposure, such as a confirmed false positive, which the rules already say providers should evaluate and can now rate PAIN0 instead of forcing into N1. The second is a finding where exploitation would not realistically reach agencies. They also said no remediation or mitigation timeframes changed with the release, and that PAIN0 carries none of its own. The speakers also said the rule now asks providers to estimate the likely potential impact of exploitation, with likely defined as a reasonable degree of probability based on context. Their example was deliberately extreme: a far-fetched scenario in which an attacker overwrites every drive in a data center does not justify the highest rating for an ordinary vulnerability. That wording comes from the meeting, and the public changelog summary does not describe it, so confirm it against the current rule text before rewriting a methodology around it. For a provider with a documented rating method, the work is small but real: add PAIN0 to the scale, define when it applies, and keep the evidence behind each use. It is reasonable to expect scrutiny of the false positive process before PAIN0 is accepted on a finding, because a rating of zero takes the finding off the remediation clock. Elevate’s Vulnerability Management as a Service is built around that evaluate-and-document loop. Public JSON Data Must Carry the Right Headers The same release clarified that any public JSON data FedRAMP requires, including the marketplace listing file covered below, must be served with proper cross-origin resource sharing (CORS) and Content-Type settings so web applications can use it (FRC-CSO-JSN). FedRAMP’s speakers said some content tools cannot set those headers, and that providers should not host public JSON on them, because FedRAMP would otherwise have to override security settings to read the file. Their advice was to hand the question to engineers, who typically treat it as routine. The practical test is simple: request the file the way a browser would and read the response headers before FedRAMP does. Two Smaller Clarifications on Logos and Cryptographic Modules The public information rule (CDS-CSO-PUB) now says the required logo link must point to a properly named image file. Speakers added that the image appears on the marketplace listing, so a white logo on a transparent background will disappear against the page. The cryptographic module rule (CMU-CSO-UVM) gained a note explaining that a validated module includes only the algorithms it was validated with. If an upstream update adds algorithms the module never carried through validation, those algorithms are not covered by the validation, even when the product keeps the same name. Providers relying on a validated module should check which algorithms their update stream has added. Marketplace Listings Now Run on Your Own JSON File What FedRAMP Now Requires for Listings FedRAMP has moved marketplace listings from email and form exchanges to a public JSON file that the provider hosts and maintains. The requirement sits in the CR26 public information rules and applies to new listings and to existing ones. Speakers said FedRAMP made exceptions for a period to speed things up and is now enforcing the rule across the board for any provider that wants to change its listing. The reason is capacity: about 76 providers sit in the initial implementation phase, more than 500 are already listed, and the team cannot keep hand-editing listings for all of them. The upside, as FedRAMP framed it, is control. The marketplace is built daily, sometimes every two days, from the provider’s file, and FedRAMP wants the lag to shrink toward several checks per day. Providers can add and remove timely content such as meetings or blog posts. Some fields stay with FedRAMP, such as the certification class, and the file should include only information that applies to the provider today. Elevate’s guide to the FedRAMP marketplace listing covers the listing itself. How to Submit the File and Avoid Rework Providers submit the JSON location through FedRAMP’s help desk form, not by email, and FedRAMP validates the file at submission against a published JSON schema. The file can live anywhere the provider controls, including a cloud bucket, but it should be protected so no one else can alter it. A speaker estimated about twenty minutes of work if the provider copies from its current listing, and asked providers not to push engineers into an emergency sprint: stage the work over the next couple of weeks. Turnaround is expected to start at a couple of days and fall over time. Basic markdown works, embedded images may not,
FedRAMP Moderate Is Now Class C: What Changed

FedRAMP Moderate certification no longer exists as a standalone destination on the FedRAMP Marketplace. Under the Consolidated Rules for 2026, the designation formerly known as FedRAMP Moderate is now Class C, and a provider searching for how to pursue Moderate authorization today is searching for a label the program retired. The underlying risk tier survives largely intact. What changed is the name, the terminology it no longer collides with, and, depending on which certification type a provider pursues, the entire evidence model behind it. This article covers why the rename happened, what actually moved versus what only got relabeled, and what a provider pursuing Class C through FedRAMP 20x specifically has to prove. Why FedRAMP Moderate Became Class C The Renaming Traces to a Specific, Documented Problem The retirement of Low, Moderate, and High was not a cosmetic decision made for its own sake. FedRAMP’s impact levels, drawn from FIPS 199, existed alongside a completely separate Department of Defense Impact Level system, IL2 through IL6, used for DoD cloud authorizations. The two systems shared vocabulary without sharing meaning. A cloud service described as FedRAMP Moderate did not automatically satisfy DoD IL4, and the overlapping language in marketing materials and procurement documents produced genuine confusion about which standard actually applied to a given requirement. The retirement was formally anchored in Public Notice NTC-0004, published February 25, 2026, and finalized as part of the Consolidated Rules for 2026 when CR26 launched in late June. The new Certification Class structure maps largely one to one to the retired levels: Class A is a new transitional tier with no direct predecessor, Class B covers what was previously Low, Class C covers what was previously Moderate, and Class D covers what was previously High. What Actually Changed Versus What Only Got Relabeled The mapping between old and new terminology is close to direct, which is worth stating plainly because it resolves the most common anxiety providers have about this change. A provider authorized at Moderate today becomes FedRAMP Certified at Class C without needing to re-authorize from scratch. The underlying risk tier, the type of data in scope, and the general severity of a breach at that tier did not move. What did change is more specific than the class label. The evidence model a provider builds against Class C depends on which certification type it pursues, Rev5 or 20x, and that choice determines whether the provider is still assembling a traditional NIST 800-53 control set or building toward a machine-readable rules and indicators structure that did not exist under the legacy Moderate baseline at all. The name change is close to cosmetic. The evidence model underneath it, for a provider on the 20x path, is not. What FedRAMP Moderate, Now Class C, Actually Covers The Data and Risk Profile Did Not Move Class C applies to systems handling Controlled Unclassified Information and other non-public federal data, where a breach could cause serious harm, meaning disrupted operations, compromised personal data, or financial loss, without rising to the catastrophic consequences reserved for Class D. This is the same profile FedRAMP Moderate covered under the legacy terminology, and it remains the most common certification tier in the program. Historical GAO reporting put roughly three-quarters of agency-leveraged authorizations at the moderate-impact tier, and there is no indication the underlying distribution of federal cloud workloads shifted when the label did. Where Class C Sits Among the Four Classes Class C sits between Class B, the lightest tier, and Class D, the tier reserved for mission-critical systems where a breach could be catastrophic. Elevate’s guide to FedRAMP controls and classes covers the full breakdown across all four classes and their approximate control counts under Rev5. What is worth stating here, rather than repeating that full breakdown, is the practical reason Class C matters disproportionately to the provider community: most SaaS products that handle any federal data land at Class C, which makes it the tier the largest share of the market actually has to build toward, rather than a specialized case. Two Paths to Class C: Rev5 and 20x Rev5 Class C Is Still the Traditional Control Model A provider pursuing Class C through Rev5 builds against the NIST SP 800-53 control catalog, roughly 323 to 325 controls at this tier, documented through a System Security Plan, assessed by a FedRAMP Recognized Assessor, and reported through the traditional narrative and spreadsheet-based evidence model that has defined FedRAMP for over a decade. This path suits providers with complex or legacy infrastructure, and it remains available through the Agency Certification path with a sponsoring agency, or in limited cases through the temporary sponsorless pipelines described in Elevate’s guide to FedRAMP ATO in 2026. 20x Class C Replaces the Control Count With Rules and Indicators A provider pursuing Class C through FedRAMP 20x builds against a structurally different evidence model. Instead of a control count, the 20x path defines Class C, labeled Significant, through a specific set of applicable rules drawn from the FedRAMP Consolidated Rules, organized across the rulesets that cover marketplace listing, certification, boundary definition, assurance, and package requirements, alongside a defined set of Key Security Indicators mapped back to NIST 800-53 controls. A provider on this path is not producing a narrative SSP. It is producing machine-readable evidence against a named, versioned rule set, submitted through the Program Certification path without requiring an agency sponsor. This is the path where the terminology change matters most in practice, because there was no 20x Class C evidence requirement under the legacy Moderate label at all. A provider that built its entire compliance muscle memory around the Rev5 control-count model is not just relearning a new name. It is potentially building toward a different kind of evidence entirely, depending on which certification type its architecture and market strategy point toward. The Two Paths, Side by Side Dimension Rev5 Class C 20x Class C Evidence basis NIST SP 800-53 controls, roughly 323 to 325 158 rules plus 46 Key Security Indicators Core artifact
FedRAMP POA&M: What Replaced It Under the Consolidated Rules for 2026

FedRAMP POA&M documents no longer exist for cloud service providers. Under the Consolidated Rules for 2026, the Plan of Action and Milestones that CSPs filed for years has been eliminated entirely and replaced with a list of Accepted Weaknesses, a change FedRAMP made on the reasoning that a POA&M line item was, in practice, mostly used to formally accept a weakness for an extended period anyway. A provider still building its evidence package around a POA&M template, or a compliance team still searching for the current POA&M requirements, is working from a document type that FedRAMP retired. This article explains what changed, what replaced it, and the one related term that survived under a different owner and a different meaning. Why FedRAMP POA&Ms No Longer Exist What POA&M Used to Cover Under the legacy Rev5 model, the POA&M was one of the core documents in a provider’s security package, alongside the System Security Plan. Its scope covered every management, operational, and technical control that an assessment found less than fully effective, not only vulnerabilities in the CVE sense. A provider used the POA&M to record each weakness, the planned remediation task, the resources assigned to it, and a target completion date, and an authorizing official used the same document to track whether the provider was actually closing those gaps over time. That scope made the POA&M a catch-all. A missing configuration baseline, an incomplete access review process, and an unpatched CVE could all live on the same document, tracked with the same milestone structure, regardless of how different those three problems actually were in terms of urgency or evidence. A provider preparing for its annual assessment often spent as much effort reconciling the POA&M narrative with what had actually happened operationally as it spent on the underlying remediation work itself, because the document was reviewed on its own schedule rather than updated continuously as findings changed. The table below summarizes what changed between the legacy document and the model that replaced it. Dimension Legacy POA&M Accepted Vulnerability / Accepted Weakness Authored by The cloud service provider The cloud service provider, evaluated continuously Review cadence Periodic, tied to assessment or reporting cycles Continuous, as part of ongoing vulnerability evaluation Scope Any control weakness or deficiency, narrative-based Defined per finding, with a formal status and citation Format Narrative document, commonly Word or Excel Structured, machine-readable evaluation record Reading across that table, the shift is not only about which document a provider produces. It is about when the justification gets written. A POA&M narrative was often assembled or refreshed ahead of a review, describing progress against milestones set earlier. An Accepted Vulnerability record is populated at the point a finding crosses its required remediation window, carrying the specific architectural or operational reason for that status rather than a retrospective summary. The Change: Accepted Weaknesses Under CR26 The Consolidated Rules for 2026 replace that catch-all document with a narrower mechanism tied directly to the new Vulnerability Detection and Response and Vulnerability Evaluation and Reporting rulesets. FedRAMP’s own summary of the change states plainly that Plans of Action and Milestones have been eliminated entirely and replaced with a list of Accepted Weaknesses. Rather than a static document reviewed periodically, the model now expects continuous evaluation of findings, with any finding that is not mitigated or remediated inside its required timeframe moving into a defined Accepted Weakness status instead of sitting on an open milestone. The formally defined version of this concept that appears in FedRAMP’s own definitions is the Accepted Vulnerability, identified under rule FRD-ALL-31: a vulnerability the provider does not intend to fully mitigate or remediate, or that has not been and will not be fully mitigated or remediated within the maximum overdue period FedRAMP recommends or requires. That definition lines up directly with the 192-day threshold under rule VER-TFR-MAV covered in Elevate’s guide to FedRAMP vulnerability management: once a finding crosses that line, it stops being an open remediation item and becomes a documented, justified Accepted Vulnerability instead. Why FedRAMP Made the Change FedRAMP’s stated reasoning is direct rather than diplomatic: a POA&M was mostly functioning as a formal way to accept a weakness for a long period, so the program removed the extra document and built that acceptance directly into the vulnerability evaluation process itself. This fits the broader pattern across the Consolidated Rules for 2026, where FedRAMP has replaced several narrative, periodically reviewed documents with structured, continuously maintained records inside the Consolidated Rules framework. A provider no longer produces a POA&M for an authorizing official to review on a set cadence. It produces a live, evaluated record of every vulnerability, and any that remain open past the required timeframe carry an Accepted Vulnerability status with a documented justification attached. The practical effect of this change is that acceptance is no longer a separate administrative step a provider takes after the fact. Under the legacy model, a provider could remediate a finding, decide later that a different finding was not worth fixing on the original timeline, and formalize that decision by adding it to the next POA&M cycle. Under the current model, the acceptance decision is embedded in the same evaluation that produced the PAIN rating in the first place. A finding either gets remediated inside its required window, or it crosses that window and becomes an Accepted Vulnerability automatically, with the justification captured at that moment rather than assembled retroactively for the next scheduled review. Accepted Vulnerability Versus Accepted Weakness: Getting the Terms Right Accepted Vulnerability Is the Defined, Citable Term For anything that runs through the VDR and VER evaluation pipeline, the term with an actual FedRAMP definition and rule citation is Accepted Vulnerability, not the broader phrase Accepted Weakness. A provider building documentation or training a team on the new terminology should anchor on Accepted Vulnerability for CVE-style findings, since that is the term with a published definition an assessor can point to directly. Where the Broader Term Still Needs Confirmation FedRAMP’s own change summary uses the phrase