# RA-03 Risk Assessment

NIST SP 800-53 control. Family: RA Risk Assessment. Function: detective. Baselines: low, moderate, high, privacy. Mapping licence: CC BY-SA 4.0.

Statement: a. Conduct a risk assessment, including: 1. Identifying threats to and vulnerabilities in the system; 2. Determining the likelihood and magnitude of harm from unauthorized access, use, disclosure, disruption, modification, or destruction of the system, the information it processes, stores, or transmits, and any related information; and 3. Determining the likelihood and impact of adverse effects on individuals arising from the processing of personally identifiable information; b. Integrate risk assessment results and risk management decisions from the organization and mission or business process perspectives with system-level risk assessments; c. Document risk assessment results in [Selection (one): security and privacy plans; risk assessment report; [Assignment: organization-defined document]]; d. Review risk assessment results [Assignment: organization-defined frequency]; e. Disseminate risk assessment results to [Assignment: organization-defined personnel or roles]; and f. Update the risk assessment [Assignment: organization-defined frequency] or when there are significant changes to the system, its environment of operation, or other conditions that may impact the security or privacy state of the system.
Guidance: Risk assessments consider threats, vulnerabilities, likelihood, and impact to organizational operations and assets, individuals, other organizations, and the Nation. Risk assessments also consider risk from external parties, including contractors who operate systems on behalf of the organization, individuals who access organizational systems, service providers, and outsourcing entities. Organizations can conduct risk assessments at all three levels in the risk management hierarchy (i.e., organization level, mission/business process level, or information system level) and at any stage in the system development life cycle. Risk assessments can also be conducted at various steps in the Risk Management Framework, including preparation, categorization, control selection, control implementation, control assessment, authorization, and control monitoring. Risk assessment is an ongoing activity carried out throughout the system development life cycle. Risk assessments can also address information related to the system, including system design, the intended use of the system, testing results, and supply chain-related information or artifacts. Risk assessments can play an important role in control selection processes, particularly during the application of tailoring guidance and in the earliest phases of capability determination.

## Enhancements (4)
- RA-03(01) Supply Chain Risk Assessment. Baselines: low, moderate, high
- RA-03(02) Use of All-source Intelligence
- RA-03(03) Dynamic Threat Awareness
- RA-03(04) Predictive Cyber Analytics
Each enhancement's statement: /api/v1/controls/RA-03?fields=enhancements

## Patterns that use it (32)
- Critical (7): SP-018 Information Security Management System; SP-035 Offensive Security Testing; SP-038 Vulnerability Management and Patching; SP-045 AI Governance and Responsible AI; SP-046 External Attack Surface Management; SP-051 Tokenised Asset Security Architecture (draft); SP-054 CBDC and Digital Currency Infrastructure (draft)
- Important (25): SP-001 Client Module; SP-002 Server Module; SP-008 Public Web Server Pattern; SP-011 Cloud Computing Pattern; SP-012 Secure Software Development Lifecycle; SP-013 Data Security Pattern; SP-014 Awareness and Training Pattern; SP-017 Secure Network Zone Module; SP-019 Secure Ad-Hoc File Exchange Pattern; SP-021 Realtime Collaboration Pattern; SP-023 Industrial Control Systems; SP-025 Advanced Monitoring and Detection; SP-026 PCI Full Environment; SP-028 Secure DevOps Pipeline Pattern; SP-029 Zero Trust Architecture; SP-030 API Security; SP-031 Security Monitoring and Response; SP-034 Cyber Resilience; SP-042 Third Party Risk Management; SP-043 Security Metrics and Measurement; SP-047 Secure Agentic AI Frameworks; SP-048 Offensive AI and Deepfake Defence (draft); SP-049 AI in Security Operations (draft); SP-052 Decentralised Identity & Verifiable Credentials (draft); SP-053 Zero-Knowledge Proof Architecture (draft)

## Clauses by framework (77 frameworks)
- iso_27001_2022: 4.1, 6.1, 6.1.3, 8.2, 8.3, 9.3, A.5.7, A.8.8. OSA's own, not in NIST's crosswalk: 4.1, 6.1.3, 8.3, A.5.7
- iso_27002_2022: 5.7
- cobit_2019: APO12, APO13, EDM03
- pci_dss_v4: 12.3
- nist_csf_2: DE.AE-04, DE.AE-07, GV.OV-02, GV.RM-04, GV.RM-06, GV.RM-07, GV.SC-03, GV.SC-07, GV.SC-09, GV.SC-10, ID.AM-05, ID.IM-01, ID.IM-02, ID.IM-03, ID.RA-01, ID.RA-03, ID.RA-04, ID.RA-05, ID.RA-06, RS.AN-08. OSA's own, not in NIST's crosswalk: DE.AE-04, GV.OV-02, GV.RM-04, GV.SC-07, ID.RA-06
- cis_controls_v8: CIS 16.6, CIS 16.14
- soc2_tsc: A1.2, CC3.2-POF1, CC3.4-POF1, CC3.4-POF2, CC3.4-POF3, CC4.1, CC7.3
- iso_42001_2023: A.5.2, A.5.3, A.5.4, A.5.5
- iec_62443: 2-1 4.3, 2-1 4.4
- nis2: Art. 21(2)(a)
- mas_trm: 4
- pra_op_resilience: SS1/21-4.1, SS1/21-6.1, SS1/21-10.1, SS2/21-4.1, SS2/21-5.1, SS2/21-16.1
- anssi: Hygiene.41, RGS.3.1, SecNumCloud.7.2
- osfi_b13: B-13.1.3, B-13.3.1
- finma_circular: IV.B.c(54), IV.B.c(55), IV.B.c(56), IV.B.c(57), IV.B.d(58)
- gdpr: Art.32(1), Art.35(1), Art.35(7)(c)
- dora: Art.6(2), Art.6(5)
- bio2: 5.7
- rbi_csf: ITGRCA.22, ITGRCA.25
- fisc: FISC.O1
- lgpd_bcb: BCB.Art.3-Supp, BCB.Art.12, BCB.Art.18, LGPD.Art.10, LGPD.Art.37-38, LGPD.BCB.Integration
- hkma_tme1: TME1.2.3, TME1.12.1
- mlps_2: 8.1.9.2, 8.1.10.3
- dnb_good_practice: DNB.3.1, DNB.4.1, DNB.4.2, DNB.10.2
- cra: CRA.Info.5
- swift_cscf: SWIFT.7.4A
- cbb_tm: TM-4, TM-15
- cbuae: CR-2
- nca_ecc: 1-5, 2-13, 5-1
- qatar_nia: RM
- sama_csf: 1.8
- uae_ia: T2
- bog_cisd: CISD-III, CISD-ISMS
- bom_ctrm: 1.4, 2.1, 4.1
- cbe_csf: CD-1, CRM-1
- cbn_csf: Part2.1, Part2.2, Part4, Part5.1
- popia: s19
- sa_js2: JS2-5, JS2-6.2, JS2-7.6
- bcbs_239: Principle 1, Principle 6, Principle 8
- bot_cyber: Ch1.2, Ch8.1
- cpmi_pfmi: CG.ID, CG.SA, PFMI.P3, PFMI.P15, PFMI.P17
- eba_ict: 3.3.3, 3.3.5, 3.7.1
- ecb_croe: CROE.2.2.1, CROE.2.7.1, CROE.2.8.2
- ffiec_is: II.A, II.A.1, II.B, II.D, III.A
- hipaa_sr: §164.308(a)(1)(i), §164.308(a)(1)(ii)(A), §164.308(a)(1)(ii)(B), §164.308(a)(8)
- iosco_cyber: GOV-3, ID-3, PFMI-3, RR-5, SA-1
- nydfs_500: 500.2, 500.9
- sebi_cscrf: GV.RM, ID.RA
- cmmc_2: RA
- nerc_cip: CIP-002-7, CIP-014-3
- nrc_73_54: RG5.71-C-PL
- tsa_psd: SD-1 Sec 3
- doe_c2m2: RISK, THREAT
- api_1164: Sec 4
- awia: Sec 2013(a)
- iaea_nss: Sec 4
- fips_140: FIPS 140-3 §7.8, FIPS 140-3 §7.12
- cbest: CBEST.2
- tiber_eu: TIBER.GTL, TIBER.TTI
- isae_3402: Clause 1, Clause 3
- fca_sysc_13: SYSC 13.1-2, SYSC 13.5.2, SYSC 13.5.3, SYSC 13.8.4, SYSC 13.G.2
- fda_21_cfr_11: §11.2
- fda_cyber: 524B-4, CRA-1, CRA-2, CRA-3, INC-2, MON-2, SPDF-2, TM-1, TM-2, TM-3, TR-2, VR-1
- hitrust_csf: 00.b, 03.a
- iso_27799: H.1
- lloyds_ms: CRM.2, MS8.11, MS10.1, MS10.2
- naic_ds: 4, 4A, 4E
- nhs_dspt: NDG-5.2
- pra_ss1_23: P1.2, P3.5, P5.1, P5.4
- solvency_ii: Art.44(1), Art.44(2), Art.45, DR.260, DR.266, DR.267, EIOPA-Cloud-GL3, EIOPA-ICT-4.2
- csa_ccm_v4: AA-03, BCR-02, CEK-06, CEK-07, DSP-09, GRC-02, STA-08, STA-14, TVM-08
- csa_aicm: A&A-03, BCR-02, CEK-06, CEK-07, DSP-09, DSP-21, GRC-02, GRC-11, GRC-14, MDS-12, MDS-13, STA-08, STA-14, TVM-08, TVM-11
- mica: Art.34(5), Art.35(1), Art.41(1), Art.47(1), Art.62(1), Art.66(1)
- basel_sco60: SCO60.1, SCO60.3, SCO60.4, SCO60.5, SCO60.13, SCO60.14, SCO60.21, SCO60.41, SCO60.50, SCO60.54, SCO60.74, SCO60.83, SCO60.84, SCO60.85
- bssc: GSP-02, TIS-01, TIS-04, TIS-05, TIS-06
- sec_custody_digital: SEC-CD-08, SEC-CD-09, SEC-CD-12, SEC-CD-18
- dpdpa: Act.8(5), Act.9(2), Act.10(2)(c), Rules.13(1)-(2), Rules.13(3), Rules.Sch1.B.7
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/RA-03
- Clauses only: /api/v1/controls/RA-03?fields=mappings
- Page for people: /controls/ra-03/
- 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.