From a Spreadsheet to the Three Report Files

This guide is based on the FedRAMP Consolidated Rules for 2026, version 2026.11.02.01, and the official schemas dated 2026-06-24. Rule identifiers are given in parentheses so you can check each statement.

These rules take effect on December 7, 2026, for obtaining and for keeping a certification. Providers have a grace period until March 7, 2027. Adoption has been optional since July 4, 2026. (VER info, VDR info)

Who this is for

This guide is for a security or compliance person at a cloud provider who tracks vulnerabilities in a spreadsheet today.

At the end you will have a spreadsheet in the checker’s layout, a list of problems the checker found in it, and the report files built from it. Three other guides go deeper: the ratings, the time limits by class and what the reports must contain.

The files and what the rules say about them

The checker builds three JSON files and, with them, the monthly report in a form people can read. Each has its own rule.

File What it holds Force
Monthly report (HTML and Markdown) Detection and response activity in a human-readable format MUST, at least monthly (VER-TFR-MHR)
Vulnerability detail report (JSON) Vulnerabilities that are not accepted MUST for the content (VER-RPT-VDT)
Accepted vulnerability info (JSON) Accepted vulnerabilities MUST for the content (VER-RPT-AVI)
Historical activity (JSON) One snapshot of all vulnerabilities MAY for class A, SHOULD for classes B, C and D (VER-TFR-MRH)

In short: the monthly human-readable report and its content are mandatory (MUST). The machine-readable JSON files are recommended (SHOULD for classes B to D, MAY for class A). No rule says in so many words that the detail and accepted content must be delivered as JSON; the rules name a schema for each. (VER-RPT-PER, VER-RPT-VDT, VER-RPT-AVI, VER-TFR-MRH)

The rules give no layout for the monthly report. (VER-TFR-MHR)

The columns

The template has one row per vulnerability and a header row. Keep the header exactly as it is. Four columns must be filled in every row: tracking_id, description, detected_at and detection_source. The other cells may be left empty until you have the answer.

Column What goes in it Rule
tracking_id Your own identifier, unique per row VER-RPT-VDT, VER-RPT-AVI
description A short description of the flaw Required by the schema; not in the rule’s list
detected_at When it was detected VER-RPT-VDT
detection_source The tool or activity that found it VER-RPT-VDT
evaluation_completed_at When your evaluation finished VER-RPT-VDT; VER-TFR-MAV counts 192 days from it
internet_reachable yes or no VER-EVA-EIR, VER-RPT-VDT
likely_exploitable yes or no VER-EVA-ELX, VER-RPT-VDT
potential_agency_impact Free text on the impact Schema only; the rule asks for a rating
rating_events The rating over time, as timestamp=N3;timestamp=N2, oldest first VER-EVA-EPA, VER-RPT-VDT
next_reduction_at, next_reduction_target When the next reduction is expected, and the rating after it VER-RPT-VDT
accepted_at, acceptance_rationale When it became an accepted vulnerability, and why VER-TFR-MAV, VER-RPT-AVI
closed_at, disposition When it was closed, and how: Fully Mitigated, Partially Mitigated, Remediated or False Positive VER-RPT-VDT
overdue_explanation Why it is overdue, if it is VER-RPT-VDT
supplementary_risk_information Anything that helps agencies assess the risk VER-RPT-VDT, VER-RPT-AVI
kev_due_date The CISA due date, if it is a Known Exploited Vulnerability VDR-TFR-KEV

Write times like 2026-11-01T09:30:00Z, with seconds and an offset. Write yes or no (true and false also work). Write ratings N0 to N5. Columns that go together, such as accepted_at and acceptance_rationale, must both be filled or both be empty.

The rules require most items “if applicable”. (VER-RPT-VDT) Do not put sensitive details that would likely lead to exploitation into any text column. (VER-RPT-NID)

Steps with the free checker

Open the checker and choose “Build from a CSV”.

  1. Download the template. You can also download a filled sample with synthetic data to see how it looks.
  2. Fill it in, one row per vulnerability. Export or save it as CSV, in UTF-8.
  3. Set the certification class, the reporting period and the address of your Certification Package Overview. Names and an overview text are optional.
  4. Choose your file, or drop it on the page. The file is read in your browser and is not uploaded.
  5. Read the results. You get a list of row problems, findings grouped by severity, and a preview of the monthly report. Rows with problems are left out of the reports until you fix them. Row 1 is the header row, so the first vulnerability is row 2.
  6. Download the files you need: the three JSON files, the monthly report as HTML or Markdown, and a tidied copy of your CSV.

Fix the spreadsheet, drop it in again, and repeat until the errors are gone. The checker does not block the downloads.

The most common problems and how to fix them

These are taken from the checker’s own messages.

  • A required column is missing, or a column name is not in the template. Add the column with the exact template name. Remove or rename any column the template does not have. A repeated column name must appear only once.
  • A row has a different number of fields than the header. Look for a missing or extra comma. Put any text that contains a comma in quotes.
  • A timestamp is not accepted. Use the form 2026-11-01T09:30:00Z. A plain date is not enough, except in kev_due_date, where 2026-11-01 is fine.
  • A value is not yes or no, or a rating is not N0 to N5. Retype it in the accepted form.
  • A rating history is not in time order. Sort the rating_events entries oldest first.
  • Only one of two paired columns is filled. Fill in both or neither: next_reduction_at with next_reduction_target, accepted_at with acceptance_rationale, closed_at with disposition.
  • A record has an evaluation time but no likely-exploitable answer, no internet-reachable answer or no rating. The checker reports an error for each missing one. A person must record them. (VER-EVA-ELX, VER-EVA-EIR, VER-EVA-EPA)
  • A record is overdue and has no explanation. The checker reports an error. Write the reason in overdue_explanation. (VER-RPT-VDT)
  • A record has gone past 192 days from evaluation without being accepted. The checker reports an error. Record the acceptance and its rationale. If the vulnerability has in fact been fully mitigated or remediated, record the closure and its disposition instead. (VER-TFR-MAV)
  • A tracking ID is used twice. Give each row its own ID. All rows with that ID are left out until you do.
  • Text looks like sensitive detail. The checker warns when a text cell seems to contain something that could lead to exploitation. Remove it, or confirm that disclosing it is safe. (VER-RPT-NID)

What the tool does not do

  • It does not decide a rating, reachability or exploitability. Those are your inputs, made by people. (VER-EVA-ELX, VER-EVA-EIR, VER-EVA-EPA)
  • It does not submit anything to anyone. You download the files and deliver them yourself.
  • It is not an assessment. It reads the spreadsheet as you wrote it and reports what it finds against the rules.

Ratings and time limits are your responsibility. Findings about deadlines are reminders, not a statement of whether you meet the rules.