Security & Compliance
CabFiles LLC — 3379 Peachtree RD NE, Suite 655, Atlanta, GA 30326 — support@cabfilesllc.com — enterprise application and managed Postgres infrastructure.
| Feature | Status | Details |
|---|---|---|
| AES-256 encryption at rest | Active | Managed Postgres and object storage on AWS are encrypted at rest with AES-256 by default on SOC 2 compliant infrastructure. |
| TLS 1.3 in transit | Active | HTTPS is enforced across the marketing site and the carrier application, negotiating TLS 1.3. |
| AWS US-East-1 (Virginia) | Active | Project region us-east-1 — United States data residency with inherited SOC 2 and ISO 27001 controls. |
| HTTPS + row-level security | Active | Row-level security is enabled on every carrier table. Carrier isolation is enforced in the database, with the enable baseline in supabase/rls_policies.sql and every access logged. |
| Daily backups | Active — Pro plan | Point-in-time recovery for 7 days plus weekly full backups, retained on a rolling schedule. |
| 7-year retention lock | Active | The application blocks deletion of a driver qualification record before seven years have elapsed, per 49 CFR 391.51 recordkeeping requirements. |
| Audit log | Active | Document access is recorded with user, carrier, timestamp and request metadata. |
| DOT compliance — 49 CFR 391.51 | Compliant workflow | The driver qualification file structure mirrors the document set the regulation requires. |
| FMCSA Clearinghouse | Compatible | Manual upload and tracking of Clearinghouse queries. Queries must be obtained from clearinghouse.fmcsa.dot.gov. CabFiles is not affiliated with FMCSA and does not provide direct API integration. |
Reporting a vulnerability
Email support@cabfilesllc.com with the details of any suspected vulnerability. We acknowledge reports within one business day, Monday – Friday, 8AM – 5PM ET.
Disclaimer: CabFiles LLC is an independent compliance software provider. CabFiles LLC is not affiliated with the FMCSA, the DOT, or any government agency. Infrastructure security controls are inherited from our managed AWS hosting provider. Compliance responsibility remains with the carrier.