4 stops on the road to PCI compliance for AWS

Netskope

Have you moved PCI cardholder data to Amazon Web Services (AWS)? AWS has been PCI DSS certified for many years but you still need to take steps to ensure the “security in the cloud.” Ultimately, the responsibility for PCI compliance rests on you, not AWS.  

According to the 2018 Cloud Security Report from Cybersecurity Insiders, the top two security control challenges SOCs struggle with most are visibility into infrastructure security (43 percent) and compliance (38 percent). With mounting pressure from regulatory, external, and internal audits, how can you achieve both compliance and security when implementing security controls?

Netskope can tell you instantly what it would take an auditor days to figure out and communicate the information back to you in an easy to understand, visual format.

With various environments and accounts, Netskope can help highlight and remediate any compliance gaps. Fix issues such as overly permissive security group rules and weak password policies, enforce requirements and prove compliance in audits.  Administrators can also create and enforce custom rules that describe unique restrictions and compliance practices in their organizations

In a few easy steps, with Netskope find out if your cloud infrastructure environment is PCI compliant:

Step 1: Grant Netskope API read-only access to the configuration settings of your cloud environment.

Netskope links to your AWS account via API access and pulls the data without any customization from the user.

Step 2: Create and run the Security Assessment policy.

From the main dashboard, select the PCI profile you want to run your assessment on for the specific accounts you want to check. Netskope security checks are mapped to PCI DSS and CIS Foundations Benchmark and will assist you in assessing your environment against these requirements.

Step 3: View your report.

See a customized report with the results of your assessment that tells you if you have met compliance standards. Failed checks are listed by severity level. Further drill into each check for recommended remediation steps to get back into compliance.

Step 4: Share report results with an auditor or internal teams.

Instantly, turn the report into a PDF and send to an auditor.