Specify the requirement and the evidence
Continuous compliance extends review into operation instead of treating a launch assessment as the last check. A related foundation is NIST’s continuous-monitoring guidance, which describes visibility into assets, threats, vulnerabilities and the effectiveness of deployed security controls (NIST SP 800-137). That guidance concerns information-security monitoring; legal and privacy questions still need people who know the applicable rules.
For each check, write down the requirement it serves, the systems and configuration it covers, where its evidence comes from, when the evidence was collected, what triggers a rerun and who responds. A new connector, destination or policy version changes the scope, so check the changed part again. Read a passing result as covering exactly what the check examined.
Keep missing evidence distinct from a passing check
Suppose connectors A and B both move to configuration v4. A configuration check compares each connector’s configured export destinations with an approved list. It reads configuration, so it will not see a runtime export that bypasses that configuration.
| Record | Evidence | What it covers |
|---|---|---|
| A, current | v4 check passed at 10:00 | A’s configured destinations under v4 |
| A, earlier | v3 check passed | A before the change |
| B, current | Evidence collection failed | Nothing yet; result unknown |
One of the two connectors has current evidence for this check. Report that as evidence coverage, one of two, and resist calling the system “50% compliant.” B’s status is unknown until collection succeeds, and A’s v3 pass describes a configuration that no longer runs. Show stale and missing evidence as their own states on the dashboard so neither reads as green.
Connect findings to an owned response
NIST’s OSCAL Assessment Results model keeps the assessment subject and the controls actually reviewed separate from observations, evidence, findings and risks (NIST OSCAL). It supports continuous assessment as well as a snapshot. That structure helps preserve what was checked and what was concluded from it.
Assign someone to investigate failed checks and collection gaps. Keep the response, any reviewed exception and the evidence for the next assessment. An alert on a dashboard is the start of the work; closing it needs a fix or a documented exception. Keep ongoing monitoring tied to periodic review and to changes in the requirements themselves.
Arguing that changing combinations of data need ongoing attention, Kris Lovejoy says, “a fundamental rethinking of compliance activity from point in time to more of a continuous compliance thing.” (episode 62, 26:54).
Her privacy examples are her argument on the show; check them against the rules in each jurisdiction you operate in. Audit trail covers retained records, model risk management covers the broader risk process, and how to govern AI agents connects monitoring to operating responsibility.
Sources
- NIST SP 800-137 — The 2011 guideline's abstract describes continuous monitoring for visibility into assets, threats, vulnerabilities and the effectiveness of deployed security controls.
- NIST OSCAL: Assessment Results model — Separates the assessment subject and reviewed controls from observations, evidence, findings and risks, and supports continuous as well as snapshot assessments.