Meeting Your Baseline with Patch Manager

Related Videos

5 Focus Areas for AWS Compliance
AWS Controls for Implementing a DMZ
AWS Firewall Manager Centralized Logging
AWS Functions to Restrict Database Access
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
AWS Web Application Firewall Defaults
Activate Microsoft Defender for Azure SQL Databases
Antivirus Solutions on EC2 Instances
Assign Appropriate Contacts to Essential Roles
Attributes of Log Data
Autoprovisioning of Microsoft Defender for Containers Components.mov
Avoid Use of the Root Account
Basic Tools for AWS Security
Best Practices for Container Security
Breaking Down AWS Security
Change-Detection Solutions in AWS
Cloud Attacks on the Rise
Configuring Network Border Controls
Create Policies for Usage of Critical Technologies
Creating a Data Flow Diagram
Creating a Network Diagram
Deploying Security Patches on EC2 Instances
Disabling Insecure Ports and Protocols
Do All Keys Have Resources Attached?
Do Not Use API Keys at the Project Level
Do Not Use RSASHA1 for DNSSEC Key-Signing Keys
Documenting a Systems Inventory in AWS
Does AWS Provide Vendor Defaults?
EC2 Instances in Availability Zones
Enable Autoprovisioning of Vulnerability Assessment for Machines
Enable DNSSEC to Protect DNS Protocols
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 Multi-Factor Authentication for Non-Service Accounts
Enable VPC Flow Logs for Every Subnet
Enabling AWS Config in All Regions
Enabling CloudTrail Log File Validation
Enabling CloudTrail in All Regions
Encrypt Dataproc Cluster Using Customer Managed Encryption Key
Encrypting Traffic In and Out of AWS
Encryption Decisions for Your Technology Stack
Encryption Opportunities
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
Enforcing Strong Encryption in AWS
Enforcing Strong TLS Ciphers
Ensure Autoprovisioning of the Log Analytics Agent Is Enabled for Azure VMs
Ensure Corporate Login Credentials are Used
Ensure KMS Cryptokeys 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 Databases Is Enabled
Ensure Microsoft Defender for Key Vaults Is Enabled
Ensure No Weak SSL Cipher Suites Are Permitted
Ensure Service Accounts Can't Access Admin Privileges
Ensure the Minimum TLS Version for Storage Accounts Is Set to 1.2
Ensure to Restrict SSH Access from the Internet
Ensuring Role Assumption is Logged
Establish Policy to Disconnect Vendor Sessions When Not in Use
Evaluate Public IP Addresses Regularly
Events that Drive Key Rotation
Exclusively Use GCP-Managed Service Account Keys
FAQs for Amazon S3 Security
Filters and Alarms in CloudWatch
GuardDuty Alerts for Control Failures
House Accounts in CloudTrail
How to Configure Encryption for EBS Volumes on Existing EC2 Instances
How to Configure Encryption for RDS
How to Configure Encryption for S3 Buckets
How to Restrict Public Access to S3 Buckets
How to Use Your AWS Report
Identify Unrestricted Access to Ports for Security Groups
Identifying and Ranking Vulnerabilities in AWS
Ignite, Launch, and Lift-Off
Industry Best Practices for Configuration Standards
Introduction to AWS Security Hub
Introduction to AWS WAF and Shield
Introduction to Amazon CloudWatch
Introduction to Amazon EKS
Introduction to Amazon Inspector
Introduction to Amazon S3 Access Points
Logging Tools in AWS
MFA for API Calls
Meeting Firewall and Router Configuration Standards
Migrate Away from RSASHA1 for DNSSEC Zone-Signing Keys
Migrate Legacy Networks to VPC Networks
Monitor Network Traffic with VPC Flow Logs
Network Segmentation for AWS
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 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.5.1.1: Detect Alert and Address Covert Malware Communication Channels
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 - 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 - 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
Penetration Testing in AWS
Perform Internal and External Vulnerability Scans
Performing Code Review Prior to Release
Physical Security Responsibilities for AWS
Physical Security Responsibilities for AWS Users
Physical Threats for AWS
Practice Regular Key Rotation for Service Accounts
Prevent Shared, Group, or Generic Accounts in AWS
Preventing Public Accessibility on DB Instances
Preventing Publicly Available CloudTrail Logs
Preventing Publicly Available S3 Buckets
Protect Admin Accounts with Security Key Enforcement
Protecting CloudTrail Logs
Re-Keying for Decryption
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 RDP Authorized Access from the Internet
Restricting Access to EBS Snapshots
Reviewing Firewall and Router Configurations
Rotate KMS Encryption Keys Regularly
Route 53 Support for DNSSEC
Run Your AWS Scan
Running Vulnerability Scans After a Significant Change
Securely Store and Access Secrets in Secrets Manager
Systems Manager Maintenance
Testing for Unauthorized Wireless Access Points
The Importance of Patching
The Most Accessible AWS Experts
The Value of Quarterly Internal Vulnerability Scans
Top 10 AWS Mistakes
Understanding the "Deny All" Function
Use Identity Aware Proxy (IAP) to Restrict Access to Network
Use Least Privilege For Users at Project Level Roles
Using Amazon Time Sync Service
Using IAM Policies
Using OWASP's Kubernetes Cheat Sheet
Using S3 Versioning
Using Systems Manager from a Service-Linked Role
Using TLS 1.2 to Encrypt Data in Transit
Using VPC Endpoints to Access Systems Manager
Using an ASV for External Vulnerability Scans
Utilize Microsoft Defender for Azure Cosmos DB
Verify that Microsoft Defender is Enabled for Containers
Welcome to a New Era of KP!
What is an AWS Scan?
When to Use S3 Access Control Lists
Why Use KirkpatrtickPrice Scans
Work with a GCP Expert
You Need an AWS Expert