← All use cases

Cloud Security Platform · Cloud Security & Digital Twin

A posture score that shows which accounts it covers

Scan results across connected accounts, where the headline score states how many accounts it was computed over and unscanned accounts stay on the list.

1. Start the scan · 2. Read each account · 3. Flag what was refused · 4. Score with coverage1Start the scan2Read eachaccount3Flag what wasrefused4Score withcoverage

The problem

Our posture score is one number for the whole estate, and everyone assumes the whole estate was read. An account that refused access contributes nothing and drops out of the report. When the score moves, we can't tell whether posture changed or coverage did.

How Aribot handles it

  1. 1

    Start the scan

    Choose the connected accounts to put in scope.

  2. 2

    Read each account

    Live resources are checked against security standards, account by account.

  3. 3

    Flag what was refused

    An account that could not be read is marked NOT SCANNED and kept on the list.

  4. 4

    Score with coverage

    The score is computed only from what was read and shown beside an account-coverage figure.

What you get

  • A score that states its basis
  • Unscanned accounts kept in view
  • Coverage reported as its own figure, so month-on-month changes can be explained
  • Checks passed and failed for each account and each provider

Related use cases