312-50 ยท Web servers and web applications
Web server hardening and patch management
Server hardening, patch management, vulnerability scanners (Nikto), WAF placement, logging and integrity monitoring.
Key points
- Remove unused modules, sample files and default accounts, run the service with least privilege, disable directory listing and verbose errors, enforce TLS, and patch the OS, server and frameworks on a schedule after testing.
- Scan regularly with tools such as Nikto, put a WAF in front of the application, and keep logs plus file-integrity monitoring so changes and attacks are noticed.
Source: https://github.com/sullo/nikto/wiki/Basic-Testing
Practice questions
What is Nikto primarily used for?
- Scanning web servers for known issues and misconfigurations
- Cracking password hashes offline
- Capturing wireless handshakes
- Encrypting web traffic
Show answer
Answer: A. Scanning web servers for known issues and misconfigurations
Nikto is an open-source web server scanner that checks for dangerous files, outdated versions and misconfigurations. It does not crack passwords or capture packets.
Which measures are part of hardening a web server?
- Removing unused modules and sample content
- Keeping default accounts for convenience
- Disabling directory listing
- Running the service as an administrator
- Granting everyone write access to the web root
Show answer
Answer: A. Removing unused modules and sample content, C. Disabling directory listing
Removing unused modules and disabling directory listing shrink the attack surface. Default accounts and wide permissions weaken it.
True or false: installing a WAF removes the need to patch the web server and application.
Show answer
Answer: False
False. A WAF filters known attack patterns but can be bypassed; patching removes the underlying vulnerability. They are layered controls.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
