PCI DSS 4.0
Req 1: Network Security Controls

PCI DSS 4.0 1.1.2: 1.1.2 Requirement 1 roles and responsibilities assigned

The duties needed to carry out the Requirement 1 activities (network security control design, configuration, change handling, reviews and diagram maintenance) must be written down, allocated to named roles or people, and understood by those who hold them. Applicability: no special notes; applies to every assessed entity. Customized approach objective: daily responsibility for all Requirement 1 work is allocated, and the people holding it are answerable for these controls operating successfully and without interruption.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

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)

CMMC 2.0 · 2 controls

FedRAMP High · 2 controls

  • PS-9 Position Descriptions (PS-9)
  • SC-1 Policy and Procedures

FedRAMP Moderate · 2 controls

  • PS-9 Position Descriptions (PS-9)
  • SC-1 Policy and Procedures

ISO 27701:2019 · 2 controls

  • 5.3.3 Organizational roles, responsibilities and authorities
  • 6.5.1 Responsibility for assets

APRA CPS 234 · 1 control

  • CPS234-14 Definition of Information Security Roles and Responsibilities
  • GS-1 Align organization roles, responsibilities and accountabilities

C5 (Germany) · 1 control

  • C5-OIS-01 Information Security Management System (ISMS)

CIS Controls v8 · 1 control

  • CIS-17.5 Assign Key Roles and Responsibilities

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 37001:2016 · 1 control

  • 5.3.1 5.3.1 Roles and responsibilities

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

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 1: Network Security Controls

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

PCI DSS 4.0 1.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 26 it maps to, and the evidence behind each claim, over MCP and REST.