PCI DSS 4.0
Req 2: Secure Configurations

PCI DSS 4.0 2.1.2: 2.1.2 Requirement 2 roles and responsibilities assigned

Responsibilities for the Requirement 2 activities (building and maintaining configuration standards, handling vendor defaults, disabling unneeded functions, securing wireless) must be written down, allocated, and understood by those who hold them. Applicability: no special notes; applies to every assessed entity. Customized approach objective: daily responsibility for all Requirement 2 work is allocated, and the holders are answerable for these controls operating successfully and continuously.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 59 controls across 31 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

HIPAA Security Rule · 4 controls

NIST SP 800-53 Rev 5 · 4 controls

NIST SP 800-66 Rev 2 · 4 controls

SOC 2 · 4 controls

  • SOC2-CC1.3 CC1.3 Structures, reporting lines, authorities and responsibilities (COSO principle 3)
  • SOC2-CC1.5 CC1.5 Accountability for internal control responsibilities (COSO principle 5)
  • SOC2-CC2.2 CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)
  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)

SWIFT CSCF · 3 controls

  • SWIFTCSCF-3 Physically Secure the Environment (Objective 3)
  • SWIFTCSCF-4 Prevent Compromise of Credentials (Objective 4)
  • SWIFTCSCF-7 Plan Incident Response (Objective 7)

CMMC 2.0 · 2 controls

FedRAMP High · 2 controls

  • CM-1 Policy and Procedures
  • CM-3(4) Security and Privacy Representatives

FedRAMP Moderate · 2 controls

  • CM-1 Policy and Procedures
  • CM-3(4) Security and Privacy Representatives
  • GGAP-IFA-AllFarmBase-Mgmt-Workers-Env-Trace GLOBALG.A.P. IFA v6 All Farm Base (AF): Management, Workers, Environment, Traceability and Food Safety
  • GGAP-IFA-CropsBase-Production-PPP-IPM GLOBALG.A.P. IFA v6 Crops Base (CB): Propagation, Soil, Water, IPM, PPP, Fertilizer and Harvest
  • ISO-15189-6.3 Facilities and environmental conditions
  • ISO-15189-6.5 Equipment calibration and metrological traceability
  • PICSGMP-3 Chapter 3: Premises and Equipment - Design, Qualification, Calibration
  • PICSGMP-4 Chapter 4: Documentation - System, Record-Keeping, Data Integrity
  • 58.49 Laboratory Operation Areas
  • GS-1 Align organization roles, responsibilities and accountabilities
  • FSSC-Additional-Requirements-v6 FSSC 22000 Additional Requirements v6 (Food Defense + Food Fraud + Allergen + Environmental + Culture)
  • IEC62304-5.1 Software Development Planning

ISO 22301:2019 · 1 control

  • 5.3 Roles, responsibilities and authorities

ISO 27001:2022 · 1 control

  • 5.2 Information security roles and responsibilities

ISO 27002:2022 · 1 control

  • 5.2 Information security roles and responsibilities

ISO 27701:2019 · 1 control

  • 5.3.3 Organizational roles, responsibilities and authorities
  • ISO-17025-6.5 Metrological traceability
  • ISO-25012-4.11 Traceability

ISO/IEC 42001:2023 · 1 control

  • 5.3 Roles, responsibilities and authorities
  • NIST-CSF-GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced
  • 2.1.3 Food Safety and Quality Culture
  • AIGF-3.3 Repeatability and Traceability

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Req 2: Secure Configurations

You are reading one control. How much of PCI DSS 4.0 have you already done?

PCI DSS 4.0 2.1.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

The graph holds this control, the 59 it maps to, and the evidence behind each claim, over MCP and REST.