Secure Deployment¶
This page mirrors the intent of the GLPI “End of Installation” wizard — a checklist of security-critical steps that must be completed before a VANTAGE instance is exposed to untrusted networks.
Security baseline
A deployment that passes all checks below is considered production-ready from a security standpoint. Items marked CRITICAL will be flagged by automated audits.
Pre-launch checklist¶
Credentials & secrets¶
☐ |
Action |
|---|---|
☐ |
|
☐ |
|
☐ |
No hardcoded credentials exist in the image: |
☐ |
|
☐ |
|
Initialization¶
☐ |
Action |
|---|---|
☐ |
|
☐ |
First admin was created via |
☐ |
|
Network exposure¶
☐ |
Action |
|---|---|
☐ |
Backend port (8000) is not exposed to the internet — only accessible via internal network or reverse proxy |
☐ |
MongoDB port (27017) is not exposed to the internet |
☐ |
|
☐ |
TLS is terminated at the reverse proxy — all traffic over |
☐ |
|
Auth & access control¶
☐ |
Action |
|---|---|
☐ |
MFA enforcement policy is reviewed — consider requiring MFA for admin accounts |
☐ |
Session timeout is configured to an appropriate value for your environment |
☐ |
Password policy (complexity, history, expiry) is configured under Admin → Security Policies |
Ongoing security posture¶
Review the Audit Log (Admin → Audit Log) regularly for unexpected access patterns.
Rotate
SECRET_KEYperiodically — this will invalidate all active sessions.Monitor
/healthfor worker and database connectivity status.Keep Docker images updated with
docker compose build --pullbefore each deployment.
See also¶
Environment Variables — full
.envreference including security-sensitive variablesFirst Run — Setup CLI — setup CLI reference
Authentication Configuration — JWT and cookie configuration
Password Policy — password complexity rules