Leadership1 distinct publisher3 min readPublished
The company argues that catching sophisticated misuse means correlating data across sessions and accounts, and regulated buyers balked at holding that data with a vendor, so the store moves to their cloud.
The Board Room · Leadership desk

Compiled by The Board RoomSomething wrong?How this is made
The engineering claim underneath this is about a correlation window. Anthropic's position is that the most sophisticated misuse spans many tasks across multiple sessions and accounts, so scoring each interaction on its own and discarding the data at once does not find it, and effective detection needs data held long enough to correlate across time and accounts [5]. That is the stated reason retention arrived at all [6]. What regulated buyers objected to was not the detection but the custody: taking on another trusted data vendor means notifying their own customers, reopening contracts and satisfying internal rules for storing and auditing sensitive material [11]. EFS answers the custody objection and leaves the correlation window intact.
The composition of the design group tells you which objection was binding. Anthropic says its conversations spanned a quarter of the Fortune 100 and every US global systemically important bank [12], which works out to roughly 25 of those hundred firms [1], and that the groups it worked with included ARC, whose membership includes the chief information security officers of Goldman Sachs, Morgan Stanley, Citi, Bank of America and Wells Fargo [9]. It also cites work with leaders at Comcast, KPMG, Mastercard, Salesforce and Visa [16]. A design fitted to the buyers with the heaviest vendor-inventory duties becomes the reference design for everyone carrying lighter ones.
What actually changes is narrower than a retention rollback. The data is still kept for a meaningful period and still monitored; what moves is the location of the store and the reviewer of the output, with flagged patterns routed to the customer for review [2][10]. On the adjacent question, Anthropic states that retention was never motivated by a wish to train on enterprise data and that it has never trained on enterprise data without explicit permission [7]. That is the company's own account, and this announcement is the whole of the record for it.
A privacy blocker has been cleared, but that is not where the work ends. Once the store sits in the customer's cloud, the completeness of misuse detection depends on the customer's own retention and logging discipline, and triage depends on a security team that already runs an insider-risk queue [10]. Anthropic reports seeing credential theft and agents autonomously engaging in destructive behaviour among recent misuse attempts [14], and the buyer is now the party that sees those signals first.
The record does not settle the operational terms. The announcement does not say how long data must persist in customer-controlled storage, who holds the keys, what happens when a customer receives a signal and declines to act, or what EFS costs [3]. Rollout is phased from later this fall, and eligible customers keep zero data retention on Fable 5 and Fable 5.1 until it is ready [3][4], so the interim arrangement hands those buyers privacy without the cross-account correlation Anthropic argues detection requires [2]. A firm that takes the bridge this quarter is also accepting a migration next quarter into storage it has to provision, audit and staff, and that cost sits with the security organisation rather than with the vendor.
Ranked by verification strength, evidence, and original report placement.
Anthropic announced Enterprise Frontier Safeguards (EFS), described as a solution combining the privacy of zero data retention with state-of-the-art safeguards for detecting misuse.
EFS works by storing data in cloud infrastructure controlled by the customer, not Anthropic.
EFS will roll out to customers in phases, starting later this fall.
Eligible customers will receive zero data retention on Fable 5 and Fable 5.1 until EFS is ready.
Anthropic introduced 30-day data retention starting with Fable 5.
EFS was developed in collaboration with more than 100 customers in industries including financial services, healthcare, manufacturing, telecom, law, retail and the public sector, and with cloud partners Amazon Web Services, Google Cloud and Microsoft Azure.
Distinct publishers with included, body-backed reporting in this cluster.
1 article · September 1, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
build
Anthropic cuts Fable 5.1 cache reads to a fortieth of its input price5 distinct publishers
leadership
Anthropic cuts Fable 5.1 prices by 25% and launches two-tier safeguard system with Mythos 5.11 distinct publisher
build
Anthropic's $35B Lambda contract puts Nvidia on both sides of the table3 distinct publishers
build
Open weights, 30% cut: Moonshot's Kimi K3 ask puts a royalty inside cloud inference pricing3 distinct publishers
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
One issuer, no outside check
Anthropic is the only voice in this reporting, and it is describing a product it has not yet shipped. The mechanics are unusually concrete for a vendor post — customer-owned buckets, a rolling analysis window, flags routed to the customer's own cleared reviewers — which is why this scores above a pure teaser. But the premise is not: 'substantial evidence of attempted misuse' arrives with no counts, no cases and no dates, and the only external testimony in the text is a partner endorsement that stops mid-word.
Announced, nothing shipped
The product does not exist for customers yet. Rollout is 'later this fall', in phases, with no first-wave named — and the giveaway is the bridge: eligible customers are handed zero data retention on Fable 5 and Fable 5.1 precisely because EFS is not ready. The 100-plus companies in the story are design interviewees, and the Fortune 100 arithmetic counts conversations. What is real today is the design partnership, not a single deployment.
Scope talk ahead of proof
Give Anthropic credit for restraint: no benchmark, no percentage improvement, and an openly admitted trade-off between privacy and detection. The overstatement sits in the framing. 'A quarter of the Fortune 100' and 'every US global systemically important bank' read as endorsement while measuring only meetings, and 'the best of both worlds' is asserted without a single number showing that cross-account correlation catches what per-interaction analysis misses. Meanwhile the terms a buyer would actually negotiate — retention window, key custody, price, what happens when a flag is ignored — are absent.
Removing its own sales blocker
Anthropic tells you the motive itself: it began retaining data for 30 days with Fable 5, and regulated buyers then found the frontier models hard to use. This post is the remedy, and it is published by the party whose pipeline depends on the remedy working — which also explains the pre-emptive line that retention was never about training on enterprise data. The architecture is genuinely responsive to the objection, and it happens to move storage cost, audit burden and human review onto the customer while opening all three hyperscaler channels at once.
Firm on the plan, thin on effects
We can be fairly sure what Anthropic has committed to publicly — the storage model, the surface list, the review split, the interim concession — because a company's own announcement is the right source for its intentions. We can be sure of very little about outcomes: whether phases land on time, whether the monitoring actually catches coordinated misuse, what enterprises pay in storage and analyst hours. Confidence should rise or fall with the first customer who describes running this rather than designing it.