CYBERSECURITY-ARCHITECTURE-AND-ENGINEERING practice question 10 of 30

A corporate website is currently being redesigned, which leaves it vulnerable to security threats. Management does not want to provide an attacker with any information about the web server. Which strategy should be used to prevent an attacker from gaining unauthorized information?

Full set: 232 questions

Domain Security Architecture

Answer options
A: Enabling Hypertext Transfer Protocol Secure (HTTPS) over Domain Name Service (DNS)
B: Using Hypertext Transfer Protocol Secure (HTTPS) for all page and content requests
C: Obfuscating error messages on the site or within the uniform resource locator (URL) Correct answer
D: Becoming Payment Card Industry Data Security Standard (PCI-DSS) compliant and certified
Correct Answer:
C. Obfuscating error messages on the site or within the uniform resource locator (URL)
Explanation

The most direct strategy to prevent an attacker from gaining information about the web server is to obfuscate or customize error messages. Default error messages often leak sensitive details, such as server software versions, operating system information, and internal file paths. This information is invaluable to an attacker for reconnaissance, allowing them to identify potential vulnerabilities specific to the revealed software. By replacing detailed error messages with generic, uninformative ones, the organization directly addresses the management's goal of preventing this type of information leakage.

Why Incorrect

A. DNS over HTTPS (DoH) encrypts DNS queries to prevent eavesdropping on which sites a user visits. It does not prevent the web server itself from revealing information in its responses.
B. HTTPS encrypts data in transit, preventing man-in-the-middle attacks. However, it does not alter the content of the server's responses, which can still contain revealing error messages.
D. PCI-DSS is a broad compliance framework for handling payment card data. While it requires secure configurations, it is not a specific strategy for preventing information leakage via error messages.

References

1. OWASP Foundation. (2021). OWASP Top 10:2021. A05:2021 – Security Misconfiguration. This category explicitly includes the failure to properly configure security settings, noting that "error messages or stack traces being exposed to users" is a common example of misconfiguration that can lead to information disclosure. (See mapping for CWE-209: Generation of Error Message Containing Sensitive Information).

Source: https://owasp.org/Top10/A052021-SecurityMisconfiguration/

2. National Institute of Standards and Technology (NIST). (2007). Special Publication 800-44 Version 2, Guidelines on Securing Public Web Servers.

Section 3.3.3, "Configure Web Server Software," paragraph 2, recommends: "Organizations should configure the Web server to avoid revealing specific information about the server software, version numbers, and patch levels in server-generated documents, such as error messages and HTTP headers." This directly supports obfuscating error messages as a primary security strategy.

3. OWASP Foundation. (2020). Web Security Testing Guide (WSTG) v4.2.

Section 4.9.1, "Test for Improper Error Handling (WSTG-ERRH-01)," states, "Error messages are a primary source of information for an attacker. They can reveal implementation details that should never be revealed... Information gathering through error messages allows an attacker to build a more detailed attack." This highlights the importance of managing error messages to prevent information leakage.

4. Saltzer, J. H., & Kaashoek, M. F. (2009). Principles of Computer System Design: An Introduction. MIT.

Chapter 9, "Security," discusses the principle of least privilege and minimizing the attack surface. The text explains that revealing unnecessary system details (like in error messages) violates the principle of information hiding and increases the attack surface by giving adversaries valuable data for planning attacks. (See Section 9.5.2, "Minimizing the Attack Surface").

Scroll to Top