What the Vulnerability Reports Must Contain

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)

Overview

There are four outputs.

Output Rule Format Force
Monthly human-readable report VER-TFR-MHR human readable, consistent format MUST (VER-TFR-MHR)
Vulnerability detail report VER-RPT-VDT, VER-RPT-PER JSON, vulnerability detail report schema MUST for the content (VER-RPT-VDT); the schema is named in VER-RPT-PER and VER-RPT-VDT
Accepted vulnerability info VER-RPT-AVI JSON, accepted vulnerability info schema MUST for the content (VER-RPT-AVI)
Historical activity VER-TFR-MRH JSON, historical activity schema MAY for Class A, SHOULD for 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).

All reports are FedRAMP Certification Data and are subject to the Certification Data Sharing rules. (VER-RPT-PER)

Reports must summarize all activity since the previous report. (VER-RPT-PER)

How the files relate

Non-accepted vulnerabilities go in the vulnerability detail report. Accepted vulnerabilities go in the accepted vulnerability info file. (schema: vulnerability detail report, accepted vulnerability info; VER-RPT-VDT, VER-RPT-AVI)

The historical file holds all non-accepted and all accepted vulnerabilities in one snapshot. (schema: historical activity; VER-TFR-MRH)

A vulnerability is an accepted vulnerability in two cases: the provider does not intend to fully mitigate or remediate it, or it has not been or will not be fully mitigated or remediated within 192 days of evaluation. (FRD: Accepted Vulnerability; VER-TFR-MAV)

Optional fields in the schema may be left out. The rule’s own words “if applicable” apply to the VER-RPT-VDT items. (schema; VER-RPT-VDT)

The monthly human-readable report

Providers MUST report detection and response activity to all necessary parties in a consistent, human-readable format at least monthly. (VER-TFR-MHR)

The rule file names no schema for this report and gives no layout. The content rules below apply when reporting on detection and response activity. (VER-TFR-MHR, VER-RPT-VDT, VER-RPT-AVI)

Required content for non-accepted vulnerabilities, “if applicable”. The eleven items are listed in the table that follows, with their JSON fields. (VER-RPT-VDT)

Required content for accepted vulnerabilities: tracking identifier, time and source of detection, time of completed evaluation, internet-reachable or not, likely exploitable or not, current estimated N-rating, explanation of why it is accepted, and any supplementary information the provider determines will responsibly help agencies assess or mitigate the risk. (VER-RPT-AVI)

Providers SHOULD add high-level overviews of all detection and response activity in the period, including vulnerability disclosure programs, bug bounty programs, penetration testing and assessments. (VER-RPT-HLO)

Providers MUST NOT irresponsibly disclose specific sensitive details that would likely lead to exploitation. They MUST still disclose enough for informed risk-based decisions. (VER-RPT-NID)

Providers MAY disclose vulnerabilities publicly or to other parties if that will not likely lead to exploitation. (VER-RPT-RPD)

The artifact listed for the report rules is “A recent vulnerability report or a sample vulnerability report”. (VER-TFR-MHR, VER-RPT-VDT, VER-RPT-AVI)

FedRAMP MAY require additional information, alternative reports or a different reporting frequency as a condition of a Corrective Action Plan or other agreements. (VER-FRP-ARP)

Rule items and their JSON fields (VER-RPT-VDT)

Rule item Where it lands in the vulnerability detail JSON
1. Tracking identifier (VER-RPT-VDT) providerTrackingId
2. Time and source of detection (VER-RPT-VDT) detection.detectedAt, detection.detectionSource
3. Time of completed evaluation (VER-RPT-VDT) evaluationCompletedAt
4. Internet-reachable or not (VER-RPT-VDT) isInternetReachable
5. Likely exploitable or not (VER-RPT-VDT) isLikelyExploitable
6. Historical and current estimated N-rating (VER-RPT-VDT) currentRating, painReductionEvents
7. Time and rating of each completed reduction (VER-RPT-VDT) painReductionEvents[].reducedAt, .rating
8. Estimated time and target rating of next reduction (VER-RPT-VDT) projectedNextReduction
9. Overdue now or likely to become overdue, with explanation (VER-RPT-VDT) overdueStatus
10. Supplementary information (VER-RPT-VDT) supplementaryRiskInformation
11. Final disposition (VER-RPT-VDT) finalDisposition

The rule says these are required “if applicable”, except for accepted vulnerabilities. (VER-RPT-VDT)

Vulnerability detail report (JSON)

Top-level fields (schema: vulnerability detail report; rules VER-RPT-VDT, VER-RPT-PER):

Field Required Meaning
certificationPackageOverviewUri Required Full URI of the provider’s Certification Package Overview
reportPeriod Required Period the report covers; must cover all activity since the previous report (VER-RPT-PER)
reportPeriod.from, reportPeriod.to Required Start and end date-times
vulnerabilities Required List of non-accepted vulnerabilities with activity in the period

Each item in vulnerabilities (schema: common definitions, vulnerabilityDetail):

Field Required Meaning Rule
providerTrackingId Required Provider’s own identifier VER-RPT-VDT item 1
detection.detectedAt Required When it was detected VER-RPT-VDT item 2
detection.detectionSource Required Tool or activity that found it VER-RPT-VDT item 2
vulnerabilityDescription Required Description of the vulnerability Schema only; not in the VER-RPT-VDT list
potentialAgencyImpact Optional Text description of the potential impact Schema only; item 6 asks for a rating
evaluationCompletedAt Optional When evaluation finished; the 192-day clock runs from it VER-RPT-VDT item 3; VER-TFR-MAV
isInternetReachable Optional Internet-reachable (true) or not (false) VER-RPT-VDT item 4; VER-EVA-EIR
isLikelyExploitable Optional Likely exploitable (true) or not VER-RPT-VDT item 5; VER-EVA-ELX; VER-EVA-AIA
currentRating Optional Current N-rating, integer 0 to 5 VER-RPT-VDT item 6; VER-EVA-EPA
projectedNextReduction.estimatedAt Required if the object is present When the next reduction is expected VER-RPT-VDT item 8
projectedNextReduction.targetRating Required if the object is present Rating after that reduction, 0 to 5 VER-RPT-VDT item 8
overdueStatus.isOverdue Required if the object is present True if overdue VER-RPT-VDT item 9
overdueStatus.explanation Required when isOverdue is true, otherwise optional Reason for the overdue status VER-RPT-VDT item 9
supplementaryRiskInformation Optional Extra information to help agencies assess risk VER-RPT-VDT item 10; VER-RPT-NID
painReductionEvents[].reducedAt Required if an event is present When a reduction was completed VER-RPT-VDT item 7
painReductionEvents[].rating Required if an event is present Rating after the reduction, 0 to 5 VER-RPT-VDT item 7
finalDisposition Optional; omit if still active One of “Fully Mitigated”, “Partially Mitigated”, “Remediated”, “False Positive” VER-RPT-VDT item 11

projectedNextReduction is to be omitted if the vulnerability is fully mitigated or none is planned. (schema: projectedNextReduction)

Accepted vulnerability info (JSON)

Top-level fields (schema: accepted vulnerability info; rule VER-RPT-AVI):

Field Required Meaning
certificationPackageOverviewUri Required As above
reportPeriod (from, to) Required As above
acceptedVulnerabilities Required List of accepted vulnerabilities with activity in the period

Each item in acceptedVulnerabilities:

Field Required Meaning Rule
vulnerabilityDetail Required The same object as one item above, with the same required and optional fields VER-RPT-AVI items 1 to 5, 6, 8
acceptanceRationale Required Why this is an accepted vulnerability VER-RPT-AVI item 7

Historical activity (JSON)

Fields (schema: historical activity; rule VER-TFR-MRH):

Field Required Meaning
certificationPackageOverviewUri Required Full URI of the Certification Package Overview
generatedAt Required When the snapshot was generated
activeVulnerabilities Required All non-accepted vulnerabilities; each follows the VER-RPT-VDT fields
acceptedVulnerabilities Required All accepted vulnerabilities; each follows the VER-RPT-AVI fields

Example files (invented data)

All values below are invented. Tracking IDs, URLs and dates are placeholders.

Vulnerability detail report

{
  "certificationPackageOverviewUri": "https://example.com/trust/package-overview.json",
  "reportPeriod": {
    "from": "2027-01-01T00:00:00Z",
    "to": "2027-01-31T23:59:59Z"
  },
  "vulnerabilities": [
    {
      "providerTrackingId": "DEMO-001",
      "detection": {
        "detectedAt": "2027-01-05T09:30:00Z",
        "detectionSource": "Example scanner A"
      },
      "vulnerabilityDescription": "Invented flaw in a file-parsing library used by the upload service.",
      "potentialAgencyImpact": "Invented: disruption of uploads for one agency.",
      "evaluationCompletedAt": "2027-01-06T14:00:00Z",
      "isInternetReachable": true,
      "isLikelyExploitable": true,
      "currentRating": 3,
      "painReductionEvents": [
        { "reducedAt": "2027-01-12T10:00:00Z", "rating": 3 }
      ],
      "projectedNextReduction": {
        "estimatedAt": "2027-02-10T00:00:00Z",
        "targetRating": 1
      },
      "overdueStatus": {
        "isOverdue": true,
        "explanation": "Invented: the vendor patch is delayed."
      },
      "supplementaryRiskInformation": "Invented: a filter in front of the service blocks known triggering payloads."
    },
    {
      "providerTrackingId": "DEMO-002",
      "detection": {
        "detectedAt": "2027-01-08T11:00:00Z",
        "detectionSource": "Example penetration test"
      },
      "vulnerabilityDescription": "Invented flaw in an internal reporting tool.",
      "evaluationCompletedAt": "2027-01-09T16:00:00Z",
      "isInternetReachable": false,
      "isLikelyExploitable": false,
      "currentRating": 0,
      "overdueStatus": { "isOverdue": false },
      "finalDisposition": "Remediated"
    }
  ]
}

Accepted vulnerability info

{
  "certificationPackageOverviewUri": "https://example.com/trust/package-overview.json",
  "reportPeriod": {
    "from": "2027-01-01T00:00:00Z",
    "to": "2027-01-31T23:59:59Z"
  },
  "acceptedVulnerabilities": [
    {
      "vulnerabilityDetail": {
        "providerTrackingId": "DEMO-003",
        "detection": {
          "detectedAt": "2026-06-20T08:00:00Z",
          "detectionSource": "Example scanner B"
        },
        "vulnerabilityDescription": "Invented flaw in a legacy component that will not be fully mitigated.",
        "evaluationCompletedAt": "2026-06-22T12:00:00Z",
        "isInternetReachable": false,
        "isLikelyExploitable": false,
        "currentRating": 2
      },
      "acceptanceRationale": "Invented: the component cannot be replaced within 192 days of evaluation."
    }
  ]
}

Historical activity

{
  "certificationPackageOverviewUri": "https://example.com/trust/package-overview.json",
  "generatedAt": "2027-02-01T00:00:00Z",
  "activeVulnerabilities": [
    {
      "providerTrackingId": "DEMO-001",
      "detection": {
        "detectedAt": "2027-01-05T09:30:00Z",
        "detectionSource": "Example scanner A"
      },
      "vulnerabilityDescription": "Invented flaw in a file-parsing library used by the upload service.",
      "evaluationCompletedAt": "2027-01-06T14:00:00Z",
      "isInternetReachable": true,
      "isLikelyExploitable": true,
      "currentRating": 3,
      "painReductionEvents": [
        { "reducedAt": "2027-01-12T10:00:00Z", "rating": 3 }
      ],
      "overdueStatus": {
        "isOverdue": true,
        "explanation": "Invented: the vendor patch is delayed."
      }
    }
  ],
  "acceptedVulnerabilities": [
    {
      "vulnerabilityDetail": {
        "providerTrackingId": "DEMO-003",
        "detection": {
          "detectedAt": "2026-06-20T08:00:00Z",
          "detectionSource": "Example scanner B"
        },
        "vulnerabilityDescription": "Invented flaw in a legacy component that will not be fully mitigated.",
        "currentRating": 2
      },
      "acceptanceRationale": "Invented: the component cannot be replaced within 192 days of evaluation."
    }
  ]
}

Open points in the sources

  • The schema comment on supplementaryRiskInformation cites “VER-RPT-VDT field 11”, but supplementary information is the tenth item in the rule’s list. The eleventh is final disposition. (schema: supplementaryRiskInformation; VER-RPT-VDT)
  • vulnerabilityDescription is required by the schema but is not in the VER-RPT-VDT or VER-RPT-AVI lists. (schema: vulnerabilityDetail)
  • Schema potentialAgencyImpact is a text field, while rule item 6 asks for a rating. (schema; VER-RPT-VDT)
  • The accepted-vulnerability item reuses the whole detail object, although VER-RPT-VDT excludes accepted vulnerabilities from its list. (schema: acceptedVulnerabilityInfo; VER-RPT-VDT)