Controls for sensitive agreements and release evidence

Encryption and integrity

• AES-256-GCM with random 96-bit nonces for sensitive fields and files.
• Context-bound authenticated data prevents ciphertext from being moved between entity and file contexts.
• Production startup fails without a 32-byte data encryption key.
• SHA-256 hashes identify agreement documents, release artifacts, policy bundles, and evidence snapshots.
• Encrypted storage paths are server-generated and never accepted from the client.

Identity and tenant isolation

• Memory-hard scrypt password hashing with per-user salts.
• Session and API tokens are random and stored only as SHA-256 hashes.
• Secure, HTTP-only, SameSite=Lax cookies and session revocation.
• Role-separated owners, admins, reviewers, and members.
• Every stateful query includes organization ownership and scoped authorization.

Application defenses

• Database-backed login throttling, signup quotas, and bounded uploads.
• Magic-byte verification, XML DTD and entity rejection, strict extraction allowlists, and CSV formula neutralization.
• Agreement documents are evidence and never instructions to the extraction model.
• HSTS, denied framing, MIME-sniffing protection, restrictive permissions policy, and a production content security policy.
• Signed webhook delivery, replay protection, retries, and durable delivery history.

Operations

The stateful application runs behind TLS with a non-root container, dropped Linux capabilities, no-new-privileges, persistent encrypted data, health monitoring, controlled backups, and recovery procedures. The marketing deployment is isolated from the stateful origin and redirects authenticated routes to the application host.

AI boundary

AI is limited to proposing structured controls from untrusted agreement text. Candidate values retain citations and confidence and cannot drive release decisions until an authorized reviewer confirms them. Deterministic code produces findings; human reviewers own interpretation, exceptions, approval, and release authority.

Trust roadmap

Before representing enterprise assurance, complete independent penetration testing, SOC 2 Type I then Type II, a vendor and subprocessor register, incident-response and disaster-recovery exercises, formal DPA and security exhibits, and customer-specific retention controls. Report issues privately to security@audarel.com without attaching customer data.