Ensure AWS Config rules are configured for critical controls
Config rules should be configured to evaluate compliance with security best practices.
Security Impact
Without Config rules, compliance with security controls is not automatically evaluated.
How to Remediate
Deploy AWS managed Config rules for security controls: encrypted-volumes, iam-password-policy, etc.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all AWS Config resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, PCI-DSS, HIPAA compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-config-5
- Service
- AWS Config
- Category
- Compliance
- Severity
- HIGH
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated AWS Config Checks
View all checksEnsure AWS Config is enabled in all regions
Ensure AWS Config is recording all resource types
Ensure AWS Config uses S3 bucket with versioning
Ensure AWS Config S3 bucket is encrypted
Ensure AWS Config uses conformance packs