# KSI-SCR-MON — Monitoring Supply Chain Risk

> FedRAMP Consolidated Rules for 2026 v2026.07.14.01 · updated 2026-07-14
> Canonical page: /ksi/ksi-scr-mon

Theme: Supply Chain Risk (`SCR`)

## Statement

Third party software information resources are automatically monitored for upstream vulnerabilities using mechanisms that may include contractual notification requirements or active monitoring services.

## NIST 800-53 controls it reaches (10)

- `AC-20` (AC) — baselines B, C, D
- `CA-03` (CA) — baselines B, C, D
- `IR-06 (03)` (IR) — baselines C, D
- `PS-07` (PS) — baselines B, C, D
- `RA-05` (RA) — baselines B, C, D
- `SA-09` (SA) — baselines B, C, D
- `SI-05` (SI) — baselines B, C, D
- `SR-05` (SR) — baselines B, C, D
- `SR-06` (SR) — baselines C, D
- `SR-08` (SR) — baselines B, C, D

## Defined terms

- **Information Resource** — Has the meaning from 44 USC § 3502 (6): "information and related resources, such as personnel, equipment, funds, and information technology." This includes any aspect of the cloud service offering, both technical and managerial, including everything that makes up the business of the offering from non-machine-based information resources like organizational policies, procedures, employees, etc. to machine-based information resources like hardware, software, cloud services, code, etc.
- **Vulnerability** — Has the meaning given to "security vulnerability" in 6 USC § 650 (25), which is "any attribute of hardware, software, process, or procedure that could enable or facilitate the defeat of [...] management, operational, and technical controls used to protect against an unauthorized effort to adversely affect the confidentiality, integrity, and availability of an information system or its information." This includes gaps in Rev5 Controls and 20x Key Security Indicators, software vulnerabilities, misconfigurations, exposures, weak credentials, insecure services, and all other such potential weaknesses in protection (intentional or unintentional).

## Default artifacts owed by every indicator

- Explanation of measures (and their objectives) that demonstrate the Key Security Indicator, or an explanation of the reason and resulting risk to customers for not having measures available for that Key Security Indicator.
- Explanation of the cycle for any measures that are implemented persistently (if applicable).
- Verification that the measures demonstrate the Key Security Indicator, or that the reason for not having them is accepted.
- Verification that the automation in place is accurate and sufficient to demonstrate appropriate measures for the Key Security Indicator, or that automation is not necessary for each measure.
- Validation that the measures are accurately produced and are in place and working as intended, or that the reason for not having them is valid.