# AWS security assessment: run the access-layer steps across the whole organization

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

An AWS security assessment of the access layer starts at the organization root: list the accounts, pull the IAM credential report, read the service control policies, turn on IAM Access Analyzer and check the organization trail. This guide gives the order, the AWS service behind each step and the check it answers.

## Seven steps cover an AWS organization

- List every account in AWS Organizations, including suspended and recently created ones.
- Pull the IAM credential report for each account and read root MFA and key age.
- Read the service control policies at the root and in each organizational unit.
- Create an IAM Access Analyzer for the organization and read the external access findings.
- Check security groups and public IP addresses for open admin and database ports.
- Check S3 Block Public Access, data perimeter conditions and customer-managed key policies.
- Check the organization trail, the log archive account and alerts for root sign-in and policy changes.

## Each step maps to checks on the 40-check list

Step 2 answers [root account MFA](/questions/root-account-mfa/) and [long-lived keys](/questions/long-lived-keys/). Step 3 answers [preventive policies](/questions/preventive-policies/) and [tamper protection](/questions/tamper-protection/). Step 4 answers [external access findings](/questions/external-access-findings/). Step 7 answers [audit logs](/questions/audit-logs-everywhere/) and [protected logs](/questions/logs-protected/).

The AWS-specific commands for these and more are on the [AWS security checklist](/aws-security-checklist/).

## AWS tools report on parts of the work

AWS says IAM Access Analyzer provides external access, internal access and unused access analyzers, plus policy validation and policy generation from CloudTrail activity (AWS documentation, read 16 Nov 2026). It charges for unused access analysis by the number of roles and users analyzed (AWS documentation, read 16 Nov 2026).

AWS Security Hub CSPM checks controls against standards such as AWS Foundational Security Best Practices and CIS, and AWS says new accounts get a 30-day free trial (AWS documentation, read 16 Nov 2026). The [options](/options/) page lists both with their makers' descriptions.

## The AWS Well-Architected Security Pillar is the provider yardstick

AWS publishes the Security Pillar of the AWS Well-Architected Framework as its guidance on securing workloads (AWS documentation, read 16 Nov 2026). The tool cites AWS documentation as the primary control for 7 of its 40 checks, where no CIS or NIST control fits the check directly.

Combine this with the scored [assessment](/) to get the order of fixes.

## Command for each step

The commands below are the AWS CLI forms of the seven steps. Run them with credentials that have read-only access in each account.

| Step | Command or console path |
| --- | --- |
| List accounts | aws organizations list-accounts |
| Credential report | aws iam generate-credential-report, then aws iam get-credential-report |
| Service control policies | aws organizations list-policies --filter SERVICE_CONTROL_POLICY |
| External access analyzer | aws accessanalyzer create-analyzer --type ORGANIZATION --analyzer-name org-external |
| Open ports | aws ec2 describe-security-groups --filters Name=ip-permission.cidr,Values=0.0.0.0/0 |
| Public access block | aws s3control get-public-access-block --account-id ACCOUNT_ID |
| Trails | aws cloudtrail describe-trails --include-shadow-trails |

## Cross-account roles deserve their own pass

List roles whose trust policy names an external account and check for an external ID or organization condition, as in [third-party access](/questions/third-party-access/). AWS describes IAM Access Analyzer external access findings as covering resources such as S3 buckets and IAM roles shared with an external entity (AWS documentation, read 16 Nov 2026). Review those findings weekly, as the [external access findings](/questions/external-access-findings/) check asks.

Add AI services to the pass. If Amazon Bedrock agents run in the account, check that each has its own role, as in [own identity](/questions/ai-own-identity/).

## Do the work from the management account only where needed

Organization-level reads, such as the list of service control policies, run from the management account or a delegated administrator. Everything else should run from a read-only role assumed into each member account, so the assessment itself follows the same rule as the [administrator roles](/questions/admin-roles-limited/) check and leaves a trail in CloudTrail.

## An AWS-only assessment misses cross-cloud trust

If the organization also runs Azure or Google Cloud, a service account or app registration can hold keys into AWS. The [workload identity](/questions/workload-identity/) check asks whether workloads use platform-issued identities, which removes most of those secrets. Run the full [cloud security assessment](/cloud-security-assessment/) if you use more than one cloud.

## Related pages

- [Cloud Risk Register Template (XLSX): Columns](/risk-register-template/)
- [Cloud Security Checklist: 15 Items for a New Account](/cloud-security-checklist/)
- [Cloud Security Assessment Checklist: 40 Checks](/cloud-security-assessment-checklist/)
- [All of them](/guides/)

## Sources

- IAM Access Analyzer: https://docs.aws.amazon.com/IAM/latest/UserGuide/what-is-access-analyzer.html (read 16 Nov 2026)
- AWS Security Hub CSPM: https://docs.aws.amazon.com/securityhub/latest/userguide/what-is-securityhub.html (read 16 Nov 2026)
- AWS Well-Architected Security Pillar: https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/welcome.html (read 16 Nov 2026)
- Service control policies: https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecurityriskassessment.com/aws-security-assessment/
