Security
Security principles
NOX does not claim NATO or national agency certifications. Those are earned through independent evaluation. What does define the product is here, without embellishment.
Real E2E
End-to-end encryption for voice and data.
Identity
Controlled onboarding; revocable.
Minimal trace
The session is not mixed with the phone.
Admin
Studio has authority over the user, not the reverse.
COTS device
Commercial phones, no dedicated hardware.
Roadmap
Audit and certification when the product is ready.
We would rather state what the product does today than display a seal that is not yet warranted. When an independent evaluation exists, it will be published here.
The problem
Why use secure communications?
Most sensitive conversations already happen on the phone.
Consumer apps were not designed for institutional control.
A lost device or a leaked group compromises the mission.
Verifiable identity and the ability to revoke an account are needed.
A record of who administers is required, not just of who chats.
Encryption is not enough if the directory stays mixed in with WhatsApp.
Roadmap
Audit and certification
Order matters: first the product, then the external evaluation, and only then the seal.
- Today
- End-to-end encryption for voice and data, onboarding and revocation controlled from NOX Studio, and minimal trace on the device.
- Next
- Independent audit of the product and of its deployment processes.
- After that
- Certification when the product is ready to sustain it, not before.
Talk to the people who build the product
If your organisation needs to review the security model in detail, we will prepare that conversation.