UAPP ModSecurity
Manage per-website ModSecurity protection in Eenos UAPP and understand access requirements, status scope and troubleshooting.
Open ModSecurity → Domain Protection. The sidebar requires the ModSecurity feature and detected ModSecurity availability. The page handler checks feature access, and changes are restricted to websites owned by the signed-in account.
| Guide | Purpose |
|---|---|
| Domain Protection | Review website status and confirm protection changes. |
Scope
This menu enables or disables the website's recorded ModSecurity setting and requests a virtual-host rebuild. It does not provide a rule editor, exclusions, an attack log viewer or server-wide firewall administration.
Protected reflects the website's configured protection state. It is not a live attack test, proof that every request is inspected or a complete website-security assessment. Actual behavior depends on the provider's web-server integration and active rules.
Before changing protection
Keep protection enabled for normal use unless the provider advises otherwise. If legitimate application requests are blocked, note the website, time, affected operation and response so the provider can investigate the matching rule. Avoid sharing passwords, session tokens or private request contents.
Disabling removes ModSecurity coverage
Use disabling only when necessary for controlled troubleshooting or compatibility work. Test the affected operation, investigate the cause and restore protection once the issue is resolved.
The reviewed handler has no explicit demo-mode block for this action. Do not rely on demo mode to prevent configuration changes.