Cloud and SaaS
Cloud Penetration Testing
Validate cloud permissions and attack paths within authorised accounts and tenants. Findings explain how compromised identities or workloads could expose data, alter resources or affect recovery.
01 / Overview
Assessment objectives and control obligations
Cloud assessment reconstructs effective authorisation across identity policies, resource grants, federation trust and organisational guardrails. Analysis follows compute and service identities to sensitive storage, secrets, snapshots and key administration. Workload compromise is evaluated against the authority available in its execution context, including indirect access absent from console role summaries.
Bounded API operations corroborate consequential paths while minimising sensitive collection. Preventive enforcement and audit visibility are assessed independently. Findings identify the principal, action, resource and governing policy interaction; provider-managed infrastructure and unrelated tenants remain outside the authorised customer boundary.
02 / Technical analysis
Failure mechanisms and security implications
Control of an application can expose workload authority without a secret in the source. Policy analysis is corroborated with allowed API behaviour so recommendations address effective access and the responsible party.
03 / Scope
Technical coverage and authorisation boundaries
Coverage is agreed in writing before testing begins. The rows below describe what this service normally examines. Exclusions, testing windows and escalation contacts are recorded in the rules of engagement.
- Effective permissions
- Role trust, resource policy, federation and escalation.
- Workload and data access
- Metadata, secrets, storage, snapshots and key administration.
- Guardrails and visibility
- Sensitive operation restrictions and audit coverage.
- Supporting tools
- Environment-appropriate instrumentation may include ScoutSuite, Prowler, PMapper, Pacu, CloudFox, Provider assessment utilities. Selection follows the investigative objective, compatibility requirements and approved operating constraints. Automated output requires corroboration against implementation evidence or observed execution before classification as a substantiated finding.
04 / Methodology
Investigation and validation methodology
Threat-informed test design aligns architectural trust boundaries, attacker prerequisites and consequential business outcomes. Automated discovery supports attack-surface coverage; manual validation establishes reachability, effective authority and the causal mechanism of each substantiated control failure.
01
Scope and safeguards
Before active work
We agree assets, test identities, techniques, windows, exclusions and stop conditions, and confirm required third party permissions.
02
Map policy and workload trust
Identify authorised accounts, identities and sensitive destinations.
03
Validate selected authority
Use bounded actions to confirm access and the controls that restrict it.
04
Review and verification
Agreed delivery
Findings pass technical review. We explain remediation and, where agreed, verify the correction during the retest window, including relevant bypass cases.
05 / Assessment options
Access models and evidential confidence
Supplied access determines investigative reach, validation depth and evidential confidence. The proposal records the access model, supporting material and unresolved coverage limitations; no model implies unrestricted authority or exhaustive verification.
- Black box
- Testing starts without supplied credentials or internal design material. External exposure is examined, while authenticated workflows may remain inaccessible.
- Grey box
- Representative accounts and selected design information support direct comparison of roles, tenants and sensitive workflows.
- White box
- Source, configuration and design evidence support root cause analysis. Runtime and access limitations are still recorded.
06 / Deliverables
Decision-support and verification deliverables
Deliverables distinguish what was observed, what was concluded and where the evidence stops. The agreed scope states which evidence, review sessions and retesting are included.
Executive summary
The summary explains the demonstrated exposure, the business functions affected and the treatment decisions required, including material uncertainty.
Technical findings
Each confirmed issue records the affected assets, prerequisites, reproduction evidence and a specific remediation. Technical severity is presented separately from business priority.
Coverage and limitations
The record identifies the systems, identities and conditions tested, together with exclusions and assumptions that affect interpretation.
Treatment and retest status
Recommendations are sequenced by risk, dependency and ownership. Any agreed retest records resolved, partly resolved and unresolved issues without implying a new assessment.
Service specific evidence
Principal, action, resource, policy state and observed API result support precise remediation.
07 / References
Applicable technical references
References are selected for the technology and objective in scope, and the edition applied is recorded. A framework mapping supports review; it is not certification or proof of complete compliance.
- AWS IAM policy evaluation
- Provider documentation explains how applicable policy types allow or restrict requests. Assessment retains principal, resource, action and condition context instead of reducing access to a role name.
- Google Cloud IAM allow policies
- Official guidance explains policy bindings and resource hierarchy inheritance. The review also considers applicable restrictive policies and service identity relationships.
- MITRE ATT&CK
- Observed adversary behaviours support scenario selection and reporting. Mappings retain procedure context and outcome; a technique label does not prove complete detection coverage.
08 / Safeguards
Operational safeguards and evidence governance
Active work is conditional on written authority from the appropriate asset owner and approved rules of engagement. The operating plan specifies permitted procedures, testing windows, prohibited actions, third-party restrictions and nominated stop authority. Unexpected instability or suspected genuine compromise triggers suspension of affected activity pending the client’s operational decision.
Evidence governance applies purpose limitation, data minimisation and access proportionality to collection, transfer, processing, retention and disposal. The signed terms define authorised recipients and any external processing arrangement. Publication, secondary use and disclosure of client material require the applicable written permission.
Conclusions distinguish substantiated exposure, untested consequence and residual uncertainty. Each material finding identifies the control obligation, causal mechanism, observed outcome and verification criteria for the proposed treatment. Technical severity informs analysis; prioritisation and acceptance of residual risk remain decisions for the client’s authorised risk owner.
Provider policies and shared responsibility constrain testing. Broad role names do not establish exposure.
09 / Suitability
Commissioning criteria
Use after cloud migration, material IAM change or discovery of workload compromise paths.
Next step
Define the assessment you need
Tell us the business decision, the systems involved and any operational constraint. We will explain the coverage proposed, the access required and the evidence the engagement can provide.
- Confidentiality first
A mutual confidentiality agreement is signed before any technical detail is exchanged, so scope discussions can happen safely.
- Scope and cost in writing
Deliverables, access expectations, timeline and fee are confirmed before the engagement begins, and a scope change needs agreement.
- Answered by the delivery team
The consultants who scope an engagement are the consultants who perform it and explain the result to your team.
