How to make your infrastructure compliant with PCI-DSS on AWS

A few hours ago Google announced that Google Cloud Platform is now certified for compliance with PCI-DSS. Payment Card Industry – Data Security Standard are security standards built by the Payment Card Industry Council to minimize the credit card frauds. These standards are applicable to organizations who deal with payment cards including credit cards and debit cards and have to ensure that cardholder’s data is completely protected from misuse of their personal information. Compliance with this standard enables customers to hold, process, or exchange cardholder information from any branded credit card.
Amazon Web Services works upon a shared security responsibility model where AWS responsibility is to secure the underlying infrastructure and it is your responsibility to secure any connection made to and any data put upon that infrastructure. For example, it is AWS’s responsibility to ensure security of their physical infrastructure, facilities, virtual infrastructure while when it is client’s responsibility when it comes to OS patching, data encryption, and of course the application itself.
PCI-DSS on AWS
AWS has already achieved PCI-DSS compliance for shared hosting providers and has successfully validated for Level-1 service provider under PCI-DSS version 3.0. In this post, we will see how you can achieve PCI-DSS compliance for your infrastructure on top of AWS. In any case, you should always ask for an independent Quality Security Assessor (QSA) to validate that your environment is PCI-DSS compliant. Nevertheless, the following 12-item checklist can really help you harden your infrastructure and protect your customers from frauds.

Make your application compliant with PCI-DSS on AWS: a 12-items checklist

1- Install and Maintain a Firewall configuration to protect cardholder data

  • Ensure your environment is configured under Virtual Private Cloud (VPC) where components are segregated into public and private subnets, the former acting as DMZ zones.
  • Ensure all critical data (like cardholder data) is stored in private subnets, not directly accessible from the Internet.
  • Use a correct combination of security groups and network ACLs.
  • Limit access to critical components.
  • Ensure that along with ingress and egress rules for security groups and network ACLs are also controlled for critical components.
  • Use Unified Threat Management (UTM) tools in DMZ zones as an additional layer of security.
  • Enable a formal process of approval to all changes made to network configuration, security groups, network ACLs, etc.

2- Do not use vendor-supplied defaults for system passwords and other security parameters

  • One primary function per instance, that is: using a single instance for multiple functions (like web server, plus a SFTP, plus a database server, etc) lowers the security level for your environment. The functions with lower security levels will introduce security weaknesses for other functions.
  • Remove unwanted packages, services and scripts from your instances.
  • Enable additional security measures on required services like passphrases on SSH key pairs or implement passwords for restarting services.

3- Protect stored cardholder data

  • Encrypt Cardholders Data at rest:
    • If cardholder data is stored on a database on EC2, client can leverage on full disk encryption to encrypt the data. There are multiple tools available on AWS marketplace which helps us to encrypt root and additional EBS volumes.
    • If cardholder data is stored on a database on RDS, client can either leverage on transparent data encryption (TDE) or encrypt data over SQL queries. Oracle and SQL server on RDS supports transparent data encryption. If you are using MySQL or PostgreSQL, you have to rely on SQL queries to encrypt data.
  • Ensure only minimal required cardholder data is stored.
  • Define policies for sensitive data retention period and processes for secure deletion of sensitive data.
  • Rotate encryption keys and store at fewest possible locations.
  • There are multiple ways to store your encryption keys:
    • using key-encrypting keys – do it yourself
    • rely on AWS partner solutions on AWS marketplace
    • use the recently launched AWS Key Management service which integrates with S3, EBS and Redshift
    • use AWS CloudHSM
  • Limit cardholder’s data access to necessary individuals only.

4- Encrypt transmission of cardholder data across open, public networks

  • It is important to encrypt sensitive information during transmission over public networks. To enable secure transmission over public networks, you need to use the appropriate certificates on EC2 instances or ELB.
  • AWS Elastic Load Balancers provides support for SSL certificates which allow you to perform SSL termination at load balancing layer.

5- Maintain a Vulnerability Management Program

  • Configure anti-virus softwares on EC2 instances and ensure all of them are timely updated.
  • Use vulnerability scanners in your AWS environment. They help you to prepare for PCI-DSS audits too.

6- Develop and Maintain secure systems and applications

  • Ensure all security patches are reviewed, tested and timely applied on your EC2 instances and other AWS resources.
  • Keep looking at AWS related security bulletins.
  • Develop your internal and external software’s according to PCI-DSS guidelines.
  • It is a best practice to segregate your development, staging and production environment.
  • Use IAM groups, roles and users. Ensure there are no test IAM users.
  • Enable MFA for IAM users with strong password policy.
  • Rotate IAM users access key and secret access key on regular intervals.
  • Enable cloudtrail logs and integrate them with cloudwatch. Setup alerts on cloudtrail activity. For example, send an alert email for failed user login after 3 attempts.
  • If you are serving web application, ensure common coding vulnerabilities (SQL injection, Cross site scripting, directory traversal etc) are taken care at application level or use a web application firewall in front of your web servers.
  • Any changes made to your environment has to be approved and documented.
  • Perform regular security audit of your environment.
  • Avoid manual deployment. Leverage on automation.

7- Restrict access to cardholders data

  • Use strict IAM user policies – limit AWS services access to individuals whose job requires such access.
  • If your organization supports SAML, you can enable single sign-on (SSO) and let users of your organization directly authenticate to AWS management console without having IAM identities.

8- Identify and authenticate access to system components

  • Ensure that everyone (even administrators) access AWS management console via IAM accounts. Root account credentials shouldn’t be used in any case.
  • Enable two factor authentication for AWS accounts. AWS has support for virtual and hardware MFA devices. For virtual MFA devices, you need to install apps on your mobile phone. It supports iPhone, Android, Windows and Blackberry phones.
  • There shouldn’t be any shared credentials. Assign unique IDs to individuals. This holds true for IAM accounts and EC2 instances.
  • Build production ready AMI’s and launch them without key pairs. This way no one will be able to login into your instances.

9- Restrict physical access to cardholder’s data

  • AWS is already PCI-DSS compliant, so that removes the burden of physically securing your cardholder’s data. No action needed here.

10- Regularly monitor and test networks

  • Perform regular audit of your cloudtrail logs to identify login details, creation and deletion of resources etc.
  • Deploy intrusion detection and prevention systems which helps us to monitor instance login details, security events, file integrity, change detection etc.
  • Ensure all instances and resources are in same time zone and synchronized with the same NTP server.

11- Regularly test security systems and processes

  • Perform vulnerability scanning, penetration testing, file integrity monitoring, log inspection, etc. on your environment at regular intervals. It is necessary to inform AWS before performing penetration testing.
  • Perform third party audit of your environment.

12- Maintain a policy that addresses information security for all personnel

  • All security policies should be documented properly and pass to individuals.
  • AWS inventory, login information, resource details should be regularly updated.
  • Implement incident response plan incase of security breach. A 24×7 monitoring team can help you to immediately respond to alerts.

Written by

Head of Managed Services at REAN Cloud. Before joining REAN Cloud, I was CEO and Founder of StraightArc Solutions which was later acquired by REAN Cloud.I started my career working on cloud computing. Loves to talk about DevOps, System Administration, Scalability, High Availability, Disaster Recovery and Cloud Security. Apart from work, I love to meet people, travel and watch sports.

Related Posts

— November 28, 2018

Two New EC2 Instance Types Announced at AWS re:Invent 2018 – Monday Night Live

Let’s look at what benefits these two new EC2 instance types offer and how these two new instances could be of benefit to you. Both of the new instance types are built on the AWS Nitro System. The AWS Nitro System improves the performance of processing in virtualized environments by...

Read more
  • AWS
  • EC2
  • re:Invent 2018
— November 21, 2018

Google Cloud Certification: Preparation and Prerequisites

Google Cloud Platform (GCP) has evolved from being a niche player to a serious competitor to Amazon Web Services and Microsoft Azure. In 2018, research firm Gartner placed Google in the Leaders quadrant in its Magic Quadrant for Cloud Infrastructure as a Service for the first time. In t...

Read more
  • AWS
  • Azure
  • Google Cloud
Khash Nakhostin
— November 13, 2018

Understanding AWS VPC Egress Filtering Methods

Security in AWS is governed by a shared responsibility model where both vendor and subscriber have various operational responsibilities. AWS assumes responsibility for the underlying infrastructure, hardware, virtualization layer, facilities, and staff while the subscriber organization ...

Read more
  • Aviatrix
  • AWS
  • VPC
— November 10, 2018

S3 FTP: Build a Reliable and Inexpensive FTP Server Using Amazon’s S3

Is it possible to create an S3 FTP file backup/transfer solution, minimizing associated file storage and capacity planning administration headache?FTP (File Transfer Protocol) is a fast and convenient way to transfer large files over the Internet. You might, at some point, have conf...

Read more
  • Amazon S3
  • AWS
— October 18, 2018

Microservices Architecture: Advantages and Drawbacks

Microservices are a way of breaking large software projects into loosely coupled modules, which communicate with each other through simple Application Programming Interfaces (APIs).Microservices have become increasingly popular over the past few years. The modular architectural style,...

Read more
  • AWS
  • Microservices
— October 2, 2018

What Are Best Practices for Tagging AWS Resources?

There are many use cases for tags, but what are the best practices for tagging AWS resources? In order for your organization to effectively manage resources (and your monthly AWS bill), you need to implement and adopt a thoughtful tagging strategy that makes sense for your business. The...

Read more
  • AWS
  • cost optimization
— September 26, 2018

How to Optimize Amazon S3 Performance

Amazon S3 is the most common storage options for many organizations, being object storage it is used for a wide variety of data types, from the smallest objects to huge datasets. All in all, Amazon S3 is a great service to store a wide scope of data types in a highly available and resil...

Read more
  • Amazon S3
  • AWS
— September 18, 2018

How to Optimize Cloud Costs with Spot Instances: New on Cloud Academy

One of the main promises of cloud computing is access to nearly endless capacity. However, it doesn’t come cheap. With the introduction of Spot Instances for Amazon Web Services’ Elastic Compute Cloud (AWS EC2) in 2009, spot instances have been a way for major cloud providers to sell sp...

Read more
  • AWS
  • Azure
  • Google Cloud
— August 23, 2018

What are the Benefits of Machine Learning in the Cloud?

A Comparison of Machine Learning Services on AWS, Azure, and Google CloudArtificial intelligence and machine learning are steadily making their way into enterprise applications in areas such as customer support, fraud detection, and business intelligence. There is every reason to beli...

Read more
  • AWS
  • Azure
  • Google Cloud
  • Machine Learning
— August 17, 2018

How to Use AWS CLI

The AWS Command Line Interface (CLI) is for managing your AWS services from a terminal session on your own client, allowing you to control and configure multiple AWS services.So you’ve been using AWS for awhile and finally feel comfortable clicking your way through all the services....

Read more
  • AWS
Albert Qian
— August 9, 2018

AWS Summit Chicago: New AWS Features Announced

Thousands of cloud practitioners descended on Chicago’s McCormick Place West last week to hear the latest updates around Amazon Web Services (AWS). While a typical hot and humid summer made its presence known outside, attendees inside basked in the comfort of air conditioning to hone th...

Read more
  • AWS
  • AWS Summits
— August 8, 2018

From Monolith to Serverless – The Evolving Cloudscape of Compute

Containers can help fragment monoliths into logical, easier to use workloads. The AWS Summit New York was held on July 17 and Cloud Academy sponsored my trip to the event. As someone who covers enterprise cloud technologies and services, the recent Amazon Web Services event was an insig...

Read more
  • AWS
  • AWS Summits
  • Containers
  • DevOps
  • serverless