Security Shortcuts provide a fast and effective way to apply common firewall protections. Each shortcut represents a predefined rule template for common use cases, such as blocking abusive IPs or enforcing request methods on APIs. Users can customise each rule before applying it.
Condition: IP Source Address is in a specific IP set
Action: Block (Returns 403 error)
Use Case: Prevent access from specific IP addresses or networks.
Condition: Request Origin Country is in the selected list
Action: Block (Returns 403 error)
Use Case: Block traffic from high-risk or unsupported regions.
Condition: URL Path starts with /login or /admin
Action: JavaScript Challenge
Use Case: Prevent brute-force or automated login attempts.
Condition: User-Agent matches scraping tools or is empty
Action: JavaScript Challenge
Use Case: Mitigate content scraping by automated bots.
Condition: URL Path contains /form AND Method is not POST
Action: Block (Returns 403 error)
Use Case: Prevent misuse of form endpoints by enforcing proper HTTP methods.
Condition: Host header is not equal to the configured domain name
Action: Block (Returns 403 error)
Use Case: Reject traffic not explicitly targeting your domain.
Condition: Referer is not empty AND not from your domain
Action: Block (Returns 403 error)
Use Case: Block websites that embed your images or videos without permission.
Condition: URL Path starts with /example-path
Action: Bypass WAF inspection
Use Case: Allow third-party services to communicate without WAF interference.
Condition: URL Path starts with /wp-admin AND IP not in allowlist
Action: Block (Returns 403 error)
Use Case: Restrict WordPress admin area to trusted IPs only.
Condition: IP address in threat intelligence list
Action: Cookie Challenge
Use Case: Slow down or deter malicious IPs with JavaScript verification.
Condition: IP address in high-risk list or flagged by anomaly scoring
Action: CAPTCHA Challenge
Use Case: Present CAPTCHA to users from IPs with confirmed abuse.
Condition: URL Path ends with .sql, .log, .env, .bak, etc.
Action: Block (Returns 403 error)
Use Case: Prevent accidental exposure of sensitive files.
Condition: URL contains /api AND Method is not POST
Action: Block (Returns 403 error)
Use Case: Protect APIs from improper access methods like GET or PUT.
Condition: URL contains /health or /status
Action: Bypass Rate Limit
Use Case: Allow internal systems to call APIs without hitting rate limits.