SI-02 (02) Automated Flaw Remediation Statussi-2.2
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.
Nothing names itNo recipe names SI-02 (02). 4 reach an indicator it shares, which is adjacency and not coverage — worth reading, not worth recording as evidence for this control.
Collect evidence (0)
Authored AWS recipes whose output is evidence for SI-02 (02). 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.
No authored recipe names SI-02 (02). The nearest authored work is below.
Nobody has assessed SI-02 (02) against AWS and pipeline yet. That is a gap in this project’s research — not a finding about the control, and not a claim that nothing collects it.
The KSI that reaches it is KSI-SVC-EIS — that is where the authoring would land. Browse /collect for the whole authored corpus.
Reaches the same indicator, not SI-02 (02)
These recipes prove a KSI that reaches it. None of them claims SI-02 (02) — treat them as neighbours worth reading, not as coverage.
- AWS Config compliance results proving the network boundary is controlled — no security group exposes SSH to the internet, groups open to 0.0.0.0/0 only allow authorized ports, and every VPC's default security group denies all traffic via KSI-SVC-EIS
- AWS Config compliance results proving continuous security monitoring is switched on account-wide — GuardDuty threat detection enabled (optionally centralized to a delegated admin) and Security Hub aggregating control findings via KSI-SVC-EIS
- Config compliance results proving the ports you declared unnecessary are not reachable from the internet and the software you declared prohibited is not installed, plus the actual installed-application set a periodic review has to read via KSI-SVC-EIS
- A Region-by-Region inventory of the resources that can hold information, the classification tags you asserted on them, and — where Macie exists — a sampled machine judgement about which S3 buckets actually contain sensitive data via KSI-SVC-EIS
What NIST requires of SI-02 (02)
The control statement from NIST 800-53 Rev5, verbatim. Square brackets are organization-defined parameters — yours to set, not FedRAMP's to dictate.
Determine if system components have applicable security-relevant software and firmware updates installed using [automated mechanisms] [frequency].
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.
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.
- Follow the FedRAMP Vulnerability Detection and Response and Vulnerability Evaluation and Reporting rules.This guidance points at the Vulnerability Detection and Response rules (VDR, 18 requirements).This guidance points at the Vulnerability Evaluation and Reporting rules (VER, 23 requirements).
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.