PRM-02: Strategic Plan & Objectives
Mechanisms exist to establish a: (1) Strategic security, compliance and resilience-specific business plan; and (2) Set of objectives to achieve that plan.
Renumbered: Formerly PRM-01.1 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, PRM-02 was Cybersecurity & Data Protection Resource Management. That control is now PRM-05.
Control Question: Does the organization establish a: (1) Strategic security, compliance and resilience-specific business plan; and (2) Set of objectives to achieve that plan?
General (8)
| Framework | Mapping Values |
|---|---|
| BSI Standard 200-1 | 4.1.2 7.0 |
| COBIT 2019 | APO01.01 APO01.02 APO01.03 APO02.02 APO02.05 APO02.06 BAI01.09 |
| ISO 22301 2019 | 6.2.1 |
| ISO 31000 2018 | 5.3 5.4.1 5.4.4 |
| ISO 42001 2023 | 4.1 4.2 |
| NIST AI 100-1 (AI RMF) 1.0 | MAP 1.3 |
| NIST 800-37 R2 | TASK P-8 |
| NIST CSF 2.0 (source) | GV GV.OC-04 GV.RM GV.OV-01 |
US (4)
| Framework | Mapping Values |
|---|---|
| USA Federal C2M2 2.1 | RISK-1a ARCHITECTURE-1a PROGRAM-1a PROGRAM-1b PROGRAM-1c PROGRAM-1d PROGRAM-1e |
| USA Federal CERT RMM 1.2 | EF:SG1 EF:SG1.SP1 EF:SG1.SP2 EF:SG2.SP1 |
| USA Federal FCA CRM 2023 | 609.935 609.935(a) |
| USA California CCPA 2025 | 7100(b) 7102(a) |
EMEA (11)
| Framework | Mapping Values |
|---|---|
| EMEA CHE FINMA Circular 2023/1 | IV.A-24 |
| EMEA Germany BAIT 2017 | 1.1 1.2 1.2(a) 1.2(b) 1.2(c) 1.2(d) 1.2(e) 1.2(f) |
| EMEA Germany C5 2026 | OIS-02.03B.4 SP-01.01B.5 |
| EMEA EU DORA 2023 | Article 6.8 Article 6.8(a) Article 6.8(b) Article 6.8(c) Article 6.8(d) Article 6.8(e) Article 6.8(f) Article 6.8(g) Article 6.8(h) |
| EMEA EU DORA RTS 2024 | Article 2.2(a) Article 3.1(f) |
| EMEA EU EBA GL/2019/04 | 3.2.1.4 3.2.2.5 3.2.2.5(a) 3.2.2.5(b) 3.2.2.5(c) 3.2.2.6 |
| EMEA Israel CDMO 2.0 | 2.A 4.1, Stage 4 4.2, Stage 1.2 |
| EMEA LUX CCSF 20/750 2020 | 3.2.1-4 3.2.2-5.a 3.2.2-5.b 3.2.2-5.c 3.2.2-6 |
| EMEA Saudi Arabia CSCC-1 2019 | 1-1-1 |
| EMEA Saudi Arabia ECC-1 2018 | 1-1-1 1-1-2 1-1-3 |
| EMEA Saudi Arabia SAMA CSF 1.0 2017 | 3.1.2 3.1.2.1 3.1.2.2 3.1.2.2.a 3.1.2.2.b 3.1.2.2.c 3.1.2.3 3.1.2.3.a 3.1.2.3.b 3.1.2.3.c |
APAC (6)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-0039 ISM-0720 |
| APAC Australia Prudential Standard CPS230 2023 | 27(b) |
| APAC India SEBI CSCRF 2024 | GV.RR.S4 |
| APAC Japan ISMAP | 5.1.1.2 |
| APAC Malaysia RMiT 2025 | 8.2(a) 8.7(a) 10.19(b) |
| APAC New Zealand NZISM 3.9 | 2.3.25.C.01 2.3.25.C.02 2.3.29.C.01 |
Americas (2)
| Framework | Mapping Values |
|---|---|
| Americas Canada OSFI B-13 2022 | 1.2.1 |
| Americas Canada OSFI Self-Assessment Guidance | 1.2.1 |
Capability Maturity Model
Level 0 — Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 — Performed Informally
SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.
Level 2 — Planned & Tracked
Project & Resource Management (PRM) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with PRM domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with PRM domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with PRM domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Project & Resource Management -related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Project & Resource Management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ The Chief Information Officer (CIO), or similar function, analyzes the organization's business strategy and prioritizes the objectives and resourcing of the security function, based on broader business requirements. ▪ A Project Management Office (PMO), or project management function, enables the implementation of cybersecurity and data protection-related resource planning controls across the System Development Lifecycle (SDLC) for all high-value projects. ▪ Quarterly Business Review (QBR), or similar status reporting, exists to provide recurring reports on the state of the cybersecurity and data protection program.
Level 3 — Well Defined
Project & Resource Management (PRM) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with PRM domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with PRM domain capabilities are well-documented and kept current by process owners. ▪ A Project Management Office (PMO), or similar function, is appropriately staffed and supported to implement and maintain PRM domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of project and resource management operations (e.g., project management solution). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with PRM domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ The Chief Information Officer (CIO), or similar function, analyzes the organization's business strategy and prioritizes the objectives and resourcing of the security function, based on broader business requirements. ▪ An implemented and operational capability exists to establish a: (1) Strategic security, compliance and resilience-specific business plan; and (2) Set of objectives to achieve that plan.
Level 4 — Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
Level 5 — Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
Assessment Objectives
- PRM-02_A01 a documented strategic cybersecurity / data privacy-specific business plan exists.
- PRM-02_A02 a documented set of objectives to achieve that cybersecurity and privacy-specific business plan exists.
Evidence Requirements
- E-PRM-01 Cybersecurity Business Plan (CBP)
-
Documented evidence of a cybersecurity-specific business plan that documents a strategic plan and discrete objectives.
Resource Management
Technology Recommendations
Micro/Small
- Include security tasks in project plans
Small
- Security requirements in project planning
- Project security checklist
Medium
- Documented cybersecurity and data protection-specific business plan
Large
- Documented cybersecurity and data protection-specific business plan
Enterprise
- Documented cybersecurity and data protection-specific business plan