💼 8.3.2 Strong cryptography is used to render all authentication factors unreadable during transmission and storage on all system components.

• Contextual name: 💼 8.3.2 Strong cryptography is used to render all authentication factors unreadable during transmission and storage on all system components.

• ID: /frameworks/pci-dss-v4.0/08/03/02

• Located in: 💼 8.3 Strong authentication for users and administrators is established and managed.

Description

Empty...

Similar

• Sections
  • /frameworks/pci-dss-v3.2.1/08/02/01
  • /frameworks/pci-dss-v4.0.1/08/03/02

Similar Sections (Take Policies From)

Section	Sub Sections	Internal Rules	Policies	Flags
💼 PCI DSS v3.2.1 → 💼 8.2.1 Using strong cryptography, render all authentication credentials unreadable during transmission and storage on all system components.			6
💼 PCI DSS v4.0.1 → 💼 8.3.2 Strong cryptography is used to render all authentication factors unreadable during transmission and storage on all system components.			6

Similar Sections (Give Policies To)

Section	Sub Sections	Internal Rules	Policies	Flags
💼 PCI DSS v3.2.1 → 💼 8.2.1 Using strong cryptography, render all authentication credentials unreadable during transmission and storage on all system components.			6
💼 PCI DSS v4.0.1 → 💼 8.3.2 Strong cryptography is used to render all authentication factors unreadable during transmission and storage on all system components.			6

Sub Sections

Section	Sub Sections	Internal Rules	Policies	Flags

Policies (6)

Policy	Logic Count	Flags
📝 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 Block Project-Wide SSH Keys is not enabled 🟢	1	🟢 x6
📝 Google GCE Instance Confidential Compute is not enabled 🟢	1	🟢 x6