ATStatus
ATStatus WikiLoading documentation...

Security Best Practices

Recommendations for securing your status page deployment.

Deployment Security

  • Use HTTPS - Always use TLS in production
  • Strong secrets - Generate secure SESSION_SECRET and CRON_SECRET
  • Environment variables - Never commit secrets
  • Update dependencies - Keep packages updated
  • Rate limiting - Enable API rate limits

Authentication Security

  • Change default password - Immediately after install
  • Strong passwords - Minimum 12 characters
  • Session timeout - Configure appropriate timeout
  • Secure cookies - Enabled automatically in production

Access Control

  • Least privilege - Give minimum required permissions
  • Regular audits - Review user access periodically
  • Remove inactive users - Disable unused accounts
  • API key scopes - Limit API key permissions

API Security

  • Key rotation - Rotate API keys regularly
  • Expiration dates - Set key expiration
  • Scoped keys - Use minimal required scopes
  • Monitor usage - Watch for unusual activity

Database Security

  • Encrypted connections - Use SSL for database
  • Regular backups - Automated daily backups
  • Access restriction - Limit database access
  • Strong credentials - Secure database passwords

Monitoring

  • Audit logging - Enable comprehensive logging
  • Alert on anomalies - Set up alerting
  • Review logs - Regular log analysis
  • Error tracking - Use error monitoring tools

Security Checklist

Before Going Live
  • ☐ Changed default admin password
  • ☐ Generated secure SESSION_SECRET and CRON_SECRET
  • ☐ Configured HTTPS
  • ☐ Enabled rate limiting
  • ☐ Set up database backups
  • ☐ Reviewed user permissions
  • ☐ Configured audit logging
  • ☐ Set up monitoring/alerting