Security Architecture

How Fortress protects institutional keys: layered architecture, client-side key generation, AES-256 at rest, TLS 1.3 in transit and documented security practices.

Offline key operations

Layer 1 Keys generated and used only while the computer is offline. Wallet stored encrypted on removable media. Media physically disconnected when not in use. Runs on hardware you own and control.

Wallet software

Layer 2 Wallet material under AES-256-GCM authenticated encryption. Optional M-of-N approval with Citadel. Standard BIP39 seeds: no vendor lock-in. Static analysis on every release.

Client portal (online)

Layer 3 Never stores or sees private keys. TLS with HSTS on every request. Brute-force protection and lockout on sign-in. Admin, Member and Viewer roles.

Data protection

Private keys: Encrypted on your removable media. Wallet material at rest: AES-256-GCM. Portal traffic: TLS, HSTS enforced. Backups: Standard BIP39, held by you. Portal data hosting: Switzerland (CH).

Static security analysis

The V1.0 assessment (March 2026) with Bandit, Semgrep and pip-audit returned zero high- and zero medium-severity findings. An independent third-party audit is planned.

Responsible disclosure

An RFC 9116 security.txt is published on our public domains, with a dedicated channel for security researchers.

Incident response

Documented escalation procedures with defined severity levels, tied to your support tier.

SOC 2

Controls aligned to the Trust Services Criteria. Formal attestation is planned, not yet issued.

GDPR

Processing documented in our Privacy Policy and Data Processing Agreement.

ISO/IEC 27001

Security practices modelled on ISO/IEC 27001. Certification is planned, not yet issued.

Licence audit log

Licence and activation changes in the client portal are recorded.