HRS-12: Incompatible Roles
Mechanisms exist to avoid incompatible development-specific roles through limiting and reviewing developer privileges to change hardware, software and firmware components within a production/operational environment.
Control Question: Does the organization avoid incompatible development-specific roles through limiting and reviewing developer privileges to change hardware, software and firmware components within a production/operational environment?
General (9)
| Framework | Mapping Values |
|---|---|
| COBIT 2019 | DSS06.03 |
| CSA CCM 4 | CEK-02 |
| ISO 27002 2022 | 5.3 |
| ISO 27017 2015 | 6.1.2 |
| NIST Privacy Framework 1.0 | ID.IM-P2 |
| NIST 800-171 R3 (source) | 03.01.04.a |
| SCF CORE Mergers, Acquisitions & Divestitures (MA&D) | HRS-12 |
| SCF CORE ESP Level 2 Critical Infrastructure | HRS-12 |
| SCF CORE ESP Level 3 Advanced Threats | HRS-12 |
US (1)
| Framework | Mapping Values |
|---|---|
| US SSA EIESR 8.0 | 5.7 |
EMEA (1)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2020 | PSS-08 |
APAC (2)
| Framework | Mapping Values |
|---|---|
| APAC China Data Security Law | 27 |
| APAC Japan ISMAP | 6.1.2 |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 | 03.01.04.A |
Capability Maturity Model
Level 0 — Not Performed
There is no evidence of a capability to avoid incompatible development-specific roles through limiting and reviewing developer privileges to change hardware, software and firmware components within a production/operational environment.
Level 1 — Performed Informally
Human Resources Security (HRS) efforts are ad hoc and inconsistent. CMM Level 1 control maturity would reasonably expect all, or at least most, the following criteria to exist:
- Personnel management is decentralized, with the responsibility for training users and enforcing policies being assigned to the user’s immediate supervisor(s)/manager(s), including the definition and enforcement of the user’s specific role(s) and responsibilities.
- The Human Resources (HR) department provides guidance on HR practices for hiring, retaining and terminating employees, contractors and other personnel that work on behalf of the organization.
- Terms of employment, including acceptable and unacceptable rules of behavior for the use of technologies, including consequences for unacceptable behavior are at the discretion of users’ management.
- Administrative processes require all employees and contractors to apply cybersecurity and data privacy principles in their daily work.
Level 2 — Planned & Tracked
Human Resources Security (HRS) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Ensures industry-recognized HR practices are implemented for hiring, managing, training, investigating and terminating employees, contractors and other personnel that work on behalf of the organization. o Defines terms of employment, including acceptable and unacceptable rules of behavior for the use of technologies, including consequences for unacceptable behavior.
- Personnel management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
- IT/cybersecurity personnel identify cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements for personnel management.
- The Human Resources (HR) department:
- The responsibility for training users and enforcing policies being assigned to user’s immediate supervisor(s)/manager(s), including the definition and enforcement of the user’s specific role(s) and responsibilities.
- Personnel managers ensure personnel are routinely made aware of the organization's cybersecurity / data privacy policies and provide acknowledgement.
- Administrative processes require all employees and contractors to apply cybersecurity and data privacy principles in their daily work.
- Administrative processes avoid incompatible development-specific roles through limiting and reviewing developer privileges to change hardware, software and firmware components within a production/operational environment.
- Administrative processes implement and maintain Separation of Duties (SoD) to prevent potential malevolent activity without collusion.
Level 3 — Well Defined
Human Resources Security (HRS) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Ensures industry-recognized HR practices are implemented for hiring, managing, training, investigating and terminating employees, contractors and other personnel that work on behalf of the organization. o Ensures that every user accessing a system that processes, stores, or transmits sensitive/regulated data is cleared and regularly trained in proper data handling practices. o Identifies and implements industry-recognized HR practices related to cybersecurity and data privacy training and awareness to help ensure secure practices are implemented in personnel operations to help manage risk to both technology assets and data. o Manages personnel security risk by assigning a risk designation to all positions and establishing screening criteria for individuals filling those positions.
- The Human Resources (HR) department:
- Administrative processes require Non-Disclosure Agreements (NDAs) or similar confidentiality agreements that reflect the needs to protect data and operational details, for both employees and third-parties.
- Administrative processes avoid incompatible development-specific roles through limiting and reviewing developer privileges to change hardware, software and firmware components within a production/operational environment.
- Administrative processes implement and maintain Separation of Duties (SoD) to prevent potential malevolent activity without collusion.
Level 4 — Quantitatively Controlled
See C|P-CMM3. There are no defined C|P-CMM4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to avoid incompatible development-specific roles through limiting and reviewing developer privileges to change hardware, software and firmware components within a production/operational environment.
Level 5 — Continuously Improving
See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to avoid incompatible development-specific roles through limiting and reviewing developer privileges to change hardware, software and firmware components within a production/operational environment.
Assessment Objectives
- HRS-11_A04 duties of individuals requiring separation are identified.
- HRS-12_A01 incompatible development-specific roles are prevented through limiting and reviewing developer privileges to change hardware, software and firmware components within a production/operational environment.
Evidence Requirements
- E-HRS-25 Separation of Duties (SoD)
-
Documented evidence of personnel management practices to implement and maintain Separation of Duties (SoD) to prevent potential inappropriate activity without collusion.
Human Resources