E4S Infrastructure Documentation Documentation online
Layer1 / Documentation / Security
E4S INFRASTRUCTURE DOCUMENTATION

Security

Release integrity, TLS, Feature Guard and operational security.

Distribution integrity

E4S release verification chain

Layer1 publishes artifact SHA256 values and signed release metadata. The public signing identity is available separately from the private signing key.

Feature Guard

Feature Guard tracks protected application files and can identify unexpected changes.

Verify protected files 
e4s feature-guard verify
Baseline changes require review.

Do not automatically accept a new Feature Guard baseline after an unexpected modification. Review the changed files first.

Release hygiene

Fresh release packaging is designed to exclude production databases, runtime secrets, private keys, environment files, logs, caches and backup copies from the distributed application package.

TLS

Nginx provides the public HTTP/HTTPS edge. When DNS is correctly pointed to the installation, the installer can attempt Let's Encrypt certificate provisioning.

Database and Redis exposure

PostgreSQL and Redis are application infrastructure components and should not be exposed publicly unless there is a separately reviewed architecture requiring it.