Vulnerability Assessment · Service

Cloud configuration review.

Using read-only access you grant, we review how your cloud accounts are set up and show you which settings expose data or give people more access than they need.

Overview

What this covers

Cloud platforms make it quick to create storage, databases, servers and user accounts. The same speed means settings are often chosen once, under time pressure, and never revisited. A storage bucket made public for a quick test, an access key with full administrator rights, or logging that was never switched on can each go unnoticed for a long time.

Our cloud configuration review looks at your AWS, Azure or Google Cloud accounts through read-only access that you create and control. We examine identity and access management, storage and database exposure, network rules, encryption settings, logging and monitoring, and the use of secrets and keys. The CIS Benchmarks for each platform serve as a reference point alongside our own review.

This is a review of configuration, not an attack on your environment. Nothing is changed. You receive a prioritised list of issues with the specific setting involved and how to correct it, so your engineers can work through it account by account.

Deliverables

What you get

Access guidance

Clear instructions for creating a read-only role for the review, so you stay in control of what we can see and can remove access at the end.

Findings report

Each issue rated by severity, with the affected resource, the current setting and why it matters.

Remediation steps

The specific change needed for each finding, written for the engineers who manage the accounts.

Identity and access summary

An overview of who and what holds broad permissions, highlighting accounts and keys that have more access than their job needs.

Recheck and confirmation

Once you have made changes, we recheck the affected settings and confirm in writing which issues are closed.

Approach

How we run it

  1. 01

    Agree the scope

    We confirm which cloud accounts, subscriptions or projects are included and how read-only access will be granted.

  2. 02

    Collect configuration

    Using the read-only role, we gather the settings for identity, storage, networking, encryption and logging.

  3. 03

    Review

    Settings are assessed against the CIS Benchmarks and against how your environment is actually used, with each finding verified by hand.

  4. 04

    Report and walk through

    Findings are prioritised and explained to your engineers on a call.

  5. 05

    Recheck

    We confirm the changes you make and record the result in writing.

Questions

Before you ask.

What access do you need?

Read-only access to the accounts in scope, through a role or user you create. We provide guidance on setting it up and recommend you remove it when the engagement ends.

Will you change anything in our accounts?

No. The review is read-only. Every change is made by your team, using the guidance in the report.

Do you cover more than one cloud provider?

Yes. We review AWS, Azure and Google Cloud, and an engagement can cover accounts on more than one of them.

Does this make us compliant with a standard?

No review can do that on its own. The report can support your compliance work by showing which settings were reviewed and what was found and fixed.

Talk to us about cloud configuration

Tell us what you want tested. We will reply with a proposed scope, the authorisation we need, and a quote.