Cloud
AWS security review
AWS risk is usually about configuration and identity rather than a single vulnerability. A useful review tests whether IAM, storage, networking, logging and workloads can be abused to expose data or gain control.
Core AWS areas to review
Focus on the controls that affect real compromise paths: IAM privilege, public exposure, secrets, logging, network boundaries, workload identity and data stores.
- IAM roles, policies, permission boundaries and federation
- S3, snapshots, backups and sensitive data exposure
- Security groups, public endpoints and management planes
- CloudTrail, GuardDuty, logging retention and alerting
Read-only access is usually enough
Most cloud configuration reviews can be performed with scoped read-only access. Risky proof-of-concept actions should be agreed separately before execution.
What good output looks like
Good findings explain the affected resource, abuse path, business impact, least-privilege fix and whether the same pattern exists elsewhere.
FAQ
Common questions
Is this the same as a CIS benchmark scan?
No. Benchmarks are useful, but a security review prioritises exploitable paths and data exposure over generic drift.
Can you review multiple AWS accounts?
Yes. Multi-account environments can be reviewed across organisations, accounts, IAM trust and shared services.
Can you provide Terraform guidance?
Yes. Where useful, remediation can include infrastructure-as-code guidance for repeatable fixes.