💼 1.3.6 Place system components that store cardholder data in an internal network zone, segregated from the DMZ and other untrusted networks.

• Contextual name: 💼 1.3.6 Place system components that store cardholder data in an internal network zone, segregated from the DMZ and other untrusted networks.
• ID: /frameworks/pci-dss-v3.2.1/01/03/06
• Located in: 💼 1.3 Prohibit direct public access between the Internet and any system component in the cardholder data environment.

Description

Empty...

Similar

• Sections
  • /frameworks/pci-dss-v4.0/01/04/04
  • /frameworks/aws-fsbp-v1.0.0/dms/01
  • /frameworks/aws-fsbp-v1.0.0/emr/01
  • /frameworks/aws-fsbp-v1.0.0/es/02
  • /frameworks/aws-fsbp-v1.0.0/opensearch/02
  • /frameworks/aws-fsbp-v1.0.0/rds/01
  • /frameworks/aws-fsbp-v1.0.0/rds/02
  • /frameworks/aws-fsbp-v1.0.0/redshift/01
  • /frameworks/aws-fsbp-v1.0.0/s3/01
  • /frameworks/aws-fsbp-v1.0.0/s3/02
  • /frameworks/aws-fsbp-v1.0.0/s3/03
  • /frameworks/aws-fsbp-v1.0.0/sagemaker/01
• Internal
  • ID: dec-c-a91acde2

Similar Sections (Take Policies From)

Section	Sub Sections	Internal Rules	Policies	Flags
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [DMS.1] Database Migration Service replication instances should not be public		1	1
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EMR.1] Amazon EMR cluster primary nodes should not have public IP addresses
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ES.2] Elasticsearch domains should not be publicly accessible
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Opensearch.2] OpenSearch domains should not be publicly accessible
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.1] RDS snapshot should be private		1	1
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.2] RDS DB Instances should prohibit public access, as determined by the PubliclyAccessible configuration		1	1
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Redshift.1] Amazon Redshift clusters should prohibit public access
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [S3.1] S3 general purpose buckets should have block public access settings enabled			1
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [S3.2] S3 general purpose buckets should block public read access
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [S3.3] S3 general purpose buckets should block public write access
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [SageMaker.1] Amazon SageMaker AI notebook instances should not have direct internet access
💼 PCI DSS v4.0 → 💼 1.4.4 System components that store cardholder data are not directly accessible from untrusted networks.			6

Similar Sections (Give Policies To)

Section	Sub Sections	Internal Rules	Policies	Flags
💼 PCI DSS v4.0 → 💼 1.4.4 System components that store cardholder data are not directly accessible from untrusted networks.			6

Sub Sections

Section	Sub Sections	Internal Rules	Policies	Flags

Policies (6)

Policy	Logic Count	Flags
📝 AWS DMS Replication Instance is publicly accessible 🟢	1	🟢 x6
📝 AWS EC2 Auto Scaling Group behind ELB assigns public IP to instances 🟢	1	🟢 x6
📝 AWS RDS Instance is publicly accessible and in an unrestricted public subnet 🟢	1	🟢 x6
📝 AWS RDS Snapshot is publicly accessible 🟢	1	🟢 x6
📝 AWS S3 Bucket is not configured to block public access 🟢	1	🟢 x6
📝 AWS VPC Subnet Map Public IP On Launch is enabled 🟢	1	🟢 x6