Most cloud security incidents aren’t caused by sophisticated attacks, but by basic settings nobody reviewed. This list covers the minimum controls we recommend enabling in any AWS account.
Identity and access
- Protect the root user: enable MFA and don’t use it for day-to-day tasks.
- Use IAM Identity Center or roles instead of users with long-lived access keys.
- Apply least privilege: every person and service gets only the permissions they need.
- Rotate or delete access keys that aren’t in use.
Visibility and logging
- Enable AWS CloudTrail in every region to record every action.
- Turn on Amazon GuardDuty to detect suspicious activity automatically.
- Use AWS Security Hub to centralize findings and measure best-practice compliance.
Data and network
- Block public S3 access at the account level, except for justified exceptions.
- Encrypt data at rest and in transit, with keys managed in AWS KMS.
- Review your security groups: no admin ports open to the entire internet.
A review that repeats
Security isn’t a state, it’s a habit. Teams change, new services appear and permissions pile up. We recommend repeating this review at least once a quarter.
Want to know where your account stands today?
With CloudInsight we assess your environment against these and other Well-Architected practices and deliver an action plan with prioritized fixes.