Security
How Covenant protects every document.
This page describes controls implemented in the architecture, along with their limits. It is not a compliance statement and does not replace an independent assessment.
01
Isolation per organization
Covenant is multi-tenant. The active organization comes from the authenticated session on the server; the system ignores any organization identifier sent by the browser.
Each transaction binds the organization and user to the database connection, and PostgreSQL enforces forced Row-Level Security policies on every organization table. The application connects with a role that does not own the tables and cannot bypass those policies.
- FORCE ROW LEVEL SECURITY
- application role without BYPASSRLS
- foreign keys that include the organization
02
Identity and sessions
Passwords are stored with Argon2id. The session is an opaque token of 32 random bytes in an HttpOnly cookie; the database only stores its SHA-256, so a copy of the database cannot be used to impersonate sessions.
Sessions expire after 30 minutes of inactivity and after 12 hours at most, and can be revoked. TOTP second factor is mandatory for platform administrators, with recovery codes. Every request that changes data requires a double-submit CSRF token.
- Argon2id
- TOTP RFC 6238
- SameSite=Lax · HttpOnly
03
Explainable authorization
Access to a document is the highest permission of the participant's group along the folder chain, where the nearest explicit permission wins over the inherited one. It is denied if the participant was revoked, the access expired, the NDA is pending or the version is not ready.
A deal administrator can request the explanation of any decision and gets the full trail of rules applied. Outside the deals you take part in, the system answers as if the deal did not exist.
- NONE · VIEW · DOWNLOAD · DOWNLOAD_ORIGINAL · MANAGE
- 404 instead of 403 outside the deal
- isolation between buyers
04
Document processing
Each file is validated by its leading bytes, not its extension. A separate process computes its SHA-256, scans it with antivirus when one is active, counts pages, renders each page and extracts text for search.
If no antivirus is configured, the scan is recorded as not performed. Office files are stored but not rendered, and the interface says so.
- QUEUED
- SCANNING
- PROCESSING
- READY
- REJECTEDFAILED
- REJECTED · FAILED
- up to 3 retries with backoff
05
Protected viewer and downloads
No document has a public address in storage. The viewer receives page images rendered on the server with a burned-in watermark: name, email, organization, IP, deal and UTC time of the viewer. Responses are not cached.
Downloading the original only exists when the permission includes it. Downloaded PDFs receive their own watermark, except with download-original permission.
- Cache-Control: no-store
- watermark per request
- PDFBox
06
Hash-chained audit
Every relevant action produces an event. Each event stores the previous event's hash and its own hash, computed over its canonical content, forming one chain per organization. The platform has its own separate chain.
The application role can only insert events: it cannot update or delete them. A verifier recomputes the full chain and points to the first inconsistent event.
- hash = sha256(prev_hash ‖ canonical json)
- INSERT only
- exportable
07
Connector secrets
Storage, mail and antivirus credentials are configured from the interface and encrypted with AES-256-GCM using a root key that only exists in the server environment.
They are write-only: the API confirms they exist and when they were updated, it never returns their value. Every change creates an audited revision that can be rolled back.
- AES-256-GCM
- write-only
- revisions with rollback
08
Infrastructure
The API is not published externally: the browser only talks to the web application, which forwards requests over a private network. Responses carry strict security headers, including a content policy that blocks framing.
Processes run as unprivileged users inside containers. Encryption in transit is terminated with TLS by the public proxy.
- CSP · X-Frame-Options: DENY
- unprivileged users
- API on a private network
Limits you should know
- 01Covenant does not claim certifications such as SOC 2, ISO 27001 or others.
- 02The trial environment runs on a single server, without high availability.
- 03Rate limiting is applied in memory per instance.
- 04Watermarks deter leaks and make them traceable; they do not stop someone from photographing the screen.
- 05Antivirus scanning is optional and depends on the connector being active.
Report a vulnerability
If you find a potential vulnerability, report it to your DC GEEKS contact with steps to reproduce it, and do not publish it until we have reviewed it together. Do not use real third-party data in your tests.
This trial environment does not yet have a public security mailbox or a bounty programme. Use the channel through which DC GEEKS gave you access (your commercial or technical contact) and put “Security” in the subject.