§ CISO Learning Journey · Week 26 · November 15, 2026 · about 5 minutes

Continuous Re-Run Is the Artifact: Why One Dated Record Becomes a Series

A dated record shows one day. A series of dated records shows a program. What to re-run, how often, what triggers an early review, and what the frameworks expect.

By Lindsay Hiebert · Founder · CISSP

Dark card: SanctumShield, CISO Learning Journey, Week Twenty-Six. Headline: The second run is the proof. A row of dated records rising gently, the latest marked by a red rule.

The first assessment is the hardest one to do and the easiest one to overvalue. It shows what the organization found and decided on one day. A reviewer looking at it a year later will ask the obvious next question: what has changed since?

AI moves faster than any annual cycle. New tools appear in a quarter. Software you already own switches on AI features in a routine update. An agent that drafted emails in spring is booking meetings in autumn. A record from January describes a different organization by June.

That is why, in governance, the re-run is the artifact.

What the frameworks already expect

None of the major frameworks treat AI governance as a one-time event.

  • ISO/IEC 42001 asks for management review at planned intervals (Clause 9.3) and continual improvement of the AI management system (Clause 10).
  • The NIST AI Risk Management Framework describes risk management as continuous across the AI lifecycle, with GOVERN as a cross-cutting function rather than a phase.
  • Colorado SB 26-189, signed May 14, 2026, with duties from January 1, 2027, asks deployers of automated decision-making technology to keep records for three years. A records duty measured in years assumes the records keep coming.
  • The EU AI Act high-risk regime, from December 2, 2027, asks for risk management as a continuous, iterative process across the system’s lifecycle (Article 9).

A dated certificate is a useful thing to have. It tells you something was checked on a given day. A series of dated records tells you the organization keeps checking, and that is what the frameworks describe.

A sensible cadence

For most mid-market organizations, a quarterly re-run is enough to keep the record current without turning governance into a full-time job. Annual is the minimum for an organization with little AI and no agents. Monthly makes sense where agents act on production systems or customer data.

The SanctumShield tools catalog and endpoint registry are refreshed every month, so each re-run reads against what exists now, not what existed when you last looked.

What should trigger an early re-run

Some changes should not wait for the calendar:

  • A new AI tool approved for company data
  • A software vendor switching on an AI feature that reaches your data
  • A new agent, or an existing agent given new permissions
  • A change of model behind a tool you rely on
  • An AI incident or near miss
  • A new obligation coming into force, such as Colorado from January 1, 2027

Each of these changes what the organization would answer to at least one assessment question. When the answer changes, the record should too.

What the series shows that a single record cannot

Put two dated records side by side and three things become visible.

Movement. Which findings closed, which stayed open, and which are new. A board can see whether the ninety-day actions did what they said.

Ownership. Whether the same names still own the same risks, or whether ownership drifted when someone changed roles.

Attention. Whether the organization looked again when it said it would. That is the plainest evidence of due diligence there is.

Each run produces its own dated documents with its own Verification URLs, and SanctumShield keeps each confirmation available for six years. Over time the organization holds a history any reviewer can check, one date at a time.

Keeping it light

A re-run is not a repeat of the first assessment. Most answers carry forward. The work is in confirming what changed, deciding anything new, and sending an updated memo. For a team that did the ninety-day program in Week 25, a quarterly re-run can often be done in an afternoon.

Your next step

Open your calendar and add the next three review dates for the coming year. Then write down the one change in your organization most likely to trigger an early review. That sentence becomes part of your policy’s review section.

Sources

Continue exploring on SanctumShield

The full library — 290 pages of CISO-grade content.

SanctumShield maintains the deepest publicly-available reference set for mid-market agentic-AI governance — primary-source cited, continuously refreshed. Related deep-dives on this article’s topic:

Continuous Re-Run Is the Artifact: Why One Dated Record Becomes a Series | SanctumShield