Loading…
Trust Center
A scanner runs other people's URLs and captures their pages. That makes isolation, egress control, and encryption load-bearing, not optional.
Verassa evidence protocol
Evidence
01Screenshot, DOM, replay, and axe baseline captured before decisions.
Judgment
02Reviewer route, rationale, and owner stay attached to lower-confidence work.
Verification
03Re-scan records and disclaimers travel with reportable outputs.
Isolation
Every customer-supplied URL is validated for DNS resolution and private-IP denial at every redirect hop, so a scan cannot be steered at internal infrastructure (SSRF protection).
Each scan runs in a fresh, sandboxed browser process with no access to the internal network. Network egress is restricted to the customer's claimed domain. A scan cannot reach where it was not asked to go.
Encryption
Data is encrypted at rest through managed Postgres and object-storage encryption, with database-level encryption where the schema requires it. Traffic is TLS 1.2 or higher in transit.
Authenticated-flow credentials are stored with envelope encryption in a dedicated credential vault, and are never sent to model providers. Code touching the vault requires human review before it merges.
SOC 2
The platform is built to be SOC 2 ready — Type 1 first, building toward Type 2. This is a posture, not a certificate: it means change management, audit logging, encryption, access control, and incident response are designed in, not retrofitted.
Every code change is a reviewed pull request. The Decision Audit Log is append-only and tamper-evident: each row references the hash of the row before it.