Your financial data, protected at every layer

Here is specifically what is in place to protect the data finance teams trust us with.

Encryption in transit, and where it matters at rest
All traffic is encrypted in transit with TLS. Connected integration credentials (API keys, OAuth secrets) are encrypted at rest with AES-256-GCM. If that encryption key isn't configured, the app refuses to save credentials at all rather than falling back to something weaker.
Multifactor authentication
Every sign in needs a verification code sent to your email, for admins and employees alike. The server records that a session passed the code, and refuses every workspace page and data request from one that has not, so a password alone is not enough. Session cookies are SameSite and sent only over HTTPS.
Workspace roles
Viewer, analyst, editor, and admin roles decide what each team member can do. Recording decisions on findings, adding data, changing settings, connecting systems and managing the team are checked on the server, not just hidden in the interface.
Append only security log
Sign-in verification, role changes, member removal, workspace joins, and integration connections are written to a server side log with no update or delete path in the application.
Hardened infrastructure
A Content Security Policy, HSTS, clickjacking protection, and security headers on every response.
Explainable, not autonomous
Anomaly detection runs on a deterministic rule engine, not a black box model. Every finding shows exactly which rule and evidence triggered it. Nothing acts on its own; every status change is a manual, logged decision by someone on your team.

Reporting a vulnerability

We take security reports seriously. If you believe you have found a vulnerability in Ventura, tell us and our team will respond promptly.