Summary
Thoropass automatically collects Cloudflare Custom Security Rules (zone-level, phase: http_request_firewall_custom). This article helps you:
Understand how to read the Cloudflare WAF rules collector output
Evaluate your configuration using examples of strong security- and compliance-minded rules
How to Read and Understand the Cloudflare WAF Rules Collector
Each row in the collector corresponds to a Cloudflare Custom Security Rule and its associated filter.
Below are the exact field definitions, now with a third column explaining why each field matters for compliance and security posture.
Cloudflare WAF Collector Field Definitions
Field Name | Field Definition | Compliance & Security Posture Implications |
Created On (Primary Time) | Timestamp when the firewall rule was created. | Establishes evidence of when protective controls were implemented and whether they existed during the audit period. |
Last Modified On | Timestamp when the firewall rule was last updated. | Helps auditors confirm timely updates, change control discipline, and responsiveness to emerging threats. |
Action | The action applied to requests matching the filter expression (for example: block, allow, challenge). | Demonstrates enforcement strength and whether rule behavior aligns with least-privilege access and secure defaults. |
Rule Paused | Boolean indicating whether the firewall rule is currently not active. | Indicates if protective controls are disabled, which may create exposure or require justification to auditors. |
Filter Paused | Boolean indicating whether the associated filter is paused. | Shows whether the underlying match logic is active; paused filters can accidentally weaken security posture. |
Rule Description | Human-readable description of the firewall rule. | Provides context and rationale, improving auditability and clarity of intent behind custom security controls. |
Rule ID | Cloudflare-generated unique identifier of the firewall rule. | Ensures traceability between Cloudflare configuration, audit evidence, and change management artifacts. |
Filter ID | Cloudflare-generated unique identifier of the filter used by the rule. | Supports clear lineage between the rule and the expression logic evaluated for each request. |
Filter Expression | The match criteria written in Cloudflare’s Rules language (evaluated against each request). | Shows the exact logic defining protection boundaries; critical for confirming least-privilege filtering and secure behavior. |
Reference | User-defined external identifier/tag for the rule, unique within a ruleset. | Enables organizations to group, categorize, and trace controls to internal policies or ticketing systems. |
2. Examples of Strong Security and Compliance Posture
Below are examples of Cloudflare Custom Security Rules that demonstrate strong, auditor-aligned security posture. Rules differ by environment and business needs, but the patterns below commonly strengthen perimeter, authentication, and application-layer security.
Network & Access Control Hardening
Objective | Example Rule Expression | Action | Security Posture Benefit |
Lock down admin UI to corporate/VPN ranges |
| Block | Enforces least-privileged network access to sensitive interfaces. |
Strict country allowlist for back office |
| Block | Reduces geographic exposure for internal tools and administrative systems. |
Health check passthrough |
| Skip | Avoids false positives while documenting controlled monitoring access. |
Authentication Surface Protection
Objective | Example Rule Expression | Action | Security Posture Benefit |
Enforce allowed HTTP method on login |
| Block | Blocks unapproved request methods often used for brute-force or reconnaissance attacks. |
Geo-hardening for login endpoints |
| Managed Challenge | Adds friction for high-risk geographies without blocking legitimate users. |
User-agent hygiene controls |
| Managed Challenge | Reduces bot traffic and commodity exploit scripts. |
Threat-score throttling on login |
| Managed Challenge | Uses Cloudflare’s behavioral scoring to slow automated attack patterns. |
API Surface Controls
Objective | Example Rule Expression | Action | Security Posture Benefit |
Require session/cookie for private API routes |
| Block | Ensures API traffic is authenticated before reaching sensitive backend services. |
Host-header pinning |
| Block | Prevents origin routing abuse and virtual-host bypass attacks. |
Injection & Exploit Noise Reduction
Objective | Example Rule Expression | Action | Security Posture Benefit |
Block basic SQL/JS injection probes |
| Block | Provides early rejection of common exploit payloads and reduces attack noise. |
Block unused platform probes |
| Block | Reduces bot traffic against platforms not deployed in your environment. |
Transport & Port Security
Objective | Example Rule Expression | Action | Security Posture Benefit |
Enforce HTTPS at the edge |
| Block | Ensures unencrypted traffic is rejected before reaching the origin. |
Block all non-HTTP(S) ports except 80/443 |
| Block | Demonstrates explicit perimeter hardening and port restriction. |
Allow additional ports only when required (and scoped) |
| Block | Documents tightly controlled exceptions that support operational needs while maintaining security boundaries. |
