Cloud Penetration Testing
The cloud shifts the security model, and misconfigurations are the new default vulnerability. We test your AWS, Azure or Google Cloud environment for exploitable weaknesses — from exposed storage to over-privileged roles to escape paths.
Verified Solvex Specialist
Verified by SolvexDirect specialist contact for Solvex engagements
What this means. An authorized Solvex administrator registered and approved this exact public identity. What it does not. Solvex has not inspected the account on the platform, and this is not the platform's own verification.
Solvex specialists never ask for your passwords, recovery phrases, one-time codes, or payments to a personal account. Work, scope and invoices are agreed in writing through the official channels on this site.
Signed authorization required. This engagement is performed only against systems you own or are contractually authorized to have tested, under an agreed scope. See the responsible testing policy.
What's covered
- Cloud configuration and identity-permission testing
- Exposed-service and storage-bucket assessment
- Privilege-escalation and lateral-movement paths in the cloud
- Serverless, container and managed-service testing
- Network and segmentation assessment
- Provider best-practice and benchmark alignment
What you receive
- Cloud pentest report with exploitable findings
- Attack-path analysis specific to your environment
- Prioritised remediation guidance
- Free retest of fixes
- Attestation letter
Evidence and reporting
How the work is kept honest- Evidence, frozen at issuanceFindings tie to something observed. When the report is issued, the evidence behind it is frozen in the same transaction and cannot be edited afterwards.
- A signed reportAn Ed25519 signature covers both the report content and the delivered file. Alter a byte of either and verification fails.
- Signed scope firstTesting starts only after written scope and signed authorization for systems you own or are entitled to have tested.
Anyone holding a Solvex report can verify it publicly without seeing its contents.
Our boundaries
What this engagement does not do, stated before it starts.
- Only cloud accounts you own or are authorised to test
- Testing within the provider's acceptable-use policy
- No denial-of-service against shared cloud infrastructure
- No exfiltration of real data beyond proof of impact
How this engagement runs
- 01
Intake
Tell us the system, the goal and the constraints. If the work is not a good fit, we say so before anyone is invoiced.
- 02
Scope and authorization
Written scope and signed authorization before anything is touched. Security testing runs only against systems you own or are contractually entitled to have tested.
- 03
Investigation or build
Specialists matched to the work. Findings are proven by hand — scanner output is a lead, never a finding.
- 04
Evidence
Every finding ties to something observed. When a report is issued, its evidence is frozen in the same transaction, so what backed the report cannot change afterwards.
- 05
Delivery
A signed report: an Ed25519 signature over both the content and the file, with a short verification reference you can read down a phone.
- 06
Verification and retest
Anyone holding the report can verify it publicly without seeing its contents. Fixes are retested as part of the engagement — “fixed” means we confirmed it.
Questions we are asked
- Which cloud platforms do you test?
- AWS, Azure and Google Cloud, including their managed, serverless and container services. Multi-cloud environments are tested per platform and at their integration points.
- Do we need the provider's permission?
- The major providers permit customer testing of your own resources within their acceptable-use policies; some activities still need notification. We handle those requirements as part of scoping.
- What do you need from us?
- Scoped access to the cloud accounts, a signed authorisation, and context on your architecture. Read access plus a limited test role usually enables the deepest assessment safely.
Related services
Cloud / DevSecOps
Cloud Security Posture Management (CSPM)
Cloud environments drift into risk one change at a time. We assess and help you continuously manage your cloud security posture — catching misconfigurations, compliance gaps and risky changes before they become incidents.
Cloud / DevSecOps
Cloud Configuration Review
A focused, expert review of your cloud account configuration against security best practice. We examine identity, storage, network and logging settings to find the risky defaults and drift that leave the door ajar.
Cloud / DevSecOps
Kubernetes Security Review
Kubernetes is powerful and easy to misconfigure into a breach. We review your clusters against security best practice — RBAC, network policies, pod security, secrets — so your orchestration platform isn't your soft underbelly.