Cyber security · 05
Cloud security review for AWS, Azure and Google Cloud.
We review how your cloud accounts are configured, who and what can do what, and how an attacker who gets one key could move from there to your data.
Overview
In the cloud, the perimeter is your IAM policy. One over-permissive role can undo the rest.
We start with a read-only review of your accounts against recognised benchmarks: storage, networking, logging, encryption and identity.
Then we think like an attacker holding a leaked key or a compromised workload, and trace the permissions that could take them from there to production data.
Standards & frameworks
- CIS Benchmarks
- CREST-aligned
- ISO 27001
- SOC 2
- CVSS 3.1
What we test
What's in scope.
And what we look for.
01 · Identity
Who can do what. IAM is where most cloud breaches start.
IAM policy analysis
Over-permissive roles, wildcard policies and unused access.
Privilege escalation
Permission combinations that let a user or workload grant itself more.
Secrets and keys
Long-lived keys, secrets in code and pipelines, rotation.
Federation and SSO
How human access is granted, reviewed and revoked.
02 · Configuration
How it is set up. Benchmarks and common misconfigurations.
Storage
Public buckets and blobs, encryption and access logging.
Network
Security groups, exposed management ports and segmentation.
Logging and detection
Whether you would notice an attack in progress.
Workloads
Containers, serverless functions and Kubernetes configuration.
Process
How a test runs, start to finish.
- 1
Scope
Accounts, subscriptions or projects agreed, with a read-only role.
- 2
Review
Automated and manual configuration review against benchmarks.
- 3
Attack paths
Manual analysis of how a foothold could escalate to sensitive data.
- 4
Report & retest
Prioritised fixes, often as infrastructure-as-code changes, then a retest.
Deliverables
What ships with
every test.
One report for two audiences: leadership gets the risk, engineers get the evidence and the fix. Here is how that compares with an automated scan.
Read the sample report →“Thank you for protecting MOD's systems and keeping us secure.”
A read-only audit role in each account or subscription. We never need write access for the review itself.
Yes. Our DevOps engineers can apply changes directly or as Terraform and CloudFormation pull requests for your team to review.
It combines a configuration review with attacker-led analysis of escalation paths. If you want active exploitation of cloud workloads, we scope that as well.
Yes, managed Kubernetes services (EKS, AKS, GKE) and their workload configuration are in scope when they are part of your estate.
Scope your cloud security review.
Get a fixed quote.
A developer or security engineer reads every enquiry and replies, not a salesperson.
- Fixed quote after a short scoping call
- NDA available before you share details
- Remediation and retest on every security engagement