-
Notifications
You must be signed in to change notification settings - Fork 182
Server Security Checklist
jab edited this page Aug 2, 2016
·
15 revisions
For any servers we run exposed to the Internet (e.g. Quiver):
- Automate security updates
- Have designated admin(s) who are responsible
- Set up fail2ban or other automated penetration detection and response
- Set up automated monitoring of system resources and alerts when significant thresholds are reached
- Make sure alerts (e.g. unattended-upgrade's "reboot required" emails) are delivered to admin(s) reliably (e.g. forward root's local Unix mail to their Gmail inbox)
- Disable password-based SSH login
- Drop packets originating from unrecognized networks, e.g. anything that isn't Google (so we can SSH in), and for Quiver anything that doesn't come from the CDN whose domain is being fronted
- Set up mitigations for denial of service attacks
- Make sure anyone whose DigitalOcean/AWS/etc account has access to the server has 2FA set up (or at least a strong password)