Security At Rhindon Cyber
A summary of the core security controls protecting RAIC and your data.
Encryption At Rest & In Transit
All customer data is encrypted at rest using AES-256 and in transit over TLS 1.2+.
SOC 2 Infrastructure
RAIC runs on SOC 2 Type II audited cloud infrastructure with continuous control monitoring.
US Data Residency
Customer data is stored and processed in US-based regions by default.
100% Tenant Isolation & Audit Integrity
Every tenant is fully isolated at the database layer, so one customer's data never reaches another. Centralized authorization protects administrative actions, and every platform audit event follows one consistent, traceable path.
PLATFORM RESILIENCE
- Two layers of backup: Every tenant is exported every day, around 08:00 UTC, and kept for 90 days. A separate platform-wide database snapshot is taken daily and kept for about 14 days. Point-in-time recovery is not offered.
- Restores are proven, not assumed: An automated check runs every week against the latest backup. It confirms the backup is complete and readable and that every table matches the live record count. Each result is logged for audit.
- Scheduled work is watched: Every scheduled job reports when it actually finishes. A watchdog alerts our support team when a job misses its expected run or keeps failing.
- Deadlines survive a missed day: Approval expiries, review-date warnings and renewal reminders act on anything due on or before today that hasn't been handled yet. A delayed run catches up, and nothing is sent twice. Every automatic approval expiry goes into the customer's audit trail.
Verifiable Evidence Lineage
Governance actions are chained with SHA-256 (entry_hash = SHA-256(prev_hash | payload_hash | seq)), each day is sealed nightly, uploaded files are fingerprinted with SHA-256, and audit packs ship with an ECDSA P-256 signature anyone can verify offline. Day roots are also committed as a Merkle tree, so RAIC produces an inclusion proof for a single record without disclosing the rest of the day.
Externally Witnessed Seals
Each nightly day root is submitted to an independent RFC 3161 timestamp authority — DigiCert as primary (US), FreeTSA as failover (DE) — and the returned token is stored with the seal, binding the root to a time Rhindon Cyber did not set. The pack records which authority issued the token so a reviewer can check it against that authority directly.
Two Independent Verifiers
The verification specification is published and versioned (text v1.4), frozen per version. A second verifier written from that specification alone — Python, standard library plus one public crypto library, no RAIC source — verifies real packs in CI with networking disabled, covering manifest hash, artifact digests, both day-root modes, inclusion proof, the P-256 signature, and the RFC 3161 token. Specification gaps the exercise exposed are published in a defect register. This is independence in interpretation; external attestation is pending. Rhindon Cyber publishes the independent verification exercise on a fixed quarterly cadence, and again whenever the verifier specification text version changes. A quarter in which a check fails publishes as a failed quarter with the defect recorded. Read the published results at https://app.rhindoncyber.com/support/verification-attestation.
Attachments are checked, not trusted
Each evidence file is inspected for what it really contains before it is stored. Disguised or oversized files are refused.
Fair AI usage per organization
Each organization has its own short-term and daily AI allowance based on its plan, so one tenant can't exhaust shared capacity.
Outside content stays content
Documents, records and web material reach the AI inside a clear boundary. They are treated as information to read, never as instructions to follow.
Sign-in abuse is throttled
Sign-in, password reset and verification-code entry are rate limited per account and per network source.
MFA exemptions expire
An MFA exemption must have an expiry of no more than 30 days, only a platform administrator can grant one, and it switches off automatically.
Error logs protect privacy
Error records no longer store email addresses. Older ones were masked.
Full Security Controls — Available Under NDA
Detailed documentation of our full security control set — including audit reports, penetration testing summaries, incident response procedures, vendor management, and subprocessor lists — is available to qualified prospects and customers under a mutual non-disclosure agreement.
To request access, contact security@rhindoncyber.com.