WiBiz Incident Response Public Summary

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

1. Purpose

WiBiz maintains an incident-response process for suspected security, privacy, availability, integrity, and service events. Detailed playbooks, internal contacts, system diagrams, evidence, and investigation records remain restricted.

2. Response lifecycle

The process covers:

1. Report and record the event through an approved route.
2. Triage severity, affected services, data, clients, and legal roles.
3. Assign an incident owner and technical, privacy, legal, communications, and provider support as needed.
4. Contain the event while preserving evidence and service safety.
5. Investigate the cause, scope, access, data impact, and timeline.
6. Eradicate the cause, recover the service, and verify safe operation.
7. Assess notification duties under the applicable law and contract.
8. Communicate verified facts to affected parties through the approved route.
9. Record corrective action, ownership, deadlines, evidence, and closure.
10. Refresh affected policies, client annexes, provider records, public claims, and training.

3. Client communication

The applicable agreement defines the client security contact, notice trigger, notice timing, required content, cooperation, and update route. Statutory deadlines depend on the jurisdiction and WiBiz's role. WiBiz does not use one public deadline as a substitute for that assessment.

4. Evidence and exercises

A completed exercise or incident produces dated records for scenario or event scope, participants, actions, decisions, result, gaps, remediation, approvals, and next review. A written plan is not evidence that an exercise or recovery action succeeded.

5. Reporting

Suspected security issue: security@wibiz.ai
Personal-data concern: dpo@wibiz.ai

WiBiz Incident Response Public Summary v1.0, 6 August 2026.