WiBiz Business Continuity and Recovery Summary

Version: v1.0
Published: 6 August 2026
Owner: WiBiz Operations
Classification: Public
Status: Current public summary

1. Purpose

This summary describes the WiBiz approach to service continuity, backup, restore, recovery, and dependency risk. Exact objectives and evidence depend on the assessed production service.

2. Control commitments

WiBiz requires applicable services to identify:

• critical functions, dependencies, owners, and failure scenarios;
• recovery time and recovery point requirements approved for the service;
• backup method, schedule, retention, protection, and separation;
• restore procedure, test scope, result, exception, and next test;
• provider and communication dependencies;
• manual continuity options where appropriate;
• client responsibilities and limits;
• material changes that require reassessment.

3. Evidence boundary

Provider-native version history or point-in-time recovery is useful, but it is not automatically an independent backup. A recovery claim requires evidence for the named system, data, environment, date, test method, restored result, timing, verifier, limitations, and remediation.

WiBiz does not claim one recovery objective or completed test across every service. Contractual commitments are recorded in the applicable service schedule and Build Security and Data Annex.

4. Exercises and change

Continuity and restore testing are risk-based and repeated after material architecture, data-path, provider, authentication, or recovery change. Findings remain open until evidence shows the corrective action operated.

5. Contact

Assurance enquiries: security@wibiz.ai

WiBiz Business Continuity and Recovery Summary v1.0, 6 August 2026.