Moving to FedRAMP 20x: Check the Basis for Assessment Demands
FedRAMP guidance says not to enforce ghost rules without a specific written requirement, while IVV evidence and technical assessment duties remain. Separate a published obligation, a request for supporting evidence, permitted advice and an agency expectation. Preserve Program-versus-legacy-Agency context, record the request’s basis and resolve questions with the responsible owner without withholding needed evidence or changing findings.
In this article
Main question
How should teams moving to 20x respond to unwritten assessment requirements?
Moving to FedRAMP 20x: Check the Basis for Assessment Demands
An assessment request arrives with an explanation that the team has always done it this way. Before rebuilding a legacy template, ask what the request is meant to establish and which published requirement applies. Handling FedRAMP 20x unwritten assessment requirements well means clarifying the basis while continuing to supply useful assessment evidence.
FedRAMP's assessor transition guidance says assessors should not enforce “ghost rules”: demands presented as FedRAMP requirements without a specific written requirement on fedramp.gov. That guidance does not remove verification, validation or technical judgment.
Distinguish the request's purpose
Several different conversations can sound like a request for more documentation. Separate them before deciding how to respond:
| Kind of request | Useful follow-up |
|---|---|
| A stated FedRAMP requirement | Ask for the written rule, current version and applicability to the offering. |
| Evidence supporting an assessment conclusion | Ask what implementation or effectiveness question the evidence will answer. |
| Suggested improvement | Clarify whether it is advice and how it relates to the assessment without compromising independence. |
| Agency-specific expectation | Identify the responsible agency owner, applicable path and basis for the expectation. |
This is an editorial discussion aid, not an official classification form. FedRAMP's provider rule guidance says applicability language is evaluated in the provider's actual context. Keep the certification type, path, class and any stated conditions beside the cited rule.
Keep evidence duties and technical review intact
IVV-CSO-SEI requires providers to supply all necessary assessors with evidence that documented measures have been implemented. IVV-CSO-SEE requires evidence that implemented measures are effective. The corresponding assessor duties, IVV-IAS-VIM and VEF, cover verifying implementation and validating intended results through technical review. Independent Verification and Validation rules
The assessment guidance also retains qualitative work: speak with engineers about design choices, operating limits and failure modes, then test their explanations through independent research and technical review.
A request for supporting evidence is therefore not automatically an unwritten rule merely because the requested evidence format is not named in a rule. Ask what it supports. If another source would answer the same question more clearly, discuss that option with the assessor instead of withholding the evidence or dismissing the finding.
Advice has its own boundary. IVV-CSO-RAA and IVV-IAS-SHA permit receiving and sharing relevant assessor advice unless doing so is likely to compromise the assessment's objectivity and integrity. An agreed improvement suggestion is not a promise of a favorable result.
Preserve the Program-versus-Agency context
FedRAMP's transition guidance says Program Certification does not use a separate Security Assessment Plan or Security Assessment Report; the assessment record stays with the maintained package. That is not a universal declaration that every SAP, SAR or screenshot request is invalid.
The same guidance separately addresses the legacy Rev5 Agency Certification path. When the agency authorizing official requests additional assessment, traditional documents or static evidence, those materials should be provided to the sponsor for its authorization work. FedRAMP's assessment and material expectations also remain; the guidance says both sets of expectations are met. Assessor transition guidance
Record the basis and resolve the open question
As an operating practice, keep a short record of the requested action, cited rule and version, applicability, purpose of the evidence, provider response and unresolved question. Include the responsible assessor or agency owner and preserve the resulting explanation.
For example, “the old checklist has this section” leaves the purpose unclear. A follow-up can identify whether the section supports a published obligation, supplies needed evidence or reflects a sponsor's separate expectation. Resolve that question before treating the format as either compulsory or unnecessary.
Use the clarification guide for a genuine interpretation question, the recommended-rule decision guide for rules with that force, and the finding-preservation guide when recording an assessor's conclusion. A request for clarification is not permission to waive a MUST or change a finding's meaning.
For 20x, the IVV rules list July 4, 2026 for optional adoption and obtaining initial certification, January 1, 2027 for maintaining ongoing certification, and grace ending on the first independent assessment started after January 1, 2027. Keep those applicability dates with the current rule version when resolving a request.
Frequently asked questions
Does a request for an unnamed evidence format create a ghost rule?
Not automatically. Providers still supply evidence of implementation and effectiveness under IVV-CSO-SEI and SEE. Clarify what the requested evidence supports and its relationship to the applicable written requirement before treating it as an additional obligation.
Are SAP, SAR and screenshot requests always invalid in 20x transition discussions?
No. Program Certification guidance says there is no separate SAP or SAR, but the legacy Rev5 Agency Certification section preserves sponsor requests for additional assessment, traditional documents and static evidence. Both agency expectations and FedRAMP assessment and material expectations are met in that context.
May an assessor suggest improvements during assessment?
IVV-CSO-RAA and IVV-IAS-SHA permit relevant advice on security or verification, validation and reporting procedures unless doing so is likely to compromise the objectivity and integrity of the assessment. Advice does not promise a favorable result.
Next step
If you want to turn this guidance into an execution plan, the product side handles control mapping, SSP drafting, and evidence collection.
Related articles
FedRAMP 20x: Coordinate CISA Directive Responses with Agencies
Coordinate directive responses around the actual service version, FedRAMP’s central collection and the agency’s responsibilities for noncertified services.
FedRAMP 20x: Make Public JSON Work in Agency Web Tools
Pair schema validation with a real cross-origin browser application check for public certification JSON, then verify the public logo link.
Moving to FedRAMP 20x: Which Rev5 Certifications Can Coexist?
Distinguish Rev5 Program from Rev5 Agency Certification before planning coexistence with 20x, and preserve the warning about complexity and confusion.