[Turbot On] PCI Compliance Controls

Evaluate PCI DSS version 3.2.1 compliance for all your AWS accounts.

Turbot includes thousands of prescriptive cloud controls to ensure cloud environments are secure and cost-optimized. These controls quickly detect issues as they occur and instantly correct misconfigurations. Customers often map Turbot controls to their own Governance Risk Compliance (GRC) tools, and use the resulting evidence to prove continuous adherence to internal controls or external standards such as Center for Internet Security (CIS), NIST 800-53, HIPAA, GDPR, SOC2, etc. 

Over the last year Turbot has open-sourced Steampipe.io, a tool that enables cloud engineers to easily query & report across their cloud, code, logs, and more, using the standard language of data: SQL. Steampipe includes thousands of ready-to-use controls and dashboards that deliver insights into your cloud data. These controls and dashboards leverage a suite of plugins that translate cloud APIs into Postgres tables. One of those plugins, by the way, translates the Turbot v5 API into SQL-queryable tables!

Cloud teams have asked Turbot to also include industry standards within the Turbot platform. We started by open-sourcing thousands of compliance controls, and enlisting the Steampipe community to provide feedback and contributions. Based on community feedback, we are now starting to port these control frameworks into Turbot.  Our first addition is the Payment Card Industry Data Security Standard (PCI DSS) v3.2.1 standard for AWS. Note: When mapping to external standards, Turbot leverages either the published industry standard mapping or the mapping provided by each cloud provider. We are excited to add the PCI controls to the platform to complement our existing CIS Controls and AWS, Azure & GCP CIS benchmarks.

This week’s [Turbot On] will look at how to enable PCI controls across all your AWS accounts in Turbot.

Traditional Workflow

There are various cloud-native and 3rd-party tools to evaluate cloud infrastructure PCI compliance. However cloud-native tools generally work with only one cloud provider, and only do periodic scans.  3rd-party tools may support multiple cloud providers, but fall short on benchmark coverage and, again, scan and report only periodically, missing real-time changes in your environment.  These tools often work on a per-account basis, without delivering resource-level granularity. And they are limited in their ability to manage the time-based exceptions that enable you to handle the nuances in your organization.

Get it done with Turbot

In Turbot, PCI guardrails are readily available to control your cloud resource configurations.  These guardrails work similar to others, continuously evaluating adherence as changes to your cloud resources occur.  First, make sure you have the `@turbot/aws-pciv3-2-1` mod installed and any dependent mods installed in your workspace.  Then you can enable PCI through the following Turbot policy in just a few clicks: `AWS > PCI v3.2.1`:

Setting the configuration via our Terraform Provider is just as simple:

After enabling this policy, Turbot will immediately evaluate all applicable resources compliance with PCI.  You can view your controls across services:

Drill further into sub controls of a specific service:

Analyze which specific resources are impacted:

Visualize all the resources primary controls including PCI:

Make it happen

See for yourself on how easy it is to view your PCI requirements across your cloud resources.  If you need any assistance please reach out to Turbot Support, and keep an eye on your inbox for another Turbot post in the near future!

Cheers,

Bob