Utilize Flow Logs to Log Traffic in Your Environment

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 Focus Areas for AWS Compliance
AWS Firewall Manager Centralized Logging
Activate Azure Key Rotation Reminders.mov
Allow Azure Services Access to Storage Accounts
Attributes of Log Data
Audit Trail Review with Kibana, Athena, and GuardDuty
Audit Your Security Groups for Insecure Ports and Protocols
Change-Detection Solutions in AWS
Configure Activity Log Container Access to Private
Configure Shared Access Security Tokens to Expire within an Hour
Configure Storage Accounts to Use Customer Managed Keys
Consider an Exclusionary Geographic Access Policy
Create Activity Log Alert for Delete SQL Server Firewall
Create Policies for Usage of Critical Technologies
Create a Review Process for Apps
Create a Review Process of Guest Users
Create an Activity Log Alert for Create or Update Public IP Address
Create an Activity Log Alert for Delete Security Solution
Define Staff Information Security Responsibilities in Policy
Disable Caching of Second Factor of Authentication Beyond One Day
Disable Public Access Level for Storage Accounts with Blob Containers
Disabling Insecure Ports and Protocols
Disallow Other Apps to Access Company Data
Distribute Policies to Affected Parties
Do Not Allow Users to Remember MFA on Devices They Trust
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 Logging of Read, Write, and Delete Requests for Blob Service
Enable Logging of Read, Write, and Delete Requests for Table Service
Enable Microsoft Defender for App Services
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 Multifactor Authentication for Administrators
Enable Multifactor Authentication for All Users
Enable Queue Storage Logging for Read Write Access
Enable Role Based Access Control (RBAC) for Azure Key Vault
Enabling AWS Config in All Regions
Encrypt Infrastructure to Further Protect Your Environment
Encrypt Storage for Cricical Data with CMKs
Enforce Multifactor Authentication for All Users
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 Diagnostic Setting Captures Appropriate Categories
Ensure Guest Accounts Are Restricted
Ensure HTTP(S) Access from the Internet Is Reviewed and Restricted
Ensure Log Alert Exists for Create or Update Network Security Group
Ensure Logging for AppServiceHTTPLogs
Ensure Microsoft Defender Is Enabled for Storage Accounts
Ensure Microsoft Defender Is Enabled for the Azure Resource Manager
Ensure Microsoft Defender for Databases Is Enabled
Ensure Microsoft Defender for Key Vaults Is Enabled
Ensure Network Security Group Flow Logs Are Sent to Log Analytics
Ensure Notifications are Enabled for Password Resets
Ensure Only Administrators Can Create Groups
Ensure Only Authorized Users Can Create Security Groups
Ensure Secure Transfer
Ensure Soft Delete Is Enabled
Ensure That a Diagnostic Setting Is Enabled
Ensure Use of CMKs for Unattached Disks
Ensure an Activity Log Alert Exists for Delete Public IP Address
Ensure that Virtual Hard Disks Are Encrypted
Ensure that an Expiration Date Is Set for All Keys in Non-RBAC Key Vaults
Ensure that an Expiration Date Is Set for All Secrets in Non-RBAC Key Vaults
Ensure the Key Vault Is Recoverable
Ensure the Minimum TLS Version for Storage Accounts Is Set to 1.2
Establish Policy to Disconnect Remote Sessions
Establish Policy to Disconnect Vendor Sessions When Not in Use
Establish a Log Metric Alert for Configuration Changes in SQL Instances
Establish a Policy to Manage Your Service Providers
Evaluate Public IP Addresses Regularly
Evaluate and Restrict UDP Access from the Internet
Filters and Alarms in CloudWatch
Generate Log Metric Alerts for Custom Role Changes
Greg Halpin Audit Tip
Historically View Project Resources in Asset Inventory
How to Disseminate an Information Security Policy
How to Edit Inbound Traffic Rules for Default Security Groups
Identify Unrestricted Access to Ports for Security Groups
Identify if EC2 Instances Are Directly Connected to the Internet
Install Endpoint Protection for All Virtual Machines
Introduction to Amazon CloudWatch
Leverage Google Cloud Engineers by Granting Access Approval
Log and Retain All Relevant Activities
Logging Tools in AWS
Monitor Your Environment with Network Watcher
Monitor for "Delete Network Security Groups" Through Log Alerts
Notify Admins of Other Admin Password Resets
Only Allow Administrators to Delete Locked Resources
Only Allow Approved Employees to Invite Guests
Only Allow Trusted Apps to Access Company Data
Only Install Company-Approved Extensions on Your Virtual Machines
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 - 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 - 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 - A1.2.1: (Multi-Tenant Service Providers) Ensure Appropriate Logging Is Enabled
Periodically Regenerate Access Keys
Policy to Prohibit Cardholder Data on Remote Technology
Prevent Bad Passwords in Azure
Protect Against Malicious Attacks with Azure AD MFA
Protect Cardholder Data Over the Internet
Protect Resources from Unauthorized Access
Protecting API Gateways with WAF Rules
Receive Alerts for Audit Configuration Changes
Receive Alerts for VPC Network Firewall Rule Changes
Reconfirm User Information Regularly
Require 2 Ways of Authentication for Resetting Passwords
Require Multifactor Authentication for Administrators
Restrict Access to Azure Active Directory (ADD)
Restrict Access to Azure Storage From All Networks
Restrict Access to Create Security Groups Only to Administrators
Restrict Access to the Administration Portal
Restrict Security Group Access to All Ports
Restrict User Authentication to Trusted Locations
Restrict Users from Adding Apps
Restrict and Review SSH Access from the Internet
Restrict and Secure Your Azure Environment
Retaining Your Audit Trail in AWS
Review Internal and External Users Monthly
Review and Restrict RDP Access from the Internet
Risky Sign-Ins: What They Are and How to Prevent Them
Screen Employees to Reduce Risk
Securing Your Log Files
Service Providers to Establish Charters for Information Security Program
Set Expectations for Daily and Quarterly Reviews in Your Policy
Set Expiration Date for All Keys in RBAC Key Vaults
Set Expiration Date for All Secrets In RBAC Key Vaults
Take Advantage of Automatic Key Rotation within Azure Key Vault
The Difference Between NACLs and Security Groups
The Importance of Publishing an Information Security Policy
The Importance of Responsibility Acknowledgement from Service Providers
Update Your Policy When Your Environment Changes
Use Cloud Logging Sinks to Retain Logs
Using a Bastion Host or Session Manager to Limit Access to Port 22
Utilize CMKs for OS and Data Disks
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
Utilize Managed Disks for Virtual Machines
Utilize Microsoft Defender for Azure Cosmos DB
Utilize Private Endpoints for Azure Key Vault
Utilize Private Endpoints to Access Storage Accounts
Utilize the Principle of Least Privilege
VPC Network Route Changes Should Trigger Alerts
Verify Log Alert Exists for Create Policy Assignment
Verify Log Alert Exists for Delete Policy Assignment
Verify Only Administrators Manage Group Membership Access
Verify that Microsoft Defender is Enabled for Containers
What to Include in a List of Service Providers
What to Include in a Written Contract with Service Providers