Define Acceptable Use of Technology Part 1
Supporting PCI Requirement 12.3 in AWS
PCI Requirement 12.3 surrounds usage policies for critical technologies. To be compliant, the PCI DSS stipulates that your usage policies for AWS must require:
- Explicit approval by authorized parties
- Authentication for the use of the technology
- A list of all devices and personnel with access
- A method to accurately and readily determine owner, contact information, and purpose
- Acceptable uses of the technology
- Acceptable network locations for the technologies
- List of company-approved products
- Automatic disconnect of sessions for remote-access technologies after a period of inactivity
- Activation of remote-access technologies for vendors and business partners only when needed
- For personnel accessing cardholder data via remote-access technologies, prohibit the copying, moving, and storage of cardholder data onto local hard drives and removable electronic media
- Protection of the data in accordance with all applicable PCI DSS requirements
AWS says, “Amazon Web Services provides customers the ability to proactively limit the software and technologies in use in their accounts. Customers can use AWS Control Tower with Service Control Policies to manage software deployed in their CDE. AWS Config Managed Rules also offer customers the ability to check for applications not allowed on their AWS Config-managed instances.” Compliance with PCI Requirement 12.3 is a critical part of protecting cardholder data in AWS.
Transcription
When we are taking a look at the PCI Requirement 12, everyone thinks it is about policies. PCI Requirement 12.3 is about policies, but it is also about how you use your equipment. The personal usage policy in PCI Requirement 12.3 defines (or should define) what can and cannot be installed on systems that are part of the cardholder data environment. This process needs to be formalized. There are things like appropriate approvals for devices to go in, appropriate approvals for changes, and authentication or authorization to actually use the technology and install it. The primary deliverable from PCI Requirement 12.3 is a list of critical devices and those who are authorized to use the devices. That list needs to include the stakeholder or owner, their contact information, the purpose of the device, how it is inventoried, and who is authorized to use it.
Related Videos
AWS Controls for Implementing a DMZ
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
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
