Identity escalation
Role assumptions and excessive permissions that expand a controlled foothold.
Cloud penetration testing
Can a small cloud foothold become broad access?
Controlled attack-path testing across cloud identities, workloads and data access.
Human-led testing.
Manually verified findings.
- OSCP-certified testers
- Written testing boundaries
- Actionable remediation
What we investigate
A scope with a purpose.
Workload and data access
Exposed services, secrets, storage permissions and control-plane paths.
Account boundaries
Cross-account trust, network paths and separation of sensitive environments.
What we need from you
- Provider, accounts or subscriptions, and critical workloads.
- Starting access and written authority.
- Provider-policy constraints and a safe test-data plan.
What you can act on
- Evidence of reachable attack paths.
- The identities and resources involved.
- Least-privilege or network fixes, plus paths we could not safely validate.
Reporting and retest terms are agreed in writing. The record separates verified fixes from outstanding work.
Limits matter
What this test does not cover
- Testing the cloud provider or another customer.
- Destructive actions.
- Baseline configuration review. That is a separate deliverable.
Questions before you book
Practical answers.
Do we need a configuration review instead?
A configuration review checks settings against a baseline. A penetration test validates exploitable paths and impact. If you need the inventory of policy gaps first, start with the review.
What does a penetration test cost?
From A$7,500 ex GST for one web application with its API and two user roles. That covers five testing days, the report and a retest of critical and high findings. More applications, endpoints or cloud accounts give an indicative range. The price is fixed once scope is agreed, in writing, before work starts.
How long will it take?
Testing effort and elapsed delivery time are different. We agree both after reviewing the scope, access readiness and your deadline. Leave time for remediation and a focused retest.
A test and a review are different purchases. Testing attacks the account, while a cloud security review reads the configuration and usually finds more per hour. We compare both options in cloud security review vs penetration test. Applications inside the account are web application penetration testing and API penetration testing. If the driver is a maturity level, the Essential Eight ML2 guide for AWS and Azure is the better starting point.
Let’s scope it
Request a quote Let’s define your cloud environments test.
Share the assets and your reason for testing. We will confirm the approach, fee and schedule.
Last reviewed: