AWS · Azure · Google Cloud
Cloud Security Assessment
An in-depth review of your AWS, Azure and Google Cloud environments: identity and access, storage exposure, encryption, network segmentation and monitoring, with the fixes ranked by risk.
- AWS, Azure and Google Cloud
- CIS Benchmarks
- Prioritised fixes
In one sentence
What is a cloud security assessment?
A cloud security assessment is an in-depth evaluation of your cloud environments to find misconfigurations, identity and access flaws, storage exposure, encryption gaps and weak network segmentation, so you can strengthen the foundations of your cloud security.
Cloud environments change daily. A configuration that was safe last year may expose data today. We review your environment against CIS Benchmarks and each provider's best practices, and confirm which weaknesses an attacker could actually use.
What we need from you
- Read-only access to the accounts, subscriptions or projects in scope
- An overview of your architecture
- A contact for questions during the review
Scope
What we review
The foundations of your cloud security, account by account.
Identity and access
Roles, users, groups, policies and permission boundaries: who can do more than they should.
- IAM
- Entra ID
- Least privilege
Storage and data exposure
Buckets, blobs, databases and snapshots that are public or shared too widely.
- Storage
- Snapshots
- Sharing
Network and segmentation
Virtual networks, security groups and exposed services.
- Security groups
- VPCs and VNets
- Exposure
Encryption and keys
Encryption at rest and in transit, and how keys and secrets are managed.
- KMS
- Key Vault
- Secrets
Logging and monitoring
Whether activity is logged everywhere and whether alerts would fire.
- Audit logs
- Alerts
- Retention
Infrastructure as code
Templates and pipelines that create your environment, so fixes stick.
- Terraform
- Templates
- Pipelines
Approach
Testing approaches based on access
Choose how much you share with us. More context means deeper coverage in the same time.
No prior knowledge
Black box
We look for your cloud services and data exposed to the internet, with no credentials.
Accounts and some context
Grey box
With typical user or developer roles, we test privilege escalation and insecure service interactions.
Full access
White box
With read access to configurations and policies, we review the whole environment in depth.
Engagement
How we work with you
Scope online
Describe what you need in Flint, our scoping platform. Answer only the questions that apply.
Proposal, signed online
Effort, price and the statement of work are built from your answers.
Ready for day one
Authorisation, test accounts and rules of engagement are agreed before testing starts.
Senior-led testing
Certified consultants lead the test. Our own AI framework, Striker AI, takes on the repetitive work.
Report and retest
Your report is ready in Slate, our client portal, within 48 hours of testing ending.
What you receive
Everything stays in one place, in your own client portal.
- A report in Slate within 48 hours of testing ending
- Every finding with evidence, a risk rating and a fix
- An executive summary for leadership
- Retests you can request finding by finding
- Downloads as PDF or Excel
- Evidence you can hand to your auditors
Standards
Standards we assess against
Aligned with industry frameworks and the providers' own best practices.
- CIS Benchmarks
- MITRE ATT&CK for Cloud
- ISO/IEC 27017
- NIST
- AWS, Azure and Google Cloud best practices
Which clouds do you assess?
What access do you need?
Do we need permission from the cloud provider?
How is this different from a cloud red team?
When will we receive the report?
Contact
Tell us what you need to test
A senior tester reads every message and replies directly.
What happens next
- A senior tester replieswith any questions about your scope.
- You scope it in Flintor on a short call, if that is quicker.
- A proposal you sign onlinewith effort, price, dates and the statement of work.
Prefer email? Write to [email protected]
