Security
Security that assumes someone is trying.
Broker OS stores SSNs, EINs and bank accounts for borrowers and reps. It was designed from the first line of code for that: per-tenant encryption, enforced isolation, verifiable audit, and strong sign-in.
Audit chain verify: ok
10:41:07 pii.revealed · ssn · step-up ✓#a91f…
10:40:52 dial.gate.denied · quiet_hours#77c0…
10:39:13 call.supervise.whisper#3e02…
10:37:44 session.revoked · self#c5d8…
What protects your data.
- Field-level encryption: PII sealed per tenant with envelope keys before it reaches the database
- Blind indexes for lookups, so search never needs plaintext
- Vault tokens for SSN, EIN and bank numbers; reveal needs permission plus a fresh step-up
- Row-level security forced on every tenant table
- Hash-chained audit log with a verify tool
- MFA: TOTP or passkeys for staff; session lists with self-revoke
- Modern TLS, HSTS and standard security headers
Live in early access
Zero plaintext PII
Our last scan: 0 plaintext PII hits across 989 database columns, with a positive control.
Live in early access
Cross-tenant tests
Automated tests confirm one tenant cannot read another's rows.
Live in early access
PII access log
Every reveal of sensitive data is an audit event.
Rolling out
Admin session control
Admin view of all users' logins and sessions with remote revoke.
Live in early access
Rate limiting
Login lockout after repeated failures; per-IP limits at the edge.
On the roadmap
Third-party audit
Independent penetration test and SOC 2 program.
Honest status: Broker OS has not completed a SOC 2 audit or independent penetration test yet; both are on the roadmap. Admin-wide session management is rolling out.
Founding partner program
See Broker OS on your own book of business.
A live 20-minute walkthrough with the founder, or a free licensing and compliance gap check for your firm. Your choice.