02 · Testing
Most AWS risk sits in the settings around the workload: who can assume administrator access, which log can be disabled, and which store is reachable from the internet. We review the accounts in scope and separate an immediate guardrail from a design change.
A well-run account is one whose boundaries you can explain.
Organisation structure, accounts, and service control policies
Identity, federation, and paths to privilege
Logging, retention, and who can disable it
Network exposure and public endpoints
Storage, encryption, and public access settings
Backup and key settings that change the blast radius
A prioritised configuration record
Items tied to Well-Architected and ISM themes where that helps the reader
A fix order that separates guardrails from redesign
Notes your cloud team can implement directly
Engagement. A fixed review of the accounts, organisations, and regions named in the scope.
Suitable for. Teams running production on Amazon Web Services who require an independent assessment of the guardrails.
Contact
Book a call about the system, your sector, and what you need to achieve.
Book a call