Security

Edition: Community and Enterprise

sealfix exists to protect production data while people change it by hand, so its own security is written down, tested and open to review.

Page	For
What sealfix protects	Security teams and auditors: the guarantees, the boundaries, and what you must do about each
Cryptography	Security architects: every key, algorithm and where it lives
Report a vulnerability	Anyone who found a weakness

The guarantees, in one table

Guarantee	Enforced by
Values are never in logs, responses, stored plaintext or SQL text	The sealing design, and a leak test in every build
Values reach the database only as bind variables	The executor; no code path builds SQL from a value
Only the executor can open a sealed value or a before-image	Key separation: the web application holds the public key only
The requester never approves their own fix; one person approves once	Domain rules, checked again by the executor before it runs
The audit log cannot be edited	Database grants (no update or delete), the hash chain, signed checkpoints
A fix runs in one transaction, and rolls back if the rows differ from the dry run	The executor