Security
Your financial data, protected at every layer
Security isn't a feature at Ventura. It's the foundation. Here's specifically what's in place to protect the data enterprise 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
Email based verification codes protect every sign in, for admins and employees alike. Session cookies are HttpOnly and SameSite.
Workspace roles
Viewer, analyst, editor, and admin roles determine what each team member can see and change in the app, checked at sign in and enforced 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
Strict 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've found a vulnerability in Ventura, please reach out and our team will respond promptly.
Contact security team