← All use cases

Platform & Strategy · CXO Workbench & Economic Intelligence

Report untested controls as untested

Aribot keeps unmeasured as its own visible state, so every score carries its coverage and an untested control never counts as a pass.

1. Ask for a posture score · 2. See what was not measured · 3. Read the reason · 4. Close the gap · 5. Report both figures1Ask for aposture score2See what was notmeasured3Read the reason4Close the gap5Report bothfigures

The problem

Our posture report shows a control nobody tested the same way as a control that passed. Percentages arrive without a denominator, so a high score over a small sample reads as estate-wide. We find the gap at audit, which is the worst place to find it.

How Aribot handles it

  1. 1

    Ask for a posture score

    Choose a scope and a framework, and the score arrives with its basis.

  2. 2

    See what was not measured

    Untested items are listed separately and left out of the denominator.

  3. 3

    Read the reason

    Where a check could not run, the reason is kept, for example that no account is connected.

  4. 4

    Close the gap

    Connect the missing source or run the test, and coverage rises on the next read.

  5. 5

    Report both figures

    The report pack states the score and how much of the estate it covers.

What you get

  • Coverage shown beside every score
  • A list of controls never evaluated, each with the reason it could not run
  • Board and audit packs that say what was not measured
  • A clear next action for each gap

Related use cases