Cloud security assessment

Cloud Security Assessment

Read-only review of your cloud and SaaS environments against CIS benchmarks and CISA SCuBA baselines, with the attack paths that connect them and a 30/60/90 roadmap.

Platforms

Infrastructure, identity, and SaaS

Attackers don't stop at the edge of one console. We review the platforms you run together, in one engagement.

Infrastructure

AWS, Azure, GCP

  • IAM
  • Network exposure
  • Storage and data exposure
  • Logging and detection
  • Workload configuration
Identity & SaaS

Google Workspace, Microsoft 365 / Entra ID

  • Admin model
  • MFA and SSO
  • OAuth and third-party app access
  • Sharing and data exposure
  • Email authentication
  • Audit logging
Standards

Measured against published baselines

CIS Foundations Benchmarks

The CIS Foundations Benchmark for each platform in scope.

AWS · Azure · GCP · Workspace · M365

CISA SCuBA baselines

CISA's Secure Cloud Business Applications baselines for Google Workspace and Microsoft 365.

Workspace · M365
Read-only

We look. Your admins change.

The assessment runs on read-only access to your configuration. We don't change settings, and we agree on the exact access method during scoping. A benchmark result is only the start, so a senior operator reviews each gap in context and tells you which ones matter.

We'll sign your NDA and MSA before any work begins.

01
Measure

Each platform against its CIS benchmark and SCuBA baselines.

02
Connect

The gaps that chain together across platforms.

03
Plan

Prioritized fixes, sequenced into 30, 60, and 90 days.

Two tiers

Pick the depth you need

Both tiers apply to any platform above.

Configuration Assessment

Where your settings stand against the baselines.

  • Each platform in scope reviewed against its benchmarks and baselines
  • Each gap with the setting, the risk, and the fix
  • Prioritized by what matters in your environment
  • Remediation retest included
Architecture Review

Everything in the Configuration Assessment, plus how an attacker would move through your environment.

  • Stakeholder interviews
  • Trust-boundary diagram
  • Attack-path analysis
  • Remediation retest included
Add-ons

Go further where it counts

Add it to either tier.

Adversarial validation

We prove the risky paths by attempting them: OAuth consent abuse, delegation and role abuse, external sharing, and email spoofing. Agreed in writing before it starts.

OAuth · Delegation · Sharing · Spoofing
Deliverables

What you get

The report

An executive summary your leadership can read, plus each finding with the current setting, the risk, the benchmark reference, and the fix.

30/60/90 roadmap

Fixes sequenced by risk and effort, so your team knows what to do first and what can wait.

Findings tracker

A working list of every finding your team can assign, update, and close.

Readout

A live walkthrough with your team to go over what we found, why it matters, and what to do next.

Remediation retest

Included in both tiers. Fix what we found, and we retest it. Retests are included within 90 days of report delivery, and the report is updated to show which findings are closed.

Scoping

What we need to scope it

Send what you have. Rough answers are fine for a first pass, and we'll come back with a scope, a timeline, and a fixed price.

  • Platforms. Which of AWS, Azure, GCP, Google Workspace, and Microsoft 365 are in scope.
  • Size. Rough count of cloud accounts, subscriptions, or projects, and SaaS users.
  • Tier and add-on. Which tier you're leaning toward, and whether you want adversarial validation.
  • The driver and the date. Audit, customer review, insurance, or your own initiative, and when you need the report.
  • A contact. The admin who can set up read-only access for us.
FAQ

Cloud assessment questions

What access do you need?
Read-only access to the configuration of each platform in scope. We agree on the exact method during scoping. We don't change settings. Your team makes the fixes.
Can you cover more than one cloud in one engagement?
Yes. One engagement can cover any mix of AWS, Azure, GCP, Google Workspace and Microsoft 365, including the attack paths that cross from one to another.
How long does it take?
Typically 2 to 4 weeks, depending on the tier and how many platforms and accounts are in scope. We'll confirm the timeline when we scope it.
Does it include exploitation?
Only with the adversarial validation add-on. The Configuration Assessment and the Architecture Review are read-only. Adversarial validation is the only active work, and it only runs against targets and accounts we agree on in writing first.

Find out how your environments connect.

Tell us your platforms and your date. We'll come back with a scope, a timeline, and a fixed price.