Establish a Log Metric Alert for Configuration Changes in SQL Instances
Related Videos
10.6.1 – Review Daily All Security Events and Logs of All System Components.mp4
10.6.2 – Review Logs of All Other System Components Based Policies and Risk Management Strategy
10.6.3 –Follow Up Exceptions and Anomalies Identified During the Review Process
5 Benchmarks of Role-Based Access Control Service Accounts
AWS Firewall Manager Centralized Logging
Achieving High Availability in AWS
Assign Appropriate Contacts to Essential Roles
Audit Trail Review with Kibana, Athena, and GuardDuty
Audit Your Security Groups for Insecure Ports and Protocols
Authenticate and Authorize Users with Client Certificates
Avoid Using Default Service Account When Configuring Instances
Best Practices for Secret Management
Change-Detection Solutions in AWS
Configure Activity Log Container Access to Private
Configure Storage Accounts to Use Customer Managed Keys
Consistently Manage User Accounts with OS Login
Create Activity Log Alert for Delete SQL Server Firewall
Create a Minimal Audit Policy for Logging
Create an Activity Log Alert for Create or Update Public IP Address
Create an Activity Log Alert for Delete Security Solution
Disabling Insecure Ports and Protocols
Do Not Enable Serial Ports for VM Instance
Do Not Use API Keys at the Project Level
Do Not Use Project-Wide SSH Keys When Authenticating Instances
Do Not Use RSASHA1 for DNSSEC Key-Signing Keys
EC2 Instances in Availability Zones
Enable Access Transparency to Monitor Google Cloud Engineer Access
Enable Alerting for Cloud Storage IAM Permission Changes
Enable Bucket Lock to Protect Sink Destinations from Modification
Enable Cloud Audit Logging Across Your Project
Enable Cloud DNS Logging for VPC Networks
Enable DNSSEC to Protect DNS Protocols
Enable HTTPS Connections on App Engine Applications
Enable Logging of Read, Write, and Delete Requests for Blob Service
Enable Logging of Read, Write, and Delete Requests for Table Service
Enable Multi-Factor Authentication for Non-Service Accounts
Enable Queue Storage Logging for Read Write Access
Enable Shielded VM to Ensure Operating System is Trustworthy
Enable VPC Flow Logs for Every Subnet
Enabling AWS Config in All Regions
Encrypt BigQuery Datasets with Customer Managed Encryption Key (CMEK)
Encrypt Dataproc Cluster Using Customer Managed Encryption Key
Encrypt Kubernetes Secrets Using Keys
Encrypted Cardholder Data and Scope
Encryption for EBS Volumes
Encryption for S3 Buckets
Enforce Separation of Duties When Assigning KMS Related Roles
Enforce Separation of Duties When Assigning Service Account Roles
Ensure Alerts Exist for Project Ownership Changes
Ensure Alerts are Received for VPC Network Changes
Ensure BigQuery Datasets Are Not Publicly Accessible
Ensure Cloud Storage Buckets Are Not Publicly Accessible
Ensure Container Network Interfaces Support Network Policies
Ensure Corporate Login Credentials are Used
Ensure Diagnostic Setting Captures Appropriate Categories
Ensure GKE Nodes are Configured Properly
Ensure KMS Cryptokeys Are Not Publicly Accessible
Ensure Kubernetes Idle Timeout Parameter is Appropriately Set
Ensure Log Alert Exists for Create or Update Network Security Group
Ensure Logging for AppServiceHTTPLogs
Ensure Network Security Group Flow Logs Are Sent to Log Analytics
Ensure No Weak SSL Cipher Suites Are Permitted
Ensure Service Accounts Can't Access Admin Privileges
Ensure That a Diagnostic Setting Is Enabled
Ensure an Activity Log Alert Exists for Delete Public IP Address
Ensure to Restrict SSH Access from the Internet
Events that Drive Key Rotation
Exclusively Use GCP-Managed Service Account Keys
Filters and Alarms in CloudWatch
GKE Authentication and Authorization Best Practices
GKE Cluster Configuration Security Benchmarks
General Policies for Cluster Management
Generate Log Metric Alerts for Custom Role Changes
Harden Cloud SQL Database with Logging
Historically View Project Resources in Asset Inventory
How Do You Scope a PCI DSS Assessment?
How To Configure Your Cluster Networks
How to Configure Kubelet Within Your Environment
How to Edit Inbound Traffic Rules for Default Security Groups
IP Forwarding Should Not Be Enabled for Instances
Identify Unrestricted Access to Ports for Security Groups
Identify if EC2 Instances Are Directly Connected to the Internet
Identity and Access Management Benchmarks in GKE
Image Registry and Scanning Best Practices
Introduction to Amazon CloudWatch
Key Rotation and Management
Leverage Confidential Computing to Protect Data
Leverage Google Cloud Engineers by Granting Access Approval
Load Balancers Must Require TLS 1.2
Log and Retain All Relevant Activities
Manage Access Securely Using Uniform Bucket-Level Access
Migrate Away from RSASHA1 for DNSSEC Zone-Signing Keys
Minimize Public IP Address on Compute Instances
Minimize Root and SA Account Access in Cloud SQL
Monitor Your Environment with Network Watcher
Monitor for "Delete Network Security Groups" Through Log Alerts
Networking Configurations in Kubernetes Environment
Node MetaData Recommendations in GKE
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 10 – Track and Monitor all Access to Network Resources and Cardholder Data
PCI Requirement 10.1 – Implement Audit Trails to Link all Access to System Components
PCI Requirement 10.2 – Implement Automated Audit Trails for all System Components
PCI Requirement 10.2.1 – All Individual User Accesses to Cardholder Data
PCI Requirement 10.2.2 – All Actions Taken by Any Individual with Root or Administrative Privileges
PCI Requirement 10.2.3 – Access to All Audit Trails
PCI Requirement 10.2.4 – Invalid Logical Access Attempts.mp4
PCI Requirement 10.2.5 – Use of and Changes to Identification Accounts with Root Privileges
PCI Requirement 10.2.6 – Initialization, Stopping, or Pausing of the Audit Logs
PCI Requirement 10.2.7 – Creation and Deletion of System-Level Objects
PCI Requirement 10.3 – Record at Least the Following Audit Trail Entries for All System Components
PCI Requirement 10.3.1 – User Identification
PCI Requirement 10.3.2 – Type of Event
PCI Requirement 10.3.3 – Date and Time
PCI Requirement 10.3.4 – Success or Failure Indication
PCI Requirement 10.3.5 – Origination of Event
PCI Requirement 10.3.6 – Identity or Name of Affected Data, System Component, or Resource
PCI Requirement 10.4 – Using Time-Synchronization Technology, Synchronize All Critical Systems
PCI Requirement 10.4.1 – Critical Systems Have the Correct and Consistent Time
PCI Requirement 10.4.2 – Time Data is Protected
PCI Requirement 10.4.3 – Time Settings Are Received from Industry-Accepted Time Sources
PCI Requirement 10.5 – Secure Audit Trails so They Cannot Be Altered
PCI Requirement 10.5.1 – Limit Viewing of Audit Trails to Those with a Job-Related Need
PCI Requirement 10.5.2 – Protect Audit Trail Files from Unauthorized Modifications
PCI Requirement 10.5.3 – Promptly Back Up Audit Trail Files to a Centralized Log Server
PCI Requirement 10.5.4 – Write Logs for External-Facing Technologies onto a Secure Device
PCI Requirement 10.5.5 – Use File-Integrity Monitoring or Change-Detection Software on Logs
PCI Requirement 10.6 – Review Logs and Security Events for All System Components
PCI Requirement 10.7 – Retain Audit Trail History for at Least One Year, with Three Months Available
PCI Requirement 10.8 –Implement a Process for the Detection of Failures of Critical Control Systems
PCI Requirement 10.8.1 –Respond to Failures of Any Critical Security Controls in a Timely Manner
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.1: Detect Alert and Address Covert Malware Communication Channels
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 - A1.2.1: (Multi-Tenant Service Providers) Ensure Appropriate Logging Is Enabled
Pods Security Policies Benchmarks
Practice Regular Key Rotation for Service Accounts
Preventing Publicly Available S3 Buckets
Protect Admin Accounts with Security Key Enforcement
Protect Against Threats With Extensible Admission Control
Protect Kernel Defaults Through Configuration Settings
Protecting API Gateways with WAF Rules
Receive Alerts for Audit Configuration Changes
Receive Alerts for VPC Network Firewall Rule Changes
Regularly Rotate API Keys
Remove Default Networks from All Projects
Restrict API Key Use to Specified Hosts and Apps
Restrict API Keys to Applications That Need Access
Restrict API Permissions If Using Default Service Accounts
Restrict RDP Authorized Access from the Internet
Restrict Security Group Access to All Ports
Restrict Unnecessary External Access in Cloud SQL
Retaining Your Audit Trail in AWS
Rotate KMS Encryption Keys Regularly
Securely Store and Access Secrets in Secrets Manager
Specify Customer-Managed Encryption Key (CMEK) as Default in BigQuery Datasets
The Difference Between NACLs and Security Groups
The Importance of Patch Management in Virtual Machines
Third Parties and Your PCI DSS Assessment
Use CMEK To Secure GKE Storage
Use Cloud Logging Sinks to Retain Logs
Use Customer Supplied Encyryption Keys (CSEK) for Critical VM Disks
Use Identity Aware Proxy (IAP) to Restrict Access to Network
Use Least Privilege For Users at Project Level Roles
Use TLS to Encrypt All Connections in Cloud SQL
Using a Bastion Host or Session Manager to Limit Access to Port 22
Utilize Flow Logs to Log Traffic in Your Environment
Utilize Log Alerts for Create or Update SQL Server Firewall
Utilize Log Alerts for Create or Update Security Solution
Utilize Logging for Azure Key Vault
VPC Network Route Changes Should Trigger Alerts
Verify Log Alert Exists for Create Policy Assignment
Verify Log Alert Exists for Delete Policy Assignment
What Data Does PCI DSS Apply To?
What is the Google Kubernetes Shared Responsibility Model
Who Does PCI DSS Apply To?
