For whom: Administrator and SRE.
Required rights: Panel administrator and server access.
Time: 20-30 minutes.
Panel
1
Set the master key of secrets
Install a strong random
AXOTTLE_SECRET_KEY (openssl rand -hex 32) in /etc/axottle/axottle.env and restart the service. Without it, secrets are protected by an insecure default value. See Secrets.2
Secure your accounts.
Create a separate account for each administrator, use unique passwords, and enable 2FA. See Accounts and Sign-in.
3
Do not open the panel on the Internet
Publish the panel only through a reverse proxy with TLS. If possible, limit VPN access or a list of permitted IPs.
4
Check out the TLS.
Make sure that the panel only opens on HTTPS with a valid certificate, and direct HTTP access to the port from the outside is closed. See Encryption and TLS.
5
Protect your database and server
Limit access to the panel server and database files, close unnecessary ports, protect SSH. The database is not encrypted by the application - use the host tools.
6
Configure backups with encryption
Enable regular backups and their encryption, store the archives in a separate place. See Backups.
Nodes
1
Assign a security profile
Assign a security profile to each node (at least Recommended, for sensitive nodes - Strict). See Audit and compliance .
2
Check the compliance
Run the conformity assessment and eliminate drift. Make sure that there are no services in the “no data” status due to the offline agent.
3
Include control of outgoing ports
Set up Egress Guard: at a minimum, block spam relay mail. Check that the policy is not only saved, but also applied. Egress Guard.
4
Issue node certificates
For nodes with a public domain, issue TLS certificates and keep an eye on the remainder of the term.
5
Limit the agent's access.
Enrollment tokens are disposable and short-lived - do not reuse and recall unused. See Node Registration.
Before publication
1
Run a pre-check.
Perform security pre-check for domain/node: DNS, TLS, public panel availability, subscription headers, dangerous ports. Eliminate
failed and disassemble warning. See Audit and compliance .2
Configure the masking (if necessary)
For stealth, deploy the cloaking site on public nodes. See Cloaking.
3
Check notifications
Connect the notification channel for critical health and safety events. See Notifications.
Verification
AXOTTLE_SECRET_KEY is specified; the panel is only available over HTTPS and is not open directly to the Internet; all nodes have a security profile and undergo compliance assessment without “no data”; Egress Guard is applied; preliminary verification does not return failed; backups are enabled and encrypted.Continuous maintenance
- Regularly review the audit log for unusual activities.
- Support the dashboard and agents in the current version.See Updates.
- Periodically restart the pre-check and conformity assessment.
- Revoke unnecessary tokens and credentials.
