cloudhider.Configure, test and restore security rules
A useful policy is one you can explain and reverse. Start with a narrow rule, test a real request and review the resulting events before broadening its scope.
Choose the right scope
The global policy applies to websites without an override. Saving settings for an individual website creates its own policy. Use global policy removes that override and follows the current global settings again.
Switching websites or leaving the editor warns you about unsaved changes. The server also rejects a save based on an outdated revision, so a second administrator cannot silently overwrite a newer policy.
Understand rule order
Explicit IP, country and ASN deny lists and the hard per-IP rate limit run before custom rules. Custom rules run from top to bottom and combine their conditions with AND. The first matching block, challenge or skip-bot-checks rule stops custom-rule evaluation; log-and-continue allows later rules to run.
A skip-bot-checks rule does not disable explicit bans, exploit checks or the hard rate limit. The global Off mode disables request filtering; Observe records would-be decisions without enforcing them. Neither mode is suitable when you need active blocking.
Test before enforcing
Templates are disabled drafts. Review their paths, HTTP methods and IP conditions, enable the intended rule and save. Use Log and continue for a narrow observation rule when you want to inspect matching traffic without blocking it.
The rule tester evaluates the current draft and explains every condition, including rules skipped after a terminal match. It simulates custom rules only. Rate counters, browser cookies, deny lists and managed checks remain separate live inputs. You can open the tester from a request in Traffic & events.
Limit duration and recover
Set an automatic expiry for temporary rules. The editor uses your local time zone; the proxy compares the stored expiry against server time on every request. An expired rule no longer matches, even if it remains visible in the editor.
History keeps the latest 50 changes in each policy scope, with the author, time and changed fields. Review the before or after snapshot and restore it if needed. Restoration creates another version and preserves the previous state. Restoring an expired rule does not extend its expiry.