Talk an Expert⚡ Try For Free
CLOUD/Continuous assessment

AWS, Google Cloud, and Azure, kept under investigation

Connected accounts stay in the research workspace. A public resource or a drifted control is a change to investigate, with the resource itself as evidence.

Find vulnerabilities. Prove their impact.

Cloud package

Three clouds. The same loop.

AWS

Accounts and regions, assessed as they change.

Google Cloud

Projects and hierarchy, with the resource on the finding.

Azure

Tenants and subscriptions, continuously checked.

Workspace is the sibling package

Microsoft 365 and Google Workspace are not cloud accounts. They are a separate surface: tenant and organization settings, investigated the same way, with the observed configuration as evidence.

Evidence

What we can prove about Cloud

Control counts are a published catalog for AWS, Google Cloud, and Azure. They are not a certificate and not a Workspace claim.

790+
Published cloud controls
340 / 212 / 245
AWS / Google Cloud / Azure

  1. Cloud assessment depth is a published control catalog.

    ResultCloud posture publishes 790+ controls: AWS 340, Google Cloud 212, Azure 245 API-auditable. Collectors emit PASS, FAIL, NOT_APPLICABLE, or UNKNOWN. Incomplete API responses are not marked Pass. Trusteed does not issue a certificate.

    MethodCount of CIS-mapped cloud controls as published on Trusteed cloud pages as of the date below.

    Scope · September 2026Connected AWS, Google Cloud, and Azure. Not a Microsoft 365 or Google Workspace control count.

    Cloud Security →Open the AWS counts →

Buying questions

Which cloud stays under investigation?

The Cloud package is AWS, Google Cloud, and Azure. Microsoft 365 and Google Workspace are the Workspace package, investigated the same way.

  1. 01What does the Cloud package cover?
  2. 02Where do Microsoft 365 and Google Workspace fit?
  3. 03When is this the wrong buy?

What does the Cloud package cover?

Published cloud posture includes 790+ controls: AWS 340, Google Cloud 212, Azure 245 API-auditable. Incomplete checks are not marked pass. This product does not issue a certificate.

When is this the wrong buy?

The Cloud package documents what the account is doing. It does not replace a certificate or endpoint protection.

Not a fitWrong buy for a policy binder with no cloud account to connect.

Start investigating →

Find vulnerabilities. Prove their impact.

Connect one account. The next change is the next investigation, with the resource attached.