Introduction to Amazon Inspector

Run Automated Security Checks 
Is your team using Amazon Inspector? This AWS service “tests the network accessibility of your Amazon EC2 instances and the security state of your applications that run on those instances.” It will measure and compare your configurations against industry standards like the CIS Benchmarks. You can integrate Amazon Inspector into your existing information security processes, as well as deployment and production processes. 

We recommend using Amazon Inspector on a weekly basis. It must be implemented in each Region. To leverage Amazon Inspector in your AWS environment, you can utilize these key features:
  • Configuration scanning and activity monitoring engine 
  • Built-in content library
  • Automation through an API 

Transcription 
A great tool available from AWS is Amazon Inspector, which provides automated security assessments for both your network or your hosts individually. Amazon provides AMIs that already have the agent installed, or you can install the agent yourself. Inspector will measure to find vulnerabilities and see if your configurations align with CIS Benchmarks. Inspector is provided on a per Region basis, so you'll need to enable it for each Region. The scan interval that is recommended is per week. You can and should use these scans to measure your configurations against the CIS Benchmarks and to find any vulnerabilities that are in your applications.

Related Videos

5 Benchmarks of Role-Based Access Control Service Accounts
AWS Controls for Implementing a DMZ
AWS Functions to Restrict Database Access
AWS Incident Response Playbook
AWS Password Best Practices
AWS Password Expiration Policies
AWS Password Reuse Policy
AWS Tools for Your SDLC
Access Control Using IAM Instance Roles
Achieving High Availability in AWS
Activate Azure Key Rotation Reminders.mov
Antivirus Solutions on EC2 Instances
Assign Access Based on Business Need to Know
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
Best Practices for Secret Management
Change-Detection Solutions in AWS
Cloud Attacks on the Rise
CloudTrail and CloudWatch Integration
Configuring Network Border Controls
Connect Your AWS Account Using CloudFormation
Creating a Compliant Incident Response Plan
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
Developing a Process for User Authentication
Disabling Insecure Ports and Protocols
Disabling Unused Credentials
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 Maintenance and Backups for RDS
Enable Role Based Access Control (RBAC) for Azure Key Vault
Enabling AWS Config in All Regions
Enabling CloudTrail Log File Validation
Enabling CloudTrail in All Regions
Enabling MFA for All IAM Users
Encrypt Infrastructure to Further Protect Your Environment
Encrypt Kubernetes Secrets Using Keys
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 with Access Controls
Enforcing Strong Encryption in AWS
Enforcing Strong TLS Ciphers
Ensure ALBs Have WAF ACLs Attached
Ensure Container Network Interfaces Support Network Policies
Ensure GKE Nodes are Configured Properly
Ensure KMS Cryptokeys Are Not Publicly Accessible
Ensure RDS Instances are Only Accessible by Internal IPs
Ensure Use of CMKs for Unattached Disks
Ensure that an Expiration Date Is Set for All Keys in Non-RBAC Key Vaults
Ensuring Role Assumption is Logged
Events that Drive Key Rotation
FAQs for Amazon S3 Security
Filters and Alarms in CloudWatch
GKE Authentication and Authorization Best Practices
GKE Cluster Configuration Security Benchmarks
General Policies for Cluster Management
GuardDuty Alerts for Control Failures
House Accounts in CloudTrail
How To Configure Your Cluster Networks
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 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
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
Image Registry and Scanning Best Practices
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 S3 Access Points
Introduction to IAM Access Analyzer
Key Rotation and Management
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
Monitor Network Traffic with VPC Flow Logs
Network Segmentation for AWS
Node MetaData Recommendations in GKE
Only Install Company-Approved Extensions on Your Virtual Machines
PCI Requirement 3.1 - Keep Cardholder Data Storage to a Minimum
PCI Requirement 3.2 - Do Not Store Sensitive Authentication Data After Authorization
PCI Requirement 3.3 Mask PAN when Displayed
PCI Requirement 3.4 Render PAN Unreadable Anywhere it Is Stored
PCI Requirement 3.4.1 Logical Access Management
PCI Requirement 3.5 Document & Implement Procedures to Protect Keys
PCI Requirement 3.5.1 Maintain a Documented Description of The Cryptographic Architecture
PCI Requirement 3.5.2 Restrict Access to Cryptographic Keys
PCI Requirement 3.5.3 Store Secret and Private Keys Used to Encrypt/Decrypt Cardholder Data
PCI Requirement 3.5.4 Store Cryptographic Keys in The Fewest Possible Locations
PCI Requirement 3.6 Document & Implement all Key-Management Processes & Procedures
PCI Requirement 3.6.1 Generation of Strong Cryptographic Keys
PCI Requirement 3.6.2 Secure Cryptographic Key Distribution
PCI Requirement 3.6.3 Secure Cryptographic Key Storage
PCI Requirement 3.6.4 Cryptographic Key Changes at Cryptoperiod Completion
PCI Requirement 3.6.5 Replacing Weakened Keys
PCI Requirement 3.6.6 Using Split Knowledge & Dual Control
PCI Requirement 3.6.7 Prevention of Unauthorized Substitution of Cryptographic Keys
PCI Requirement 3.6.8 Key-Custodian Responsibilities
PCI Requirement 3.7 Security Policies & Operational Procedures
PCI Requirement 4.1 – Use Strong Cryptography & Security Protocols to Safeguard Sensitive CHD
PCI Requirement 4.1.1 – Ensure Wireless Network Transmitting CHD Use Strong Encryption
PCI Requirement 4.3 – Ensure Security Policies and Procedures are Known to all Affected Parties
PCI Requirements 3.2.1, 3.2.2, & 3.2.3 Do Not Store Tracks, Codes, or PINs After Authorization
PCI v4.0 - 3.1.1 & 3.1.2: Have Requirement 3 Policies and Procedures Assigned and In Place
PCI v4.0 - 3.2.1: Only Retain the Minimum Account Data Needed
PCI v4.0 - 3.3.1, 3.3.1.1, 3.3.1.2, & 3.3.1.3: Do Not Retain Any Sensitive Authentication Data
PCI v4.0 - 3.3.2: Encrypt Sensitive Authentication Data If Retained for Any Length of TIme
PCI v4.0 - 3.3.3: (Issuers Only) Store Only the Minimum Amount of Sensitive Authentication Data Needed
PCI v4.0 - 3.4.1: Mask Displayed Primary Account Number
PCI v4.0 - 3.4.2: Do Not Allow Primary Account Numbers to Be Copied When Using Remote Access
PCI v4.0 - 3.5.1.1: Ensure All Hashes Are Keyed
PCI v4.0 - 3.5.1.2: Correctly Utilize Disk-Level Encryption of Primary Account Numbers
PCI v4.0 - 3.5.1.3: Ensure Disk-Level Encryption Meets Requirements
PCI v4.0 - 3.5.1: Store Primary Account Numbers Appropriately
PCI v4.0 - 3.6.1.1: (Service Providers) Document and Describe the Cryptographic Architecture
PCI v4.0 - 3.6.1.3 & 3.6.1.4: Use Fewest Possible Custodians and Locations for Cryptographic Keys
PCI v4.0 - 3.6.1: Use Fewest Possible Number of Key Custodians Locations and Forms
PCI v4.0 - 3.7.1: Utilize Procedures to Generate Strong Cryptographic Keys
PCI v4.0 - 3.7.2 & 3.7.3: Implement Policies and Procedures to Safely Distribute and Store Keys
PCI v4.0 - 3.7.4: Define Cryptoperiods in Policies and Procedures for Key Management
PCI v4.0 - 3.7.5: Properly Retire Replace or Destroy Keys When Appropriate
PCI v4.0 - 3.7.6: Use Split Knowledge and Dual Control for Manual Cleartext Key Management
PCI v4.0 - 3.7.7: Do Not Allow Unauthorized Key Substitution
PCI v4.0 - 3.7.8: Require Key Custodians to Acknowledge and Accept Their Responsibilities
PCI v4.0 - 4.1.1 & 4.1.2: Have Requirement 4 Policies and Procedures Assigned and In Place
PCI v4.0 - 4.2.1.1: Maintain Inventory of Trusted Keys and Certificates
PCI v4.0 - 4.2.1.2: Utilize Strong Cryptography When Transmitting Primary Account Numbers on Wireless Networks
PCI v4.0 - 4.2.1: Properly Secure Primary Account Numbers During Transmission
PCI v4.0 - 4.2.2: Secure Primary Account Numbers When Transmitting via End User Messaging
Penetration Testing for AWS Segmentation Controls
Performing Code Review Prior to Release
Performing a BIA for AWS
Periodically Regenerate Access Keys
Physical Security Responsibilities for AWS
Physical Security Responsibilities for AWS Users
Physical Threats for AWS
Pods Security Policies Benchmarks
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 Against Threats With Extensible Admission Control
Protect Your Data with PCI DSS
Protecting API Gateways with WAF Rules
Protecting CloudTrail Logs
Protecting Web Applications in AWS
Publish and Maintain an Information Security Policy
Quarterly Reviews of Your Security Program
Re-Keying for Decryption
Requirement 4 - Encrypt Transmission of Cardholder Data Across Open, Public Networks
Requirement 4.2 – Never Send Unprotected PAN by End-User Technologies
Restrict Access to CloudTrail Logs in S3 Buckets
Restrict Security Group Access to All Ports
Restricting Access to EBS Snapshots
Retaining Your Audit Trail in AWS
Reviewing Firewall and Router Configurations
Rotate KMS Encryption Keys Regularly
Rotating Access Keys
Route 53 Support for DNSSEC
Routing Outbound Traffic Through NAT Gateways
Running Vulnerability Scans After a Significant Change
Secure Code Development in AWS
Securing Your Log Files
Security Awareness Training for CHD Policies
Separation of Duties in Penetration Testing
Shared Responsibility Matrix in PCI
Support MFA through IAM Policies
Systems Manager Maintenance
Take Advantage of Automatic Key Rotation within Azure Key Vault
Testing Your Business Continuity and Disaster Recovery Plans
Testing for Unauthorized Wireless Access Points
The AWS Shared Responsibility Model
The Difference Between NACLs and Security Groups
The Value of Quarterly Internal Vulnerability Scans
Top 10 AWS Mistakes
Understanding the "Deny All" Function
Use CMEK To Secure GKE Storage
Using AWS KMS
Using Amazon Time Sync Service
Using IAM Instance Roles for AWS Resource Access
Using IAM Policies
Using OWASP's Kubernetes Cheat Sheet
Using Prowler to Evaluate AWS Security
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 a Bastion Host or Session Manager to Limit Access to Port 22
Using an ASV for External Vulnerability Scans
Utilize CMKs for OS and Data Disks
Utilize Private Endpoints for Azure Key Vault
When to Use S3 Access Control Lists
Your Data Backup Strategy in AWS