WHO THIS HELPS

Clarity across cloud accounts and responsibilities.

For organisations adopting cloud services, preparing for assurance reviews or seeking clarity about inherited configurations.

Conceptual cloud assessment showing identity, configuration, device and evidence controls around a cloud service.

THE PROBLEM TO SOLVE

Broad permissions, unmanaged secrets and unclear logging can persist even when workloads are hosted on a major cloud platform. The shared-responsibility boundary needs to be understood for each service.

What you receive

Receive a scoped configuration assessment, prioritised findings, ownership recommendations and a remediation roadmap. The report identifies evidence gaps and services outside the review.

A DEFINED ENGAGEMENT

What the work can cover.

01

Review of agreed subscriptions, accounts, workloads and trust boundaries.

02

Assessment of identity, privileged access, network exposure and configuration.

03

Review of relevant logging, encryption, secrets and recovery arrangements.

04

Recommendations tied to business risk and operational ownership.

How delivery works

We map the environment and available documentation, agree least-privilege review access, assess the selected controls and discuss feasible improvements with your team.

After delivery

Remediation can be delivered in controlled stages, followed by a configuration reassessment. Ongoing management can track drift where agreed.

What shapes scope and price

Platform mix, subscription or account count, workload diversity, architecture complexity and required implementation depth shape the engagement. Penetration testing is separately authorised and scoped.

Your proposal sets out the deliverables, assumptions, exclusions and responsibilities before work begins. No fixed price or contractual inclusion is implied by this page.

Questions worth asking.

Is this a cloud penetration test?

A configuration and architecture review is different from active exploitation. Testing techniques are specified before access is granted.

Does cloud hosting transfer all security responsibility?

No. Responsibilities vary by service model and contract. Customers retain important duties around identity, configuration, data and operations.

What cloud access is needed for an assessment?

We agree permissions appropriate to the environment and review objectives. Account or subscription boundaries, architecture information and service owners help establish context. Access should be controlled and removed or reviewed when the engagement ends.

Can the assessment cover more than one cloud environment?

It can, where those environments are explicitly included. Subscription count, architecture, identity connections and third-party responsibilities affect coverage. The proposal should state which accounts, services and integrations are included and which need separate work.

Does the assessment include making cloud configuration changes?

The assessment identifies findings and a practical improvement plan. Implementation can be scoped separately with change approval, pilot checks and rollback considerations. Assessment access should not be treated as blanket permission to alter production services.

LET’S DEFINE THE RIGHT SCOPE

Agree the scope of your cloud assessment

Outline the cloud platforms, accounts and workloads you want reviewed. We can scope a configuration assessment and any separately authorised testing or implementation.

Microsoft 365 Security →
Penetration Testing →
Virtual CISO →