PCI v4.0 - 11.5.1.1: Detect Alert and Address Covert Malware Communication Channels

Related Videos

5 Focus Areas for AWS Compliance
AWS Incident Response Playbook
AWS Incident Response Playbook for Credential compromise
AWS Incident Response Playbook for Ransomware
AWS Incident Response Playbook for S3 Buckets
AWS Security Needs a Growth Mindset
Achieving High Availability in AWS
Activate Microsoft Defender for Azure SQL Databases
Antivirus Solutions on EC2 Instances
Autoprovisioning of Microsoft Defender for Containers Components.mov
Avoid Using Default Service Account When Configuring Instances
Consistently Manage User Accounts with OS Login
Deploying Security Patches on EC2 Instances
Disabling Insecure Ports and Protocols
Do Not Enable Serial Ports for VM Instance
Do Not Use Project-Wide SSH Keys When Authenticating Instances
Do You Have to Do PCI?
EC2 Instances in Availability Zones
Enable Access Transparency to Monitor Google Cloud Engineer Access
Enable Alerting for Cloud Storage IAM Permission Changes
Enable Autoprovisioning of Vulnerability Assessment for Machines
Enable Bucket Lock to Protect Sink Destinations from Modification
Enable Cloud Audit Logging Across Your Project
Enable Cloud DNS Logging for VPC Networks
Enable HTTPS Connections on App Engine Applications
Enable Microsoft Defender for DNS
Enable Microsoft Defender for IoT
Enable Microsoft Defender for Open Source Relationship Databases
Enable Microsoft Defender for SQL Server on Machines
Enable Microsoft Defender for Servers
Enable Shielded VM to Ensure Operating System is Trustworthy
Encrypt BigQuery Datasets with Customer Managed Encryption Key (CMEK)
Encrypted Cardholder Data and Scope
Encryption Opportunities
Encryption for EBS Volumes
Encryption for S3 Buckets
Ensure Alerts Exist for Project Ownership Changes
Ensure Alerts are Received for VPC Network Changes
Ensure Autoprovisioning of the Log Analytics Agent Is Enabled for Azure VMs
Ensure BigQuery Datasets Are Not Publicly Accessible
Ensure Cloud Storage Buckets Are Not Publicly Accessible
Ensure Microsoft Defender Is Enabled for Storage Accounts
Ensure Microsoft Defender Is Enabled for the Azure Resource Manager
Ensure Microsoft Defender for Key Vaults Is Enabled
Ensure the Minimum TLS Version for Storage Accounts Is Set to 1.2
Establish a Log Metric Alert for Configuration Changes in SQL Instances
Evaluate Public IP Addresses Regularly
Events that Drive Key Rotation
Generate Log Metric Alerts for Custom Role Changes
Getting Started with PCI Compliance
Harden Cloud SQL Database with Logging
Historically View Project Resources in Asset Inventory
How Do You Scope a PCI DSS Assessment?
IP Forwarding Should Not Be Enabled for Instances
Identifying and Ranking Vulnerabilities in AWS
Key Rotation and Management
Leverage Confidential Computing to Protect Data
Leverage Google Cloud Engineers by Granting Access Approval
Limiting PCI DSS Scope
Load Balancers Must Require TLS 1.2
Manage Access Securely Using Uniform Bucket-Level Access
Minimize Public IP Address on Compute Instances
Minimize Root and SA Account Access in Cloud SQL
PCI Compliance One Step at a Time
PCI DSS Assessment Scope: Identify All Other People Processes and Technology
PCI DSS Assessment Scope: Identify Cardholder Data Flows
PCI DSS Assessment Scope: Identify People and Processes
PCI DSS Assessment Scope: Identify Technology
PCI DSS Assessment Scope: Identify Third Parties
PCI Requirement 11.1.2 – Unauthorized Wireless Access Points Detection
PCI Requirement 11.2 – Quarterly Internal & External Vulnerability Scans
PCI Requirement 11.2.1 – Perform Quarterly Internal Vulnerability Scans
PCI Requirement 11.2.2 – Perform Quarterly External Vulnerability Scans
PCI Requirement 11.2.3 – Perform Internal and External Scans and Rescans as Needed
PCI Requirement 11.4 – Use Intrusion-Detection and/or Intrusion-Prevention Techniques
PCI Requirement 11.5 – Deploy a Change-Detection Mechanisms to Alert Personnel
PCI Requirement 5.1 – Deploy Anti-Virus Software on all Commonly Affected Systems
PCI Requirement 5.1.1 – Ensure Anti-Virus Programs Detect, Remove and Protect Against Malware
PCI Requirement 5.1.2 – Perform Evaluations to Identify & Evaluate Evolving Malware Threats
PCI Requirement 5.2 – Ensure Anti-Virus Mechanisms are Current, Perform Scans, & Generate Audit Logs
PCI Requirement 5.3 – Ensure Anti-Virus Mechanisms are Active and Can’t be Altered
PCI Requirement 6.1 – Establish a Process to Identify Security Vulnerabilities
PCI Requirement 6.5.6 – All “High Risk” Vulnerabilities
PCI Requirement 6.6 – Address Threats & Vulnerabilities Regularly for Public-Facing Web Applications
PCI v3.2.1 vs. PCI 4.0: What's Changed?
PCI v4.0 - 1.1.1: Requirement 1 Policies and Procedures Are In Place
PCI v4.0 - 1.1.2: Requirement 1 Roles and Responsibilities Are In Place
PCI v4.0 - 1.2.1: Configuration Standards for Network Security Controls Are Implemented
PCI v4.0 - 1.2.2: Changes to Network Connections and Security Controls Are Approved
PCI v4.0 - 1.2.3: Maintain an Accurate Network Diagram
PCI v4.0 - 1.2.4: Maintain an Accurate Data-Flow Diagram
PCI v4.0 - 1.2.5: All Services Protocols and Ports Are Identified and Approved
PCI v4.0 - 1.2.6: Security Features Are Implemented on All Services Protocols and Ports
PCI v4.0 - 1.2.7: Network Security Controls Configurations Are Reviewed Regularly
PCI v4.0 - 1.2.8: Keep Configuration Files for Network Security Controls Secure and Consistent
PCI v4.0 - 1.3.1: Inbound Cardholder Data Environment Traffic Is Restricted
PCI v4.0 - 1.3.2: Outbound Traffic from the Cardholder Data Environment Is Restricted
PCI v4.0 - 1.3.3: Implement a Network Security Control Between Wireless Network and Wired CDE Segments
PCI v4.0 - 1.4.1: Network Security Controls Are Installed Between Trusted and Untrusted Networks
PCI v4.0 - 1.4.2: Inbound Traffic From Untrusted to Trusted Networks Is Restricted
PCI v4.0 - 1.4.3: Anti-Spoofing Measures Are In Place
PCI v4.0 - 1.4.4: Ensure Stored Cardholder Data Is Not Accessible from Untrusted Networks
PCI v4.0 - 1.4.5: Internal IP Addresses And Routing Information Is Only Disclosed to Authorized Parties
PCI v4.0 - 1.5.1: Security Controls Are Implemented on Any Computing Devices
PCI v4.0 - 10.1.1: Requirement 10 Policies and Procedures Are In Place
PCI v4.0 - 10.1.2: Requirement 10 Roles and Responsibilities Are In Place
PCI v4.0 - 10.2.1.1: Logs Capture Individual User Access to Cardholder Data
PCI v4.0 - 10.2.1.2: Logs Capture All Actions by Someone with Administrative Access
PCI v4.0 - 10.2.1.3: Logs Capture All Access to Audit Logs
PCI v4.0 - 10.2.1.4: Logs Capture All Invalid Logical Access Attempts
PCI v4.0 - 10.2.1.5: Logs Capture All Changes to Identification and Authentication Credentials
PCI v4.0 - 10.2.1.6: Logs Capture All Initialization Starting Stopping and Pausing of Audit Logs
PCI v4.0 - 10.2.1.7: Logs Capture All Creation and Deletion of System Level Objects
PCI v4.0 - 10.2.1: Audit Logs Are Enabled and Active
PCI v4.0 - 10.2.2: Audit Logs Record All Appropriate Information for Each Auditable Event
PCI v4.0 - 10.3.1: Read Access to Audit Log Files Is Limited
PCI v4.0 - 10.3.2: Audit Log Files Are Protected from Modification
PCI v4.0 - 10.3.3: Audit Log Files Are Properly Backed Up
PCI v4.0 - 10.3.4: Utilize File Integrity Monitoring or Change-Detection Tools on Audit Logs
PCI v4.0 - 10.4.1 & 10.4.1.1: Perform Specific Daily Audit Log Reviews Using Automated Mechanisms
PCI v4.0 - 10.4.2 & 10.4.2.1: Periodically Perform Other Audit Log Reviews
PCI v4.0 - 10.4.3: Address Identified Exceptions and Anomalies
PCI v4.0 - 10.5.1: Retain Audit Log History for At Least 12 Months
PCI v4.0 - 10.6.1: System Clocks and Time Are Synchronized
PCI v4.0 - 10.6.2: Systems Are Configured to the Correct and Consistent Time
PCI v4.0 - 10.6.3: Time Synchronization Settings and Data Are Protected
PCI v4.0 - 10.7.1: (Service Providers) Critical Security Control System Failures Are Addressed
PCI v4.0 - 10.7.2: Failure of Critical Security Control Systems Are Handled Appropriately
PCI v4.0 - 10.7.3: Failure of Any Critical Security Controls Are Promptly Addressed
PCI v4.0 - 11.1.1: Requirement 11 Polices and Procedures Are In Place
PCI v4.0 - 11.1.2: Requirement 11 Roles and Responsibilities Are In Place
PCI v4.0 - 11.2.1: Wireless Access Points Are Properly Managed
PCI v4.0 - 11.2.2: Maintain Inventory of All Authorized Wireless Access Points
PCI v4.0 - 11.3.1.1: Manage Non-High Risk and Non-Critical Vulnerabilities Appropriately
PCI v4.0 - 11.3.1.2: Use Authenticated Vulnerability Scanning Tools for Internal Scans
PCI v4.0 - 11.3.1.3: Perform Internal Scans After Significant Changes
PCI v4.0 - 11.3.1: Perform Internal Vulnerability Scans Frequently
PCI v4.0 - 11.3.2.1: Perform External Scans After Significant Changes
PCI v4.0 - 11.3.2: Perform External Vulnerability Scans Frequently
PCI v4.0 - 11.4.1: Define Document and Implement a Penetration Testing Methodology
PCI v4.0 - 11.4.2: Regularly Perform Internal Penetration Testing
PCI v4.0 - 11.4.3: Regularly Perform External Penetration Testing
PCI v4.0 - 11.4.4: Correct Vulnerabilities Found in Penetration Testing
PCI v4.0 - 11.4.5 & 11.4.6: Test the Effectiveness of Segmentation Controls Regularly
PCI v4.0 - 11.4.7: Multi-Tenant Service Providers Support Customers for External Penetration Testing
PCI v4.0 - 11.5.1: Implement Intrusion Detection and or Prevention Techniques
PCI v4.0 - 11.5.2: Deploy a Change-Detection Mechanism
PCI v4.0 - 11.6.1: Change-Detection or Tamper-Detection Mechanisms Are Deployed on Payment Pages
PCI v4.0 - 12.1.1: Have and Utilize an Information Security Policy
PCI v4.0 - 12.1.2: Review and Update Your Information Security Policy Regularly
PCI v4.0 - 12.1.3: Ensure Your Information Security Policy Defines Roles and Responsibilities
PCI v4.0 - 12.1.4: Formally Assign Information Security Responsibility to a CISO
PCI v4.0 - 12.10.1: Establish a Comprehensive Incident Response Plan
PCI v4.0 - 12.10.2: Regularly Review the Incident Response Plan
PCI v4.0 - 12.10.3: Ensure Specific Security Personnel Are Available for Incident Response
PCI v4.0 - 12.10.4.1: Utilize the Targeted Risk Analysis to Determine Incident Response Training Frequency
PCI v4.0 - 12.10.4: Appropriately Train Incident Response Personnel
PCI v4.0 - 12.10.5: Include Monitoring and Responding to Alerts in the Incident Response Plan
PCI v4.0 - 12.10.6: Modify the Incident Response Plan as Needed
PCI v4.0 - 12.10.7: Implement Incident Response Procedures Upon Detection of Stored Primary Account Numbers
PCI v4.0 - 12.2.1: Acceptable Use Policies Are Documented and Implemented
PCI v4.0 - 12.3.1: Use Targeted Risk Analyses to Support Flexible Testing
PCI v4.0 - 12.3.2: Perform Targeted Risk Analyses for Customized Approach
PCI v4.0 - 12.3.3: Document and Review Cryptographic Cipher Suites and Protocols in Use
PCI v4.0 - 12.3.4: Review Software and Hardware Technologies
PCI v4.0 - 12.4.1: Service Providers Must Establish Protections for Card Holder Data
PCI v4.0 - 12.4.2.1: Document the Reviews Performed in Requirement 12.4.2
PCI v4.0 - 12.4.2: Ensure Personnel Are Performing Their Duties
PCI v4.0 - 12.5.1: Maintain an Inventory of System Components That Are in Scope
PCI v4.0 - 12.5.2.1: Service Providers Must Document and Confirm Scope Frequently
PCI v4.0 - 12.5.2: Document and Confirm Scope Regularly
PCI v4.0 - 12.5.3: Review Scope After Significant Changes to Organizational Structure
PCI v4.0 - 12.6.1: Implement Formal Security Awareness Training
PCI v4.0 - 12.6.2: Review Your Information Security Awareness Program Regularly
PCI v4.0 - 12.6.3.1: Include Specific Threats and Vulnerabilities in Information Security Awareness Trainings
PCI v4.0 - 12.6.3.2: Include Acceptable Use Policies in Security Awareness Trainings
PCI v4.0 - 12.6.3: Hold Information Security Awareness Trainings Regularly
PCI v4.0 - 12.7.1: Screen Personnel Who Have Access to the Cardholder Data Environment
PCI v4.0 - 12.8.1: Keep Record of Third-Party Service Providers that Account Data Is Shared With
PCI v4.0 - 12.8.2: Maintain Written Requirements with Third-Party Service Providers
PCI v4.0 - 12.8.3: Establish a Process for Engaging with Third-Party Service Providers
PCI v4.0 - 12.8.4: Monitor the PCI DSS Compliance of Third-Party Service Providers
PCI v4.0 - 12.8.5: Detail Responsibilities Held by Third-Party Service Providers
PCI v4.0 - 12.9.1: Acknowledge Account Security Responsibilities
PCI v4.0 - 12.9.2: Provide Compliance Information to Clients Upon Request
PCI v4.0 - 2.1.1: Requirement 2 Policies and Procedures Are In Place
PCI v4.0 - 2.1.2: Requirement 2 Roles and Responsibilities Are In Place
PCI v4.0 - 2.2.1: Configuration Standards Are Developed Implemented and Maintained
PCI v4.0 - 2.2.2: Vendor Default Accounts Are Managed Properly
PCI v4.0 - 2.2.3: Primary Functions Requiring Different Security Levels Are Managed
PCI v4.0 - 2.2.4: Unnecessary Functionalities Are Removed or Disabled
PCI v4.0 - 2.2.5: Insecure Daemons Protocols and Services Have Additional Security Features
PCI v4.0 - 2.2.6: System Security Parameters Are Configured to Prevent Misuse
PCI v4.0 - 2.2.7: Non-Console Administrative Access Is Encrypted
PCI v4.0 - 2.3.1: Wireless Vendor Defaults Are Changed or Confirmed to Be Secure
PCI v4.0 - 2.3.2: Wireless Encryption Keys Are Changed Accordingly
PCI v4.0 - 3.1.1 & 3.1.2: Have Requirement 3 Policies and Procedures Assigned and In Place
PCI v4.0 - 3.2.1: Only Retain the Minimum Account Data Needed
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
PCI v4.0 - 3.3.2: Encrypt Sensitive Authentication Data If Retained for Any Length of TIme
PCI v4.0 - 3.3.3: (Issuers Only) Store Only the Minimum Amount of Sensitive Authentication Data Needed
PCI v4.0 - 3.4.1: Mask Displayed Primary Account Number
PCI v4.0 - 3.4.2: Do Not Allow Primary Account Numbers to Be Copied When Using Remote Access
PCI v4.0 - 3.5.1.1: Ensure All Hashes Are Keyed
PCI v4.0 - 3.5.1.2: Correctly Utilize Disk-Level Encryption of Primary Account Numbers
PCI v4.0 - 3.5.1.3: Ensure Disk-Level Encryption Meets Requirements
PCI v4.0 - 3.5.1: Store Primary Account Numbers Appropriately
PCI v4.0 - 3.6.1.1: (Service Providers) Document and Describe the Cryptographic Architecture
PCI v4.0 - 3.6.1.3 & 3.6.1.4: Use Fewest Possible Custodians and Locations for Cryptographic Keys
PCI v4.0 - 3.6.1: Use Fewest Possible Number of Key Custodians Locations and Forms
PCI v4.0 - 3.7.1: Utilize Procedures to Generate Strong Cryptographic Keys
PCI v4.0 - 3.7.2 & 3.7.3: Implement Policies and Procedures to Safely Distribute and Store Keys
PCI v4.0 - 3.7.4: Define Cryptoperiods in Policies and Procedures for Key Management
PCI v4.0 - 3.7.5: Properly Retire Replace or Destroy Keys When Appropriate
PCI v4.0 - 3.7.6: Use Split Knowledge and Dual Control for Manual Cleartext Key Management
PCI v4.0 - 3.7.7: Do Not Allow Unauthorized Key Substitution
PCI v4.0 - 3.7.8: Require Key Custodians to Acknowledge and Accept Their Responsibilities
PCI v4.0 - 4.1.1 & 4.1.2: Have Requirement 4 Policies and Procedures Assigned and In Place
PCI v4.0 - 4.2.1.1: Maintain Inventory of Trusted Keys and Certificates
PCI v4.0 - 4.2.1.2: Utilize Strong Cryptography When Transmitting Primary Account Numbers on Wireless Networks
PCI v4.0 - 4.2.1: Properly Secure Primary Account Numbers During Transmission
PCI v4.0 - 4.2.2: Secure Primary Account Numbers When Transmitting via End User Messaging
PCI v4.0 - 5.1.1: Have Requirement 5 Policies and Procedures In Place
PCI v4.0 - 5.1.2: Have Requirement 5 Roles and Responsibilities In Place
PCI v4.0 - 5.2.1: Deploy Anti-Malware Solutions on All System Components
PCI v4.0 - 5.2.2: Utilize Sufficient Anti-Malware Solutions
PCI v4.0 - 5.2.3.1: Define Frequency of Periodic Evaluations of Systems in the Targeted Risk Analysis
PCI v4.0 - 5.2.3: Periodically Review Systems Not Protected by Anti-Malware Solutions
PCI v4.0 - 5.3.1: Keep Anti-Malware Solutions Up to Date
PCI v4.0 - 5.3.2.1: Define Frequency of Anti-Malware Scans in Targeted Risk Analysis
PCI v4.0 - 5.3.2: Ensure Anti-Malware Solution Performs Scans or Continuous Behavior Analyses
PCI v4.0 - 5.3.3: Utilize Anti-Malware Solutions for Removable Media
PCI v4.0 - 5.3.4: Enable and Retain Audit Logs for Anti-Malware Solutions
PCI v4.0 - 5.3.5: Do Not Allow Anti-Malware Solutions to Be Altered or Disabled
PCI v4.0 - 5.4.1: Have Protections in Place to Prevent Phishing Attacks
PCI v4.0 - 6.1.1: Requirement 6 Policies and Procedures Are In Place
PCI v4.0 - 6.1.2: Requirement 6 Roles and Responsibilities Are In Place
PCI v4.0 - 6.2.1: Bespoke and Custom Software Are Developed Securely
PCI v4.0 - 6.2.2: Train Personnel Developing Custom Software in Secure Software Practices
PCI v4.0 - 6.2.3 & 6.2.3.1: Bespoke and Custom Software Is Reviewed Before Being Released
PCI v4.0 - 6.2.4: Utilize Software Engineering Techniques to Secure Bespoke and Custom Software
PCI v4.0 - 6.3.1: Identify Security Vulnerabilities in Software
PCI v4.0 - 6.3.2: Maintain a List of Bespoke and Custom and Third-Party Software
PCI v4.0 - 6.3.3: Remediate Known Vulnerabilities Through Security Patches
PCI v4.0 - 6.4.1: Protect Public-Facing Web Applications
PCI v4.0 - 6.4.2: Use an Automated Solution to Protect Public-Facing Web Applications
PCI v4.0 - 6.4.3: Payment Page Scripts Are Managed Properly
PCI v4.0 - 6.5.1: Have a Documented Change Process for All System Components
PCI v4.0 - 6.5.2: Ensure Applicable PCI DSS Requirements Are In Place After Significant Changes
PCI v4.0 - 6.5.3: Pre-Production and Production Environments Are Separated
PCI v4.0 - 6.5.4: Separate Duties Between Production and Pre-Production Environments
PCI v4.0 - 6.5.5: Live Primary Account Numbers Are Not Used In Pre-Production Environments
PCI v4.0 - 6.5.6: Ensure Test Data and Accounts Are Removed Before Going into Production
PCI v4.0 - 7.1.1: Have Requirement 7 Policies and Procedures In Place
PCI v4.0 - 7.1.2: Have Requirement 7 Roles and Responsibilities In Place
PCI v4.0 - 7.2.1: Have an Access Control Model In Place
PCI v4.0 - 7.2.2: Grant Access Appropriately
PCI v4.0 - 7.2.3: Access Privileges Are Granted by Authorized Personnel
PCI v4.0 - 7.2.4: Periodically Review Access Privileges
PCI v4.0 - 7.2.5.1: Review Application and System Access Privileges
PCI v4.0 - 7.2.5: Assign and Manage System and Application Access Privileges Appropriately
PCI v4.0 - 7.2.6: Restrict Access to Query Repositories of Cardholder Data
PCI v4.0 - 7.3.1: Have an Access Control System In Place
PCI v4.0 - 7.3.2: Access Control System Is Configured Correctly
PCI v4.0 - 7.3.3: Access Control System Is Set to Deny All By Default
PCI v4.0 - 8.1.1: Have Requirement 8 Policies and Procedures In Place
PCI v4.0 - 8.1.2: Have Requirement 8 Roles and Responsibilities In Place
PCI v4.0 - 8.2.1: All Users Are Assigned Unique User IDs
PCI v4.0 - 8.2.2: Group Shared or Generic Accounts Are Only Used When Necessary
PCI v4.0 - 8.2.3: (Service Providers) Use Unique Authentication Factors to Remotely Access Customer Premises
PCI v4.0 - 8.2.4: User IDs and Identifier Objects Are Managed Appropriately
PCI v4.0 - 8.2.5: Revoke Access for Terminated Users Immediately
PCI v4.0 - 8.2.6: Inactive User Accounts Are Removed or Disabled
PCI v4.0 - 8.2.7: Properly Manage Accounts Used By Third Parties
PCI v4.0 - 8.2.8: Require Reauthentication if User Session Has Been Idle for More Than 15 Minutes
PCI v4.0 - 8.3.10.1: (Service Providers) Change Customer User Passwords and Passphrases Once Every 90 Days
PCI v4.0 - 8.3.10: (Service Providers) Provide Password and Passphrase Guidance to Customer Users
PCI v4.0 - 8.3.11: Assign Authentication Factors to Individual Users
PCI v4.0 - 8.3.1: Access to System Components Is Properly Authenticated
PCI v4.0 - 8.3.2: Use Strong Cryptography on All Authentication Factors
PCI v4.0 - 8.3.3: Verify User Identify Before Modifying Any Authentication Factor
PCI v4.0 - 8.3.4: Limit Invalid Authentication Attempts
PCI v4.0 - 8.3.5: Set and Reset Passphrases and Passwords Appropriately
PCI v4.0 - 8.3.6: Ensure Passphrases and Passwords Meet Minimum Levels of Complexity
PCI v4.0 - 8.3.7: Passwords Are Not the Same as at Least the Previous Four Passwords
PCI v4.0 - 8.3.8: Authentication Policies and Procedures Are Documented and Communicated
PCI v4.0 - 8.3.9: Passwords and Passphrases Are Changed Once Every 90 Days
PCI v4.0 - 8.4.1: Multi-Factor Authentication Is Implemented for All Non-Console Access
PCI v4.0 - 8.4.2: Multi-Factor Authentication Is Implemented for All Access to Cardholder Data Environment
PCI v4.0 - 8.4.3: Multi-Factor Authentication Is Utilized for All Remote Network Access
PCI v4.0 - 8.5.1: Multi-Factor Authentication Systems Are Implemented Appropriately
PCI v4.0 - 8.6.1: Interactive Logins Are Managed Properly
PCI v4.0 - 8.6.2: Passwords and Passphrases For System Accounts Are Not Hardcoded
PCI v4.0 - 8.6.3: Passwords and Passphrases Are Protected from Misuse
PCI v4.0 - 9.1.1: Requirement 9 Policies and Procedures Are In Place
PCI v4.0 - 9.1.2: Requirement 9 Roles and Responsibilities Are In Place
PCI v4.0 - 9.2.1 & 9.2.1.1: Monitor and Restrict Physical Access to Cardholder Data Environment Areas
PCI v4.0 - 9.2.2: Restrict the Use of Publicly Accessible Network Jacks
PCI v4.0 - 9.2.3: Access to Network Access Points Is Restricted
PCI v4.0 - 9.2.4: Console Access in Sensitive Data Area Is Restricted
PCI v4.0 - 9.3.1.1: Physical Access to Sensitive Areas Within the Cardholder Data Environment Is Controlled
PCI v4.0 - 9.3.1: Procedures Are In Place for Physical Access to the Cardholder Data Environment
PCI v4.0 - 9.3.2: Implement Procedures for Visitor Access to the Cardholder Data Environment
PCI v4.0 - 9.3.3: Visitor Badges or Identification Are Surrendered Before Leaving
PCI v4.0 - 9.3.4: Maintain a Visitor Log
PCI v4.0 - 9.4.1, 9.4.1.1, & 9.4.1.2: Media with Cardholder Data Is Physically Secured
PCI v4.0 - 9.4.2: All Media with Cardholder Data Is Classified
PCI v4.0 - 9.4.3: Properly Secure Media with Cardholder Data Sent Outside the Facility
PCI v4.0 - 9.4.4: Management Approves Sending Media with Cardholder Data Outside the Facility
PCI v4.0 - 9.4.5 & 9.4.5.1: Inventory Logs of Electronic Media with Cardholder Data Are Maintained
PCI v4.0 - 9.4.6: Hard-Copy Materials with Cardholder Data Are Destroyed
PCI v4.0 - 9.4.7: Destroy Digital Media With Cardholder Data
PCI v4.0 - 9.5.1.1: Maintain an Up-to-Date List of Point-of-Interaction Devices
PCI v4.0 - 9.5.1.2 & 9.5.1.2.1: Periodically Inspect Point-of-Interaction Devices
PCI v4.0 - 9.5.1.3: Provide Training for Personnel in Point-of-Interaction Environments
PCI v4.0 - 9.5.1: Point-of-Interaction Devices Are Protected
PCI v4.0 - A1.1.1: (Multi-Tenant Service Providers) Logical Separation Is Implemented Appropriately
PCI v4.0 - A1.1.2: (Multi-Tenant Service Providers) Each Customer Can Only Access Its Own Data and Environment
PCI v4.0 - A1.1.3: (Multi-Tenant Service Providers) Customers Can Only Access Resources Allocated to Them
PCI v4.0 - A1.1.4: (Multi-Tenant Service Providers) Logical Separation Control Effectiveness Is Tested Regularly
PCI v4.0 - A1.2.1: (Multi-Tenant Service Providers) Ensure Appropriate Logging Is Enabled
PCI v4.0 - A1.2.2: (Multi-Tenant Service Providers) Implement Processes to Support Forensic Investigations
PCI v4.0 - A1.2.3: (Multi-Tenant Service Providers) Implement Processes for Reporting and Addressing Security Incidents
Preventing Publicly Available S3 Buckets
Protect Your Data with PCI DSS
Re-Keying for Decryption
Receive Alerts for Audit Configuration Changes
Receive Alerts for VPC Network Firewall Rule Changes
Restrict API Permissions If Using Default Service Accounts
Restrict Unnecessary External Access in Cloud SQL
Running Vulnerability Scans After a Significant Change
SOC 2 Academy: Performing Daily Log Reviews
Shared Responsibility Matrix in PCI
Specify Customer-Managed Encryption Key (CMEK) as Default in BigQuery Datasets
Testing for Unauthorized Wireless Access Points
The Importance of Patch Management in Virtual Machines
The Value of Quarterly Internal Vulnerability Scans
Third Parties and Your PCI DSS Assessment
Use Cloud Logging Sinks to Retain Logs
Use Customer Supplied Encyryption Keys (CSEK) for Critical VM Disks
Use TLS to Encrypt All Connections in Cloud SQL
Using Systems Manager from a Service-Linked Role
Using VPC Endpoints to Access Systems Manager
Utilize Microsoft Defender for Azure Cosmos DB
VPC Network Route Changes Should Trigger Alerts
Verify that Microsoft Defender is Enabled for Containers
What Data Does PCI DSS Apply To?
Who Does PCI DSS Apply To?
Who Is Involved In PCI?