Skip to main content

💼 3.7 Ensure that security policies and operational procedures for protecting stored cardholder data are documented, in use, and known to all affected parties.

  • Contextual name: 💼 3.7 Ensure that security policies and operational procedures for protecting stored cardholder data are documented, in use, and known to all affected parties.
  • ID: /frameworks/pci-dss-v3.2.1/03/07
  • Located in: 💼 3 Protect stored cardholder data

Description​

Empty...

Similar​

  • Sections
    • /frameworks/pci-dss-v4.0/03/01/01
  • Internal
    • ID: dec-c-8a3547eb

Similar Sections (Take Policies From)​

SectionSub SectionsInternal RulesPoliciesFlags
💼 PCI DSS v4.0 → 💼 3.1.1 All security policies and operational procedures identified in Requirement 3 are documented, kept up to date, in use, and known to all affected parties.5

Similar Sections (Give Policies To)​

SectionSub SectionsInternal RulesPoliciesFlags
💼 PCI DSS v4.0 → 💼 3.1.1 All security policies and operational procedures identified in Requirement 3 are documented, kept up to date, in use, and known to all affected parties.5

Sub Sections​

SectionSub SectionsInternal RulesPoliciesFlags

Policies (5)​

PolicyLogic CountFlags
📝 Google BigQuery Dataset is not encrypted with Customer-Managed Encryption Key (CMEK) 🟢1🟢 x6
📝 Google BigQuery Table is not encrypted with Customer-Managed Encryption Key (CMEK) 🟢1🟢 x6
📝 Google Dataproc Cluster is not encrypted using Customer-Managed Encryption Key 🟢1🟢 x6
📝 Google GCE Disk for critical VMs is not encrypted with Customer-Supplied Encryption Key (CSEK) 🟢1🟢 x6
📝 Google GCE Instance Confidential Compute is not enabled 🟢1🟢 x6