1. Assessment Phase

  • PCI DSS 3.2.1 Compliance Assessment Execution
20 Credits

PCI DSS 3.2.1 Compliance Report

Overview

This report evaluates AWS configurations against the automated controls mapped to PCI DSS 3.2.1. The assessment covers 38 mapped controls using 43 enabled configuration checks. Framework requirements without automated mappings remain available for manual review. Technical findings support compliance evidence collection and remediation; they do not certify compliance.

Mapped controls

  • PCI DSS 1.2.1: Restrict inbound and outbound traffic to that which is necessary for the cardholder data environment (CDE), and specifically deny all other traffic: No Public S3 Buckets, S3 Block Public Access is Enabled (Account-Level), No Security Group Rules Allowing 0.0.0.0/0 and ::/0 to SSH (TCP 22), No Public EBS Snapshots, Default Security Group No Rules, No Public RDS Instances, No Public RDS Snapshots, Amazon Elasticsearch Domain is in a VPC, No Public Redshift Clusters, No Direct Internet Access for SageMaker Notebook Instance, Database Migration Service Instance Not Public
  • PCI DSS 1.3.1: Implement a DMZ to limit inbound traffic to only system components that provide authorized publicly accessible services, protocols, and ports: No Public S3 Buckets, S3 Block Public Access is Enabled (Account-Level), No Security Group Rules Allowing 0.0.0.0/0 and ::/0 to SSH (TCP 22), No Public EBS Snapshots, No Public RDS Instances, No Public RDS Snapshots, Amazon Elasticsearch Domain is in a VPC, No Public Redshift Clusters, No Direct Internet Access for SageMaker Notebook Instance, Database Migration Service Instance Not Public
  • PCI DSS 1.3.2: Limit inbound internet traffic to IP addresses within the DMZ: No Public S3 Buckets, S3 Block Public Access is Enabled (Account-Level), No Public RDS Instances, No Public RDS Snapshots, Amazon Elasticsearch Domain is in a VPC, No Public Redshift Clusters, No Direct Internet Access for SageMaker Notebook Instance, Database Migration Service Instance Not Public
  • PCI DSS 1.3.4: Do not allow unauthorized outbound traffic from the cardholder data environment to the internet: No Public S3 Buckets, S3 Block Public Access is Enabled (Account-Level), No Public EBS Snapshots, Default Security Group No Rules, No Public RDS Instances, No Public RDS Snapshots, Amazon Elasticsearch Domain is in a VPC, No Public Redshift Clusters, No Direct Internet Access for SageMaker Notebook Instance, Database Migration Service Instance Not Public
  • PCI DSS 1.3.6: Place system components that store cardholder data (such as a database) in an internal network zone, segregated from the DMZ and other untrusted networks: No Public S3 Buckets, S3 Block Public Access is Enabled (Account-Level), No Public RDS Instances, No Public RDS Snapshots, Amazon Elasticsearch Domain is in a VPC, No Public Redshift Clusters, No Direct Internet Access for SageMaker Notebook Instance, Database Migration Service Instance Not Public
  • PCI DSS 2.1: Always change vendor-supplied defaults and remove or disable unnecessary default accounts before installing a system on the network: Default Security Group No Rules, No Access Keys for Root Account
  • PCI DSS 2.2: Develop configuration standards for all system components. Assure that these standards address all known security vulnerabilities and are consistent with industry-accepted system hardening standards: No Access Keys for Root Account
  • PCI DSS 2.2.2: Enable only necessary services, protocols, daemons, etc., as required for the function of the system: No Security Group Rules Allowing 0.0.0.0/0 and ::/0 to SSH (TCP 22)
  • PCI DSS 2.3: Encrypt all nonconsole administrative access using strong cryptography: Application Load Balancer HTTP to HTTPS Redirect Enabled
  • PCI DSS 2.4: Maintain an inventory of system components that are in scope for PCI DSS: Elastic IP Addresses In Use, EC2 Instances Managed by Systems Manager (SSM), No Unused Security Groups
  • PCI DSS 3.4: Render Primary Account Numbers (PAN) unreadable anywhere it is stored (including on portable digital media, backup media, and in logs): S3 Bucket Encryption is Enabled, Ensure that CloudTrail logs are encrypted using KMS, Elasticsearch Storage Encryption is Enabled
  • PCI DSS 3.6.4: Cryptographic keys should be changed once they have reached the end of their cryptoperiod: Ensure that KMS Key Rotation is Enabled
  • PCI DSS 4.1 Use strong cryptography and security protocols to safeguard sensitive cardholder data during transmission over open, public networks: S3 Bucket Encryption in Transit is Enforced, Application Load Balancer HTTP to HTTPS Redirect Enabled
  • PCI DSS 6.2 Ensure that all system components and software are protected from known vulnerabilities by installing applicable vendor supplied security patches. Install critical security patches within one month of release: EC2 Instances Managed by Systems Manager (SSM), EC2 Instances Compliant with SSM Patching Requirements
  • PCI DSS 7.2.1: Establish an access control system(s) for systems components that restricts access based on a user’s need to know, and is set to "deny all" unless specifically allowed. This access control system(s) must include the following: Coverage of all system components: No Access Keys for Root Account, No IAM Principals with Full Administrator Permissions ":", No SSO Permission Set with Full Administrator Permissions ":", No Public S3 Buckets, No Public EBS Snapshots, No Public RDS Instances, No Public RDS Snapshots
  • PCI DSS 8.1.4 Remove/disable inactive user accounts within 90 days: No Unused IAM User Credentials (90 Days), IAM Password Policy Expires Passwords within 90 Days or less, IAM Password Policy Requires Uppercase Characaters, IAM Password Policy Requires Lowercase Characaters, IAM Password Policy Requires Symbols, IAM Password Policy Requires Numbers, IAM Password Policy Requires Minimum Length of 14 Characters, IAM Password Policy Configured to Prevent Password Reuse (24 or Greater)
  • PCI DSS 8.2.1: Using strong cryptography, render all authentication credentials (such as passwords/phrases) unreadable during transmission and storage on all system components: CodeBuild Environment Variables Do No Contain Secrets, CodeBuild GitHub or Bitbucket Use OAuth
  • PCI DSS 8.2.3: Passwords/passphrases must meet the following: Require a minimum length of at least seven characters and Contain both numeric and alphabetic characters: IAM Password Policy Expires Passwords within 90 Days or less, IAM Password Policy Requires Uppercase Characaters, IAM Password Policy Requires Lowercase Characaters, IAM Password Policy Requires Symbols, IAM Password Policy Requires Numbers, IAM Password Policy Requires Minimum Length of 14 Characters, IAM Password Policy Configured to Prevent Password Reuse (24 or Greater)
  • PCI DSS 8.2.4: Change user passwords/passphrases at least once every 90 days: IAM Password Policy Expires Passwords within 90 Days or less, IAM Password Policy Requires Uppercase Characaters, IAM Password Policy Requires Lowercase Characaters, IAM Password Policy Requires Symbols, IAM Password Policy Requires Numbers, IAM Password Policy Requires Minimum Length of 14 Characters, IAM Password Policy Configured to Prevent Password Reuse (24 or Greater)
  • PCI DSS 8.2.5: Do not allow an individual to submit a new password/passphrase that is the same as any of the last four passwords/passphrases he or she has used: IAM Password Policy Expires Passwords within 90 Days or less, IAM Password Policy Requires Uppercase Characaters, IAM Password Policy Requires Lowercase Characaters, IAM Password Policy Requires Symbols, IAM Password Policy Requires Numbers, IAM Password Policy Requires Minimum Length of 14 Characters, IAM Password Policy Configured to Prevent Password Reuse (24 or Greater)
  • PCI DSS 8.3.1: Incorporate multi-factor authentication for all non-console access into the cardholder data environment (CDE) for personnel with administrative access: MFA for Root Account is Enabled, MFA for Users with Console Access, Hardware MFA for Root Account is Enabled
  • PCI DSS 10.1: Implement audit trails to link all access to system components to each individual user: Ensure CloudTrail is Enabled for this Region
  • PCI DSS 10.2.1: Implement automated audit trails for all system components to reconstruct the following events: All individual user accesses to cardholder data: Ensure CloudTrail is Enabled for this Region
  • PCI DSS 10.2.2: Implement automated audit trails for all system components to reconstruct the following events: All actions taken by any individual with root or administrative privileges: Ensure CloudTrail is Enabled for this Region
  • PCI DSS 10.2.3: Implement automated audit trails for all system components to reconstruct the following events: Access to all audit trail: Ensure CloudTrail is Enabled for this Region
  • PCI DSS 10.2.4: Implement automated audit trails for all system components to reconstruct the following events: Invalid logical access attempts: Ensure CloudTrail is Enabled for this Region
  • PCI DSS 10.2.5: Implement automated audit trails for all system components to reconstruct the following events: Use of and changes to identification and authentication mechanisms—including but not limited to creation of new accounts and elevation of privileges—and all changes, additions, or deletions to accounts with root or administrative privileges: Ensure CloudTrail is Enabled for this Region
  • PCI DSS 10.2.6: Implement automated audit trails for all system components to reconstruct the following events: Initialization, stopping, or pausing of the audit logs: Ensure CloudTrail is Enabled for this Region
  • PCI DSS 10.2.7: Implement automated audit trails for all system components to reconstruct the following events: Creation and deletion of system-level objects: Ensure CloudTrail is Enabled for this Region
  • PCI DSS 10.3.1: Record at least the following audit trail entries for all system components for each event: User identification: Ensure CloudTrail is Enabled for this Region
  • PCI DSS 10.3.2: Record at least the following audit trail entries for all system components for each event: Type of event: Ensure CloudTrail is Enabled for this Region
  • PCI DSS 10.3.3: Record at least the following audit trail entries for all system components for each event: Date and time: Ensure CloudTrail is Enabled for this Region, VPC Flow Logs Enabled
  • PCI DSS 10.3.4: Record at least the following audit trail entries for all system components for each event: Success or failure indication: Ensure CloudTrail is Enabled for this Region, VPC Flow Logs Enabled
  • PCI DSS 10.3.5 Verify origination of event is included in log entries: Ensure CloudTrail is Enabled for this Region, VPC Flow Logs Enabled
  • PCI DSS 10.3.6 Verify identity or name of affected data, system component, or resources is included in log entries: Ensure CloudTrail is Enabled for this Region, VPC Flow Logs Enabled
  • PCI DSS 10.5.2: Protect audit trail files from unauthorized modifications: Ensure that CloudTrail Log File Validation is Enabled, Ensure that AWS Config is Enabled, PCI DSS Compliance Monitoring Standard Enabled
  • PCI DSS 11.4 Use intrusion-detection and/or intrusion-prevention techniques to detect and/or prevent intrusions into the network: Amazon GuardDuty is Enabled
  • PCI DSS 11.5: Deploy a change-detection mechanism to alert personnel to unauthorized modification of critical system files, configuration files, or content files; and configure the software to perform critical file comparisons at least weekly: Ensure that AWS Config is Enabled

The report includes actionable findings and remediation guidance for supported checks.