Join our Newsletter — 33% off our NHI Course

Why treat design control and design of record together?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20217
Topic starter  

TL;DR: AI approval weakens into a poor control when the live system can drift from the approved design without a new review, JetStream Security explains. Runtime evidence has to show the running system still matches what was signed off, not just what was documented.

Editorial analysis by NHI Mgmt Group, based on content published by JetStream Security: “A Policy Is Not a Control”.

Key questions

Q: Why does AI governance need both oversight and evidence capture?

A: Oversight without evidence is hard to defend, and evidence without oversight is just recordkeeping.

Q: How should teams govern model, tool, and identity changes together?

A: Treat them as one change-managed system.

Q: What breaks when AI approval is only a one-time review?

A: Approval without ongoing design control leaves no reliable way to prove the live system still matches what was approved.

Practitioner guidance

  • Implement a design of record for every AI system Name the models, tools, data sources, and identities that make up each production AI workflow, then keep that record aligned with runtime reality.
  • Version every material AI change Require a new reviewable version whenever the system changes in a way that could affect behavior, access, or compliance evidence.
  • Tie approvals to runtime evidence Make sign-off contingent on being able to show the current system still matches the approved design, not just that the approval happened.

Bottom line: AI approval becomes weak control if the live system can diverge from the documented design without a new review.

Glossary terms: Design Control, Design Of Record, Runtime Drift, AI governance evidence

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20707
 

Design control is the missing governance layer between AI approval and AI operation. Policies, risk reviews, and sign-offs matter, but they do not keep a live system aligned with the version that was approved. In agentic environments, the control has to travel with the system and keep drift visible. The practical conclusion is simple: if the runtime can change without a new evidence trail, the governance model is incomplete.

A question worth separating out:

Q: When does AI design drift become a compliance problem?

A: It becomes a compliance problem as soon as the live system no longer matches the documented one and the organization cannot prove when the change occurred or who approved it. At that point, the gap is no longer just operational drift. It is a governance failure that can undermine auditability and accountability.

👉 Read our full editorial: AI design control turns approval into a living governance control


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.