IR-03 (02) Coordination with Related Plansir-3.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 IR-03 (02). 1 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 IR-03 (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 IR-03 (02). The nearest authored work is below.
Nobody has assessed IR-03 (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 KSIs that reach it are KSI-PIY-RIS, KSI-RPL-TRC — that is where the authoring would land. Browse /collect for the whole authored corpus.
Reaches the same indicator, not IR-03 (02)
These recipes prove a KSI that reaches it. None of them claims IR-03 (02) — treat them as neighbours worth reading, not as coverage.
What NIST requires of IR-03 (02)
The control statement from NIST 800-53 Rev5, verbatim. Square brackets are organization-defined parameters — yours to set, not FedRAMP's to dictate.
Coordinate incident response testing with organizational elements responsible for related plans.
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 (2)
Under 20x, these indicators are how this control is demonstrated — automated KSI evidence stands in for narrative control evidence.
- PIYKSI-PIY-RISReviewing Investments in Security
The effectiveness of the provider's investments in achieving security goals is persistently reviewed.
- RPLKSI-RPL-TRCTesting Recovery Capabilities
The capability to recover from incidents and contingencies aligned with defined recovery objectives is persistently tested.
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 Incident Evaluation and Communication rules.This guidance points at the Incident Evaluation and Communication rules (IEC, 8 requirements).
All 8 IEC 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.