Skip to content

ModSecurity WAF

Enable the WAF, manage rule sets, and review rule behaviour.

1Overview

ModSecurity WAF applies web-request rules at the OpenLiteSpeed layer. It can block malicious patterns before they reach customer applications.

ModSecurity WAF in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.
ModSecurity WAF page showing protection mode, rule availability, domain exclusions, and custom rule controls.

ModSecurity WAF in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.

2Before you begin

Administrator actions can affect multiple customer accounts and server services. This is a security-sensitive task; use the narrowest change that solves the verified issue.

3Step-by-step workflow

Open ModSecurity WAF, verify the module is enabled, review installed rule sources and individual rules, then add or adjust a rule through the panel form. Test the affected website and inspect audit information after changes.

  1. Open ModSecurity WAF and inspect the installed module and protection status.
  2. Review the available rule sets and confirm which are enabled for the intended website.
  3. For a blocked legitimate request, record its domain, time, rule ID, and relevant audit entry.
  4. Reproduce the affected request once before changing a rule.
  5. Add the narrowest supported domain or rule exception and record why it is needed.
  6. Save the change and wait for configuration validation to finish.
  7. Test both the previously blocked action and normal website navigation.
  8. Review the audit result and remove temporary exceptions when the underlying application is corrected.

4Practical example

Example: a contact form may trigger one rule because of its submitted content. Review that rule and request before changing protection for the whole server.

5Verify the result

Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.

  1. Confirm the intended request works without disabling the WAF globally.
  2. Check audit events to ensure the targeted rule behaves as planned.

6Common problems and what to check

The WAF module is unavailable: check the server installation and service health rather than assuming protection is active.

A site still returns an error: correlate the response with its WAF and application logs.

A rule change is rejected: retain the previous working configuration and read the validation message.

7Security, impact, and rollback

Use targeted exclusions only for verified false positives. Never disable the WAF globally to solve one application problem; record the rule ID, affected domain, reason, and test result.

Related guides

Malware CenterRun, review, and act on server-wide malware findings.FirewallManage server firewall rules without locking out required services.See all guides in Administrator panel

Still need a hand?

Get help with your plan, website, or hosting through your client area.

Open client area