Separate announcement, rollout and purchased availability
| Record | Anthropic states | Buyer evidence |
|---|---|---|
| Announcement | EFS was announced on September 1, 2026. | Dated source and named product surface. |
| Rollout | Customers receive access in phases, starting later in fall. | Written eligibility and expected enablement date. |
| Interim route | Eligible customers receive ZDR on Fable 5 and 5.1 until EFS is ready. | Organization, model, platform and effective-date notice. |
| Supported surfaces | Anthropic names Claude and cloud-platform routes. | Confirmation for the exact purchased SKU and region. |
What the announced architecture is designed to change
Anthropic says activity data used for monitoring can remain in customer-controlled cloud infrastructure under the customer’s encryption keys, access policies and audit logging. Automated systems analyze a rolling window for serious misuse signals, and flagged signals go to the customer for review. Anthropic’s announcement says Anthropic human review is not required for that EFS path.
Those statements describe the intended service architecture. They do not establish that a particular firm, cloud account or Claude surface has been enabled, configured or contractually covered. Procurement should keep the architecture claim and the customer-specific implementation evidence in separate rows.
Request evidence for each control boundary
| Control | Request | Stop condition |
|---|---|---|
| Storage | Cloud account, region, object lifecycle and backup treatment | Data location or owner remains Unknown |
| Encryption | Key owner, rotation, recovery and service access | Customer control is only a marketing statement |
| Monitoring | Events analyzed, rolling window, flags and model scope | Monitoring period conflicts with approved data use |
| Review | Customer roles, queue, access logs and false-positive path | No accountable reviewer or least-privilege design |
| Incident | Notification, containment, evidence and support route | Firm and provider paths do not connect |
Verify the interim ZDR bridge in writing
The announcement says eligible customers receive ZDR on Fable 5 and Fable 5.1 until EFS is ready. Eligibility is therefore a firm-specific fact. Preserve the notice, organization identifier, platform, covered model, start and end conditions, and any safeguard obligations. Do not extend one customer’s or one cloud route’s status to another account.
The Fable retention and ZDR guide separates commercial no-training language from covered-model retention and exceptions. Use that record to confirm what applies before and after EFS enablement.
Assign the customer-side operating roles
Customer-controlled infrastructure transfers work to the customer. Security must own storage, encryption and access configuration. Legal ops must map the approved workflow and users. Privacy or counsel must review the data and contractual boundary. An incident owner must connect monitoring signals to the firm’s response process. EFS does not remove those responsibilities.
Define who may review a flag, which context they can open, how false positives are cleared, how access is logged and when a workflow pauses. A sophisticated architecture without a staffed review path is not an operating safeguard.
Run a bounded enablement test
- Confirm EFS availability for the exact account and platform.
- Use non-sensitive canary data to test storage, encryption and access.
- Generate or simulate an approved monitoring event and verify the customer queue.
- Confirm the reviewer can resolve and document the flag without broad access.
- Test export, deletion, incident contact and rollback to the approved route.
- Record the configuration, evidence, owner and next review date.
Keep legal conclusions outside the product claim
EFS availability or configuration does not establish privilege preservation, compliance with a professional rule, client consent, security certification or the absence of misuse. Those conclusions depend on the workflow, agreement, jurisdiction and firm controls. This guide creates a procurement record for review; it is not legal advice.
FAQ
Is Anthropic EFS generally available?
Anthropic’s September 1 announcement says rollout will occur in phases starting later in fall 2026. Availability for a particular organization remains Unknown until confirmed.
Does EFS mean Anthropic stores no customer data?
Anthropic describes activity data stored in customer-controlled cloud infrastructure for monitoring. Confirm the exact architecture, window and customer responsibilities for the purchased route.
Do all Fable 5.1 customers receive interim ZDR?
No universal entitlement is stated. Anthropic refers to eligible customers, so the organization, platform and written notice must be verified.
Sources checked
- Enterprise Frontier Safeguards announcement, checked 2026-09-03.
- Fable and Mythos 5.1 system card, checked 2026-09-03.
- Covered Models retention practices, checked 2026-09-03.
- Commercial Terms of Service, checked 2026-09-03.
Operational information, not legal advice. Verify current terms, account configuration and applicable professional duties before use.