Skip to main content

FedRAMP 20x Class A: Build a Vulnerability Detection Calendar

Class A recommends monthly machine status verification and validation, 14-day detection on representative samples of similar machines, detection every three months across all resources likely to drift, and every six months across all resources not likely to drift. Keep those SHOULD decisions separate from mandatory broad detection, evaluation timing, and migration report collection.

Written by Boundera Team|November 19, 2026|7 min read

Main question

How should a FedRAMP 20x Class A team build its vulnerability detection calendar?

A useful FedRAMP 20x Class A vulnerability detection calendar starts with the activity and resource population, then assigns a cycle. A single recurring scanner job leaves too many questions unanswered: did the team check machine status, detect vulnerabilities in a representative sample, or cover the entire population that can drift?

For Class A, plan four distinct recommended cycles: monthly machine status verification and validation, representative-sample detection at least every 14 days, detection across all resources likely to drift at least every three months, and detection across all resources not likely to drift at least every six months. These are Class A SHOULD rules. They sit alongside the mandatory vulnerability detection rule; completing a scheduled job does not, by itself, demonstrate that broader rule.

Start with the mandatory detection responsibility

FRC-CLA-MFR includes VDR-CSO-DET among the mandatory Class A rules. VDR-CSO-DET requires systematic, persistent and prompt discovery and identification of vulnerabilities within the cloud service offering. Detection includes persistently verifying and validating that information resources and processes operate as intended and documented for FedRAMP Practices.

The Class A detection rule covers appropriate techniques including assessment, scanning, threat intelligence, vulnerability disclosure mechanisms, penetration testing and other relevant capabilities. Its scope extends beyond traditional vulnerability scanning or testing.

Build your calendar around that operational responsibility. For example, put a recurring machine check beside the process that receives disclosures, and identify who handles findings from each. This is a planning suggestion: the appropriate detection methods depend on the offering and the weaknesses being sought.

Give each Class A recommendation its own calendar line

FRC-CLA-RFR lists the following recommended Class A rules, if applicable. The activity and population in each row matter as much as its interval.

RuleClass A activity and populationRecommended interval
VDR-TFR-MVXVerify and validate the status of machine-based information resourcesAt least once every month
VDR-TFR-PSDPerform vulnerability detection on representative samples of similar machine-based information resourcesAt least once every 14 days
VDR-TFR-PDDPerform vulnerability detection on all information resources likely to driftAt least once every 3 months
VDR-TFR-PCDPerform vulnerability detection on all information resources not likely to driftAt least once every 6 months

These intervals come from the Class A related rules. Preserve the source's units when configuring jobs: every 14 days and once every month describe different cycles.

MVX asks about machine-resource status verification and validation. PSD asks about vulnerability detection in representative samples of similar machines. PDD and PCD divide all information resources by whether they are likely to drift. The latter two rules are not limited to machine-based resources in their Class A wording.

Keep evidence for those purposes distinguishable even when a single tool run supports more than one. A monthly status check needs evidence of what was verified and validated; its timestamp alone does not explain the sample population or demonstrate coverage of either drift branch. Similarly, a completed sample run does not establish that every information resource in an all-resource population received detection.

Make the population and ownership visible

Use a small internal planning record to make the work inspectable. The following fields are suggested operating aids:

  • Rule and activity: name the work being scheduled.
  • Population: identify the machine group, representative sample, or full drift-based resource population.
  • Method and rationale: explain the detection or verification approach, including why the grouping or drift assignment makes sense.
  • Owner and backup: assign responsibility for the run and for investigating missing evidence.
  • Latest completion and evidence: link the result and record the next planned cycle.
  • Departures and follow-up: link the decision about a recommendation and any resulting action.

For an illustrative service, the monthly line might cover verification and validation of production machine status. A separate 14-day line might select a representative sample from a documented group of similar application instances. Three-month and six-month lines would track the full populations assigned to the respective drift branches. These examples do not establish an appropriate sample size or drift classification for your environment.

Have the resource owner explain each assignment. When a deployment pattern changes, review whether the grouping and drift rationale still fit. Put that review beside the engineering workflow that can supply the evidence, so the calendar points to completed work rather than simply producing another reminder.

Record decisions about SHOULD rules

Class A's recommended intervals retain the force of SHOULD. FedRAMP's definition of SHOULD permits valid reasons to depart in particular circumstances, while requiring the full implications to be understood and carefully weighed. Parties MUST explain their decisions about handling such rules in their security documentation.

Give each applicable recommendation a recorded decision. If the team implements the recommended cycle, identify the process and evidence. If it chooses a departure, explain the circumstances and implications in the security documentation and link that explanation from the planning record. A blank calendar row gives the next operator no useful basis for understanding the decision.

Separate detection cycles from evaluation timing

The Class A VER-TFR-EVU recommendation addresses a different clock: providers SHOULD evaluate all vulnerabilities as required by VER-EVA within 14 days of detection.

Track detection time and evaluation progress on each finding. The 14-day representative-sample cycle schedules detection activity; the 14-day evaluation recommendation runs from detection of a vulnerability. Keeping those records separate makes it easier to see which work is due. This calendar does not calculate mitigation or remediation deadlines.

Keep adoption dates separate from the migration data call

Publication, applicability and collection dates answer different questions. The relevant rule changelogs record the Consolidated Rules launch on June 24, 2026. The Class A certification rules page lists July 4, 2026 for optional adoption and obtaining initial certification, January 1, 2027 for maintaining ongoing certification, and the first FedRAMP independent assessment started after January 1, 2027 as the end of its grace period. The overall timeline makes general mandatory adoption subject to specific applicability and effective dates.

Use those applicable Class A sources when planning adoption. Keep any migration collection task on a separate line from the standing operating calendar.

As checked on November 19, 2026, the FY27 Q1 Emergency Test page lists FedRAMP 20x Class A among the profiles exempt from VDR/VER Migration Progress Report collection. It says offerings outside that migration process receive a standard Emergency Test message requiring acknowledgment, and warns that collection details can change up to the test day.

That passage concerns the collection. It does not remove VDR-CSO-DET from FRC-CLA-MFR or the recommendations from FRC-CLA-RFR. Keep those rule decisions and operating cycles visible even when a migration progress report is not requested.

Review one completed cycle before relying on the calendar

Choose a recent completion and follow its evidence through the record. Can an operator identify the population, the method used, what the result established, and who owns the next action? Then check each of the other activity types separately.

A calendar becomes useful when it lets the next person answer those questions without reconstructing the work. Start with the four Class A recommendation rows, connect them to the broader detection process, and maintain the decisions and evidence as the offering changes.

Frequently asked questions

What are the four Class A vulnerability detection calendar recommendations?

VDR-TFR-MVX recommends machine status verification and validation at least monthly. VDR-TFR-PSD recommends representative-sample detection on similar machines at least every 14 days. VDR-TFR-PDD recommends detection across all information resources likely to drift at least every three months, and VDR-TFR-PCD across all information resources not likely to drift at least every six months.

Are the Class A recommended intervals mandatory?

These four Class A rules use SHOULD. FedRAMP requires parties to explain their decisions about handling SHOULD rules in their security documentation, with valid reasons and the full implications carefully weighed when departing. VDR-CSO-DET remains a mandatory Class A detection rule.

Does the FY27 Q1 migration report collection exemption remove Class A detection rules?

No. The Emergency Test page lists Class A as exempt from VDR/VER Migration Progress Report collection and says offerings outside that migration process receive a standard test requiring acknowledgment. The standing mandatory and recommended Class A rules remain distinct from that collection.

Is the 14-day sample detection cycle also the evaluation clock?

They are separate recommendations. VDR-TFR-PSD concerns detection on representative samples of similar machines at least every 14 days. Class A VER-TFR-EVU recommends evaluation of all vulnerabilities as required by VER-EVA within 14 days of detection.

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