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.

CollectAWS overlay v3.0.0, pipeline overlay v0.8.0

Draw a controlOne numbered security requirement — AC-02, “account management” — from NIST SP 800-53, the catalogue FedRAMP draws its baselines from. family or a control id and this narrows to the AWS and pipeline calls that fetch its evidence, with one script for the whole scope. Every recipeThis product’s unit of collection, and its own coinage: an authored command, plus what one pass of it proves and how often to re-run it. carries the command, the cadenceHow often the rules require a piece of evidence to be refreshed. The clock on an obligation, not the command that satisfies it., and the indicators and controls a pass proves. The readings below count the whole Rev5 baselineThe set of controls one impact level requires. FedRAMP Rev5 publishes three, and which one binds you is the whole question of scope. union: what a recipe reaches, what only a Key Security Indicator (KSI)FedRAMP 20x’s unit of assurance: a question asked of the running system — “is MFA enforced?” — that a machine can answer, grouped into themes. reaches, and what is narrativeNo AWS or pipeline API answers this — it is a document you write. — a document somebody writes rather than a command anybody runs.

Corpusrecipes in the authored overlay

authored
64
automatable
0 of 64
partial
63 of 64
narrative
1 of 64

Authored opinion, versioned separately from the dataset. The upstream FedRAMP rules name no vendor and no product.

Every baselinecontrols in the Rev5 baseline union

have a recipe
94 of 409
KSI only, no recipe
105 of 409
orphan — narrative only
210 of 409

KSI only means no recipe fetches it — which is our backlog for some and a document you owe for others; the automation register says which. orphan is permanent — no telemetry will ever prove it. Same join as the catalog.

Control scope

94 / 409 controls across every Rev5 baseline have one — draw a family to scope the corpus to it

  • recipean authored recipe collects evidence for this control
  • KSI onlya Key Security Indicator reaches it, but no recipe is authored yet
  • orphanno Key Security Indicator reaches it — a person writes it up instead

The call

tool64 in the corpus
  • automatable
  • partial — needs judgement
  • narrative — no API proves this