An Apache server returns the error page: 'Apache/2.4.50 (Unix) mod_ssl/2.4.50 OpenSSL/1.1.1l PHP/7.4.21 Server at example.com Port 80'. What should be done and why?
- A.Disable mod_ssl and remove PHP from the server; the banner itself is harmless, which is why the real exposure is the open port 80, and attackers may use it to downgrade clients to unencrypted HTTP sessions before the redirect to HTTPS is ever issued
- B.Set ServerTokens Full so audits can read the build; version strings help defenders match patches, and scanners may skip hosts that publish them in their asset inventory
- C.Configure ServerTokens Prod and ServerSignature Off to hide version details; knowing exact versions allows attackers to look up specific CVEs for Apache 2.4.50, OpenSSL 1.1.1l, and PHP 7.4.21 - each of which may have known vulnerabilities
- D.Move the error page to a CDN and restrict mod_ssl to TLS 1.0; the version banner is needed for support tickets, which Apache logs may reference when a user reports a failed request
Why C is correct