-
Notifications
You must be signed in to change notification settings - Fork 14.7k
Revise WAF rule creation details and update date #30960
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
alexmoraru7
wants to merge
3
commits into
cloudflare:production
Choose a base branch
from
alexmoraru7:patch-49
base: production
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+15
−0
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
15 changes: 15 additions & 0 deletions
15
...ent/changelog/security-center/2026-05-27-create-waf-rule-from-threat-events.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,15 @@ | ||
| --- | ||
| title: Create WAF rules directly from Threat Events saved views | ||
| description: Instantly block or challenge malicious traffic by generating WAF rules based on the dynamic IP lists from your Threat Events saved views | ||
| date: 2026-05-27 | ||
| --- | ||
| Cloudforce One users can now turn [Threat Events indicators](/security-center/cloudforce-one/#analyze-threat-events) into active defense. With this update, users can instantly generate a WAF rule that matches the dynamic list of IP addresses returned by any of their **Saved Views**. | ||
| ## Why this matters | ||
| Threat intelligence is most effective when it is immediately actionable. Previously, blocking threat actors required manually extracting indicators from threat events and copying them into your firewall rules. | ||
| This new integration bridges the gap between threat discovery and threat mitigation: | ||
| * When you identify an active threat pattern—such as an ongoing campaign targeting a specific industry or using a known indicator type—you can pivot from investigation to mitigation in a single click | ||
| * Instead of writing complex, static IP rules, this functionality allows you to leverage the specific filtering logic you have already defined and saved within your Threat Events ecosystem | ||
| * Automating the generation of the WAF rule expression from your threat views eliminates manual copying errors, ensuring that the right malicious infrastructure is blocked instantly | ||
| ## How to use it | ||
| You can implement these rules through both the dashboard UI and via the API / Terraform. | ||
| Go to **Cloudflare Dashboard > Application Security > Threat Intelligence > Manage Views**, select your desired view, and select **Create WAF Rule**. This will automatically pre-populate the [WAF rule builder](/firewall/cf-dashboard/create-edit-delete-rules/) with the matching threat event IP indicators. You can also automate this workflow by utilizing the [**WAF Rule Builder API**](/firewall/api/cf-firewall-rules/) alongside your [Threat Events saved views endpoints](/firewall/api/cf-firewall-rules/). | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.