AWS Controls for Implementing a DMZ
Using CloudFront and API Gateway for PCI Requirement 1
PCI Requirement 1 has several sub-requirements regarding the implementation of a demilitarized zone (DMZ). These requirements include:
- PCI Requirement 1.1.4 requires “a firewall at each internet connection and between any DMZ and the internal network zone.”
- PCI Requirement 1.3.1 states, “Implement a DMZ to limit inbound traffic to only system components that provide authorized publicly accessible services, protocols, and ports.”
- PCI Requirement 1.3.6 says, “Place system components that store cardholder data in an internal network zone, segregated from the DMZ and other untrusted networks.”
To support compliance for this requirement, AWS provides services such as CloudFront and API Gateway to protect your network and prohibit untrusted networks from accessing your VPC. By using these capabilities from AWS, you are using a PCI-compliant service.
Transcription
The PCI Requirement 1 has a few requirements in there that talk about implementing a DMZ (a demilitarized zone). You can utilize services from AWS such as CloudFront or API Gateway in order to achieve compliance in these areas. It’s about not allowing untrusted networks, such as the public Internet, from accessing your VPC. By implementing these controls that AWS provides to you, you can accomplish these requirements and, actually put those requirements on AWS. AWS goes through their own PCI Data Security Standard assessment every year and these services, such as CloudFront and API Gateway, are assessed as a part of that; so they don’t have to be reassessed as part of your engagement. If you do utilize those controls that they provide to you in order to accomplish those requirements, those requirements become the responsibility of AWS and are not tested as part of your engagement.
Related Videos
AWS Functions to Restrict Database Access
AWS Password Best Practices
AWS Password Expiration Policies
AWS Password Reuse Policy
AWS Tools for Your SDLC
Access Control Using IAM Instance Roles
Assign Access Based on Business Need to Know
Attaching IAM Policies to Groups or Roles
Avoid Use of the Root Account
Basics of Role Assumption
Best Practices for Change Management in AWS
Best Practices for Password Parameters
Cloud Attacks on the Rise
Configuring Network Border Controls
Creating a Data Flow Diagram
Creating a Network Diagram
Define Acceptable Use of Technology Part 1
Defining Resources in IAM Policies
Defining Resources in S3 Bucket Policies
Defining Roles and Responsibilities in AWS
Developing a Process for User Authentication
Disabling Insecure Ports and Protocols
Disabling Unused Credentials
Do All Keys Have Resources Attached?
Documenting a Systems Inventory in AWS
Enabling MFA for All IAM Users
Encrypting Traffic In and Out of AWS
Encryption Decisions for Your Technology Stack
Encryption Opportunities
Encryption for EBS Volumes
Encryption for S3 Buckets
Enforce Separation with Access Controls
Enforcing Strong Encryption in AWS
Enforcing Strong TLS Ciphers
Events that Drive Key Rotation
House Accounts in CloudTrail
How to Attach IAM Policies to Groups or Roles
How to Check MFA in a Credential Report
How to Check Use of the Root Account
How to Configure Encryption for EBS Volumes on Existing EC2 Instances
How to Configure Encryption for EBS Volumes on New EC2 Instances
How to Configure Encryption for RDS
How to Configure Encryption for S3 Buckets
How to Find Administrative Privileges in IAM Policies
How to House Multiple Accounts Within an AWS Organization
How to Modify Password Complexity in a Password Policy
How to Modify Permissions to EBS Snapshots
How to Prevent Password Reuse in a Password Policy
How to Restrict Public Access to S3 Buckets
How to Use S3 Bucket Policies
IAM Policies for Account Authentication
IAM Policies that Address Administrative Privileges
Identifying Unused Credentials in a Credential Report
Industry Best Practices for Configuration Standards
Introduction to AWS Network Firewall
Introduction to Amazon EKS
Introduction to Amazon S3 Access Points
Introduction to IAM Access Analyzer
Key Rotation and Management
Load Balancers Must Require TLS 1.2
MFA for API Calls
Meeting Firewall and Router Configuration Standards
Network Segmentation for AWS
Performing Code Review Prior to Release
Physical Security Responsibilities for AWS
Physical Security Responsibilities for AWS Users
Physical Security Threats for AWS
Prevent Shared, Group, or Generic Accounts in AWS
Preventing Public Accessibility on DB Instances
Preventing Publicly Available CloudTrail Logs
Preventing Publicly Available S3 Buckets
Protecting Web Applications in AWS
Publish and Maintain an Information Security Policy
Quarterly Reviews of Your Security Program
Restricting Access to EBS Snapshots
Reviewing Firewall and Router Configurations
Rotating Access Keys
Route 53 Support for DNSSEC
Secure Code Development in AWS
Support MFA through IAM Policies
Systems Manager Maintenance
The AWS Shared Responsibility Model
Understanding the "Deny All" Function
Using AWS KMS
Using IAM Instance Roles for AWS Resource Access
Using OWASP's Kubernetes Cheat Sheet
Using Prowler to Evaluate AWS Security
Using Systems Manager from a Service-Linked Role
Using TLS 1.2 to Encrypt Data in Transit
