# KSI-CED-RAT — Reviewing All Training

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

Theme: Cybersecurity Education (`CED`)

## Statement

The effectiveness of relevant cybersecurity education and training is persistently reviewed, including at least general training for all employees, role-specific training for employees in high risk roles, training for development and engineering staff on secure software delivery, and training for staff involved with incident response or disaster recovery.

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

- `AT-02` (AT) — baselines B, C, D
- `AT-02 (02)` (AT) — baselines B, C, D
- `AT-02 (03)` (AT) — baselines C, D
- `AT-03` (AT) — baselines B, C, D
- `AT-03 (05)` (AT) — in no class baseline
- `AT-04` (AT) — baselines B, C, D
- `CP-03` (CP) — baselines B, C, D
- `IR-02` (IR) — baselines B, C, D
- `IR-02 (03)` (IR) — in no class baseline
- `PS-06` (PS) — baselines B, C, D
- `SR-11 (01)` (SR) — baselines B, C, D

## Defined terms

- **Incident** — Has the meaning given in 44 USC § 3552 (b)(2) which is "an occurrence that (A) actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system; or (B) constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies."
- **Persistently** — Occurring in a firm, steady way that is repeated over a long period of time in spite of obstacles or difficulties. Persistent activities may vary between actors, may occur irregularly, and may include interruptions or waiting periods between cycles. These attributes of persistent activities should be intentional, understood, and documented; the status of persistent activities will always be known.
- **Vulnerability Response** — The systematic process of tracking, evaluating, mitigating, monitoring, remediating, assessing exploitation, reporting, and otherwise managing detected vulnerabilities.

## 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.