LR-301d · Module 2

Continuous Gap Monitoring

3 min read

Gap analysis is not a point-in-time exercise. New regulations create new obligations. System changes create new controls that need mapping. Evidence cadences lapse. Remediation actions are completed but not verified. Continuous gap monitoring checks the compliance matrix on an ongoing basis rather than waiting for the next formal gap analysis.

  1. Regulatory Change Triggers Every new regulation, amendment, or enforcement guidance triggers a gap check: does the new requirement create an unmapped obligation? If so, add it to the taxonomy and check for a corresponding control. The trigger-based approach catches new gaps as they emerge, not months later in a scheduled review.
  2. System Change Triggers Every new AI deployment, model update, or integration change triggers a gap check: does the change affect any existing control? Does it create a need for new controls? System changes that bypass the compliance check create gaps that persist until the next formal analysis.
  3. Cadence Monitoring Track evidence production cadences automatically. If a quarterly risk assessment is overdue, alert the control owner before the gap materializes. Cadence monitoring catches control drift — the gradual lapse of periodic controls — before it produces an audit finding. [RECOMMEND]: Automate cadence monitoring with calendar alerts tied to the compliance matrix.