Security

Built to be verified.

How Naad Secure protects every message, file and call.

Read this first. Each principle maps to a mechanism in the code. Certifications are not claimed; the platform is open to independent evaluation.

Design principles

Six principles, each with a mechanism.

Text, files, voice and video alike.

Abstract render of layered translucent shield plates
  1. 01

    A person is a key

    Identity is a hash of three public keys and can be recomputed from those keys.

  2. 02

    Nothing in the middle is trusted

    Seeds can withhold, never forge. Relays splice ciphertext only.

  3. 03

    Bind the session to the wire

    The initiator signs a value unique to the connection. A relay that terminates the transport is refused.

  4. 04

    Post-quantum at every step

    Every ratchet step uses a post-quantum hybrid key exchange. There is no classical-only path.

  5. 05

    The cheapest honest path

    A direct path is tried first. Every route is cryptographically identical.

  6. 06

    Sealed at rest, guarded on screen

    Identity is PIN-sealed and history encrypted. The window resists screen capture.

Collaboration safeguards

Protection that extends to groups, calls and files.

Members, devices and forwarders get nothing they can read.

  • Group keys

    Group keys are protected by post-quantum hybrid sessions and rotated on every join or leave.

  • Membership changes

    Removing a member rotates the group keys; the removed member does not receive the new seed.

  • Calls

    Three nested layers per frame; the call key travels inside the ratchet.

  • Files

    Chunked and encrypted; received files land in a confined folder.

  • Offline delivery

    Sealed sender hides the sender from the store; the recipient stays visible.

  • Devices

    Device certificates are signed by the person’s key and can be revoked. Recovery uses k-of-n shares of an encrypted vault.

On the wire

Post-quantum keys are larger. The design budgets for it.

Standard sizes from the NIST FIPS documents and RFCs.

Size comparisonPublic keys: classical vs post-quantum
Public keys: classical vs post-quantum, in bytes
AlgorithmBarSize (bytes)
X25519 public key32 bytes
RSA-2048 public modulus256 bytes
ML-KEM-512 encapsulation key800 bytes
ML-KEM-768 encapsulation key1,184 bytes
ML-KEM-1024 encapsulation key1,568 bytes
ML-DSA-65 public key1,952 bytes

ML-KEM ciphertexts are 768, 1,088 and 1,568 bytes for the three parameter sets.

Sources NIST FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), FIPS 205 (SLH-DSA), FIPS 186-5 (ECDSA); RFC 7748 (X25519); RFC 8032 (Ed25519).

Size comparisonSignatures: classical vs post-quantum
Signatures: classical vs post-quantum, in bytes
AlgorithmBarSize (bytes)
Ed2551964 bytes
ECDSA P-25664 bytes
RSA-2048256 bytes
ML-DSA-442,420 bytes
ML-DSA-653,309 bytes
ML-DSA-874,627 bytes
SLH-DSA-SHA2-128s7,856 bytes
SLH-DSA-SHA2-128f17,088 bytes

SLH-DSA keeps a 32-byte public key but carries the largest signatures.

Sources NIST FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), FIPS 205 (SLH-DSA), FIPS 186-5 (ECDSA); RFC 7748 (X25519); RFC 8032 (Ed25519).

Trust by deployment type

What each deployment type removes from the trust path.

These properties belong to the deployment type, not to every installation.

Trust properties of Naad Secure by deployment type
IdentityServers in the pathCloud and internet
Self-hosted, including air-gappedA key only. No phone number, SIM or e-mail address.Seed, relay and store run by the customer. No central server in the trust path.Air-gapped: no internet dependency and no foreign push or cloud service in the trust path.
Tenant-hostedKey-based identity.Operated by Knowlcom for one organisation. Relays splice ciphertext only.Depends on placement. Private infrastructure is available.
Public infrastructureKey-based identity.Public relay and store carry ciphertext only.Not a no-cloud deployment.

Stated plainly

Known limits and work ahead.

  • Independent cryptanalysis by a third-party laboratory is on the roadmap.
  • Hardware key custody and signed distribution are work ahead.
  • Relays can still observe message size and timing.