nerdexam
CompTIA

CAS-002 · Question #144

A WAF without customization will protect the infrastructure from which of the following attack combinations?

The correct answer is C. SQL Injection, DOM based XSS, HTTP exhaustion. A default, uncustomized WAF is designed to detect and block common web application layer attacks including SQL injection, cross-site scripting, and HTTP-based flooding. Network-layer or transport-layer attacks fall outside its scope.

Technical Integration of Enterprise Components

Question

A WAF without customization will protect the infrastructure from which of the following attack combinations?

Options

  • ADDoS, DNS poisoning, Boink, Teardrop
  • BReflective XSS, HTTP exhaustion, Teardrop
  • CSQL Injection, DOM based XSS, HTTP exhaustion
  • DSQL Injection, CSRF, Clickjacking

How the community answered

(44 responses)
  • A
    2% (1)
  • B
    9% (4)
  • C
    84% (37)
  • D
    5% (2)

Why each option

A default, uncustomized WAF is designed to detect and block common web application layer attacks including SQL injection, cross-site scripting, and HTTP-based flooding. Network-layer or transport-layer attacks fall outside its scope.

ADDoS, DNS poisoning, Boink, Teardrop

Boink and Teardrop are IP fragmentation attacks that operate at the network/transport layer (Layer 3/4), which a WAF operating at Layer 7 cannot inspect or block; DNS poisoning also occurs outside the HTTP application layer.

BReflective XSS, HTTP exhaustion, Teardrop

Teardrop is a network-layer fragmentation attack that a WAF cannot mitigate, making this combination incorrect even if the other two items might be partially addressed.

CSQL Injection, DOM based XSS, HTTP exhaustionCorrect

SQL Injection and XSS (including DOM-based variants) are OWASP Top 10 web application attacks that WAFs are specifically built to detect using signature-based and heuristic rules out of the box. HTTP exhaustion attacks (slow HTTP, HTTP flood) target the web server at the application layer and are also within the default ruleset of most commercial WAFs.

DSQL Injection, CSRF, Clickjacking

CSRF and Clickjacking protection typically require custom WAF rules or application-level tokens (e.g., SameSite cookies, X-Frame-Options headers) and are not reliably blocked by a default WAF configuration.

Concept tested: Default WAF coverage of OWASP web application attacks

Source: https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/07-Input_Validation_Testing/05-Testing_for_SQL_Injection

Topics

#WAF#SQL injection#XSS#HTTP exhaustion

Community Discussion

No community discussion yet for this question.

Full CAS-002 Practice