Ensure Soft Delete Is Enabled

Related Videos

5 Focus Areas for AWS Compliance
AWS Controls for Implementing a DMZ
AWS Tools for Your SDLC
AWS Web Application Firewall Defaults
Activate Azure Key Rotation Reminders.mov
Activate Microsoft Defender for Azure SQL Databases
Allow Azure Services Access to Storage Accounts
Authenticate and Authorize Users with Client Certificates
Autoprovisioning of Microsoft Defender for Containers Components.mov
Avoid Using Default Service Account When Configuring Instances
Benefits of a Gap Analysis
Best Practices for Container Security
Best Practices for Secret Management
Cloud Security Posture Management
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
Configuring Network Border Controls
Consider an Exclusionary Geographic Access Policy
Create Activity Log Alert for Delete SQL Server Firewall
Create Policies for Usage of Critical Technologies
Create a Minimal Audit Policy for Logging
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
Do Not Enable Serial Ports for VM Instance
Do Not Use Project-Wide SSH Keys When Authenticating Instances
Don't Face Cloud Security Alone
Enable Autoprovisioning of Vulnerability Assessment for Machines
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 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
Enable Shielded VM to Ensure Operating System is Trustworthy
Encrypt BigQuery Datasets with Customer Managed Encryption Key (CMEK)
Encrypt Infrastructure to Further Protect Your Environment
Encrypt Storage for Critical Data with CMKs
Enforce Multifactor Authentication for All Users
Ensure ALBs Have WAF ACLs Attached
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 Container Network Interfaces Support Network Policies
Ensure Diagnostic Setting Captures Appropriate Categories
Ensure GKE Nodes are Configured Properly
Ensure Guest Accounts Are Restricted
Ensure HTTP(S) Access from the Internet Is Reviewed and Restricted
Ensure Kubernetes Idle Timeout Parameter is Appropriately Set
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 No Weak SSL Cipher Suites Are Permitted
Ensure Notifications are Enabled for Password Resets
Ensure Only Administrators Can Create Groups
Ensure Only Authorized Users Can Create Security Groups
Ensure RDS Instances are Only Accessible by Internal IPs
Ensure Secure Transfer
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
Ensure to Restrict SSH Access from the Internet
Establish Policy to Disconnect Remote Sessions
Establish Policy to Disconnect Vendor Sessions When Not in Use
Establish a Policy to Manage Your Service Providers
Evaluate Public IP Addresses Regularly
Evaluate and Restrict UDP Access from the Internet
GKE Cluster Configuration Security Benchmarks
General Policies for Cluster Management
Greg Halpin Audit Tip
Harden Cloud SQL Database with Logging
House Accounts in CloudTrail
How To Configure Your Cluster Networks
How to Configure Kubelet Within Your Environment
How to Disseminate an Information Security Policy
How to Leverage a Remediation Plan
How to Prepare for a Gap Analysis
How to Use Your AWS Report
IP Forwarding Should Not Be Enabled for Instances
Image Registry and Scanning Best Practices
Industry Best Practices for Configuration Standards
Install Endpoint Protection for All Virtual Machines
Introduction to AWS Network Firewall
Introduction to Amazon EKS
Introduction to PCI DSS Requirement 1
Introduction to PCI Requirement 2.mp4
Learn from an Azure Expert
Leverage CIS Benchmarks for Cloud Security
Leverage Confidential Computing to Protect Data
Log and Retain All Relevant Activities
Manage Access Securely Using Uniform Bucket-Level Access
Meeting Firewall and Router Configuration Standards
Migrate Away from RSASHA1 for DNSSEC Zone-Signing Keys
Migrate Legacy Networks to VPC Networks
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
Network Segmentation for AWS
Networking Configurations in Kubernetes Environment
Node MetaData Recommendations in GKE
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 DSS Requirement 1.1.1 - Implementing a Change Control Program
PCI DSS Requirement 1.1.2 and 1.1.3 - Network Documentation Best Practices
PCI DSS Requirement 1.1.4 - Establishing a Firewall and DMZ
PCI DSS Requirement 1.1.6 Documentation of Business Justification & Approval for use of all Services, Ports and Protocols
PCI DSS Requirement 1.1.7 - Review Firewall and Router Rule Sets
PCI DSS Requirement 1.2 Restrict Connections to Untrusted Networks
PCI DSS Requirement 1.2.1 Restrict Traffic to that which is Necessary
PCI DSS Requirement 1.2.2 Secure and Synchronize Router Configuration Files
PCI DSS Requirement 1.2.3 Install Firewalls Between all Wireless Networks and the CDE
PCI DSS Requirement 1.3 Examine Firewall and Router Configurations
PCI DSS Requirement 1.3.1 - Establishing a DMZ
PCI DSS Requirement 1.3.2 Limit Inbound Internet Traffic
PCI DSS Requirement 1.3.3 - Implement Anti Spoofing Measures
PCI DSS Requirement 1.3.4 - Deny Unauthorized Outbound Traffic
PCI DSS Requirement 1.3.5 - Permit Only Established Connections into the Network
PCI DSS Requirement 1.3.6 Segregate the CDE from the DMZ
PCI DSS Requirement 1.3.7 Do Not Disclose Private IP Addresses
PCI DSS Requirement 1.4 Install Personal Firewall Software
PCI DSS Requirement 1.5 Ensure Security Policies are Known to all Affected Parties
PCI Requirement 2.1 - Always Change Vendor-Supplied Defaults
PCI Requirement 2.1.1 - Change all Wireless Vendor Defaults
PCI Requirement 2.2 - Develop Configuration Standards for all System Components
PCI Requirement 2.2.1 - Implement Only One Primary Function Per Server
PCI Requirement 2.2.2 - Enable Only Necessary Services, Protocols and Daemons
PCI Requirement 2.2.3 - Implement Additional Security Features
PCI Requirement 2.2.4 - Configure System Security Parameters to Prevent Misuse
PCI Requirement 2.2.5 - Remove all Unnecessary Functionality
PCI Requirement 2.3 - Encryption
PCI Requirement 2.4 - Maintain an Inventory of In-Scope System Components
PCI Requirement 2.5 - Ensure Security Policies Are Known to All Affected Parties
PCI Requirement 2.6 - Shared Hosting Providers Must Protect Each Entity’s Hosted Environment
PCI Requirement 6.4 – Follow Change Control Processes & Procedures for Changes to System Components
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 - 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 - 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
Partner with Gap Analysis Experts
Perform Your Azure Scan
Periodically Regenerate Access Keys
Pods Security Policies Benchmarks
Policy to Prohibit Cardholder Data on Remote Technology
Prevent Bad Passwords in Azure
Preventing Publicly Available S3 Buckets
Protect Against Malicious Attacks with Azure AD MFA
Protect Against Threats With Extensible Admission Control
Protect Cardholder Data Over the Internet
Protect Kernel Defaults Through Configuration Settings
Remove Default Networks from All Projects
Require 2 Ways of Authentication for Resetting Passwords
Require Multifactor Authentication for Administrators
Restrict API Permissions If Using Default Service Accounts
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 RDP Authorized Access from the Internet
Restrict Unnecessary External Access in Cloud SQL
Restrict Users from Adding Apps
Restrict and Review SSH Access from the Internet
Restrict and Secure Your Azure Environment
Review and Restrict RDP Access from the Internet
Reviewing Firewall and Router Configurations
Risky Sign-Ins: What They Are and How to Prevent Them
SOC 2 Academy: Change Control Processes
SOC 2 Academy: Change Management Best Practices
Screen Employees to Reduce Risk
Service Providers to Establish Charters for Information Security Program
Set Expectations for Daily and Quarterly Reviews in Your Policy
Specify Customer-Managed Encryption Key (CMEK) as Default in BigQuery Datasets
Systems Manager Maintenance
The Importance of Patch Management in Virtual Machines
The Importance of Publishing an Information Security Policy
The Importance of Responsibility Acknowledgement from Service Providers
Update Your Policy When Your Environment Changes
Use Customer Supplied Encyryption Keys (CSEK) for Critical VM Disks
Use Identity Aware Proxy (IAP) to Restrict Access to Network
Use TLS to Encrypt All Connections in Cloud SQL
Utilize Flow Logs to Log Traffic in Your Environment
Utilize Managed Disks for Virtual Machines
Utilize Private Endpoints to Access Storage Accounts
Verify Only Administrators Manage Group Membership Access
What is the Google Kubernetes Shared Responsibility Model
What to Include in a List of Service Providers
What to Include in a Written Contract with Service Providers
OSZAR »