How to Check Use of the Root Account

Related Videos

5 Benchmarks of Role-Based Access Control Service Accounts
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 Password Best Practices
AWS Password Expiration Policies
AWS Password Reuse Policy
AWS Security Needs a Growth Mindset
AWS Tools for Your SDLC
AWS Web Application Firewall Defaults
Access Control Using IAM Instance Roles
Achieving High Availability in AWS
Activate Microsoft Defender for Azure SQL Databases
Allow Azure Services Access to Storage Accounts
Antivirus Solutions on EC2 Instances
Assign Access Based on Business Need to Know
Assign Appropriate Contacts to Essential Roles
Assigning Information Security Management Responsibility
Attaching IAM Policies to Groups or Roles
Attributes of Log Data
Audit Trail Review with Kibana, Athena, and GuardDuty
Audit Your Security Groups for Insecure Ports and Protocols
Avoid Use of the Root Account
Basic Tools for AWS Security
Basics of Role Assumption
Best Practices for Change Management in AWS
Best Practices for Container Security
Best Practices for Password Parameters
Breaking Down AWS Security
Change-Detection Solutions in AWS
Cloud Attacks on the Rise
Cloud Security Posture Management
CloudTrail and CloudWatch Integration
Configuring Network Border Controls
Connect Your AWS Account Using CloudFormation
Connect with AWS Security Experts
Consider Remote Assessment Competency & Experience
Consider an Exclusionary Geographic Access Policy
Consistently Manage User Accounts with OS Login
Create Policies for Usage of Critical Technologies
Create a Review Process for Apps
Create a Review Process of Guest Users
Creating a Data Flow Diagram
Creating a Network Diagram
Define Acceptable Use of Technology Part 1
Defining Business Continuity and Disaster Recovery
Defining Resources in IAM Policies
Defining Resources in S3 Bucket Policies
Defining Roles and Responsibilities in AWS
Deploying Security Patches on EC2 Instances
Determining Remote Assessment Feasibility
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 Insecure Ports and Protocols
Disabling Unused Credentials
Do All Keys Have Resources Attached?
Do Not Allow Users to Remember MFA on Devices They Trust
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?
Don't Face Cloud Security Alone
EC2 Instances in Availability Zones
Enable Autoprovisioning of Vulnerability Assessment for Machines
Enable DNSSEC to Protect DNS Protocols
Enable Maintenance and Backups for RDS
Enable Multi-Factor Authentication for Non-Service Accounts
Enable Multifactor Authentication for Administrators
Enable Multifactor Authentication for All Users
Enable VPC Flow Logs for Every Subnet
Enabling AWS Config in All Regions
Enabling CloudTrail Log File Validation
Enabling CloudTrail in All Regions
Enabling MFA for All IAM Users
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 Multifactor Authentication for All Users
Enforce Separation of Duties When Assigning KMS Related Roles
Enforce Separation of Duties When Assigning Service Account Roles
Enforce Separation with Access Controls
Enforcing Strong Encryption in AWS
Enforcing Strong TLS Ciphers
Ensure ALBs Have WAF ACLs Attached
Ensure Corporate Login Credentials are Used
Ensure Guest Accounts Are Restricted
Ensure HTTP(S) Access from the Internet Is Reviewed and Restricted
Ensure KMS Cryptokeys Are Not Publicly Accessible
Ensure No Weak SSL Cipher Suites Are Permitted
Ensure Notifications are Enabled for Password Resets
Ensure Only Administrators Can Create Groups
Ensure RDS Instances are Only Accessible by Internal IPs
Ensure Service Accounts Can't Access Admin Privileges
Ensure to Restrict SSH Access from the Internet
Ensuring Role Assumption is Logged
Establish Confidentiality & Security Requirements for Remote Assessments
Establish Policy to Disconnect Vendor Sessions When Not in Use
Evaluate and Restrict UDP Access from the Internet
Events that Drive Key Rotation
Exclusively Use GCP-Managed Service Account Keys
FAQs for Amazon S3 Security
Filters and Alarms in CloudWatch
GKE Authentication and Authorization Best Practices
Greg Halpin Audit Tip
GuardDuty Alerts for Control Failures
House Accounts in CloudTrail
How to Attach IAM Policies to Groups or Roles
How to Check MFA in a Credential Report
How to Configure Encryption for EBS Volumes on Existing EC2 Instances
How to Configure Encryption for EBS Volumes on New EC2 Instances
How to Configure Encryption for RDS
How to Configure Encryption for S3 Buckets
How to Edit Inbound Traffic Rules for Default Security Groups
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 Restrict Public Access to S3 Buckets
How to Use S3 Bucket Policies
How to Use S3 Versioning and Lifecycle Rules
How to Use Your AWS Report
IAM Policies for Account Authentication
IAM Policies that Address Administrative Privileges
Identify Unrestricted Access to Ports for Security Groups
Identify if EC2 Instances Are Directly Connected to the Internet
Identifying Assets, Threats, and Vulnerabilities
Identifying Unused Credentials in a Credential Report
Identifying and Ranking Vulnerabilities in AWS
Identity and Access Management Benchmarks in GKE
Ignite, Launch, and Lift-Off
Industry Best Practices for Configuration Standards
Introduction to AWS Network Firewall
Introduction to AWS Security Hub
Introduction to AWS WAF and Shield
Introduction to Amazon CloudWatch
Introduction to Amazon Detective
Introduction to Amazon EKS
Introduction to Amazon Inspector
Introduction to Amazon S3 Access Points
Introduction to IAM Access Analyzer
Join the KirkpatrickPrice Community
Key Rotation and Management
Learn from an AWS Security Expert
Leverage CIS Benchmarks for Cloud Security
Load Balancers Must Require TLS 1.2
Logging Tools in AWS
Logging Web ACL Data in Amazon Kinesis
MFA for API Calls
Meeting Firewall and Router Configuration Standards
Meeting Your Baseline with Patch Manager
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
New Cloud Security Capabilities for the Online Audit Manager
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
Our Security Standards
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.2 – Verify User Identity Before Modifying Any Authentication Credential
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 - 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 - 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
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
Practice Regular Key Rotation for Service Accounts
Prevent Bad Passwords in Azure
Prevent Shared, Group, or Generic Accounts in AWS
Preventing Public Accessibility on DB Instances
Protect Admin Accounts with Security Key Enforcement
Protect Against Malicious Attacks with Azure AD MFA
Regularly Rotate API Keys
Remove Default Networks from All Projects
Require 2 Ways of Authentication for Resetting Passwords
Require Multifactor Authentication for Administrators
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 RDP Authorized Access from the Internet
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 and Restrict RDP Access from the Internet
Risky Sign-Ins: What They Are and How to Prevent Them
Rotate KMS Encryption Keys Regularly
Rotating Access Keys
SOC 2 Academy: Access Controls for Remote Employees
SOC 2 Academy: Additional Points of Focus for Logical Access
SOC 2 Academy: Assigning Roles and Responsibilities
SOC 2 Academy: Dealing with External Threats
SOC 2 Academy: How to Perform Thorough Inventory
SOC 2 Academy: Movement of Data
SOC 2 Academy: Preventing and Detecting Unauthorized Software
SOC 2 Academy: Protection Through Logical Access
SOC 2 Academy: Registering Internal and External Users
Securely Store and Access Secrets in Secrets Manager
Support MFA through IAM Policies
Systems Manager Maintenance
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 IAM Instance Roles for AWS Resource Access
Using IAM Policies
Using Systems Manager from a Service-Linked Role
Using VPC Endpoints to Access Systems Manager
Utilize Private Endpoints to Access Storage Accounts
Verify Only Administrators Manage Group Membership Access
What is an AWS Scan?
When to Use S3 Access Control Lists
Your AWS Accountability Partner