Incident to report to a regulator?Incident to report? Intake Line

Security testing

Cloud Security Assessment

Most cloud incidents come from configuration, not from the cloud provider. We review who can do what in your AWS, Azure or Google Cloud environment, verify what is really exposed to the internet and check your setup against CIS Benchmarks.

Written scope and rules of engagement first · Recognised methods · Retest on request · Download the Service Sheet (PDF)

Request a Proposal

A principal consultant replies within one working day. No sales sequence.

Add details (optional)
  • Next available start: week of Monday 23 November

We use your details only to prepare your proposal and treat your answers as confidential; we sign your NDA on request. Privacy notice

500+ Regulations Laws and standards
40 Countries Europe, Gulf, Asia and North America
25+ Years In regulated sectors
9 Industries From banking to healthcare

WHY IT MATTERS

In the cloud, one permission can be the whole perimeter

The problem

Fast change, wide permissions

Teams move quickly, and wide roles and public storage are easy to create and easy to forget.

  • Over-broad roles
  • Public storage and snapshots
  • Logging not switched on everywhere

The solution

Policies read, exposure tested

We review your configuration with read-only access, then verify from the outside what really is reachable.

  • Read-only access
  • Automated and manual review
  • Several accounts, subscriptions or projects

The outcome

A cloud setup you can explain

You know the real risks across accounts, and the changes that reduce them most.

  • Fixes by service
  • Priorities by exposure
  • Evidence for customers and auditors

What we check

What we test

For each requirement we review the evidence and check that the control works, so you know exactly where you stand.

Identity and access

Roles and policies that give more than they should, and paths to higher privileges.

Attack surface

Storage, compute, databases and APIs that answer from the internet, each one verified.

Configuration

Encryption, logging, network rules and account settings across your services.

Detection

Whether the logs you need exist and are protected.

Container Security

A test of your container platform from outside and from inside a compromised pod, with a hardening review against the CIS Kubernetes Benchmark.

HOW IT RUNS

From scope to verified fixes

The phases stay the same; their length follows your scope.

A typical engagement
  1. Before testing

    Scoping

    Targets, people, test windows and exclusions, with written authorisation and rules of engagement.

  2. Phase 1

    Access review

    Read-only access set up; identity and access policies reviewed.

  3. Phase 2

    Attack surface

    Public services identified and verified; configuration compared with the benchmark.

  4. After testing

    Report

    Findings with evidence, risk and a fix, a management summary and a walkthrough with your team.

  5. On request

    Retest

    We check your fixes and update the report.

A guide, not a fixed promise: the length of each phase depends on your scope.

GET A PROPOSAL

Tell us what you want tested

Tell us the targets and any deadline. We send a written proposal with scope, dates and a fee.

WORKING WITH US

What it takes from your side

A named contact, the access we agree and a little of your team's time.

Your trusted contact

One person who knows the test is happening, makes decisions and can reach the right people if something needs to stop.

Targets and exclusions

Addresses, accounts and documents for what is in scope, and clear limits on what is not. You inform any provider or third party affected.

Testing carries some risk

We agree windows and limits to keep it low. No test can promise to find every weakness; it shows what we found in the agreed scope and time.

What you receive

The cloud security report

Each finding with its evidence, risk, the steps to reproduce it and a fix.

PDF

A management summary

What was tested, the main risks and the decisions needed, without the technical detail.

In the report

A walkthrough

A session with your team to go through the findings and answer questions.

Video call

A retest on request

We check your fixes and update the report, so you can show the result to auditors and customers.

Updated report

Why organisations choose GRC+

Independent of your suppliers

We test what you have. We take no margin on a product we assess or recommend.

Findings tied to your requirements

Our team also works on NIS2, DORA, ISO 27001, PCI DSS and Swift CSP, so results can serve your audits too.

Risk rated for your business

We rate each finding by what it could cost you, not only by a scanner's score.

Written rules of engagement first

Scope, limits and contacts are agreed in writing before any test starts.

FAQ

Cloud Security Assessment: frequently asked questions

Something else? Ask us in a 30-minute call.

Book a 30-Minute Call

Do you need permission from the cloud provider to test?

AWS, Microsoft and Google allow customers to test many of their own services without asking first, under their published policies. We check the current policy against your scope before we start.

What do you need to test our cluster?

A test namespace with a pod we can use as a starting point, read access for the benchmark and the design review, and your network and platform documents.

What access do you need to our cloud environment?

A read-only role in your AWS accounts, Azure subscriptions or Google Cloud projects, which you create for the assessment and remove afterwards. We do not change anything in your environment.

Do you test production clusters?

We can, with agreed limits. A staging cluster built the same way is often a better place to try attack paths, with a read-only check of production.

What does a cloud security assessment cost?

The fee follows your scope. You receive a written proposal with scope, dates and a fee before any work starts.

Plan your cloud security assessment

In 30 minutes you learn what is in scope, how we would approach it and what drives the fee. A written proposal follows within two working days. sales@grc.plus +44 74 7927 55 00

Related: Source Code ReviewPenetration Testing

Request a Proposal

A principal consultant replies within one working day. No sales sequence.

Add details (optional)
  • Next available start: week of Monday 23 November

We use your details only to prepare your proposal and treat your answers as confidential; we sign your NDA on request. Privacy notice

Loading the form…