DeepSeek: Response and recovery
Expanded web report · Related PDF snapshot: 22 October 2026 · PDF page 6
Research reviewed 22 October 2026 · Evidence and editorial planning guidance are distinguished below.
Start with the incident-specific sequence
Route applicability and contractual questions to procurement and legal owners. Preserve configuration and usage evidence, then restrict prohibited routes where the responsible authority determines this is required.
Use the current primary guidance and the accountable incident lead to resolve sequencing conflicts. Coordinate parallel teams before changing shared identities or destroying evidence. Urgent containment may need to proceed before every record is collected, but the decision and evidence lost should be documented.
Restore a trusted operating path
Replace the relevant model or supplier path using representative tests for quality, permissions, data handling and cost. Update customer-facing descriptions and internal approved-tool records.
- Control approved routing centrally and review changes as part of configuration management.
- Run a representative evaluation set against the replacement and retain the model/configuration identifiers.
- List customer commitments that explicitly constrain model or supplier use.
Verify before resuming
Demonstrate which model actually handles a request, which subprocessors receive data, and how routing and procurement controls prevent an unapproved fallback.
Ask the operational owner to exercise the essential workflow, including background tasks and customer exceptions. Keep a short record of what passed, what failed and what remains untested. Define who may accept an exception and when it must be revisited; an exception should not disappear into a general restoration announcement.
A scenario to rehearse
Illustrative exercise, not an observed customer incident: A service desk buys an AI assistant under one brand, but its fallback model comes from a restricted provider. The exercise traces the routing configuration and customer commitments before switching the assistant back on.
Keep customers informed
Use approved wording for provider and data-handling questions.
A frontline workflow and escalation sheet consistent with the organisation’s approved-tool policy.
Restart decision
Resume the affected workflow when the authorised policy owner accepts the implementation evidence and business testing shows the replacement is usable.
After stabilization, review which shared dependency allowed the exposure to spread or slowed recovery. Choose a measurable improvement and an accountable owner. A new platform is useful only when its responsibilities, evidence and recovery path fit the business requirement.