Skip to content
FedRAMP Rules Hub
JSON — GET /api/baseline

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 everything⌘K

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

SI-04 System Monitoringsi-4

JSON — GET /api/baselineMD — /control/si-4.md — this page as markdown, for pasting into an agent

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.

Partial1 of 1 recipe reaches SI-04, and none is rated full — the output narrows the question, a human judgement closes it.

AWS Config · Amazon GuardDuty · AWS Security Hub1 recipe · 7 calls

The calls

Collect evidence (1)

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

What NIST requires of SI-04

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

a. Monitor the system to detect: 1. Attacks and indicators of potential attacks in accordance with the following monitoring objectives: [monitoring objectives]; and 2. Unauthorized local, network, and remote connections; b. Identify unauthorized use of the system through the following techniques and methods: [techniques and methods]; c. Invoke internal monitoring capabilities or deploy monitoring devices: 1. Strategically within the system to collect organization-determined essential information; and 2. At ad hoc locations within the system to track specific types of transactions of interest to the organization; d. Analyze detected events and anomalies; e. Adjust the level of system monitoring activity when there is a change in risk to organizational operations and assets, individuals, other organizations, or the Nation; f. Obtain legal opinion regarding system monitoring activities; and g. Provide [system monitoring information] to [personnel or roles] [assignment].

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 (2)

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.