Tribastion TI handles sensitive breach-exposure data, so security and privacy are built into the product, not bolted on. This page summarises our certifications, controls and design principles.
SOC 2 Type II
Our controls are independently examined against the AICPA SOC 2 Trust Services Criteria over an audit period (Type II). Controls are mapped across the applicable criteria:
| Criterion | Representative controls |
|---|---|
| Security | role-based access control (RBAC) with segregation of duties; per-account, rate-limited, credit-metered API keys; strict Content-Security-Policy and security headers; hardened session auth with lockout; secure-SDLC change management. |
| Availability | health checks, cache-backed hot paths, replicated database backups, cloud file-offload with redundancy. |
| Confidentiality | encryption of secrets and integration credentials at rest (AES); masked-by-default output; least-privilege data access; TLS in transit. |
| Processing Integrity | deterministic collection pipeline with a 48-hour cache, idempotent imports, and an interlink graph rebuilt from source records. |
| Privacy | DPDPA-aligned notice & consent, data-principal rights intake, retention limits, and a documented grievance process. |
A copy of the current SOC 2 Type II report is available to customers under NDA on request.
Privacy by Design
We follow the seven foundational principles of Privacy by Design:
- Proactive not reactive — privacy risks are addressed in design and review, before release.
- Privacy as the default — passwords and secrets are masked by default; full reveal is a deliberate, per-account entitlement.
- Privacy embedded into design — access control, encryption and audit are core architecture, not add-ons.
- Full functionality, positive-sum — strong security without sacrificing usability.
- End-to-end security — data is protected across its full lifecycle, from collection to deletion.
- Visibility & transparency — clear notices, an on-site consent manager, and an auditable trail.
- Respect for user privacy — easy consent withdrawal and data-principal rights.
Secure SDLC
- Change management with reviewed, versioned releases and reproducible builds.
- Least-privilege by default; permissions enforced in the platform, not only the interface.
- Input validation, output encoding, and a strict CSP (no third-party JavaScript by default).
- Secrets kept out of source control; credentials encrypted at rest and never returned by any page or API.
- Dependency and configuration hygiene; environment separation (production / UAT / demo).
- Comprehensive, tamper-evident audit logging of significant actions.
Data handling & masking
Exposure output is masked by default across the console and API. Validation of whether a leaked credential still works is performed from the customer’s own authorised position — the platform never uses a recovered credential itself. Connected storage and integration credentials are encrypted and never exposed.
Reporting a vulnerability
If you believe you’ve found a security issue, please contact ASM@tribastion.com. We acknowledge reports promptly and work with reporters in good faith.