Skip to content
Genesis Ark

Trust

Security built for systems that move real orders

A trading system holds the keys to your venue accounts and the full record of your business. Qubit's security starts from two facts. First, it is software only: it never holds client funds and is never in the flow of funds. Second, it runs on infrastructure you control or on a dedicated instance used only by you. This page describes the controls we build into the product and the way we develop it.

01

Venue credentials and key management

  • Venue and liquidity provider API keys are encrypted at rest with envelope encryption. The key-encryption key can live in your cloud KMS, your HSM or HashiCorp Vault.
  • Credentials are write-only in the interface: once entered, they are never displayed again, only replaced or revoked.
  • We recommend trade-only API keys with withdrawals disabled and IP allowlisting at the venue, and the onboarding checklist asks you to confirm both.
  • Qubit cannot withdraw from a venue unless you give it a key with withdrawal rights, and it is not designed to need one.
  • Access to stored credentials is limited to the execution gateway service and is logged.

02

Access control

  • Role-based access control. Permissions are granted by role and scoped to accounts, books, instruments and venues. Traders see and trade only what their role allows.
  • Server-side enforcement. Every request is authorized on the server. Hiding a button in the interface is never the only check.
  • Four-eyes approvals. Sensitive actions, such as changing limits, fee schedules or balance adjustments, can require a second approver.
  • Segregation of duties. The people who configure risk limits can be different from the people who trade against them.
  • Service accounts and API keys for systems are scoped to the minimum permissions they need, can carry IP restrictions and are stored only as hashes.

03

Authentication

  • Single sign-on through your identity provider over SAML 2.0 or OpenID Connect, so joiners, movers and leavers are handled in one place.
  • Time-based one-time password (TOTP) two-factor authentication for local accounts, enforceable by policy.
  • Session timeouts and re-authentication for sensitive actions.

04

Audit log

  • Every order event, risk decision, configuration change, login and approval is written to an append-only audit log with the user, time, source and before-and-after values.
  • The log is tamper-evident: entries are chained so that an altered or deleted entry can be detected.
  • Audit records can be exported to your SIEM and your long-term archive.

05

Encryption

  • TLS 1.2 or later for all traffic between clients, services and external venues.
  • Encryption at rest for databases, backups and the event log, using keys you control in a self-hosted deployment.

06

Secure development

  • Every change is reviewed by a second engineer before it is merged.
  • Dependency and container image scanning run on every build. Known vulnerabilities are triaged against a published severity policy.
  • Static analysis and secret scanning run in the build pipeline. Secrets never live in source code.
  • Release artifacts are signed and published with a software bill of materials, so you can verify what you install and check it against your own vulnerability feeds.
  • Order, ledger and risk logic carry automated tests that run before every release.

Penetration testing

We commission independent penetration tests of the application and its APIs, and test again after significant changes. Summaries of results are shared with clients and prospects under NDA once available. Self-hosted clients are welcome to run their own tests against their deployment; tell us first so we can help with scope.

Certification roadmap

SOC 2 Type II
Roadmap
ISO 27001
Roadmap

Qubit does not hold SOC 2 or ISO 27001 certification today. Both are on our roadmap, and we will state progress here only when it is real. Until then, we answer security questionnaires in full, share our control descriptions and walk your security team through the architecture. In a self-hosted deployment, the infrastructure controls are part of your own control environment.

Report a vulnerability

Responsible disclosure

If you believe you have found a vulnerability in Qubit or this website, contact us through the contact page with steps to reproduce.

  • We acknowledge reports within two business days and keep you updated until the issue is resolved.
  • We will not take legal action against good-faith research that avoids privacy violations, data destruction and disruption of service, and that does not access data belonging to our clients.
  • Please give us a reasonable window to fix the issue before public disclosure. We are glad to credit you once it is fixed.

What we will never ask for

  • Your venue API keys, by email, chat or phone. Credentials are entered only into your Qubit deployment.
  • Wallet seed phrases or private keys.
  • Payment to a personal account or wallet.

If someone claiming to be Genesis Ark asks for any of these, it is not us. Report it to us through the contact page.

Send us your security questionnaire

We will answer it in full and set up a session with your security team to go through the architecture.