
Most AWS accounts that have never had a security review do not have one problem. They have a long list of findings, and no way of telling which five matter.
The short answer: an AWS security review is only useful if it tells you what to fix first. Sorting findings by severity does not, because severity ignores whether a weakness connects to anything an attacker wants. Linking findings into attack paths, from the internet or an outside account to administrator access or sensitive data, changes the order: the fix that breaks the most paths goes first, and many "high" findings that sit on no path can wait. Run it from a role that is truly read-only, treat what it could not see as unknown, not clean, and re-check after you fix.
For CTOs, heads of engineering and founders running on AWS without a dedicated security team.
A typical AWS security assessment produces a list: an open security group, an access key nobody has used in months, an unencrypted volume, a role with more permissions than it needs. The instinct is to sort by severity and work down. That order is usually wrong, for three reasons.
An attack path joins findings into a chain from an entry point to a target. Entry points are the ways in: the internet, a principal in another AWS account, or a credential that has leaked. Targets are what an attacker wants: administrator-equivalent access to the account, or a store of sensitive data.
That is what AWS attack path analysis is for: it does not replace the list, it gives it an order.
The example below is illustrative. It is not taken from any real account.
| Step | What the review saw | Why it is a step |
|---|---|---|
| Entry: the internet | SSH open to anywhere on a web server with a public IP address | Anyone can attempt to reach the server |
| Step 2: the server | The server still allows the older instance metadata service (IMDSv1) | A request the server can be tricked into making can read its role's temporary credentials more easily |
| Step 3: the role | The server's instance role has administrator permissions | Whoever holds those credentials holds the account |
| Target | Administrator-equivalent access | The path is complete |
How to read it:
A useful AWS security audit checklist covers six areas, each of which tends to play a particular part on a path.
| Area | What to check | How it shows up on a path |
|---|---|---|
| Network | Admin ports open to the internet in security groups or network ACLs; all-traffic rules; rules on default security groups; public load balancers and outdated TLS; Lambda function URLs and API Gateway routes without authentication; DNS records pointing at deleted resources | Usually the entry point |
| Identity | Root access keys and root MFA; users without MFA; old keys, and unused users with active keys; administrator principals; roles that can escalate their own privileges; cross-account trust without an external ID; admin instance roles; external access found by IAM Access Analyzer | Usually the step that turns a foothold into control |
| Data | Public S3 buckets and account-level Block Public Access; public snapshots and AMIs; queue, topic, key and registry policies open to anyone; unencrypted EBS and RDS; open OpenSearch domains; CloudFront origins reachable directly | Usually the target, sometimes the entry |
| Servers | Instance metadata v1 still allowed; public IP addresses; instances not managed by Systems Manager; deprecated Lambda runtimes; public EKS endpoints; publicly accessible RDS; outdated AMIs, database engines and operating systems | The middle of a path: where an entry becomes access to a role |
| Logging | CloudTrail across all regions with log file validation; GuardDuty on; VPC flow logs; AWS Config recording; activity in regions you do not use; KMS key rotation | Rarely a step; decides whether you would notice anyone walking one |
| Credentials and stored secrets | Stored secrets that are never rotated; databases still on a static master password; an inventory of which credentials exist at all | A leaked or long-lived credential is an entry point in its own right |
Two optional areas go deeper and need more access: known vulnerabilities on servers and packages, and secrets left in configuration, such as keys in function settings, server user data or deployment templates. AWS's own IAM security best practices are a sound reference for the identity rows; they recommend MFA, least privilege and regularly removing unused users, roles and credentials.
A review that adds a new way into your account has defeated its own purpose, so check "read-only" line by line.
SecurityAudit and ViewOnlyAccess.A cybersecurity risk assessment is the larger exercise across vendors, people and compliance; an AWS security review is one input to it.
AWS offers two related services. The comparison below uses AWS's own documentation.
| AWS Security Hub CSPM | AWS Security Hub (latest) | A point-in-time attack path review | |
|---|---|---|---|
| How it runs | Inside your accounts, continuous checks | Inside your accounts, enabled per account or across an organisation | When you choose, from a read-only role |
| What it checks against | Standards: AWS Foundational Security Best Practices, CIS, PCI DSS, NIST | Correlates CSPM, Amazon Inspector, Macie and GuardDuty signals into exposure findings | Misconfigurations linked into paths to admin access or data |
| Attack paths | Not described in the CSPM overview | Yes, an attack path graph | Yes, with fixes ranked by paths broken |
| Prerequisites | AWS Config enabled and recording, for most controls | Uses findings from the services it correlates | A role in the account |
| Response | Automation rules, EventBridge | Automated response workflows and ticketing integrations | A report for a person to act on |
| Cost | 30-day free trial, then billed by AWS | See AWS's Security Hub pricing | Depends on the provider |
Sources: Security Hub CSPM and Security Hub documentation.
If you need continuous monitoring, compliance scores or automatic response across an organisation, Security Hub is built for that. If you need an ordered answer to "what do we fix first in this account?" without switching services on, a point-in-time path review is the shorter route. They are not exclusive.
AWS Cloud Security is this review as a product on Tomorrow Central. You connect an account with a read-only role from a CloudFormation template; only Tomorrow Central can use it, with a code tied to your connection, for an hour per session at most. A scan runs 53 read-only checks across the six areas, in every enabled region, links what it finds into attack paths and ranks the fixes by how many paths each one breaks. Severity is adjusted for the paths a finding is on, and anything the scan could not read is listed as a gap. Two optional scans, for known vulnerabilities and for secrets left in configuration, are off until you allow them on the role; a secret scan keeps only a fingerprint and a masked preview of what it finds, never the value.
Its limits: it scans one account at a time, when you run it; it does not evaluate service control policies or permission boundaries, so permission steps are marked possible; it does not score compliance, monitor continuously or fix anything for you; and it is not a complete security assessment.
A structured read of one AWS account's configuration to find what an attacker could use: who can reach what from the internet, which identities and keys are too powerful, which data is exposed and what is not being logged. A good review ends with an ordered list of fixes, not just a list of findings.
At least six areas: network exposure, identity and access keys, data stores and their policies, servers and runtimes, logging and detection, and stored credentials and secrets. The checklist matters less than the order you fix things in, which is where attack paths help.
Security Hub runs inside your accounts, checks them continuously against standards such as AWS Foundational Security Best Practices and CIS, relies on AWS Config for most checks, and in its latest version correlates findings into exposure findings with an attack path graph. A point-in-time path review runs when you choose from a read-only role and ranks fixes by the paths they break. They answer different questions, and many teams will want both.
Before an audit, a launch or a customer's security questionnaire, after a significant change to the account, and after each round of fixes to confirm they held. If you need to know within hours when something changes, you need continuous monitoring as well.
No. A configuration review reads how the account is set up; it does not test, probe or attack anything. A penetration test tries to exploit what is running. The review tells you where a tester's time is best spent.
To run this review on one of your accounts, request access to AWS Cloud Security on Tomorrow Central; it is switched on for each organisation while it is new. If you would rather have the review run, interpreted and the fixes carried out for you, see ITMTB's cybersecurity services or contact us.
We work with mid-to-large enterprises to map cloud exposure, identity risk, vendor dependencies, infrastructure vulnerabilities, and compliance readiness — and deliver a remediation roadmap with named owners, not just a list of findings.