Trust

Security control summary

Implemented controls

  • Tenant and role authority come from a fresh database membership read. Hostnames and workspace cookies select a candidate tenant but never grant membership.
  • Private-plane repositories require collectiveId; the model-classification test fails when a new model has not been assigned to the tenant, network, identity, or global plane.
  • Guest access requires both an environment capability flag and a tenant-level flag. New universities default to closed; platform administration always requires a real identity session plus an email allowlist.
  • Invitations use 256-bit random tokens, SHA-256 hashes at rest, seven-day expiry, address matching, revocation, seat quotas, domain policy, and fixed-window rate limits.
  • Vault files are capped, tenant-scoped, quota-checked, audited, and stored in private Vercel Blob or S3-compatible storage. Database bytes are a local/test and legacy fallback.
  • Customer AI use is off by default and requires tenant approval in addition to a configured provider key. Deterministic checks remain authoritative.
  • Security headers disable framing, MIME sniffing, sensitive browser capabilities, and loose referrer behavior.
  • Liveness and readiness endpoints separate process health from database, identity, storage, and guest-boundary configuration.

Required operational controls

The operator must provide TLS, managed secrets, least-privilege database and bucket credentials, encrypted backups, restore testing, centralized immutable-enough logs, vulnerability scanning, dependency patching, alerting, incident response, and employee access review. The repository does not claim SOC 2, ISO 27001, penetration-test completion, or a particular recovery objective.

  • Architecture/data-flow diagram and inventory
  • Current vulnerability and container scan
  • Independent penetration-test executive summary and remediation letter
  • Backup/restore drill evidence
  • Access-review and secure-development procedures
  • Incident-response tabletop evidence
  • Completed customer HECVAT with control-owner signoff

Next: privacy FERPA