Skip to content
Cloud Security Risk Assessment

AWS security checklist: 12 access checks to run in every account

The AWS security checklist here picks 12 of the 40 access-layer checks and says where to look in AWS for each: the IAM credential report, security groups, S3 Block Public Access, service control policies, IAM Access Analyzer and CloudTrail. Run them in every account of the organization. Read 16 Nov 2026.

Start the assessment ยท All guides

Twelve checks cover the AWS access layer

The checks below come from the 40-check assessment checklist. They are the ones with a direct AWS console or CLI test. Run each in every account of the organization, not only the production account, because one forgotten account is enough for a path in.

CheckWhere to look in AWS
Root or global administrator has phishing-resistant MFA and no keysIn the IAM console credential report, check that the root row shows mfa_active true and access_key_1_active and access_key_2_active false, in every account of the organization.
Long-lived keys removed or rotated every 90 daysDownload the IAM credential report and sort by access_key_last_rotated and access_key_last_used; every active key older than 90 days is a finding.
Workloads use platform-issued identitiesCheck that EC2, ECS, EKS and Lambda use execution or instance roles and that CI systems use OIDC federation to assume roles instead of stored access keys.
No admin or database port open to the internetDescribe security groups with ip-permission.cidr 0.0.0.0/0 on ports 22, 3389, 3306, 5432 and 1433, or use the matching AWS Config managed rules.
Metadata service hardenedDescribe instances and check MetadataOptions.HttpTokens is required, and that the account default under EC2 data protection and security is set to required.
Public object storage blocked organization-wideCheck S3 Block Public Access at the account level in every account, or the organization-level policy, with all four settings on.
Sharing limited to your own organizationCheck SCPs or resource control policies for aws:PrincipalOrgID and aws:ResourceOrgID conditions, and test with Access Analyzer external access findings.
External access findings reviewed weeklyCheck that an IAM Access Analyzer for the organization exists with external access type, and count active findings and their age.
Deny policies at the organization levelList SCPs attached to the organization root and OUs (aws organizations list-policies) and check they deny actions such as disabling logging or leaving the organization.
Guardrails protected from tamperingCheck SCPs deny cloudtrail:StopLogging, config:StopConfigurationRecorder and guardduty:DeleteDetector except for a security role.
Audit logs on in every account and regionCheck for an organization trail covering all regions with management events, and data events for sensitive S3 buckets.
Logs stored where workload admins cannot change themCheck the trail's destination bucket is in a log archive account with Object Lock and CloudTrail log file validation enabled.

The CIS AWS Foundations Benchmark is the reference for the root and logging checks

The first check cites the CIS AWS Foundations Benchmark (controls 1.4 and 1.5 in the edition the tool cites). CIS announced AWS Foundations Benchmark v7.1.0 in its November 2026 update, and CIS lists expanded AWS Organizations and IAM coverage, enhanced access and credential management guidance and a new section on AWS Bedrock security and governance as highlights (CIS, read 16 Nov 2026).

Check the control numbers against the edition you hold before you cite them in an audit. The tool refers to CIS controls by number and short title only.

Three AWS services give most of the evidence

The IAM credential report shows root MFA, key age and key use for every user in an account, which answers root account MFA and long-lived keys in one file. AWS describes IAM Access Analyzer as finding resources shared with an external entity, internal access to chosen resources and unused access (AWS documentation, read 16 Nov 2026).

AWS Trusted Advisor is a third source. AWS says that with Basic Support you can use the console for all Service Limits checks and selected checks in the Security and Fault tolerance categories, and that all checks need Business Support+, Enterprise Support or Unified Operations (AWS documentation, read 16 Nov 2026). The options page lists the AWS tools side by side.

Organization-level controls beat account-by-account fixes

Four of the twelve checks are set once at the organization level: deny policies, tamper protection, the organization boundary and the organization trail. Service control policies reach every member account, so a single deny covers accounts created next year.

Fix the low-effort items first. Root account MFA, open admin ports, IMDSv2, S3 public access and audit logging are all rated low effort and weigh 3 in the score.

The checklist leaves out workload and posture scanning

Vulnerabilities in workloads and general posture scanning are separate jobs with their own tools and are not covered here. For an AWS-specific walk-through of a full assessment, see the AWS security assessment guide.

Sources

  1. IAM Access Analyzer, read 16 Nov 2026
  2. AWS Trusted Advisor, read 16 Nov 2026
  3. CIS Benchmarks November 2026 Update, read 16 Nov 2026
  4. IAM security best practices, read 16 Nov 2026
  5. Service control policies, read 16 Nov 2026

Last reviewed 16 Nov 2026.