Zivanox

Security

Security overview

Zivanox uses tenant-scoped authorization, hashed credentials and one-time tokens, revocable sessions, audit records, and controlled business transitions.

Boundaries

Production, staging, and future demo environments are separate. Sensitive application pages are not publicly cached.

Reporting

Closed-beta security concerns must be reported through the private support channel supplied during onboarding. Do not include passwords or secret tokens.

Assurance

Independent certification and penetration testing are future gates and are not claimed by this overview.