SC-28 (01) Cryptographic Protectionsc-28.1
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 SC-28 (01). 7 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 SC-28 (01). 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 SC-28 (01). The nearest authored work is below.
Key-backed encryption is readable: ENCRYPTED_VOLUMES and RDS_STORAGE_ENCRYPTED take a kmsId/kmsKeyId parameter, and GetBucketEncryption returns the SSEAlgorithm and key. The information this enhancement protects is an SSP list, and which key ownership counts as the organization's is a policy. Dropped from config-encryption-at-rest on 2026-08-26, where no key was asserted and the S3 rule could not fail.
A recipe would call:
This project’s assessment (automation register v0.9.0, reviewed 2026-08-26), 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 KSI that reaches it is KSI-SVC-SIN — that is where the authoring would land. Browse /collect for the whole authored corpus.
Reaches the same indicator, not SC-28 (01)
These recipes prove a KSI that reaches it. None of them claims SC-28 (01) — treat them as neighbours worth reading, not as coverage.
- AWS Config compliance results across the storage services proving customer data is encrypted at rest — S3 buckets with default server-side encryption, EBS volumes encrypted, and RDS storage encrypted, all backed by KMS via KSI-SVC-SIN
- AWS Config compliance results proving data in transit is protected by TLS — S3 bucket policies denying non-TLS requests, load-balancer listeners restricted to SSL/HTTPS, and Redshift clusters requiring SSL via KSI-SVC-SIN
- AWS Config compliance results proving KMS customer-managed keys are lifecycle-managed — automatic annual rotation enabled and no active key scheduled for deletion — the key-hygiene half of the cryptographic-protection control via KSI-SVC-SIN
- DNSSEC signing status of every public hosted zone, with the key-signing key state and the DS record that carries the chain of trust to the parent via KSI-SVC-SIN
- Per-VPC DNSSEC validation status of the Route 53 Resolver, joined against the full VPC inventory so that a VPC which never enabled validation is visible rather than absent via KSI-SVC-SIN
What NIST requires of SC-28 (01)
The control statement from NIST 800-53 Rev5, verbatim. Square brackets are organization-defined parameters — yours to set, not FedRAMP's to dictate.
Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of the following information at rest on [system components or media]: [information].
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.
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.