Security
Security and data handling
Where your code goes, what leaves your network, and what we can prove. This page states the posture that exists today in present tense, and labels everything that does not exist yet as roadmap.
True today
The posture today.
- scanning
- Scanning runs against your repositories and produces structural facts: services, APIs, events, tables, ownership. The output is the graph and its evidence, not a mirror of your codebase.
- evidence + ledger
- Evidence and the hash-chained ledger live in Findry's Postgres instance deployed for your pilot. One pilot, one database.
- model calls
- Model calls are key-gated and off by default. Deterministic fallbacks are the default: extraction, impact analysis, and the governed pipeline run without a model key. LLM output is never evidence.
- simulation
- Simulated execution is always labelled. A simulated stage carries its simulated flag verbatim in the attestation; it is never omitted.
- export
- The evidence ledger is exportable. The attestation trail, hash chain intact, leaves with you.
- third parties
- No code is retained by third parties through Findry.
On the roadmap
- sso / saml
- Federation with your identity provider via SAML or OIDC.
- rbac
- Role separation with approval separation: an approver cannot approve their own change.
- kms-backed secrets
- Envelope encryption for integration tokens, with log redaction.
- soc 2 program
- A formal SOC 2 program. We do not claim SOC 2 compliance today, and will not before a report exists.
Security questions from your review team are welcome: [email protected]. We answer with what is true, in the same tense it is true in.