In This Article
Watch the video: What Goes in the VER Machine-Readable Report?
What exactly goes in the FedRAMP VER machine-readable report? If you've spent years building POA&M spreadsheets and walking agency reviewers through them line by line, this change asks a lot of your team. The new rules replace that spreadsheet with structured JSON files that agencies pull straight into their own tools, and the requirements have short names like VER-RPT-VDT that are easy to mix up.
This article walks through the three JSON files FedRAMP's Vulnerability Evaluation and Reporting (VER) rules call for, why FedRAMP is moving away from human-readable reports, what each vulnerability record contains, and how the 192-day rule decides which report a vulnerability belongs in.
What are the FedRAMP VER machine-readable reports?
FedRAMP's Vulnerability Evaluation and Reporting rules define persistent reporting requirements for cloud service providers.
Those requirements come down to three machine-readable JSON files, and FedRAMP publishes an official JSON schema for each one.
All three should come from the same source of truth about your vulnerability detection, response and evaluation activities. They're three similar files that give your federal agency customers different views of the same work.
FedRAMP also sets how often the historical activity should be updated, by certification class: at least monthly for Class A and Class B, every 14 days for Class C and every 7 days for Class D, according to the VER rules.
Why FedRAMP is replacing POA&M spreadsheets with machine-readable reports
The value of these reports is biggest on the agency side. Government customers reviewing vulnerabilities in your cloud service offering will no longer ask for an Excel spreadsheet of your POA&Ms and then talk through it: let's go through line three, let's go through line four ... etc
That's a slow, manual process.
It takes a lot of time for the cloud service provider to create and update those POA&M spreadsheets, and a lot of time on the agency side to review them and work out what they mean.
Operating at machine speeds means moving from human-readable reports only, like a PDF or an Excel spreadsheet, to machine-readable reports.
Machine-readable reports aren't meant to be read by a person. They're meant to be pulled in automatically to a GRC or risk management platform.
This shift is on a firm schedule. In Notice NTC-0014, FedRAMP made the Vulnerability Detection and Response (VDR) and VER rules mandatory by December 7, 2026 to align with CISA BOD 26-04. If you're weighing what happens after that date, here's how the VDR grace period works.
How VER reporting works for cloud service providers and agencies
Every vulnerability in these reports carries a Potential Agency Impact N-rating, or PAIN level, from N0 to N5, along with whether it's internet reachable and whether it's likely exploitable.
If those terms are new, start with what FedRAMP VDR and VER are and how the PAIN scale works.
Here's how that data moves from a cloud service provider to an agency.
What's in each vulnerability record?
Each open vulnerability in these reports includes the same core details.
As you carry out ongoing mitigation to reduce the severity of vulnerabilities in your systems, those details update continuously in the machine-readable JSON reports. The agency gets a near real-time view of the likely impact to their system if those vulnerabilities are exploited.
The full VER-RPT-VDT requirement also asks for the source of the detection, whether the vulnerability is or is likely to become overdue, any supplementary information that helps agencies assess the risk, and its final disposition.
Accepted vulnerability records add an explanation of why each one is accepted.
The 192-day rule for accepted vulnerabilities
A vulnerability moves from the non-accepted report to the accepted vulnerability report if it isn't fully mitigated or remediated within 192 days of evaluation. Under VER-TFR-MAV, you must mark a vulnerability as accepted once it's been more than 192 days and it hasn't been fully remediated or mitigated.
That means every vulnerability sits in one of two places.
How Paramify produces and ingests FedRAMP VER reports

Paramify is a modern GRC tool that supports the FedRAMP Consolidated Rules for 2026 (CR26), including the VDR and VER requirements to produce and ingest machine-readable JSON reports.
Every finding is tracked as an Issue from open to remediated, and that data feeds the three schema-validated VER reports instead of a spreadsheet.
Agencies can pull those reports through an API rather than waiting on a submission.
See the details on the VDR and VER compliance product page, or how VER fits into the rest of Paramify's FedRAMP 20x certification software.
For the full list of reports, here are the CR26 deliverables Paramify automates. If you're comparing options, start with how to choose a FedRAMP VDR tool.
Moving from POA&M spreadsheets to VER JSON
FedRAMP VER reporting replaces the line-by-line POA&M review with three machine-readable JSON files: the vulnerability detail report, the accepted vulnerability info and the historical activity report.
It's a lot to take in.
Paramify can help you produce and ingest these reports, so if you have questions or want to see what this looks like in practice, reach out to us or request a demo below.
Read more
- What Are FedRAMP VDR and VER? The Difference, the Deadline, and the PAIN Scale
- What Happens If You Miss the December 7 FedRAMP VDR Deadline? The Grace Period, Explained
- Understanding BOD 26-04 and FedRAMP VDR: What You Need to Do to Stay Compliant
- Why Isn't CVSS Enough for FedRAMP Anymore?
- How FedRAMP VDR Maps to RA-5 and SI-2 (and What Replaces Monthly ConMon Scans)
FAQ
What are the three FedRAMP VER machine-readable reports?
The vulnerability detail report (VER-RPT-VDT), the accepted vulnerability info report (VER-RPT-AVI) and the historical vulnerability evaluation and reporting activity (VER-TFR-MRH). All three are JSON files built from the same source of truth.
What's the difference between the vulnerability detail report and the accepted vulnerability info report?
The vulnerability detail report covers non-accepted vulnerabilities. The accepted vulnerability info report covers accepted ones. Both include the same kind of detection and response activity for the reporting period.
When does a vulnerability become an accepted vulnerability?
When it isn't fully mitigated or remediated within 192 days of evaluation. VER-TFR-MAV requires you to categorize it as accepted at that point.
What does PAIN mean in FedRAMP VER?
PAIN stands for Potential Agency Impact N-rating. It runs from N0 (exploitation is extremely unlikely to affect agencies) to N5 (a debilitating effect on more than one agency).
Do VER reports replace POA&M spreadsheets?
They replace the spreadsheet workflow. Instead of an Excel file reviewed line by line, agencies pull machine-readable JSON into their own GRC or risk management tools.
How do agencies use VER JSON files?
They ingest the files through automation, set thresholds, alerts or configurations, and get a near real-time view of the risk your cloud service offering poses to their information system.
When are the VER rules required?
FedRAMP made the VDR and VER rules mandatory by December 7, 2026, with a grace period that ends March 7, 2027.



