HRS-04: Defined Roles & Responsibilities
Mechanisms exist to define cybersecurity roles & responsibilities for all personnel.
Renumbered: Formerly HRS-03 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, HRS-04 was Personnel Screening. That control is now HRS-05.
Control Question: Does the organization define cybersecurity roles & responsibilities for all personnel?
General (56)
| Framework | Mapping Values |
|---|---|
| AICPA Privacy Management Framework (PMF) | M1.2-POF3 |
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC1.2 CC1.2-POF1 CC1.2-POF2 CC1.3 CC1.3-POF3 CC1.3-POF4 CC1.3-POF5 CC1.4-POF6 CC1.5-POF1 CC2.1-POF6 CC2.2 CC2.2-POF5 CC5.3-POF2 CC7.4-POF1 |
| APEC Privacy Framework 2015 | 9 |
| BSI Standard 200-1 | 7.2 |
| COBIT 2019 | DSS06.03 |
| COSO 2013 | 2.0 3.0 14.0 |
| CSA CCM 4.1.0 | CEK-02 GRC-06 HRS-09 |
| CSA IoT SCF 2 | GVN-01 |
| IEC 62443-2-1 2024 | ORG 1.3 |
| IEC 62443-4-1 2018 | SM-2 |
| IMO Maritime Cyber Risk Management | 3.5.1 |
| ISO/SAE 21434 2021 | RQ-05-07 RQ-06-01 |
| ISO 22301 2019 | 5.3 8.4.2.2 8.4.2.4(a) 8.4.2.4(b) |
| ISO 27001 2022 (source) | 5.3 7.3 7.3(b) |
| ISO 27002 2022 | 5.2 |
| ISO 27017 2015 | 6.1.1 |
| ISO 27018 2025 | 5.2 |
| ISO 27701 2025 | 4.2 5.3 7.3 |
| ISO 31000 2018 | 5.4.3 |
| ISO 42001 2023 | 5.3 7.2 A.3.2 |
| MPA Content Security Program 5.3.1 | OR-3.1 |
| NIST AI 100-1 (AI RMF) 1.0 | GOVERN 2.0 GOVERN 2.1 |
| NIST AI 600-1 | GOVERN 1.5 GV-1.5-001 |
| NIST 800-37 R2 | TASK P-1 |
| NIST 800-53 R4 | PM-13 |
| NIST 800-53 R5.2 | PM-13 PS-09 |
| NIST 800-53B R5 (low) (source) | PS-09 |
| NIST 800-53B R5 (moderate) (source) | PS-09 |
| NIST 800-53B R5 (high) (source) | PS-09 |
| NIST 800-53B R5 (privacy) (source) | PM-13 |
| NIST SP 800-66 R2 | 164.308(a)(3) 164.310(a) 164.312(a) |
| NIST 800-82 R3 | PM-13 PS-09 |
| NIST 800-82 R3 LOW OT Overlay | PM-13 PS-09 |
| NIST 800-82 R3 MODERATE OT Overlay | PM-13 PS-09 |
| NIST 800-82 R3 HIGH OT Overlay | PM-13 PS-09 |
| NIST 800-161 R1 | PM-13 |
| NIST 800-161 R1 Level 1 | PM-13 |
| NIST 800-161 R1 Level 2 | PM-13 |
| NIST 800-171 R3 (source) | 03.01.22.a 03.02.02.a.01 03.06.04.a 03.06.05.d 03.07.06.a 03.07.06.d 03.08.02 03.15.03.b 03.16.03.b |
| NIST 800-171A R3 (source) | A.03.01.22.a A.03.02.02.a.01[01] A.03.06.04.ODP[01] A.03.06.05.d A.03.07.06.a A.03.07.06.d[02] A.03.08.02 A.03.15.03.b A.03.16.03.b |
| NIST 800-172 R3 | 03.01.08E 03.01.11E 03.14.17E 03.14.18E 03.17.03E |
| NIST 800-172A R3 | A.03.01.08E.ODP[02] A.03.01.11E.ODP[01] A.03.14.17E.ODP[01] DS-A.03.14.18E A.03.14.18E.ODP[01] A.03.17.03E.ODP[03] |
| NIST 800-218 | PO.2 PO.2.1 |
| NIST CSF 2.0 (source) | GV.RM-05 GV.RR GV.RR-02 ID.AM |
| NIST Privacy Framework 1.0 | GV.PO-P2 GV.PO-P3 CM.PO-P2 |
| PCI DSS 4.0.1 (source) | 1.1.2 2.1.2 3.1.2 3.7.8 4.1.2 5.1.2 6.1.2 7.1.2 8.1.2 9.1.2 10.1.2 11.1.2 12.1.3 12.10.1 A3.1.3 |
| PCI DSS 4.0.1 SAQ A (source) | 12.10.1 |
| PCI DSS 4.0.1 SAQ A-EP (source) | 12.1.3 12.10.1 |
| PCI DSS 4.0.1 SAQ B (source) | 12.1.3 12.10.1 |
| PCI DSS 4.0.1 SAQ B-IP (source) | 12.1.3 12.10.1 |
| PCI DSS 4.0.1 SAQ C (source) | 12.1.3 12.10.1 |
| PCI DSS 4.0.1 SAQ C-VT (source) | 12.10.1 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 1.1.2 2.1.2 3.1.2 3.7.8 4.1.2 5.1.2 6.1.2 7.1.2 8.1.2 9.1.2 10.1.2 11.1.2 12.1.3 12.10.1 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 1.1.2 2.1.2 3.1.2 3.7.8 5.1.2 6.1.2 7.1.2 8.1.2 9.1.2 10.1.2 11.1.2 12.1.3 12.10.1 |
| PCI DSS 4.0.1 SAQ P2PE (source) | 12.1.3 12.10.1 |
| TISAX ISA 6.0.3 | 1.2.2 1.2.4 2.1.1 9.7.2 |
US (23)
| Framework | Mapping Values |
|---|---|
| USA Federal CMS MARS-E 2.0 | PM-13 |
| USA Federal DHS CISA TIC 3.0 | 3.UNI.UATRA |
| USA Federal C2M2 2.1 | THREAT-2a RESPONSE-3a WORKFORCE-3a WORKFORCE-3b WORKFORCE-3c WORKFORCE-3d |
| USA Federal CERT RMM 1.2 | ADM:GG2.GP4 ADM:GG2.GP6 AM:GG2.GP4 AM:GG2.GP6 COMM:GG2.GP4 COMM:GG2.GP6 COMP:GG2.GP4 COMP:GG2.GP6 CTRL:GG2.GP4 CTRL:GG2.GP6 EC:GG2.GP4 EC:GG2.GP6 EF:GG2.GP4 EF:GG2.GP6 EXD:GG2.GP4 EXD:GG2.GP6 FRM:GG2.GP4 FRM:GG2.GP6 HRM:SG3.SP1 HRM:GG2.GP4 HRM:GG2.GP6 ID:GG2.GP4 ID:GG2.GP6 IMC:GG2.GP4 IMC:GG2.GP6 KIM:GG2.GP4 KIM:GG2.GP6 MA:GG2.GP4 MA:GG2.GP6 MON:GG2.GP4 MON:GG2.GP6 OPD:GG2.GP4 OPD:GG2.GP6 OPF:GG2.GP4 OPF:GG2.GP6 OTA:GG2.GP4 OTA:GG2.GP6 PM:GG2.GP4 PM:GG2.GP6 RISK:GG2.GP4 RISK:GG2.GP6 RRD:GG2.GP4 RRD:GG2.GP6 RRM:GG2.GP4 RRM:GG2.GP6 RTSE:GG2.GP4 RTSE:GG2.GP6 SC:GG2.GP4 SC:GG2.GP6 TM:GG2.GP4 TM:GG2.GP6 VAR:GG2.GP4 VAR:GG2.GP6 GG2.GP4 GG2.GP6 |
| USA Federal NNPI (unclass) 2010 | 9-2.e |
| USA Federal CJIS Security Policy 6.0 | PS-9 |
| USA Federal 21 CFR Part 11 2025 | 11.10(i) |
| USA Federal FedRAMP R5 (low) | PS-09 |
| USA Federal FedRAMP R5 (moderate) | PS-09 |
| USA Federal FedRAMP R5 (high) | PS-09 |
| USA Federal FedRAMP R5 (LI-SaaS) | PS-09 |
| USA Federal IRS 1075 2021 | PS-9 |
| USA Federal 33 CFR Part 101 Subpart F | 101.620(b)(2) 101.625(a) |
| USA Federal HIPAA Security Rule NIST SP 800-66 R2 | § 164.308(a)(3)(ii)(B) § 164.310(a)(2)(i) § 164.312(a)(1) |
| USA Federal HIPAA Administrative Simplification 2013 | § 164.308(a)(3)(ii)(B) § 164.310(a)(2)(i) § 164.312(a)(1) § 164.530(a)(2) |
| USA Federal NERC CIP 2024 | CIP-008-6 1.3 CIP-009-6 1.2 |
| USA Federal NISPOM 2020 | §117.18(c)(2) §117.18(c)(2)(i) §117.18(c)(2)(ii) §117.18(c)(2)(iii) §117.18(c)(2)(iv) §117.18(c)(2)(v) §117.18(c)(2)(vi) §117.18(c)(2)(vii) §117.18(c)(2)(vii)(A) §117.18(c)(2)(vii)(B) §117.18(c)(2)(vii)(C) §117.18(c)(2)(vii)(D) §117.18(c)(2)(vii)(E) §117.18(c)(2)(vii)(F) §117.18(c)(2)(vii)(G) §117.18(c)(2)(vii)(H) §117.18(c)(2)(vii)(I) §117.18(c)(3) §117.18(c)(3)(i) §117.18(c)(3)(ii) §117.18(c)(3)(iii) §117.18(c)(4) §117.18(c)(4)(i) §117.18(c)(4)(ii) §117.18(c)(4)(iii) §117.18(c)(4)(iv) §117.18(c)(4)(v) §117.18(c)(4)(vi) |
| USA Federal FIPPS 1973 | 2.0 |
| USA Federal FCA CRM 2023 | 609.930(b)(3) 609.930(c)(4) |
| USA Illinois IPA 2009 | 35(a)(3) 37(a)(3) |
| USA Massachusetts 201 CMR 17.00 2008 | 17.03(2)(b)2 |
| USA New York DFS 23 NYCRR500 2023 Amd 2 | 500.10(a)(1) 500.16(a)(2)(ii) |
| USA Texas DIR SCSC 2.2 2025 | PS-09 |
EMEA (22)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2026 | SP-01.01B.3 OPS-10.01B.4 OPS-32.03B.1 |
| EMEA Spain CCN-STIC 825 | org.4 |
| EMEA Spain Royal Decree 311 2022 | Article 12(1)(c) Article 13(2) |
| EMEA EU DORA 2023 | Article 5.2(c) |
| EMEA EU DORA RTS 2024 | Article 2.2(d) Article 15.3(b) Article 17.2(c) Article 19.1(a) Article 21.1(e)(i) Article 23.1 Article 28.2(b) |
| EMEA EU EBA GL/2019/04 | 3.2.1.2 3.3.1.12 3.4.1.29 |
| EMEA EU GDPR 2016 | Article 32.4 |
| EMEA EU NIS2 Annex 2024 | 1.1.1(g) 1.2.1 1.2.4 1.2.6 2.1.2(i) 3.1.2(c) 3.1.3 4.2.4(c) 4.3.2(a) 10.1.1 |
| EMEA UK DEFSTAN 05-138 2024 | 1102 2321 3101 3102 |
| EMEA UK DEFSTAN 05-138 - L1 2024 | 1102 2321 3101 |
| EMEA UK DEFSTAN 05-138 - L2 2024 | 1102 2321 3101 |
| EMEA UK DEFSTAN 05-138 - L3 2024 | 1102 2321 3102 |
| EMEA Hungary Act CXII 2011 | II.18.24(2) |
| EMEA Israel PPL 2025 | s.17B2 |
| EMEA Italy PDPC 2018 | Article 2-o(1) Article 2-o(2) |
| EMEA LUX CCSF 20/750 2020 | 3.6.1-63.b |
| EMEA Saudi Arabia IoT CGIoT-1 2024 | 1-3-1 1-3-2 1-8-1 |
| EMEA Saudi Arabia ECC-1 2018 | 1-4-1 1-4-2 1-9-1 |
| EMEA Saudi Arabia OTCC-1 2022 | 1-2-1 1-2-1-2 |
| EMEA Saudi Arabia PDPL | Article 30.2 |
| EMEA Saudi Arabia SACS-002 2022 | VII.B.TPC-26 |
| EMEA Saudi Arabia SAMA CSF 1.0 2017 | 3.1.4.6 3.1.4.6.a 3.3.1.3.a |
APAC (13)
| Framework | Mapping Values |
|---|---|
| APAC Australia CCM 2026 | RES-05 |
| APAC Australia ISM June 2026 | ISM-0717 ISM-0720 ISM-0724 ISM-0725 ISM-0726 ISM-0731 ISM-0732 ISM-0733 ISM-0734 ISM-0735 ISM-2035 ISM-2036 |
| APAC Australia Prudential Standard CPS234 2019 | 19.0 |
| APAC India DPDPA 2023 | 6(9) 10(2)(a)(iv) |
| APAC India SEBI CSCRF 2024 | DE.DP.S1 GV.RR.S2 PR.AT.S4 PR.AT.S5 RS.CO.S1 |
| APAC Japan ISMAP | 4.5.2.2 6.1.1 6.1.1.1 6.1.1.2 6.1.1.3 6.1.1.4 6.1.1.5 6.1.1.6 6.1.1.7 6.1.1.13.PB |
| APAC Malaysia RMiT 2025 | 10.35(b) A10-A6(b) |
| APAC New Zealand HISF Microsmall 2023 | HMS01 |
| APAC New Zealand HISF MLHSP 2023 | HHSP02 HHSP23 HML02 HML23 |
| APAC New Zealand HISF Suppliers 2023 | HSUP02 HSUP21 |
| APAC New Zealand NZISM 3.9 | 3.3.4.C.01 3.3.4.C.02 3.3.4.C.03 3.3.4.C.04 3.3.4.C.05 3.3.5.C.01 3.3.5.C.02 3.3.6.C.01 3.3.6.C.02 3.3.6.C.03 3.3.6.C.04 3.3.6.C.05 3.3.6.C.06 3.3.7.C.01 3.3.8.C.01 3.3.8.C.02 3.3.8.C.03 3.3.8.C.04 3.3.8.C.05 3.3.9.C.01 3.3.10.C.01 3.3.10.C.02 3.3.10.C.03 3.3.10.C.04 3.3.11.C.01 3.3.12.C.01 3.3.13.C.01 3.3.13.C.02 3.3.14.C.01 3.3.14.C.02 3.3.14.C.03 3.3.15.C.01 3.4.10.C.01 3.4.10.C.02 17.9.35.C.01 |
| APAC Singapore CCOP CII 2026 | 3.2.2 3.2.2(b) |
| APAC Singapore MAS TRM 2021 | 3.5.1 |
Americas (3)
| Framework | Mapping Values |
|---|---|
| Americas Argentina Reg 132 2018 | B.2.2 E.1.2-1 F.1.3 |
| Americas Canada ITSP-10-171 2025 | 03.01.22.A 03.02.02.A.01 03.06.04.A 03.06.05.D 03.07.06.A 03.07.06.D 03.08.02 03.15.03.B 03.16.03.B |
| Americas Canada OSFI Self-Assessment Guidance | 2.7.2 |
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
Human Resources Security (HRS) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with HRS domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Personnel management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ The Human Resources (HR) department provides guidance on secure HR practices for hiring, retaining and terminating employees, contractors and other personnel that work on behalf of the organization. ▪ Formal roles and responsibilities for cybersecurity and/or data protection are not consistent and/or standardized.
Level 2 — Planned & Tracked
Human Resources Security (HRS) 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 HRS domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with HRS 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 HRS domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Personnel management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Personnel management is decentralized at a localized/regionalized function, where there are non-standardized methods to govern personnel matters across the organization. ▪ Localized HR practices are implemented for hiring, managing, training, investigating and terminating employees, contractors and other personnel that work on behalf of the organization.
Level 3 — Well Defined
Human Resources Security (HRS) 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 HRS 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 HRS domain capabilities are well-documented and kept current by process owners. ▪ A Human Resources (HR) team, or similar function, is appropriately staffed and supported to implement and maintain HRS domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of human resources security operations (e.g., personnel management software 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 HRS 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). ▪ An implemented and operational capability exists to define cybersecurity roles & responsibilities for all personnel.
Level 4 — Quantitatively Controlled
Human Resources Security (HRS) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.
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
- HRS-04_A01 cybersecurity / data privacy roles and responsibilities are incorporated into organizational position descriptions.
- HRS-04_A02 the incident response plan is protected from unauthorized disclosure.
Evidence Requirements
- E-HRS-02 Assigned Roles - Application Developers
-
List of employed or contract personnel assigned to application development roles.
Human Resources - E-HRS-03 Assigned Roles - Cybersecurity Staff
-
List of employed or contract personnel assigned to cybersecurity roles.
Human Resources - E-HRS-04 Assigned Roles - Data Privacy Staff
-
List of employed or contract personnel assigned to data privacy roles.
Human Resources - E-HRS-13 Defined Cybersecurity & Data Privacy Responsibilities
-
Documented evidence of a role-based cybersecurity & data privacy responsibilities to ensure personnel are both educated on the role and are responsible for the associated control execution.
Human Resources - E-HRS-14 Responsibilities Review
-
Documented evidence of a formal review process to ensure assigned responsibilities currently reflect business needs for the assigned role.
Human Resources
Technology Recommendations
Micro/Small
- NIST NICE cybersecurity workforce framework alignment
- Responsible, Accountable, Supporting, Consulted and Informed (RASCI) matrix
Small
- NIST NICE cybersecurity workforce framework alignment
- Responsible, Accountable, Supporting, Consulted and Informed (RASCI) matrix
Medium
- NIST NICE cybersecurity workforce framework alignment
- Responsible, Accountable, Supporting, Consulted and Informed (RASCI) matrix
Large
- NIST NICE cybersecurity workforce framework alignment
- Responsible, Accountable, Supporting, Consulted and Informed (RASCI) matrix
Enterprise
- NIST NICE cybersecurity workforce framework alignment
- Responsible, Accountable, Supporting, Consulted and Informed (RASCI) matrix