Built for examination.
A forensic evidence system that can't defend its own data integrity is worthless.
We designed Redan starting from that assumption.
Evidence Integrity
Immutable by architecture.
Evidence uploads, automated analysis findings, approval events, and audit history are written once. Any attempt to alter or delete them is rejected by the database before Redan's application code runs. This is a structural property of the system, not a configurable setting.
SHA-256 · Chain of Custody
EXAMPLE9f3c2a8b7d4e1f02a6c89b3f5d2e8c1a4b7f6e9d0c3a8b5f2e1d4c7a9b3e6f05
Export recorded · 2026-04-23 14:23:04 UTC
When a CCO exports the compliance record, Redan computes a SHA-256 hash of the package and records it at the moment of export. If a single byte changes afterward, the hash will not match. The chain of custody is independently verifiable — an examiner does not need to trust Redan.
Live Audit Trail
2026-04-23 14:07:32 UTC
by claire.whitfield
2026-04-23 14:09:11 UTC
by hunter.alarcon
2026-04-23 14:22:58 UTC
by andrew.payton
2026-04-23 14:23:04 UTC
by system
Every approval, export, and finding — written once, attributed to a named operator, immutable.
Access & Authentication
Closed by default.
Role-Based Access Control
Two-Layer EnforcementAccess is enforced at two independent layers. The application checks the user’s role and firm before any data is read. The database enforces the same boundary independently — a query authenticated to one firm cannot return another firm’s rows even if application code is compromised. The two layers fail closed.
Employee accounts are blocked from compliance workflows at the database level, not just the UI
Cross-tenant access is restricted to a single founder-only role, reviewed monthly
Multi-Factor Authentication
Required — No Skip OptionTOTP MFA is required for every user. Users without an enrolled factor are routed directly to enrollment — there is no skip path. MFA enrollment is part of first login.
Passwords found in known breach datasets are rejected at creation and at change
Session & Deprovisioning
Immediate RevocationWhen a user is removed from a firm, access is revoked at the application layer on their next request — without waiting for a session to expire. For confirmed compromise, active sessions can be terminated at the authentication provider, cutting access regardless of session state.
Target time to revoke: under 15 minutes from detection for confirmed compromise
Every deprovisioning event is written to the immutable audit trail, with the operator named
Tenant Isolation
Cross-Firm BoundaryRedan is multi-tenant by architecture — every firm’s data shares the same infrastructure but cannot cross the boundary. A session authenticated to one firm cannot return another firm’s data. Your compliance record is not visible to another Redan customer — not to their users, their administrators, or their compliance team.
Every customer record is tagged with its owning firm; the tag is enforced at the database, not the application
A query authenticated to one firm cannot read another firm’s rows — even if application code is wrong
Infrastructure & Availability
Redundant by default.
Redan holds SOC 2 Type I at the company level. Database, application delivery, and automated analysis providers each carry SOC 2 Type II independently.
Governance & Data Rights
The record is yours.
Redan is the custodian of your firm's compliance record, not the owner. The commitments below are contractual — fixed at signing, not subject to unilateral change.
Your firm owns all data you upload. Redan does not sell it, share it for commercial purposes, or use it to train models. Export requests fulfilled within 30 days. privacy@redancompliance.com
If a breach affecting your firm's data is confirmed, Redan notifies you within 24 hours of discovery, in writing. The first notice may be preliminary; we update as facts develop.
Background checks required for all individuals with access to production systems or customer data — criminal history (7-year lookback), employment history verification, and education verification for credential-requiring roles.
Forensic analysis of any incident is backed by a WORM audit trail that cannot be altered after the fact — not by Redan, not by a compromised privileged account.
WORM-protected records may be subject to SEC recordkeeping retention requirements that supersede deletion requests under commitment 01.
Verify it yourself.
We walk through the technical architecture, answer your compliance team's questions directly, and provide security documentation under NDA. Thirty minutes.
BOOK A DEMO