Require Multifactor Authentication for Administrators
Related Videos
5 Benchmarks of Role-Based Access Control Service Accounts
AWS Functions to Restrict Database Access
AWS Password Best Practices
AWS Password Expiration Policies
AWS Password Reuse Policy
Access Control Using IAM Instance Roles
Activate Azure Key Rotation Reminders.mov
Activate Microsoft Defender for Azure SQL Databases
Allow Azure Services Access to Storage Accounts
Assign Access Based on Business Need to Know
Assign Appropriate Contacts to Essential Roles
Attaching IAM Policies to Groups or Roles
Autoprovisioning of Microsoft Defender for Containers Components.mov
Avoid Use of the Root Account
Basics of Role Assumption
Best Practices for Change Management in AWS
Best Practices for Password Parameters
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 Acceptable Use of Technology Part 1
Define Staff Information Security Responsibilities in Policy
Defining Resources in IAM Policies
Defining Resources in S3 Bucket Policies
Defining Roles and Responsibilities in AWS
Developing a Process for User Authentication
Disable Caching of Second Factor of Authentication Beyond One Day
Disable Public Access Level for Storage Accounts with Blob Containers
Disabling Unused Credentials
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
Documenting a Systems Inventory in AWS
Enable Autoprovisioning of Vulnerability Assessment for Machines
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 Multi-Factor Authentication for Non-Service Accounts
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 MFA for All IAM Users
Encrypt Dataproc Cluster Using Customer Managed Encryption Key
Encrypt Infrastructure to Further Protect Your Environment
Encrypt Storage for Cricical Data with CMKs
Enforce Multifactor Authentication for All Users
Enforce Separation of Duties When Assigning Service Account Roles
Enforce Separation with Access Controls
Enforcing Strong Encryption in AWS
Ensure Autoprovisioning of the Log Analytics Agent Is Enabled for Azure VMs
Ensure Corporate Login Credentials are Used
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 Service Accounts Can't Access Admin Privileges
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 Policy to Manage Your Service Providers
Evaluate Public IP Addresses Regularly
Evaluate and Restrict UDP Access from the Internet
Exclusively Use GCP-Managed Service Account Keys
GKE Authentication and Authorization Best Practices
How to Attach IAM Policies to Groups or Roles
How to Check MFA in a Credential Report
How to Check Use of the Root Account
How to Disseminate an Information Security Policy
How to Find Administrative Privileges in IAM Policies
How to House Multiple Accounts Within an AWS Organization
How to Modify Password Complexity in a Password Policy
How to Modify Permissions to EBS Snapshots
How to Prevent Password Reuse in a Password Policy
How to Use S3 Bucket Policies
IAM Policies for Account Authentication
IAM Policies that Address Administrative Privileges
Identifying Unused Credentials in a Credential Report
Identity and Access Management Benchmarks in GKE
Install Endpoint Protection for All Virtual Machines
Introduction to Amazon S3 Access Points
Introduction to IAM Access Analyzer
Log and Retain All Relevant Activities
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 7 – Restrict Access to Cardholder Data by Business Need to Know.mp4
PCI Requirement 7.1 – Limit Access to System Components and Cardholder Data
PCI Requirement 7.1.1 – Define Access Needs for Each Role
PCI Requirement 7.1.2 – Restrict Access to Privileged User IDs to Least Privileges Necessary
PCI Requirement 7.1.3 - Assign access based on individual personnel’s job classification & function
PCI Requirement 7.1.4 – Require Documented Approval by Authorized Parties
PCI Requirement 7.2 – Establish an Access Control System
PCI Requirement 7.2.1 – Coverage of all System Components
PCI Requirement 7.2.2 – Assignment of Privileges Based on Job Function
PCI Requirement 7.2.3 – Default “Deny-All” Setting
PCI Requirement 7.3 – Document Policies & Procedures for Restricting Access to Cardholder Data
PCI Requirement 8 - Identify and Authenticate Access to System Components
PCI Requirement 8.1 – Define and Implement Policies and Procedures to Ensure Proper User Management
PCI Requirement 8.1.2 – Control Addition, Deletion, and Modification of User IDs, Credentials
PCI Requirement 8.1.3 – Immediately Revoke Access for Terminated Users
PCI Requirement 8.1.4 – RemoveDisable Inactive User Accounts Within 90 Days
PCI Requirement 8.1.5 – Manage IDs Used by 3rd Parties to Access, Support, or Maintain System Comps
PCI Requirement 8.1.6 – Limit Repeated Access Attempts by Locking Out User ID After Six Attempts
PCI Requirement 8.1.7 – Set Lockout Duration to a Minimum of 30 Minutes
PCI Requirement 8.1.8 – Require Re-Authentication After 15 Minutes of Inactivity
PCI Requirement 8.2 – Ensure Proper User-Authentication Management by Something You Know
PCI Requirement 8.2.1 – Use Strong Cryptography to Render All Authentication Credentials Unreadable
PCI Requirement 8.2.3 – Passwords Require a Min. of Seven Characters and Contain Numbers & Letters
PCI Requirement 8.2.4 – Change User PasswordsPassphrases at Least Once Every 90 Days
PCI Requirement 8.2.5 – New Passwords Can’t Be the Same as Any of the Last Four Passwords Used
PCI Requirement 8.2.6 – Set Passwords for First-Time Use and Upon Reset to a Unique Value
PCI Requirement 8.3 – Secure All Individual Non-Console Administrative Access
PCI Requirement 8.3.1 – Incorporate Multi-Factor Authentication for All Non-Console Access
PCI Requirement 8.3.2 – Incorporate Multi-Factor Authentication for all Remote Network Access
PCI Requirement 8.4 – Document and Communicate Authentication Policies and Procedures to All Users
PCI Requirement 8.5 – Do Not Use Group, Shared, or Generic IDs, or Passwords
PCI Requirement 8.5.1 – Remote Access to Customer Premises Must Use Unique Authentication
PCI Requirement 8.6 – Authentication Mechanisms Must Not Be Shared Among Multiple Accounts
PCI Requirement 8.7 – Restrict All Access to Any Database Containing Cardholder Data
PCI Requirement 8.8 – Ensure Policies & Procedures for Authentication are Documented
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 - 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 - 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
Periodically Regenerate Access Keys
Policy to Prohibit Cardholder Data on Remote Technology
Practice Regular Key Rotation for Service Accounts
Prevent Bad Passwords in Azure
Prevent Shared, Group, or Generic Accounts in AWS
Protect Admin Accounts with Security Key Enforcement
Protect Against Malicious Attacks with Azure AD MFA
Protect Cardholder Data Over the Internet
Protect Resources from Unauthorized Access
Reconfirm User Information Regularly
Regularly Rotate API Keys
Require 2 Ways of Authentication for Resetting Passwords
Restrict API Key Use to Specified Hosts and Apps
Restrict API Keys to Applications That Need Access
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 User Authentication to Trusted Locations
Restrict Users from Adding Apps
Restrict and Review SSH Access from the Internet
Restrict and Secure Your Azure Environment
Restricting Access to EBS Snapshots
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
SOC 2 Academy: Access Controls for Remote Employees
SOC 2 Academy: Dealing with External Threats
SOC 2 Academy: Movement of Data
SOC 2 Academy: Preventing and Detecting Unauthorized Software
SOC 2 Academy: Protection Through Logical Access
Screen Employees to Reduce Risk
Securely Store and Access Secrets in Secrets Manager
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
Support MFA through IAM Policies
Take Advantage of Automatic Key Rotation within Azure Key Vault
The Importance of Publishing an Information Security Policy
The Importance of Responsibility Acknowledgement from Service Providers
Understanding the "Deny All" Function
Update Your Policy When Your Environment Changes
Use Least Privilege For Users at Project Level Roles
Using IAM Instance Roles for AWS Resource Access
Utilize CMKs for OS and Data Disks
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
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
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
When to Use S3 Access Control Lists
