Method

Versions in use

Rule and schema versions
Rules version2026.11.02.01
FedRAMP Vulnerability Detail Report (VER-RPT-VDT)version 0.1.1, dated 2026-06-24
FedRAMP Accepted Vulnerability Info (VER-RPT-AVI)version 0.1.1, dated 2026-06-24
FedRAMP Historical Vulnerability Evaluation and Reporting Activity (VER-TFR-MRH)version 0.1.1, dated 2026-06-24
FedRAMP Common Definitionsversion 0.4.2, dated 2026-06-24

This page says exactly what the tool relies on, so you can check its work.

What the tool does not do

  • It never decides a rating, or whether a vulnerability is internet-reachable or likely exploitable. Those are your decisions. The tool checks and formats what you give it.
  • It does not give compliance, legal or security advice.
  • It does not send your files anywhere. They stay in your browser.
  • It does not replace reading the rules. Each finding links to the official rule page.

The rules make the evaluation decisions, the content of the reports and a human-readable report at least monthly mandatory (MUST). The machine-readable JSON files are recommended: SHOULD for certification classes B to D, MAY for class A. The tool produces both.

If the rules change

The official rules and schemas are still being revised. We compare our copies with the official ones every week and update the tool when they differ. The versions in use are listed below and printed in every report.

How the tool reads the open points

The rules leave some questions open. These are the readings the tool uses.

I-1: The response time limits run from the evaluation and depend on the current rating. Does the clock restart when the rating is reduced?

No. The due date is the evaluation time plus the time limit for the current rating. A provider may choose to measure from the latest rating change instead; the report says which was used.

I-2: Which vulnerabilities appear in a period's report?

Every vulnerability with a dated event in the period (detected, evaluated, rating changed, accepted or closed), and every vulnerability still open at the end of the period.

I-3: What happens when a rating goes up?

The official format records only reductions. An increase is kept in the provider's own history and stated in the supplementary information, for example "Rating re-evaluated from N2 to N3 on 2026-12-01."

I-4: Which vulnerabilities must be categorised as accepted after 192 days?

Any that is still open, or closed only as partially mitigated, 192 days after its evaluation and has not been accepted. One closed as fully mitigated, remediated or a false positive needs no acceptance.

I-5: As at what moment is each vulnerability shown?

As at the end of the reporting period. Later events are left for the next report.

I-6: When is a vulnerability shown as overdue?

When it is open, not accepted, and past any of three dates: its mitigation or remediation date (VDR-TFR-PVR), its evaluation date if it has not been evaluated (VER-TFR-EVU), or the 192-day date (VER-TFR-MAV).

I-7: Is a deadline missed at the exact moment it falls?

No. It is missed only after that moment.

I-8: Which certification classes are covered?

All four. The rules list classes B, C and D as their scope but also give wording for class A, which the tool uses for class A.

I-9: What happens to records the tool cannot read?

A record with a missing or invalid required value, or one that shares its tracking ID with another, is left out of every file and listed as an input problem. A vulnerability detected after the end of the period waits for the next report.