Skip to main content
  1. Revoke affected model, forge, integration, and service credentials.
  2. Pause impacted queues and preserve audit, provider, and deployment evidence.
  3. If execution isolation may be compromised, destroy the worker pool and caches before resuming.
  4. Rotate secret versions and restart workloads so they reload credentials.
  5. Restore regional service from a validated database checkpoint and matching object versions when required.
  6. Document impact, data classes, containment, corrective actions, and customer notification decisions.
Customers should route audit export and platform logs to their SIEM and retain the correlation IDs used by Veridical support. Support access and impersonation require explicit approval, a bounded duration, least privilege, and an audit record.
Last modified on July 28, 2026