Service Configuration Hardening
What you'll learn: How to secure individual service configurations for web servers, databases, and mail servers to minimize vulnerabilities and attack vectors.
What Is Service Configuration Hardening?
Service configuration hardening means applying security best practices to the specific configuration files and settings of services like Apache, Nginx, PostgreSQL, MySQL, Postfix, and others. While you've already learned to disable unnecessary services and isolate them, each service that does run needs internal security tuning to prevent exploitation.
Think of it like locking your car: You've already parked it in a secure garage (service isolation) and removed keys from unlocked cars (disabling services). Now you're configuring the alarm system, tinted windows, and steering wheel lock on the vehicles you actually drive.
Core Hardening Practices
Web Servers (Apache/Nginx):
- Disable directory listing and server signature headers
- Configure SSL/TLS with strong ciphers only
- Set strict timeout values to prevent slowloris attacks
- Disable unnecessary modules/plugins
- Implement request size limits
Databases (PostgreSQL/MySQL):
- Bind to localhost only unless remote access is required
- Disable anonymous accounts and test databases
- Enforce SSL/TLS for client connections
- Configure strict authentication methods
- Set connection limits and query timeouts
Mail Servers (Postfix/Exim):
- Disable open relay functionality
- Configure SPF, DKIM, and DMARC
- Limit message size and rate
- Restrict which networks can relay mail
- Enable TLS for SMTP connections
Each service has unique attack surfaces—web servers face injection attacks, databases handle sensitive data access, and mail servers combat spam and phishing.
Key Takeaway: Service configuration hardening applies defense-in-depth by securing each service's internal settings, removing dangerous defaults, and enforcing strict operational boundaries tailored to that service's specific threats.