Prototype. Fictional sample cases only. Sign-in, file storage, and AI analysis are not connected yet, so do not upload real client documents.

Caseframe

Security controls

The status of each control Caseframe is designed around. None is marked implemented until it has been built and tested.

This prototype is not secure enough for client data. It runs entirely on fictional sample data. Do not upload real documents until the controls below are implemented and independently tested.

Identity & access

  • Lawyer sign-in and firm registration

    Netlify Identity with invite-only users per firm. The sign-in screens exist, but no backend is connected.

    Designed, not builtMilestone 2

  • Multi-factor authentication

    Require TOTP for every account, either through an identity provider that enforces MFA or with a second-factor check on the server.

    PlannedMilestone 2

  • Secure session management

    HttpOnly, Secure, SameSite cookies with short-lived tokens, idle timeout, and server-side revocation.

    PlannedMilestone 2

  • Strict per-case authorization

    Every server function checks firm membership and case assignment before reading or writing. Default is deny.

    Designed, not builtMilestone 3

Data protection

  • Encryption in transit

    HTTPS on every request through Netlify’s managed TLS, plus HSTS and strict security headers.

    PlannedMilestone 2

  • Encryption at rest

    Use the platform’s at-rest encryption for the database and file storage. Assess whether sensitive matters need extra per-firm encryption at the application level.

    PlannedMilestone 4

  • Firm data separation

    Every record carries a firm ID, and file storage keys are prefixed by firm. All queries are scoped on the server, never by the browser.

    Designed, not builtMilestone 3

  • Private document storage

    Files are kept in private storage and streamed only through authorized server functions. No public or shareable URLs.

    PlannedMilestone 4

  • Upload validation

    The browser preview already checks file type and size. The server will re-check type, size, and file signature, and reject encrypted or malformed files.

    Designed, not builtMilestone 4

Operations

  • Server-only secrets

    AI and email credentials are read only in server functions from environment variables. Nothing secret is bundled for the browser.

    Designed, not builtMilestone 5

  • Audit logging

    Append-only log of sign-ins, views, uploads, downloads, and deletions, visible to firm administrators. The dashboard shows a sample.

    Designed, not builtMilestone 3

  • Secure deletion

    Deleting a case or document purges its files and derived analysis, with retention holds and a deletion record in the audit log.

    PlannedMilestone 7

  • Backups & recovery

    Scheduled database backups, a written recovery plan with target times, and tested restores.

    PlannedMilestone 7

  • Independent security testing

    Third-party penetration test and controls review before any real client data is accepted.

    PlannedMilestone 8