A constraint from the first line, not a review before launch.
CapitalOS carries fundraising and governance data that institutional investors and OSG itself depend on being handled correctly. Here is how we approach that.
What this looks like in the architecture.
Design-time threat modeling
Access boundaries and data exposure are scoped before a feature is built, not reviewed once it's already shipped.
Least-privilege access
Every system and every person operates with the minimum access required, reviewed on a defined cadence rather than granted once and forgotten.
Auditable by default
Actions that touch sensitive fundraising or governance data are logged in a form an institutional auditor could review without translation.
Disclosure
We would rather hear about a vulnerability directly than have it found for us. A formal disclosure process is part of what we're building alongside CapitalOS.
Reporting a concern.
If you've found a security issue in CapitalOS or elsewhere in OSG's infrastructure, we want to hear about it directly.
This address has not yet been confirmed as an actively monitored inbox. Treat it as provisional until this notice is removed.