# SC-28 Protection of Information at Rest

NIST SP 800-53 control. Family: SC System and Communications Protection. Function: preventative. Baselines: moderate, high. Mapping licence: CC BY-SA 4.0.

Statement: Protect the [Selection (one or more): confidentiality; integrity] of the following information at rest: [Assignment: organization-defined information at rest].
Guidance: Information at rest refers to the state of information when it is not in process or in transit and is located on system components. Such components include internal or external hard disk drives, storage area network devices, or databases. However, the focus of protecting information at rest is not on the type of storage device or frequency of access but rather on the state of the information. Information at rest addresses the confidentiality and integrity of information and covers user information and system information. System-related information that requires protection includes configurations or rule sets for firewalls, intrusion detection and prevention systems, filtering routers, and authentication information. Organizations may employ different mechanisms to achieve confidentiality and integrity protections, including the use of cryptographic mechanisms and file share scanning. Integrity protection can be achieved, for example, by implementing write-once-read-many (WORM) technologies. When adequate protection of information at rest cannot otherwise be achieved, organizations may employ other controls, including frequent scanning to identify malicious code at rest and secure offline storage in lieu of online storage.

## Enhancements (3)
- SC-28(01) Cryptographic Protection. Baselines: moderate, high
- SC-28(02) Offline Storage
- SC-28(03) Cryptographic Keys
Each enhancement's statement: /api/v1/controls/SC-28?fields=enhancements

## Patterns that use it (16)
- Critical (7): SP-015 Secure Remote Working; SP-037 Privileged User Management; SP-039 Client-Side Encryption and Data Privacy; SP-050 Mobile Security Architecture (draft); SP-051 Tokenised Asset Security Architecture (draft); SP-053 Zero-Knowledge Proof Architecture (draft); SP-054 CBDC and Digital Currency Infrastructure (draft)
- Important (8): SP-028 Secure DevOps Pipeline Pattern; SP-029 Zero Trust Architecture; SP-034 Cyber Resilience; SP-040 Post-Quantum Cryptography and Quantum Readiness; SP-042 Third Party Risk Management; SP-047 Secure Agentic AI Frameworks; SP-049 AI in Security Operations (draft); SP-052 Decentralised Identity & Verifiable Credentials (draft)
- Standard (1): SP-030 API Security

## Clauses by framework (74 frameworks)
- iso_27001_2022: A.5.10, A.5.33, A.7.9, A.8.1, A.8.24. OSA's own, not in NIST's crosswalk: A.7.9, A.8.1, A.8.24
- iso_27002_2022: 6.7, 7.9, 8.1, 8.11, 8.24
- cobit_2019: APO14
- pci_dss_v4: 3.1, 3.3, 3.5
- nist_csf_2: PR.DS-01
- cis_controls_v8: CIS 3, CIS 3.6, CIS 3.9, CIS 3.11, CIS 4, CIS 11.3
- finos_ccc: CCC-C02
- iec_62443: 3-3 SR 4.1
- nis2: Art. 21(2)(h)
- apra_cps_234: Para 22-23
- mas_trm: 10, 15
- pra_op_resilience: SS2/21-11.1
- bsi_grundschutz: CON.1, CON.7, OPS.1.2.4, SYS.2.1
- anssi: Hygiene.19
- gdpr: Art.5(1)(f), Art.32(1)(a), Rec.83
- dora: Art.9(3)
- bio2: 6.7, 7.9, 8.1, 8.11, 8.24
- rbi_csf: Annex1.15, ITGRCA.16
- fisc: FISC.T4, FISC.T5
- lgpd_bcb: BCB.Art.3, LGPD.Art.11, LGPD.Art.46
- hkma_tme1: TME1.9.1, TME1.9.2, TME1.10.2, TME1.10.3, TME1.11.2, TME1.12.4
- mlps_2: 8.1.4.7, 8.1.4.8, 8.2
- dnb_good_practice: DNB.12.3
- cra: CRA.I.2b, CRA.I.2e
- swift_cscf: SWIFT.1.3, SWIFT.2.5A, SWIFT.5.4, SWIFT.6.3
- cbb_tm: TM-9
- cbuae: CR-5, CR-8
- nca_ecc: 2-3, 2-6, 2-7, 2-8, 4-2
- qatar_nia: CS
- sama_csf: 3.4, 4.3
- uae_ia: T4, T8
- bog_cisd: CISD-V, CISD-VI, CISD-XII
- bom_ctrm: 3.4, 3.10, 3.12
- cbe_csf: CTO-2, CTO-3
- cbn_csf: Part3.3, Part3.4
- popia: s19
- sa_js2: JS2-8.2, JS2-8.3
- bcbs_239: Principle 2, Principle 3
- bot_cyber: Ch2.3, Ch2.7
- cpmi_pfmi: CG.PR, PFMI.P17
- eba_ict: 3.4.4
- ecb_croe: CROE.2.2.2, CROE.2.3.3
- ffiec_is: II.C.13, II.C.13(a), II.C.18, II.C.19
- hipaa_sr: §164.310(c), §164.310(d)(2)(iv), §164.312(a)(1), §164.312(a)(2)(iv), §164.312(c)(1), §164.312(c)(2)
- iosco_cyber: PROT-3
- nydfs_500: 500.15
- sebi_cscrf: DATALOC, PR.CS, PR.DS
- cmmc_2: MP, SC
- nerc_cip: CIP-011-3
- nrc_73_54: 73.54(c)(1), RG5.71-A-SC
- api_1164: Sec 8
- pci_pts: C
- fips_140: FIPS 140-3 §7.8, FIPS 140-3 §7.9
- cbest: CBEST.9
- tiber_eu: TIBER.CONF
- common_criteria: CC Part 2 — FCS
- isae_3402: Clause 4
- fca_sysc_13: SYSC 13.7.3
- fda_21_cfr_11: §11.10(b), §11.10(c), §11.70
- fda_cyber: SA-2, SA-4
- hitrust_csf: 01.d, 09.f, 10.c, 13.e
- iso_27799: 6.3, 10.1, 12.3, H.4
- naic_ds: 4-encryption, 4B
- nhs_dspt: NDG-1.1, NDG-9.6, NDG-9.7
- pra_ss1_23: P-IT.3
- solvency_ii: Art.49(3), DR.266-DataSec, EIOPA-Cloud-GL9, EIOPA-ICT-4.7
- owasp_masvs_v2: MASVS-STORAGE-1, MASVS-STORAGE-2
- csa_ccm_v4: CEK-03, DSP-07, DSP-17, UEM-08
- csa_aicm: CEK-03, DSP-07, DSP-17, UEM-08
- ccss_v9: 1.01.1, 1.01.4, 1.03.1, 1.03.6, 1.05.5
- mica: Art.40(1), Art.55(1), Art.62(9), Art.63(1), Art.67(1), Art.97(1), Art.98(1)
- bssc: GSP-09, GSP-13
- sec_custody_digital: SEC-CD-08
- dpdpa: Act.8(5), Rules.6(1)(a), Rules.Sch1.B.7, Rules.Sch2
OSA's mapping for iso_27001_2022 and nist_csf_2 takes NIST's published crosswalk as its base. A clause not marked as OSA's own is in that crosswalk.

## More
- This control as JSON, with guidance and ATT&CK techniques: /api/v1/controls/SC-28
- Clauses only: /api/v1/controls/SC-28?fields=mappings
- Page for people: /controls/sc-28/
- Found an error? Open an issue at https://github.com/opensecurityarchitecture/osa-data/issues with the id, what OSA says and what the source says.