Skip to main content

Offensium Vault

AWS Security Misconfigurations: 8 Common Risks to Fix

AWS Security Misconfigurations: 8 Common Risks to Fix
Spread the love

Most cloud breaches are not caused by sophisticated zero-day exploits. They happen because something was set up the wrong way: an over-permissive IAM role, a storage bucket that should have been private, a database open to the internet or logging that was never turned on. AWS security misconfigurations are among the most common and preventable causes of data exposure for growing companies.

This guide covers the AWS security misconfigurations we see most often, why they matter and how to find and fix them before an attacker does.

The Shared Responsibility Model in Brief

AWS follows a shared responsibility model. AWS is responsible for security of the cloud: the physical data centres, hardware and core infrastructure. You are responsible for security in the cloud: identities and permissions, network rules, data protection, operating systems and application configuration. Every misconfiguration below sits on the customer side of that line.

The Most Common AWS Security Misconfigurations

1. Over-Permissive IAM Policies

  • Users, roles or services with wildcard permissions such as "Action": "*" or "Resource": "*".
  • Long-lived access keys for IAM users, often left in code repositories or laptops.
  • No multi-factor authentication on the root account or privileged users.
  • Unused roles and users that still have active permissions.

Overly broad permissions turn a small compromise, such as one leaked key, into full account takeover.

2. Publicly Accessible S3 Buckets

AWS has enabled S3 Block Public Access by default for new buckets since April 2023, but older buckets and buckets where settings were changed can still expose data. Watch for public bucket policies, permissive ACLs and pre-signed URLs with very long expiry times.

3. Open Security Groups

Security groups that allow inbound traffic from 0.0.0.0/0 to SSH (22), RDP (3389), databases or admin panels give attackers a direct path to brute-force or exploit those services. Restrict access to known IP ranges or use private connectivity such as Session Manager or a VPN.

4. Exposed Databases and Snapshots

RDS instances marked as publicly accessible, unencrypted databases, and EBS or RDS snapshots shared publicly can all leak sensitive data without any exploit at all.

5. Missing or Incomplete Logging

Without CloudTrail enabled in every region, VPC flow logs and service-level logs, you may not detect an intrusion or be able to investigate it. In India, incomplete logs can also make it harder to meet CERT-In’s log retention and reporting requirements, as explained in our CERT-In guidelines guide.

6. Weak Encryption and Secrets Management

  • Data stored without encryption at rest, or with keys managed loosely.
  • Secrets such as database passwords stored in environment variables, code or AMIs instead of AWS Secrets Manager or Parameter Store.

7. Instance Metadata Service v1 (IMDSv1)

EC2 instances that still allow IMDSv1 are more exposed to server-side request forgery (SSRF) attacks that steal temporary credentials from the metadata service. Enforcing IMDSv2 adds session-based protection.

8. Unmonitored and Forgotten Resources

Test environments, old API gateways, unused load balancers and shadow accounts often miss patches and monitoring, which makes them easy entry points.

Impact and Quick Fixes at a Glance

Misconfiguration Possible impact Quick fix
Wildcard IAM permissions Full account takeover from one compromised identity Apply least privilege, use IAM Access Analyzer
Public S3 bucket Mass data exposure Enable Block Public Access at account level
Open security groups Brute force or exploitation of exposed services Restrict sources, use Session Manager or VPN
Public databases or snapshots Direct data theft Disable public access, encrypt, review sharing
No CloudTrail or flow logs Undetected breaches, failed investigations Enable organisation-wide logging and retention
IMDSv1 enabled Credential theft via SSRF Require IMDSv2 on all instances

How to Find AWS Security Misconfigurations

  1. Use native tools: AWS Security Hub, AWS Config rules, IAM Access Analyzer and GuardDuty provide continuous visibility.
  2. Benchmark your setup: compare accounts against the CIS AWS Foundations Benchmark and the AWS Foundational Security Best Practices standard.
  3. Review identities manually: automated tools flag issues, but understanding which permissions are genuinely needed requires context.
  4. Test from an attacker’s view: a cloud security assessment combines configuration review with penetration testing to show which misconfigurations are actually exploitable.

AWS Hardening Checklist

  1. Enable MFA on the root account and lock away root credentials.
  2. Replace long-lived IAM user keys with roles and single sign-on.
  3. Apply least-privilege policies and remove unused identities.
  4. Enable S3 Block Public Access at the account level.
  5. Restrict security groups and remove direct internet access to admin ports.
  6. Encrypt data at rest and manage secrets centrally.
  7. Enable CloudTrail in all regions, VPC flow logs and GuardDuty.
  8. Enforce IMDSv2 on EC2 instances.
  9. Tag resources and regularly remove unused ones.
  10. Schedule regular cloud security reviews and penetration tests.

Running containers on EKS? Our upcoming guide to Kubernetes security covers the cluster-specific risks, and our container security service can help review them.

Frequently Asked Questions

Who is responsible for AWS security misconfigurations, AWS or the customer?

Under the AWS shared responsibility model, AWS secures the underlying cloud infrastructure, while customers are responsible for how they configure their own services, including identity and access, network rules, storage permissions, encryption and logging. Most cloud breaches come from customer-side misconfiguration.

Are new S3 buckets public by default?

No. Since April 2023, AWS enables S3 Block Public Access and disables access control lists by default for all new buckets. Older buckets, or buckets where these settings were changed, can still be exposed, so they should be reviewed regularly.

How often should we review our AWS configuration?

Continuous monitoring with tools such as AWS Config and Security Hub is recommended, combined with an in-depth manual review at least once a year and after major architectural changes, new accounts or migrations.

Conclusion

AWS gives you powerful security controls, but they only work when configured correctly. By fixing the most common AWS security misconfigurations, including over-permissive IAM, public storage, open network access, missing logs and weak secrets management, you remove the easiest paths attackers use to reach your data.

Want an expert review of your AWS environment? Contact the Offensium Vault team about a cloud security assessment, or explore our cybersecurity services.

Where we work: Offensium Vault provides penetration testing for businesses in India, UAE, USA, UK, Australia and clients worldwide, delivered remotely from India.

Free 30-minute consultation

Want an expert view of your security?

Talk to our ISO 27001 certified team about penetration testing, cloud security or compliance. No obligation, and we are happy to sign an NDA.

Book a Free ConsultationExplore our services →
Penetration testing for businesses in India · UAE · USA · UK · Australia and clients worldwide — delivered remotely from Bhubaneswar, India.
Chat on WhatsApp