HRS-04.1: Assigned Roles & Responsibilities Awareness
Mechanisms exist to communicate with users about their roles and responsibilities to maintain a safe and secure working environment.
Renumbered: Formerly HRS-03.1 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, HRS-04.1 was Roles With Special Protection Measures. That control is now HRS-05.1.
Control Question: Does the organization communicate with users about their roles and responsibilities to maintain a safe and secure working environment?
General (22)
| Framework | Mapping Values |
|---|---|
| AICPA Privacy Management Framework (PMF) | M1.2-POF3 |
| BSI Standard 200-1 | 4.2 6.0 |
| COSO 2013 | 4.0 |
| CSA CCM 4.1.0 | HRS-09 HRS-13 |
| ISO 27001 2022 (source) | 7.3 7.3(a) 7.3(b) 7.3(c) |
| ISO 27701 2025 | 7.3 |
| ISO 42001 2023 | 7.3 |
| MPA Content Security Program 5.3.1 | OR-3.1 OP-2.0 |
| NIST AI 100-1 (AI RMF) 1.0 | GOVERN 4.1 |
| NIST 800-171 R3 (source) | 03.01.22.a 03.15.03.b |
| NIST 800-171A R3 (source) | A.03.01.22.a A.03.15.03.b |
| NIST CSF 2.0 (source) | GV.RR-04 |
| NIST Privacy Framework 1.0 | GV.PO-P2 |
| PCI DSS 4.0.1 (source) | 1.1.2 2.1.2 3.1.2 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.6.3 |
| PCI DSS 4.0.1 SAQ A-EP (source) | 12.1.3 |
| PCI DSS 4.0.1 SAQ B (source) | 12.1.3 |
| PCI DSS 4.0.1 SAQ B-IP (source) | 12.1.3 |
| PCI DSS 4.0.1 SAQ C (source) | 12.1.3 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 1.1.2 2.1.2 3.1.2 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.6.3 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 1.1.2 2.1.2 3.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.6.3 |
| PCI DSS 4.0.1 SAQ P2PE (source) | 12.1.3 |
| TISAX ISA 6.0.3 | 2.1.3 |
US (8)
| Framework | Mapping Values |
|---|---|
| USA Federal DHS CISA TIC 3.0 | 3.UNI.UATRA |
| USA Federal C2M2 2.1 | WORKFORCE-1e WORKFORCE-2a |
| USA Federal CERT RMM 1.2 | HRM:SG3.SP2 |
| USA Federal 33 CFR Part 101 Subpart F | 101.625(d)(8) |
| USA Federal NERC CIP 2024 | CIP-004-7 R2 CIP-004-7 2.2 |
| USA Federal FCA CRM 2023 | 609.930(c)(4) |
| USA Massachusetts 201 CMR 17.00 2008 | 17.03(2)(b)2 |
| USA New York DFS 23 NYCRR500 2023 Amd 2 | 500.10(a)(2) |
EMEA (7)
| Framework | Mapping Values |
|---|---|
| EMEA EU NIS2 Annex 2024 | 8.1.1 10.1.2(a) 10.1.2(b) 10.1.2(c) |
| EMEA UK DEFSTAN 05-138 2024 | 2600 2603 |
| EMEA UK DEFSTAN 05-138 - L1 2024 | 2600 2603 |
| EMEA UK DEFSTAN 05-138 - L2 2024 | 2600 2603 |
| EMEA UK DEFSTAN 05-138 - L3 2024 | 2600 2603 |
| EMEA Saudi Arabia ECC-1 2018 | 1-9-4-1 |
| EMEA Saudi Arabia SAMA CSF 1.0 2017 | 3.1.6.5.b |
APAC (3)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-0824 |
| APAC India SEBI CSCRF 2024 | GV.RR.S6 PR.AT.S4 PR.AT.S5 |
| APAC Japan ISMAP | 4.5.2.6 4.5.2.7 4.5.2.8 7.1.2.7 7.2 7.2.1.4 8.1.3.1 |
Americas (2)
| Framework | Mapping Values |
|---|---|
| Americas Argentina Reg 132 2018 | B.2.2 |
| Americas Canada ITSP-10-171 2025 | 03.01.22.A 03.15.03.B |
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
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 communicate with users about their roles and responsibilities to maintain a safe and secure working environment.
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.1_A01 users are formally made aware of their roles and responsibilities to maintain a safe and secure working environment.
- HRS-04.1_A02 acknowledgement of user awareness is maintained by the organization.
Evidence Requirements
- 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
Technology Recommendations
Micro/Small
- Formal onboarding training
- Acceptable Use / Rules of Behavior (RoB)
Small
- Formal onboarding training
- Acceptable Use / Rules of Behavior (RoB)
Medium
- Formal onboarding training
- Acceptable Use / Rules of Behavior (RoB)
Large
- Formal onboarding training
- Acceptable Use / Rules of Behavior (RoB)
Enterprise
- Formal onboarding training
- Acceptable Use / Rules of Behavior (RoB)