PCI DSS 4.0
Req 4: Protect Cardholder Data in Transit

PCI DSS 4.0 4.1.1: All security policies and operational procedures that are identified in Requirement 4 are: • Documented. • Kept up to date. • In use. • Known to all affected parties

All security policies and operational procedures that are identified in Requirement 4 are: • Documented. • Kept up to date. • In use. • Known to all affected parties

What else in your programme already covers this

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

ISO 22301:2019 · 5 controls

  • 4.4 Business continuity management system
  • 5.2.2 Communicating the business continuity policy
  • 7.5.1 General
  • 7.5.2 Creating and updating
  • 7.5.3 Control of documented information

ISO 27001:2022 · 5 controls

  • 5.1 Policies for information security
  • 5.35 Independent review of information security
  • 5.36 Compliance with policies, rules and standards for information security
  • 5.37 Documented operating procedures
  • 6.3 Information security awareness, education and training

NIST SP 800-53 Rev 5 · 5 controls

  • NIST800-AT-1 Policy and procedures for awareness and training
  • NIST800-CA-1 Policy and procedures for assessment, authorization, and monitoring
  • NIST800-PL-1 Policy and procedures for planning
  • NIST800-PM-1 Information Security Program Plan. Develop and disseminate an organization-wide information security program plan that: Provides an overview of the requirements for the security program and a description of the security program management controls and
  • NIST800-SC-1 Policy and procedures for system and communications protection

CIS Controls v8 · 4 controls

  • CIS-14.1 Establish and Maintain a Security Awareness Program
  • CIS-17.4 Establish and Maintain an Incident Response Process
  • CIS-4.1 Establish and Maintain a Secure Configuration Process
  • CIS-8.1 Establish and Maintain an Audit Log Management Process

CMMC 2.0 · 4 controls

ISO 27701:2019 · 4 controls

  • 5.3.2 Policy
  • 5.5.4 Communication
  • 5.5.5 Documented information
  • 6.2.1 Management direction for information security

ISO/IEC 42001:2023 · 4 controls

SOC 2 · 4 controls

  • SOC2-CC2.2 COSO principle 14: Internally communicates information including objectives and responsibilities
  • SOC2-CC4.1 COSO principle 16: Selects and develops ongoing and separate evaluations
  • SOC2-CC4.2 COSO principle 17: Evaluates and communicates deficiencies in a timely manner
  • SOC2-CC5.3 COSO principle 12: Deploys control activities through policies and procedures

ISO 27002:2022 · 2 controls

  • 5.1 Policies for information security
  • 5.37 Documented operating procedures
  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
  • NIST-CSF-GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission
  • ASBv3-GS-3 Define and implement data protection strategy

C5 (Germany) · 1 control

  • CCM-CEK-01 Encryption and Key Management Policy and Procedures

FedRAMP High · 1 control

  • SC-1 Policy and Procedures

FedRAMP Moderate · 1 control

  • SC-1 Policy and Procedures
  • SC-1 Policy and Procedures
  • SC-1 Policy and Procedures
  • SC-1 Policy and Procedures

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 4: Protect Cardholder Data in Transit

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

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