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.
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
Ask for a posture score
Choose a scope and a framework, and the score arrives with its basis.
- 2
See what was not measured
Untested items are listed separately and left out of the denominator.
- 3
Read the reason
Where a check could not run, the reason is kept, for example that no account is connected.
- 4
Close the gap
Connect the missing source or run the test, and coverage rises on the next read.
- 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
Show the board exposure in currency, with coverage
Aribot prices security exposure per system and shows, beside every score, how many controls were tested, so the board can see what the figure rests on.
Framework scores that show how many controls were assessed
Aribot maps findings to the controls in each framework you report on, and every framework score states how many controls were actually assessed.
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.