Sign In
Explore
AWS
Azure
GCP
Information Security Policy
PCI Assessment
Risk Assessment
SOC 2 Audit
Audit
Start A Scan
Information Security Policy Review
PCI Report Analysis
Risk Assessment Review
SOC 2 Report Analysis
Learn
Contact
Pricing
Sign In
PCI v4.0 - A1.2.1: (Multi-Tenant Service Providers) Ensure Appropriate Logging Is Enabled
Related Videos
10.6.1 – Review Daily All Security Events and Logs of All System Components.mp4
Copy Link
10.6.2 – Review Logs of All Other System Components Based Policies and Risk Management Strategy
Copy Link
10.6.3 –Follow Up Exceptions and Anomalies Identified During the Review Process
Copy Link
AWS Firewall Manager Centralized Logging
Copy Link
AWS Password Best Practices
Copy Link
AWS Password Expiration Policies
Copy Link
AWS Password Reuse Policy
Copy Link
Assign Appropriate Contacts to Essential Roles
Copy Link
Attaching IAM Policies to Groups or Roles
Copy Link
Attributes of Log Data
Copy Link
Audit Trail Review with Kibana, Athena, and GuardDuty
Copy Link
Audit Your Security Groups for Insecure Ports and Protocols
Copy Link
Avoid Use of the Root Account
Copy Link
Basics of Role Assumption
Copy Link
Change-Detection Solutions in AWS
Copy Link
Configure Activity Log Container Access to Private
Copy Link
Configure Storage Accounts to Use Customer Managed Keys
Copy Link
Create Activity Log Alert for Delete SQL Server Firewall
Copy Link
Create an Activity Log Alert for Create or Update Public IP Address
Copy Link
Create an Activity Log Alert for Delete Security Solution
Copy Link
Defining Resources in IAM Policies
Copy Link
Disabling Insecure Ports and Protocols
Copy Link
Disabling Unused Credentials
Copy Link
Do All Keys Have Resources Attached?
Copy Link
Do Not Use API Keys at the Project Level
Copy Link
Do Not Use RSASHA1 for DNSSEC Key-Signing Keys
Copy Link
Do You Have to Do PCI?
Copy Link
Enable Access Transparency to Monitor Google Cloud Engineer Access
Copy Link
Enable Alerting for Cloud Storage IAM Permission Changes
Copy Link
Enable Bucket Lock to Protect Sink Destinations from Modification
Copy Link
Enable Cloud Audit Logging Across Your Project
Copy Link
Enable Cloud DNS Logging for VPC Networks
Copy Link
Enable DNSSEC to Protect DNS Protocols
Copy Link
Enable Logging of Read, Write, and Delete Requests for Blob Service
Copy Link
Enable Logging of Read, Write, and Delete Requests for Table Service
Copy Link
Enable Multi-Factor Authentication for Non-Service Accounts
Copy Link
Enable Queue Storage Logging for Read Write Access
Copy Link
Enable VPC Flow Logs for Every Subnet
Copy Link
Enabling AWS Config in All Regions
Copy Link
Enabling MFA for All IAM Users
Copy Link
Encrypt Dataproc Cluster Using Customer Managed Encryption Key
Copy Link
Encrypted Cardholder Data and Scope
Copy Link
Enforce Separation of Duties When Assigning KMS Related Roles
Copy Link
Enforce Separation of Duties When Assigning Service Account Roles
Copy Link
Ensure Alerts Exist for Project Ownership Changes
Copy Link
Ensure Alerts are Received for VPC Network Changes
Copy Link
Ensure Corporate Login Credentials are Used
Copy Link
Ensure Diagnostic Setting Captures Appropriate Categories
Copy Link
Ensure KMS Cryptokeys Are Not Publicly Accessible
Copy Link
Ensure Log Alert Exists for Create or Update Network Security Group
Copy Link
Ensure Logging for AppServiceHTTPLogs
Copy Link
Ensure Network Security Group Flow Logs Are Sent to Log Analytics
Copy Link
Ensure No Weak SSL Cipher Suites Are Permitted
Copy Link
Ensure Service Accounts Can't Access Admin Privileges
Copy Link
Ensure That a Diagnostic Setting Is Enabled
Copy Link
Ensure an Activity Log Alert Exists for Delete Public IP Address
Copy Link
Ensure to Restrict SSH Access from the Internet
Copy Link
Ensuring Role Assumption is Logged
Copy Link
Establish a Log Metric Alert for Configuration Changes in SQL Instances
Copy Link
Exclusively Use GCP-Managed Service Account Keys
Copy Link
Filters and Alarms in CloudWatch
Copy Link
Generate Log Metric Alerts for Custom Role Changes
Copy Link
Getting Started with PCI Compliance
Copy Link
Historically View Project Resources in Asset Inventory
Copy Link
House Accounts in CloudTrail
Copy Link
How Do You Scope a PCI DSS Assessment?
Copy Link
How to Edit Inbound Traffic Rules for Default Security Groups
Copy Link
IAM Policies that Address Administrative Privileges
Copy Link
Identify Unrestricted Access to Ports for Security Groups
Copy Link
Identify if EC2 Instances Are Directly Connected to the Internet
Copy Link
Introduction to Amazon CloudWatch
Copy Link
Leverage Google Cloud Engineers by Granting Access Approval
Copy Link
Limiting PCI DSS Scope
Copy Link
Log and Retain All Relevant Activities
Copy Link
Logging Tools in AWS
Copy Link
MFA for API Calls
Copy Link
Migrate Away from RSASHA1 for DNSSEC Zone-Signing Keys
Copy Link
Monitor Your Environment with Network Watcher
Copy Link
Monitor for "Delete Network Security Groups" Through Log Alerts
Copy Link
PCI Compliance One Step at a Time
Copy Link
PCI DSS Assessment Scope: Identify All Other People Processes and Technology
Copy Link
PCI DSS Assessment Scope: Identify Cardholder Data Flows
Copy Link
PCI DSS Assessment Scope: Identify People and Processes
Copy Link
PCI DSS Assessment Scope: Identify Technology
Copy Link
PCI DSS Assessment Scope: Identify Third Parties
Copy Link
PCI Requirement 10 – Track and Monitor all Access to Network Resources and Cardholder Data
Copy Link
PCI Requirement 10.1 – Implement Audit Trails to Link all Access to System Components
Copy Link
PCI Requirement 10.2 – Implement Automated Audit Trails for all System Components
Copy Link
PCI Requirement 10.2.1 – All Individual User Accesses to Cardholder Data
Copy Link
PCI Requirement 10.2.2 – All Actions Taken by Any Individual with Root or Administrative Privileges
Copy Link
PCI Requirement 10.2.3 – Access to All Audit Trails
Copy Link
PCI Requirement 10.2.4 – Invalid Logical Access Attempts.mp4
Copy Link
PCI Requirement 10.2.5 – Use of and Changes to Identification Accounts with Root Privileges
Copy Link
PCI Requirement 10.2.6 – Initialization, Stopping, or Pausing of the Audit Logs
Copy Link
PCI Requirement 10.2.7 – Creation and Deletion of System-Level Objects
Copy Link
PCI Requirement 10.3 – Record at Least the Following Audit Trail Entries for All System Components
Copy Link
PCI Requirement 10.3.1 – User Identification
Copy Link
PCI Requirement 10.3.2 – Type of Event
Copy Link
PCI Requirement 10.3.3 – Date and Time
Copy Link
PCI Requirement 10.3.4 – Success or Failure Indication
Copy Link
PCI Requirement 10.3.5 – Origination of Event
Copy Link
PCI Requirement 10.3.6 – Identity or Name of Affected Data, System Component, or Resource
Copy Link
PCI Requirement 10.4 – Using Time-Synchronization Technology, Synchronize All Critical Systems
Copy Link
PCI Requirement 10.4.1 – Critical Systems Have the Correct and Consistent Time
Copy Link
PCI Requirement 10.4.2 – Time Data is Protected
Copy Link
PCI Requirement 10.4.3 – Time Settings Are Received from Industry-Accepted Time Sources
Copy Link
PCI Requirement 10.5 – Secure Audit Trails so They Cannot Be Altered
Copy Link
PCI Requirement 10.5.1 – Limit Viewing of Audit Trails to Those with a Job-Related Need
Copy Link
PCI Requirement 10.5.2 – Protect Audit Trail Files from Unauthorized Modifications
Copy Link
PCI Requirement 10.5.3 – Promptly Back Up Audit Trail Files to a Centralized Log Server
Copy Link
PCI Requirement 10.5.4 – Write Logs for External-Facing Technologies onto a Secure Device
Copy Link
PCI Requirement 10.5.5 – Use File-Integrity Monitoring or Change-Detection Software on Logs
Copy Link
PCI Requirement 10.6 – Review Logs and Security Events for All System Components
Copy Link
PCI Requirement 10.7 – Retain Audit Trail History for at Least One Year, with Three Months Available
Copy Link
PCI Requirement 10.8 –Implement a Process for the Detection of Failures of Critical Control Systems
Copy Link
PCI Requirement 10.8.1 –Respond to Failures of Any Critical Security Controls in a Timely Manner
Copy Link
PCI v3.2.1 vs. PCI 4.0: What's Changed?
Copy Link
PCI v4.0 - 1.1.1: Requirement 1 Policies and Procedures Are In Place
Copy Link
PCI v4.0 - 1.1.2: Requirement 1 Roles and Responsibilities Are In Place
Copy Link
PCI v4.0 - 1.2.1: Configuration Standards for Network Security Controls Are Implemented
Copy Link
PCI v4.0 - 1.2.2: Changes to Network Connections and Security Controls Are Approved
Copy Link
PCI v4.0 - 1.2.3: Maintain an Accurate Network Diagram
Copy Link
PCI v4.0 - 1.2.4: Maintain an Accurate Data-Flow Diagram
Copy Link
PCI v4.0 - 1.2.5: All Services Protocols and Ports Are Identified and Approved
Copy Link
PCI v4.0 - 1.2.6: Security Features Are Implemented on All Services Protocols and Ports
Copy Link
PCI v4.0 - 1.2.7: Network Security Controls Configurations Are Reviewed Regularly
Copy Link
PCI v4.0 - 1.2.8: Keep Configuration Files for Network Security Controls Secure and Consistent
Copy Link
PCI v4.0 - 1.3.1: Inbound Cardholder Data Environment Traffic Is Restricted
Copy Link
PCI v4.0 - 1.3.2: Outbound Traffic from the Cardholder Data Environment Is Restricted
Copy Link
PCI v4.0 - 1.3.3: Implement a Network Security Control Between Wireless Network and Wired CDE Segments
Copy Link
PCI v4.0 - 1.4.1: Network Security Controls Are Installed Between Trusted and Untrusted Networks
Copy Link
PCI v4.0 - 1.4.2: Inbound Traffic From Untrusted to Trusted Networks Is Restricted
Copy Link
PCI v4.0 - 1.4.3: Anti-Spoofing Measures Are In Place
Copy Link
PCI v4.0 - 1.4.4: Ensure Stored Cardholder Data Is Not Accessible from Untrusted Networks
Copy Link
PCI v4.0 - 1.4.5: Internal IP Addresses And Routing Information Is Only Disclosed to Authorized Parties
Copy Link
PCI v4.0 - 1.5.1: Security Controls Are Implemented on Any Computing Devices
Copy Link
PCI v4.0 - 10.1.1: Requirement 10 Policies and Procedures Are In Place
Copy Link
PCI v4.0 - 10.1.2: Requirement 10 Roles and Responsibilities Are In Place
Copy Link
PCI v4.0 - 10.2.1.1: Logs Capture Individual User Access to Cardholder Data
Copy Link
PCI v4.0 - 10.2.1.2: Logs Capture All Actions by Someone with Administrative Access
Copy Link
PCI v4.0 - 10.2.1.3: Logs Capture All Access to Audit Logs
Copy Link
PCI v4.0 - 10.2.1.4: Logs Capture All Invalid Logical Access Attempts
Copy Link
PCI v4.0 - 10.2.1.5: Logs Capture All Changes to Identification and Authentication Credentials
Copy Link
PCI v4.0 - 10.2.1.6: Logs Capture All Initialization Starting Stopping and Pausing of Audit Logs
Copy Link
PCI v4.0 - 10.2.1.7: Logs Capture All Creation and Deletion of System Level Objects
Copy Link
PCI v4.0 - 10.2.1: Audit Logs Are Enabled and Active
Copy Link
PCI v4.0 - 10.2.2: Audit Logs Record All Appropriate Information for Each Auditable Event
Copy Link
PCI v4.0 - 10.3.1: Read Access to Audit Log Files Is Limited
Copy Link
PCI v4.0 - 10.3.2: Audit Log Files Are Protected from Modification
Copy Link
PCI v4.0 - 10.3.3: Audit Log Files Are Properly Backed Up
Copy Link
PCI v4.0 - 10.3.4: Utilize File Integrity Monitoring or Change-Detection Tools on Audit Logs
Copy Link
PCI v4.0 - 10.4.1 & 10.4.1.1: Perform Specific Daily Audit Log Reviews Using Automated Mechanisms
Copy Link
PCI v4.0 - 10.4.2 & 10.4.2.1: Periodically Perform Other Audit Log Reviews
Copy Link
PCI v4.0 - 10.4.3: Address Identified Exceptions and Anomalies
Copy Link
PCI v4.0 - 10.5.1: Retain Audit Log History for At Least 12 Months
Copy Link
PCI v4.0 - 10.6.1: System Clocks and Time Are Synchronized
Copy Link
PCI v4.0 - 10.6.2: Systems Are Configured to the Correct and Consistent Time
Copy Link
PCI v4.0 - 10.6.3: Time Synchronization Settings and Data Are Protected
Copy Link
PCI v4.0 - 10.7.1: (Service Providers) Critical Security Control System Failures Are Addressed
Copy Link
PCI v4.0 - 10.7.2: Failure of Critical Security Control Systems Are Handled Appropriately
Copy Link
PCI v4.0 - 10.7.3: Failure of Any Critical Security Controls Are Promptly Addressed
Copy Link
PCI v4.0 - 11.1.1: Requirement 11 Polices and Procedures Are In Place
Copy Link
PCI v4.0 - 11.1.2: Requirement 11 Roles and Responsibilities Are In Place
Copy Link
PCI v4.0 - 11.2.1: Wireless Access Points Are Properly Managed
Copy Link
PCI v4.0 - 11.2.2: Maintain Inventory of All Authorized Wireless Access Points
Copy Link
PCI v4.0 - 11.3.1.1: Manage Non-High Risk and Non-Critical Vulnerabilities Appropriately
Copy Link
PCI v4.0 - 11.3.1.2: Use Authenticated Vulnerability Scanning Tools for Internal Scans
Copy Link
PCI v4.0 - 11.3.1.3: Perform Internal Scans After Significant Changes
Copy Link
PCI v4.0 - 11.3.1: Perform Internal Vulnerability Scans Frequently
Copy Link
PCI v4.0 - 11.3.2.1: Perform External Scans After Significant Changes
Copy Link
PCI v4.0 - 11.3.2: Perform External Vulnerability Scans Frequently
Copy Link
PCI v4.0 - 11.4.1: Define Document and Implement a Penetration Testing Methodology
Copy Link
PCI v4.0 - 11.4.2: Regularly Perform Internal Penetration Testing
Copy Link
PCI v4.0 - 11.4.3: Regularly Perform External Penetration Testing
Copy Link
PCI v4.0 - 11.4.4: Correct Vulnerabilities Found in Penetration Testing
Copy Link
PCI v4.0 - 11.4.5 & 11.4.6: Test the Effectiveness of Segmentation Controls Regularly
Copy Link
PCI v4.0 - 11.4.7: Multi-Tenant Service Providers Support Customers for External Penetration Testing
Copy Link
PCI v4.0 - 11.5.1.1: Detect Alert and Address Covert Malware Communication Channels
Copy Link
PCI v4.0 - 11.5.1: Implement Intrusion Detection and or Prevention Techniques
Copy Link
PCI v4.0 - 11.5.2: Deploy a Change-Detection Mechanism
Copy Link
PCI v4.0 - 11.6.1: Change-Detection or Tamper-Detection Mechanisms Are Deployed on Payment Pages
Copy Link
PCI v4.0 - 12.1.1: Have and Utilize an Information Security Policy
Copy Link
PCI v4.0 - 12.1.2: Review and Update Your Information Security Policy Regularly
Copy Link
PCI v4.0 - 12.1.3: Ensure Your Information Security Policy Defines Roles and Responsibilities
Copy Link
PCI v4.0 - 12.1.4: Formally Assign Information Security Responsibility to a CISO
Copy Link
PCI v4.0 - 12.10.1: Establish a Comprehensive Incident Response Plan
Copy Link
PCI v4.0 - 12.10.2: Regularly Review the Incident Response Plan
Copy Link
PCI v4.0 - 12.10.3: Ensure Specific Security Personnel Are Available for Incident Response
Copy Link
PCI v4.0 - 12.10.4.1: Utilize the Targeted Risk Analysis to Determine Incident Response Training Frequency
Copy Link
PCI v4.0 - 12.10.4: Appropriately Train Incident Response Personnel
Copy Link
PCI v4.0 - 12.10.5: Include Monitoring and Responding to Alerts in the Incident Response Plan
Copy Link
PCI v4.0 - 12.10.6: Modify the Incident Response Plan as Needed
Copy Link
PCI v4.0 - 12.10.7: Implement Incident Response Procedures Upon Detection of Stored Primary Account Numbers
Copy Link
PCI v4.0 - 12.2.1: Acceptable Use Policies Are Documented and Implemented
Copy Link
PCI v4.0 - 12.3.1: Use Targeted Risk Analyses to Support Flexible Testing
Copy Link
PCI v4.0 - 12.3.2: Perform Targeted Risk Analyses for Customized Approach
Copy Link
PCI v4.0 - 12.3.3: Document and Review Cryptographic Cipher Suites and Protocols in Use
Copy Link
PCI v4.0 - 12.3.4: Review Software and Hardware Technologies
Copy Link
PCI v4.0 - 12.4.1: Service Providers Must Establish Protections for Card Holder Data
Copy Link
PCI v4.0 - 12.4.2.1: Document the Reviews Performed in Requirement 12.4.2
Copy Link
PCI v4.0 - 12.4.2: Ensure Personnel Are Performing Their Duties
Copy Link
PCI v4.0 - 12.5.1: Maintain an Inventory of System Components That Are in Scope
Copy Link
PCI v4.0 - 12.5.2.1: Service Providers Must Document and Confirm Scope Frequently
Copy Link
PCI v4.0 - 12.5.2: Document and Confirm Scope Regularly
Copy Link
PCI v4.0 - 12.5.3: Review Scope After Significant Changes to Organizational Structure
Copy Link
PCI v4.0 - 12.6.1: Implement Formal Security Awareness Training
Copy Link
PCI v4.0 - 12.6.2: Review Your Information Security Awareness Program Regularly
Copy Link
PCI v4.0 - 12.6.3.1: Include Specific Threats and Vulnerabilities in Information Security Awareness Trainings
Copy Link
PCI v4.0 - 12.6.3.2: Include Acceptable Use Policies in Security Awareness Trainings
Copy Link
PCI v4.0 - 12.6.3: Hold Information Security Awareness Trainings Regularly
Copy Link
PCI v4.0 - 12.7.1: Screen Personnel Who Have Access to the Cardholder Data Environment
Copy Link
PCI v4.0 - 12.8.1: Keep Record of Third-Party Service Providers that Account Data Is Shared With
Copy Link
PCI v4.0 - 12.8.2: Maintain Written Requirements with Third-Party Service Providers
Copy Link
PCI v4.0 - 12.8.3: Establish a Process for Engaging with Third-Party Service Providers
Copy Link
PCI v4.0 - 12.8.4: Monitor the PCI DSS Compliance of Third-Party Service Providers
Copy Link
PCI v4.0 - 12.8.5: Detail Responsibilities Held by Third-Party Service Providers
Copy Link
PCI v4.0 - 12.9.1: Acknowledge Account Security Responsibilities
Copy Link
PCI v4.0 - 12.9.2: Provide Compliance Information to Clients Upon Request
Copy Link
PCI v4.0 - 2.1.1: Requirement 2 Policies and Procedures Are In Place
Copy Link
PCI v4.0 - 2.1.2: Requirement 2 Roles and Responsibilities Are In Place
Copy Link
PCI v4.0 - 2.2.1: Configuration Standards Are Developed Implemented and Maintained
Copy Link
PCI v4.0 - 2.2.2: Vendor Default Accounts Are Managed Properly
Copy Link
PCI v4.0 - 2.2.3: Primary Functions Requiring Different Security Levels Are Managed
Copy Link
PCI v4.0 - 2.2.4: Unnecessary Functionalities Are Removed or Disabled
Copy Link
PCI v4.0 - 2.2.5: Insecure Daemons Protocols and Services Have Additional Security Features
Copy Link
PCI v4.0 - 2.2.6: System Security Parameters Are Configured to Prevent Misuse
Copy Link
PCI v4.0 - 2.2.7: Non-Console Administrative Access Is Encrypted
Copy Link
PCI v4.0 - 2.3.1: Wireless Vendor Defaults Are Changed or Confirmed to Be Secure
Copy Link
PCI v4.0 - 2.3.2: Wireless Encryption Keys Are Changed Accordingly
Copy Link
PCI v4.0 - 3.1.1 & 3.1.2: Have Requirement 3 Policies and Procedures Assigned and In Place
Copy Link
PCI v4.0 - 3.2.1: Only Retain the Minimum Account Data Needed
Copy Link
PCI v4.0 - 3.3.1, 3.3.1.1, 3.3.1.2, & 3.3.1.3: Do Not Retain Any Sensitive Authentication Data
Copy Link
PCI v4.0 - 3.3.2: Encrypt Sensitive Authentication Data If Retained for Any Length of TIme
Copy Link
PCI v4.0 - 3.3.3: (Issuers Only) Store Only the Minimum Amount of Sensitive Authentication Data Needed
Copy Link
PCI v4.0 - 3.4.1: Mask Displayed Primary Account Number
Copy Link
PCI v4.0 - 3.4.2: Do Not Allow Primary Account Numbers to Be Copied When Using Remote Access
Copy Link
PCI v4.0 - 3.5.1.1: Ensure All Hashes Are Keyed
Copy Link
PCI v4.0 - 3.5.1.2: Correctly Utilize Disk-Level Encryption of Primary Account Numbers
Copy Link
PCI v4.0 - 3.5.1.3: Ensure Disk-Level Encryption Meets Requirements
Copy Link
PCI v4.0 - 3.5.1: Store Primary Account Numbers Appropriately
Copy Link
PCI v4.0 - 3.6.1.1: (Service Providers) Document and Describe the Cryptographic Architecture
Copy Link
PCI v4.0 - 3.6.1.3 & 3.6.1.4: Use Fewest Possible Custodians and Locations for Cryptographic Keys
Copy Link
PCI v4.0 - 3.6.1: Use Fewest Possible Number of Key Custodians Locations and Forms
Copy Link
PCI v4.0 - 3.7.1: Utilize Procedures to Generate Strong Cryptographic Keys
Copy Link
PCI v4.0 - 3.7.2 & 3.7.3: Implement Policies and Procedures to Safely Distribute and Store Keys
Copy Link
PCI v4.0 - 3.7.4: Define Cryptoperiods in Policies and Procedures for Key Management
Copy Link
PCI v4.0 - 3.7.5: Properly Retire Replace or Destroy Keys When Appropriate
Copy Link
PCI v4.0 - 3.7.6: Use Split Knowledge and Dual Control for Manual Cleartext Key Management
Copy Link
PCI v4.0 - 3.7.7: Do Not Allow Unauthorized Key Substitution
Copy Link
PCI v4.0 - 3.7.8: Require Key Custodians to Acknowledge and Accept Their Responsibilities
Copy Link
PCI v4.0 - 4.1.1 & 4.1.2: Have Requirement 4 Policies and Procedures Assigned and In Place
Copy Link
PCI v4.0 - 4.2.1.1: Maintain Inventory of Trusted Keys and Certificates
Copy Link
PCI v4.0 - 4.2.1.2: Utilize Strong Cryptography When Transmitting Primary Account Numbers on Wireless Networks
Copy Link
PCI v4.0 - 4.2.1: Properly Secure Primary Account Numbers During Transmission
Copy Link
PCI v4.0 - 4.2.2: Secure Primary Account Numbers When Transmitting via End User Messaging
Copy Link
PCI v4.0 - 5.1.1: Have Requirement 5 Policies and Procedures In Place
Copy Link
PCI v4.0 - 5.1.2: Have Requirement 5 Roles and Responsibilities In Place
Copy Link
PCI v4.0 - 5.2.1: Deploy Anti-Malware Solutions on All System Components
Copy Link
PCI v4.0 - 5.2.2: Utilize Sufficient Anti-Malware Solutions
Copy Link
PCI v4.0 - 5.2.3.1: Define Frequency of Periodic Evaluations of Systems in the Targeted Risk Analysis
Copy Link
PCI v4.0 - 5.2.3: Periodically Review Systems Not Protected by Anti-Malware Solutions
Copy Link
PCI v4.0 - 5.3.1: Keep Anti-Malware Solutions Up to Date
Copy Link
PCI v4.0 - 5.3.2.1: Define Frequency of Anti-Malware Scans in Targeted Risk Analysis
Copy Link
PCI v4.0 - 5.3.2: Ensure Anti-Malware Solution Performs Scans or Continuous Behavior Analyses
Copy Link
PCI v4.0 - 5.3.3: Utilize Anti-Malware Solutions for Removable Media
Copy Link
PCI v4.0 - 5.3.4: Enable and Retain Audit Logs for Anti-Malware Solutions
Copy Link
PCI v4.0 - 5.3.5: Do Not Allow Anti-Malware Solutions to Be Altered or Disabled
Copy Link
PCI v4.0 - 5.4.1: Have Protections in Place to Prevent Phishing Attacks
Copy Link
PCI v4.0 - 6.1.1: Requirement 6 Policies and Procedures Are In Place
Copy Link
PCI v4.0 - 6.1.2: Requirement 6 Roles and Responsibilities Are In Place
Copy Link
PCI v4.0 - 6.2.1: Bespoke and Custom Software Are Developed Securely
Copy Link
PCI v4.0 - 6.2.2: Train Personnel Developing Custom Software in Secure Software Practices
Copy Link
PCI v4.0 - 6.2.3 & 6.2.3.1: Bespoke and Custom Software Is Reviewed Before Being Released
Copy Link
PCI v4.0 - 6.2.4: Utilize Software Engineering Techniques to Secure Bespoke and Custom Software
Copy Link
PCI v4.0 - 6.3.1: Identify Security Vulnerabilities in Software
Copy Link
PCI v4.0 - 6.3.2: Maintain a List of Bespoke and Custom and Third-Party Software
Copy Link
PCI v4.0 - 6.3.3: Remediate Known Vulnerabilities Through Security Patches
Copy Link
PCI v4.0 - 6.4.1: Protect Public-Facing Web Applications
Copy Link
PCI v4.0 - 6.4.2: Use an Automated Solution to Protect Public-Facing Web Applications
Copy Link
PCI v4.0 - 6.4.3: Payment Page Scripts Are Managed Properly
Copy Link
PCI v4.0 - 6.5.1: Have a Documented Change Process for All System Components
Copy Link
PCI v4.0 - 6.5.2: Ensure Applicable PCI DSS Requirements Are In Place After Significant Changes
Copy Link
PCI v4.0 - 6.5.3: Pre-Production and Production Environments Are Separated
Copy Link
PCI v4.0 - 6.5.4: Separate Duties Between Production and Pre-Production Environments
Copy Link
PCI v4.0 - 6.5.5: Live Primary Account Numbers Are Not Used In Pre-Production Environments
Copy Link
PCI v4.0 - 6.5.6: Ensure Test Data and Accounts Are Removed Before Going into Production
Copy Link
PCI v4.0 - 7.1.1: Have Requirement 7 Policies and Procedures In Place
Copy Link
PCI v4.0 - 7.1.2: Have Requirement 7 Roles and Responsibilities In Place
Copy Link
PCI v4.0 - 7.2.1: Have an Access Control Model In Place
Copy Link
PCI v4.0 - 7.2.2: Grant Access Appropriately
Copy Link
PCI v4.0 - 7.2.3: Access Privileges Are Granted by Authorized Personnel
Copy Link
PCI v4.0 - 7.2.4: Periodically Review Access Privileges
Copy Link
PCI v4.0 - 7.2.5.1: Review Application and System Access Privileges
Copy Link
PCI v4.0 - 7.2.5: Assign and Manage System and Application Access Privileges Appropriately
Copy Link
PCI v4.0 - 7.2.6: Restrict Access to Query Repositories of Cardholder Data
Copy Link
PCI v4.0 - 7.3.1: Have an Access Control System In Place
Copy Link
PCI v4.0 - 7.3.2: Access Control System Is Configured Correctly
Copy Link
PCI v4.0 - 7.3.3: Access Control System Is Set to Deny All By Default
Copy Link
PCI v4.0 - 8.1.1: Have Requirement 8 Policies and Procedures In Place
Copy Link
PCI v4.0 - 8.1.2: Have Requirement 8 Roles and Responsibilities In Place
Copy Link
PCI v4.0 - 8.2.1: All Users Are Assigned Unique User IDs
Copy Link
PCI v4.0 - 8.2.2: Group Shared or Generic Accounts Are Only Used When Necessary
Copy Link
PCI v4.0 - 8.2.3: (Service Providers) Use Unique Authentication Factors to Remotely Access Customer Premises
Copy Link
PCI v4.0 - 8.2.4: User IDs and Identifier Objects Are Managed Appropriately
Copy Link
PCI v4.0 - 8.2.5: Revoke Access for Terminated Users Immediately
Copy Link
PCI v4.0 - 8.2.6: Inactive User Accounts Are Removed or Disabled
Copy Link
PCI v4.0 - 8.2.7: Properly Manage Accounts Used By Third Parties
Copy Link
PCI v4.0 - 8.2.8: Require Reauthentication if User Session Has Been Idle for More Than 15 Minutes
Copy Link
PCI v4.0 - 8.3.10.1: (Service Providers) Change Customer User Passwords and Passphrases Once Every 90 Days
Copy Link
PCI v4.0 - 8.3.10: (Service Providers) Provide Password and Passphrase Guidance to Customer Users
Copy Link
PCI v4.0 - 8.3.11: Assign Authentication Factors to Individual Users
Copy Link
PCI v4.0 - 8.3.1: Access to System Components Is Properly Authenticated
Copy Link
PCI v4.0 - 8.3.2: Use Strong Cryptography on All Authentication Factors
Copy Link
PCI v4.0 - 8.3.3: Verify User Identify Before Modifying Any Authentication Factor
Copy Link
PCI v4.0 - 8.3.4: Limit Invalid Authentication Attempts
Copy Link
PCI v4.0 - 8.3.5: Set and Reset Passphrases and Passwords Appropriately
Copy Link
PCI v4.0 - 8.3.6: Ensure Passphrases and Passwords Meet Minimum Levels of Complexity
Copy Link
PCI v4.0 - 8.3.7: Passwords Are Not the Same as at Least the Previous Four Passwords
Copy Link
PCI v4.0 - 8.3.8: Authentication Policies and Procedures Are Documented and Communicated
Copy Link
PCI v4.0 - 8.3.9: Passwords and Passphrases Are Changed Once Every 90 Days
Copy Link
PCI v4.0 - 8.4.1: Multi-Factor Authentication Is Implemented for All Non-Console Access
Copy Link
PCI v4.0 - 8.4.2: Multi-Factor Authentication Is Implemented for All Access to Cardholder Data Environment
Copy Link
PCI v4.0 - 8.4.3: Multi-Factor Authentication Is Utilized for All Remote Network Access
Copy Link
PCI v4.0 - 8.5.1: Multi-Factor Authentication Systems Are Implemented Appropriately
Copy Link
PCI v4.0 - 8.6.1: Interactive Logins Are Managed Properly
Copy Link
PCI v4.0 - 8.6.2: Passwords and Passphrases For System Accounts Are Not Hardcoded
Copy Link
PCI v4.0 - 8.6.3: Passwords and Passphrases Are Protected from Misuse
Copy Link
PCI v4.0 - 9.1.1: Requirement 9 Policies and Procedures Are In Place
Copy Link
PCI v4.0 - 9.1.2: Requirement 9 Roles and Responsibilities Are In Place
Copy Link
PCI v4.0 - 9.2.1 & 9.2.1.1: Monitor and Restrict Physical Access to Cardholder Data Environment Areas
Copy Link
PCI v4.0 - 9.2.2: Restrict the Use of Publicly Accessible Network Jacks
Copy Link
PCI v4.0 - 9.2.3: Access to Network Access Points Is Restricted
Copy Link
PCI v4.0 - 9.2.4: Console Access in Sensitive Data Area Is Restricted
Copy Link
PCI v4.0 - 9.3.1.1: Physical Access to Sensitive Areas Within the Cardholder Data Environment Is Controlled
Copy Link
PCI v4.0 - 9.3.1: Procedures Are In Place for Physical Access to the Cardholder Data Environment
Copy Link
PCI v4.0 - 9.3.2: Implement Procedures for Visitor Access to the Cardholder Data Environment
Copy Link
PCI v4.0 - 9.3.3: Visitor Badges or Identification Are Surrendered Before Leaving
Copy Link
PCI v4.0 - 9.3.4: Maintain a Visitor Log
Copy Link
PCI v4.0 - 9.4.1, 9.4.1.1, & 9.4.1.2: Media with Cardholder Data Is Physically Secured
Copy Link
PCI v4.0 - 9.4.2: All Media with Cardholder Data Is Classified
Copy Link
PCI v4.0 - 9.4.3: Properly Secure Media with Cardholder Data Sent Outside the Facility
Copy Link
PCI v4.0 - 9.4.4: Management Approves Sending Media with Cardholder Data Outside the Facility
Copy Link
PCI v4.0 - 9.4.5 & 9.4.5.1: Inventory Logs of Electronic Media with Cardholder Data Are Maintained
Copy Link
PCI v4.0 - 9.4.6: Hard-Copy Materials with Cardholder Data Are Destroyed
Copy Link
PCI v4.0 - 9.4.7: Destroy Digital Media With Cardholder Data
Copy Link
PCI v4.0 - 9.5.1.1: Maintain an Up-to-Date List of Point-of-Interaction Devices
Copy Link
PCI v4.0 - 9.5.1.2 & 9.5.1.2.1: Periodically Inspect Point-of-Interaction Devices
Copy Link
PCI v4.0 - 9.5.1.3: Provide Training for Personnel in Point-of-Interaction Environments
Copy Link
PCI v4.0 - 9.5.1: Point-of-Interaction Devices Are Protected
Copy Link
PCI v4.0 - A1.1.1: (Multi-Tenant Service Providers) Logical Separation Is Implemented Appropriately
Copy Link
PCI v4.0 - A1.1.2: (Multi-Tenant Service Providers) Each Customer Can Only Access Its Own Data and Environment
Copy Link
PCI v4.0 - A1.1.3: (Multi-Tenant Service Providers) Customers Can Only Access Resources Allocated to Them
Copy Link
PCI v4.0 - A1.1.4: (Multi-Tenant Service Providers) Logical Separation Control Effectiveness Is Tested Regularly
Copy Link
PCI v4.0 - A1.2.2: (Multi-Tenant Service Providers) Implement Processes to Support Forensic Investigations
Copy Link
PCI v4.0 - A1.2.3: (Multi-Tenant Service Providers) Implement Processes for Reporting and Addressing Security Incidents
Copy Link
Practice Regular Key Rotation for Service Accounts
Copy Link
Preventing Public Accessibility on DB Instances
Copy Link
Protect Admin Accounts with Security Key Enforcement
Copy Link
Protect Your Data with PCI DSS
Copy Link
Protecting API Gateways with WAF Rules
Copy Link
Receive Alerts for Audit Configuration Changes
Copy Link
Receive Alerts for VPC Network Firewall Rule Changes
Copy Link
Regularly Rotate API Keys
Copy Link
Remove Default Networks from All Projects
Copy Link
Restrict API Key Use to Specified Hosts and Apps
Copy Link
Restrict API Keys to Applications That Need Access
Copy Link
Restrict RDP Authorized Access from the Internet
Copy Link
Restrict Security Group Access to All Ports
Copy Link
Restricting Access to EBS Snapshots
Copy Link
Retaining Your Audit Trail in AWS
Copy Link
Rotate KMS Encryption Keys Regularly
Copy Link
Rotating Access Keys
Copy Link
Securely Store and Access Secrets in Secrets Manager
Copy Link
Securing Your Log Files
Copy Link
Systems Manager Maintenance
Copy Link
The Difference Between NACLs and Security Groups
Copy Link
Third Parties and Your PCI DSS Assessment
Copy Link
Use Cloud Logging Sinks to Retain Logs
Copy Link
Use Identity Aware Proxy (IAP) to Restrict Access to Network
Copy Link
Use Least Privilege For Users at Project Level Roles
Copy Link
Using IAM Instance Roles for AWS Resource Access
Copy Link
Using Systems Manager from a Service-Linked Role
Copy Link
Using VPC Endpoints to Access Systems Manager
Copy Link
Using a Bastion Host or Session Manager to Limit Access to Port 22
Copy Link
Utilize Flow Logs to Log Traffic in Your Environment
Copy Link
Utilize Log Alerts for Create or Update SQL Server Firewall
Copy Link
Utilize Log Alerts for Create or Update Security Solution
Copy Link
Utilize Logging for Azure Key Vault
Copy Link
VPC Network Route Changes Should Trigger Alerts
Copy Link
Verify Log Alert Exists for Create Policy Assignment
Copy Link
Verify Log Alert Exists for Delete Policy Assignment
Copy Link
What Data Does PCI DSS Apply To?
Copy Link
Who Does PCI DSS Apply To?
Copy Link
Who Is Involved In PCI?
Copy Link