Coverage and timeliness: how far the checks reach and how long the gap is
A monitoring programme owes two answers about its own reach and its own lag.

A monitoring programme owes two answers about its own work before it reports on the estate: how much of the estate the checks actually reached, and how long the gap is between a change or a finding arising and the observation that catches it. Neither is a single number: coverage is an attribute of how an assessment was built, and timeliness is a frequency chosen against risk, not against a clock. Coverage quoted without its sampling rule, and timeliness quoted without the population it describes, both read as precision that is not there.
the question the number that answers it it means nothing without
---------------------- -------------------------------- ---------------------------
how much was reached? the coverage of the assessment the sampling rule: population,
method, objects per type
how long is the gap? the frequency of monitoring and the population it describes:
of assessment assets, changes, findings
Coverage is an attribute of the assessment, not a percentage of the estate
SP 800-53A says where coverage lives: “Depth and coverage are attributes associated with assessment methods and the generation of security and privacy evidence” (lines 995–996). The coverage attribute “is associated with the assessment methods employed during development and operations, addressing the scope and breadth of assessment objects included in the assessments” (lines 1020–1022). The same publication removes any expectation of a universal target: organisations are “not expected to employ all of the assessment methods and assessment objects contained within the assessment procedures identified in this publication” (lines 605–607), and instead choose “the level of effort needed and the assurance required for a particular assessment” (lines 608–609). Coverage is a decision recorded with the assessment — how wide, and how deep at least partial coverage — not a state of the estate. A programme reporting full coverage is describing its own procedure; whether that is enough depends on which objects the procedure ever reached.
Coverage without the sampling rule is uninterpretable
Assessing everything is not affordable: SP 800-137 says collecting data from every object “may be impractical or cost-prohibitive” (lines 1330–1331), and sampling “may make ISCM more cost-effective” (lines 1331–1333). It names the risk — a sample “may fail to capture the variations in assessment outcomes” (lines 1333–1334) — and the remedy, a strategy carrying “provisions for ensuring sufficient depth and coverage when sampling methodologies are utilized” (lines 1242–1244). For the mechanics it points across: “NIST SP 800-53A, as amended, describes how to achieve satisfactory coverage when determining sample populations for the three named assessment methods: examine, interview, and test” (lines 1337–1339). There coverage “is satisfied through consideration of three criteria” (lines 1344–1345): the types of objects, “enough” objects of each type, and enough per type to account for “the known or anticipated variance in assessment outcomes” (lines 1352–1355). A coverage figure is interpretable only as the output of a stated sampling rule — which population, which method, how many of each type.
Timeliness: the frequency is set against risk, not the calendar
SP 800-137 states timeliness as sufficiency: “The frequency of assessments should be sufficient to assure adequate security commensurate with risk” (lines 798–799). The floor it records is statutory — agencies must assess “at a frequency appropriate to risk, but no less than annually” (lines 361–362) — and the frequency is “determined in part by the objectives and priorities of the mission or business process and measurement capabilities inherent in the infrastructure” (lines 668–671). SP 800-53 Rev. 5 makes the demand a control: CA-7 requires “Establishing the following system-level metrics to be monitored” (lines 6766–6767) and “Establishing [Assignment: organization-defined frequencies] for monitoring and … for assessment of control effectiveness” (lines 6769–6770), then “Ongoing control assessments in accordance with the continuous monitoring strategy” (line 6772). A timeliness claim carries three facts: what is measured, how often it is observed, and how often its controls are assessed.
From one observation to a signal
A single observation is an event; a trend is a signal, and SP 800-53 Rev. 5 makes that an enhancement: “Employ trend analyses to determine if control implementations, the frequency of continuous monitoring activities, and the types of activities used in the continuous monitoring process need to be modified based on empirical data” (lines 6843–6845). The same control holds frequency to its purpose — “continuous” and “ongoing” “imply that organizations assess and monitor their controls and risks at a frequency sufficient to support risk-based decisions” (lines 6792–6793) — and requires the “Correlation and analysis of information generated by control assessments and monitoring” (line 6777) that lets repeated observations accumulate. SP 800-55 Vol. 1 gives timeliness its measurement vocabulary: efficiency measures “examine the timeliness of controls by determining the speed at which they give useful feedback and how quickly those issues are addressed” (lines 1012–1013), and measurements “can provide information on the implementation, effectiveness, efficiency, and business impacts of controls” (lines 621–622). Timeliness is measurable in two directions: how fast the check notices, and how fast the thing noticed is dealt with.
Where both numbers lie
Neither metric survives being quoted alone. SP 800-137 is explicit that full inspection is not the goal — “It is impractical to collect security-related information and assess every aspect of every security control deployed across an organization at all times” (lines 795–796) — and that “Sampling of information system security objects, rather than 100 percent inspection, can also be an efficient and effective means of monitoring” (lines 807–808). So 100% coverage is rarely achievable and not always worth its cost, and a coverage number separated from its sampling rule cannot be read at all. Timeliness fails the same way: a frequency stated without the population it refers to — which assets, which changes, which findings — hides the backlog, since a mean interval can be met while a queue grows behind it. Both failures share a cause. The measure cheap to automate tends to displace the one that matters, and SP 800-137 warns that even where automation is impossible, “all implemented security controls, including management and operational controls, must be regularly assessed for effectiveness” (lines 258–260). The two numbers are worth reporting only together: how much was reached, under which rule, and how long it took, over which population.
Level and prerequisites
L4 — assurance and measurement: this sheet fixes what two of a monitoring programme’s own numbers mean and what must travel with each, rather than running the programme. It assumes the L1 vocabulary (a control designed, implemented and verified; evidence and audit trails), the L2 records (control objectives and verification criteria; the risk and exception register) and the L3 processes (vulnerability management; remediation verification; inventory coverage). The KPI/KRI definitions, the freshness of one piece of evidence and the limits of a composite maturity score are the neighbouring sheets’ subjects, named only to be left to them.
Where to go next
- Knowledge — the Knowledge register this sheet belongs to.
- Cybersecurity Governance — the macro-area.
- Assurance — the node this sheet sits in.
References
- NIST SP 800-137, Information Security Continuous Monitoring (ISCM) — the coverage attribute and sampling, the frequency set against risk, and the limits of full inspection.
- NIST SP 800-53A Rev. 5 — depth and coverage as attributes of assessment methods, and the three criteria that satisfy coverage when sampling.
- NIST SP 800-53 Rev. 5 — CA-7’s metrics, frequencies, ongoing assessments and correlation, and the trend analyses enhancement.
- NIST SP 800-55 Vol. 1 — efficiency measures and the four things measurements can inform.