SR-10 Inspection of Systems or Componentssr-10
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 SR-10. 9 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 SR-10. 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 SR-10. The nearest authored work is below.
Inspecting hardware for tampering is AWS's responsibility under the shared model, evidenced by its own authorization package rather than by anything you can call. The customer-side inspection — when components are examined, by whom, and what indication of need triggered it — is a documented procedure and its records, which is what a 3PAO reads.
This project’s assessment (automation register v0.9.0, reviewed 2026-08-04), 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.
The KSIs that reach it are KSI-SVC-ACM, KSI-SVC-EIS, KSI-SVC-VRI — which is what asks for it. The evidence it asks for is written, not fetched. Browse /collect for the whole authored corpus.
Reaches the same indicator, not SR-10
These recipes prove a KSI that reaches it. None of them claims SR-10 — treat them as neighbours worth reading, not as coverage.
- AWS Config compliance results plus the State Manager association list proving a defined configuration is actually applied and re-applied to every managed node — instances are under SSM management, and the associations that carry your baseline report COMPLIANT on a schedule rather than drifting via KSI-SVC-ACM
- The machine-maintained component inventory — Config's recorder status and discovered-resource counts proving supported resources are tracked continuously and the list stays current without anyone editing a spreadsheet, plus Systems Manager Inventory's node and installed-application metadata for what runs inside them via KSI-SVC-ACM
- 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
What NIST requires of SR-10
The control statement from NIST 800-53 Rev5, verbatim. Square brackets are organization-defined parameters — yours to set, not FedRAMP's to dictate.
Inspect the following systems or system components [assignment] to detect tampering: [systems or 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.
KSI indicators reaching this control (3)
Under 20x, these indicators are how this control is demonstrated — automated KSI evidence stands in for narrative control evidence.
- SVCKSI-SVC-ACMAutomating Configuration Management
The configuration of machine-based information resources is managed using automation and persistently reviewed for drift.
- SVCKSI-SVC-EISEvaluating and Improving Security
Information resources are persistently evaluated for opportunities to improve security and those improvements are persistently made.
- SVCKSI-SVC-VRIValidating Resource Integrity
Use cryptographic methods to validate the integrity of machine-based information resources.
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.