WiBiz Encryption and Key Management Summary

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

1. Purpose

This summary describes the protection required for data in transit, data at rest, backups, exported files, secrets, and cryptographic keys. Exact implementation depends on the selected provider and build architecture.

2. Control commitments

WiBiz requires:

TLS 1.2 or higher for supported production data transport;
risk-appropriate at-rest protection for production data, logs, backups, and exports;
credentials and secrets to remain in approved secret or environment stores rather than source code or ordinary documents;
restricted administration of keys, certificates, credentials, and recovery material;
documented ownership, rotation, revocation, and replacement procedures;
verification of provider-managed encryption settings and limitations;
prompt remediation of exposed or compromised secrets.

3. Evidence boundary

WiBiz does not apply one encryption algorithm, key-management service, or key-custody statement to every active provider by default. A client or system claim requires current evidence for the named data store, transport path, backup, log, export, key owner, and configuration.

Provider documentation describes a provider capability. It does not prove that a WiBiz account or build enabled, inherited, or correctly configured that capability.

4. Client-build application

The Build Security and Data Annex records:

transport protocols and termination points;
at-rest protection for each data store, log, backup, and export;
key owner and administrative roles;
certificate and secret storage;
rotation, revocation, and emergency replacement;
provider limitations, exceptions, and verification evidence.

5. Contact

Security enquiries: security@wibiz.ai

WiBiz Encryption and Key Management Summary v1.0, 6 August 2026.