NeuroWall

Security overview

How NeuroWall licensing protects keys, signatures and administrative actions, and how to report a vulnerability.

Updated 2026-11-10

This page describes how the licensing service is designed. It does not replace a security review of your own deployment.

License keys

Keys are shown once. Only a short prefix and a SHA-256 fingerprint are stored, so a database copy cannot reveal a key. Keys are never written to logs.

Signed entitlements and device binding

Entitlements are signed with EdDSA and verified on the appliance against a trust bulletin signed by offline root keys. An entitlement is bound to the device that activated, so a copy on another device is refused. Older entitlements cannot replace newer ones.

Signing keys

By design the online signing key is held in a key-management service (OpenBao Transit) and used by a separate signer process that cannot read the key. The offline roots are a separate 2-of-3 trust layer and are not part of any online service.

Administrative actions

Every administrative change requires a recorded reason and is written to an append-only audit trail. Grants and subscription changes follow an approval policy that needs a second person for sensitive actions.

This website

Pages are served with a strict content security policy: no inline script or style, no third-party scripts and no framing. Public forms are rate limited and protected against automated submissions.

Reporting a vulnerability

Please report security issues privately. Our contact and policy are published at /.well-known/security.txt. Do not include license keys or personal data in a report.