Skip to content

Keyboard shortcuts

Go

  • Scope — the control cataloggm
  • Plan — your last certification classgp
  • Collect — the recipe indexgc
  • The control you are workinggw
  • Startgh

Move

  • Next rowj
  • Previous rowk
  • Previous in this run[
  • Next in this run]
  • Filter this page's list/
  • Search everythingK

Act

  • Copy this page's permalinky
  • Toggle dark moded
  • This sheet?

Rows are whatever the current page lists — controls on Scope, recipes on Plan and Collect.

Control index

Whether an AWS call fetches evidence for this control, and what to run. Its Rev5 baselines, the indicators that reach it and the FedRAMP guidance attached to it open below.

No AWS API proves itA Key Security Indicator reaches RA-05 (11) and no AWS API decides it. This project has assessed it and closed it: the evidence is a document a person writes and an assessor reads, not telemetry. The reason is below.

Collect evidence (0)

Authored AWS and pipeline recipes whose output is evidence for RA-05 (11). This mapping is this project’s opinion (AWS overlay v3.0.0, pipeline overlay v0.8.0), versioned separately from the dataset — the upstream FedRAMP rules name none of these tools.

AssessedNo AWS API proves RA-05 (11).

A public disclosure program is a published intake channel and a commitment to act on what arrives through it. A 3PAO reads the published policy, the disclosure page or security.txt, and the history of reports received and resolved; no AWS call reports that a reporting channel exists, let alone that anyone answered it.

This project’s assessment (automation register v0.9.0, reviewed 2026-08-11), versioned separately from the dataset and from the evidence overlays. It is an opinion about the AWS surface on that date, and the surface moves.

No recipe reaches it through its indicators either. The KSI that reaches it is KSI-PIY-RVD — which is what asks for it. The evidence it asks for is written, not fetched. Browse /collect for the whole authored corpus.

What NIST requires of RA-05 (11)

The control statement from NIST 800-53 Rev5, verbatim. Square brackets are organization-defined parameters — yours to set, not FedRAMP's to dictate.

Establish a public reporting channel for receiving reports of vulnerabilities in organizational systems and system components.

NIST SP 800-53 Rev5 catalog 5.2.0, from usnistgov/oscal-content at 78650f0. The FedRAMP dataset carries no control text; this is borrowed and pinned.

Rev5 baseline membership

Membership is the whole relationship — a baseline is a set of control ids. Class A carries no baseline at all. The Low/Moderate/High labels are an interpretation from control counts, not a dataset fact.

Class Bour reading: Rev5 Low
in baseline
Class B readiness
Class Cour reading: Rev5 Moderate
in baseline
Class C readiness
Class Dour reading: Rev5 High
in baseline
Class D readiness

KSI indicators reaching this control (1)

Under 20x, these indicators are how this control is demonstrated — automated KSI evidence stands in for narrative control evidence.

FedRAMP guidance & parameters

Where you read the rule. Guidance names an FRR document, never a clause, so the links below offer the whole document and leave the reading to you.

Pages exist for the 209 controls reached by at least one KSI. Baseline-only controls are the orphans on /coverage. Control titles and full text live in the NIST catalog, not this dataset.