Your encryption-at-rest control passes on 92% of the 60% of systems you can assess — how do you report it?
answer
- two numbers, never their product
- 92% of what we can see, and we can see 60%
- coverage is the headline at this level
- different owners fix each number
- exclusion needs approver, rationale, expiry
basics
~20 sReport both numbers separately, never their product and never the flattering one alone: coverage of the estate, and pass rate within that coverage. Name what is unassessed and who owns closing it, with a dated plan to raise coverage first.
solid answer
~50 sThe sentence I would use is: 92% of what we can see, and we can see 60%. Publishing 92% alone claims something about systems nobody looked at. Blending to 55% is equally wrong in the other direction, because it asserts the unassessed 40% would fail, which is unknown. The two numbers also drive different work by different people: coverage is closed by getting enumeration and credentials into accounts they are not in, which is usually an ownership and access problem, while pass rate is closed by remediation. So I present coverage as the headline metric with a dated plan and a named owner, and the pass rate underneath it as a secondary figure. If a business unit wants part of the estate declared out of scope, that is a legitimate outcome, but as a recorded risk decision with a named approver, a written rationale and an expiry — not a quiet edit to a collector's configuration.
go deeper
Know that a compliance figure should always arrive with a statement of how much of the estate it covers, and that a percentage with no coverage figure attached cannot be interpreted.
Be able to explain why blending coverage and pass rate into one number is a claim about systems nobody examined, and why the two figures are closed by different kinds of work.
Show the operational side: the unassessed bucket broken out by reason, each reason routed to an owner, and coverage tracked as its own metric with dates rather than as a footnote.
Own the reporting standard and the exclusion process. Decide what a scope reduction requires — approver, rationale, expiry — and design reporting so that discovering more systems is rewarded rather than punished.
This is a reporting and governance question rather than a technical one, and it is where control programmes most often lose their integrity. The pressure is always toward one number that is green. ## Three ways the number gets faked, all of them without anyone lying **Shrink the denominator.** Narrow applicability until only well-managed systems remain in scope. The pass rate rises and nothing about the estate changed. **Fold unassessed into pass.** Usually accidental: the report counts what was evaluated, and what could not be evaluated contributes to neither number, so under-coverage silently flatters the result. **Blend into one figure.** Multiplying coverage by pass rate produces a number that looks conservative and is actually an unfounded claim — it treats every unassessed system as failing. It also destroys the separation that makes the report actionable, because a reader can no longer tell whether to fund access work or remediation work. ## The honest structure A control's line in the report has four parts: - **Population and its provenance** — how many systems the control applies to and which independent enumeration produced that figure. - **Coverage** — what fraction of that population was actually assessed this period, with the unassessed part broken out by reason. - **Pass rate within coverage** — stated explicitly as a rate over the assessed subset, never over the population. - **Exclusions** — what was declared out of scope, by whom, why, and when that decision expires. With 60% coverage, coverage is the headline. Pass rate is a real number but a secondary one: improving it while 40% of the estate is invisible is optimising the part you can already see. ## Scope reduction as a governed decision Sometimes the right answer genuinely is to shrink scope. A segment may be isolated, decommissioning, or genuinely outside the control's intent. That is a legitimate decision and it should be easy to make properly and hard to make quietly. Properly means: a named approver with the authority to accept the residual risk, a written rationale, any compensating measure recorded alongside it, an expiry date, and the exclusion visible in the same report as the coverage figure so nobody has to go looking for it. Quietly means someone removes an account from a collector's configuration and the coverage percentage improves. The difference between those two is the entire difference between a control programme and a reporting exercise. ## When leadership wants the single number anyway They often do, and refusing outright is not a strategy. What works is attaching the qualifier so tightly to the number that they cannot travel separately: one figure with the coverage stated in the same breath, in the same cell, in the same slide line. It also helps to give leadership a metric they can actually move. Coverage responds to organisational action — mandating that new accounts are created through the provisioning path, assigning owners to unowned accounts, funding the access work — in a way that a pass rate does not, so making coverage the tracked commitment for a quarter or two is usually both more honest and more useful. ## The incentive trap Every improvement in visibility makes the numbers look worse. Discovery adds systems to the denominator, and the newly discovered systems are the least well configured, so both coverage and pass rate dip at the moment the programme is working best. If the reporting culture punishes that dip, teams learn not to look. The countermeasure is to report population growth as a positive line in its own right, to compare like-for-like against the previous period's population when discussing the pass rate, and to say explicitly at the time that a dip caused by discovery is the expected shape of a programme that is improving. ## What a reviewer will ask Anyone reviewing the control, internal or external, will eventually ask how you know the population is complete. 'Our tooling reported 98%' is not an answer to that question; 'here is the independent enumeration, here is the reconciliation against it, here is the unassessed bucket with owners and dates' is. Being able to produce that is worth more than a higher percentage, because it is the thing a percentage cannot demonstrate on its own.
- Leadership insists on one number for the board pack. What do you give them?One number with the coverage attached inseparably in the same line, and coverage as the tracked commitment for the next two quarters. Coverage is the metric they can actually move through organisational action — mandating the provisioning path, assigning owners to orphaned accounts — whereas the pass rate mostly moves when engineers remediate.
- A business unit asks to declare a subnet out of scope for this control. What do you require?A named approver with authority to accept the residual risk, a written rationale, any compensating measure recorded with it, and an expiry date after which it returns to scope automatically. The exclusion is published in the same report as the coverage figure, so the number and the reason it is high sit together.
- Coverage rose from 60% to 85% and the pass rate fell from 92% to 74%. How do you present that?As the programme working. The newly visible systems were always non-compliant; only the measurement changed. I would show the pass rate against the old population alongside the new one so the like-for-like comparison is visible, and headline the coverage gain rather than the ratio dip.
saying these in an interview costs you the question
- Publishes the pass rate without any coverage figure
- Blends coverage and pass rate into a single percentage
- Improves coverage by removing accounts from the collector
- Treats scope exclusion as a configuration change, not a decision
- Lets exclusions run with no expiry or review
- Presents a discovery-driven dip as a regression in posture