02.3 / Service
Cloud Assumed-Breach Test
We start from a realistic foothold in your cloud tenant, like a phished user account, and show you how far an attacker could get and how to stop them.
- Timeline
- Typically 2–3 weeks of testing
- Pricing
- Fixed scope, quoted after a short scoping call
What it is
Most cloud breaches don’t start with a clever exploit. They start with one stolen password or session token. In this test, you give us the access a typical compromised user would have, and we see what an attacker could reach from there: email, files, admin roles, other tenants, and your on-premises network.
Who it’s for
- Companies running on Microsoft 365, Entra ID, Azure, AWS, or Google Cloud
- Teams that have MFA and conditional access in place and want to know if they actually hold up
- Companies where a customer or insurer is asking about cloud security controls
What’s included
- Starting foothold. A standard user account you create for the test, with the same access as a typical employee.
- Identity and privilege review. Paths from that account to admin roles, through misconfigured permissions, app registrations, or group membership.
- Data exposure. What sensitive files, mailboxes, and shared resources that account can reach that it shouldn’t.
- Control testing. Whether your MFA, conditional access, and alerting notice what we’re doing.
- Non-destructive by default. We stop at proof. We don’t delete, encrypt, or change production data.
What’s not included
- Phishing your employees to get the starting account
- Denial-of-service testing
- Testing tenants or services you don’t own or control
What you get
- An executive summary and technical report with attack paths, evidence, and fixes
- A list of what your monitoring did and didn’t catch
- A walkthrough with your IT team
What we need from you
- A signed agreement and written authorization
- A test account and the tenant or subscription IDs in scope
- A technical contact during testing
- Any rules from your cloud provider or managed service provider that apply
— / Next step
Start with a short call.
Tell us what prompted the question. We'll tell you whether we can help and what it would take.