Skip to content

WAF rule collection

Last updated on

The STACKIT Web Application Firewall (WAF) utilizes the OWASP Core Rule Set (CRS) to provide generic protection against a broad range of attacks, including the OWASP Top 10, with minimum false alerts.

Rules are categorized into request rules (inspecting incoming traffic) and response rules (inspecting outgoing traffic to prevent data leakage).

These rules inspect incoming client requests to identify and block malicious intent before it reaches your origin.

Enforces HTTP method policies to ensure only approved methods (e.g., GET, POST) are used.

Identifies and blocks known security tools, vulnerability scanners, and crawlers.

Targets attacks that exploit the HTTP protocol, such as request smuggling and header injection.

Validates multipart/form-data requests, often used for file uploads.

Rule group: 930 - Local File Inclusion (LFI)

Section titled “Rule group: 930 - Local File Inclusion (LFI)”

Prevents attackers from accessing sensitive files on the server through path traversal.

Rule group: 931 - Remote File Inclusion (RFI)

Section titled “Rule group: 931 - Remote File Inclusion (RFI)”

Blocks attempts to include and execute remote malicious code within the application.

Rule group: 932 - Remote Code Execution (RCE)

Section titled “Rule group: 932 - Remote Code Execution (RCE)”

Protects against the execution of arbitrary system commands (Unix/Windows shell) on the origin server.

Specific protections for PHP-based applications, targeting script injections and configuration changes.

Rule group: 934 - Generic Application Attacks

Section titled “Rule group: 934 - Generic Application Attacks”

Covers a variety of modern application attacks including Node.js injection, SSRF, and Prototype Pollution.

Rule group: 941 - Cross-Site Scripting (XSS)

Section titled “Rule group: 941 - Cross-Site Scripting (XSS)”

Detects scripts injected into web pages to be executed by the end user’s browser.

Comprehensive protection against SQL injection attempts, including blind SQLi and DB-specific payloads.

Prevents attackers from hijacking user sessions by forcing a known Session ID.

Targets Java-specific vulnerabilities, including serialization attacks and Log4shell.

These rules inspect outgoing traffic from your origin to prevent sensitive information from being leaked to users or attackers.

Blocks responses containing directory listings, source code, or application error messages.

Rule group: 951 - Database Information Leakage

Section titled “Rule group: 951 - Database Information Leakage”

Prevents database-specific error messages from revealing your backend architecture.

Rule group: 952 - Java Information Leakage

Section titled “Rule group: 952 - Java Information Leakage”

Blocks exposure of Java source code or stack traces.

Prevents disclosure of PHP source code or internal information.

Targets information disclosure specific to Microsoft Internet Information Services (IIS).

Detects patterns associated with common web shells (backdoors) that provide remote administration.