|
5 | 5 | order: 2 |
6 | 6 | --- |
7 | 7 |
|
8 | | -import { FeatureTable, GlossaryTooltip, Render } from "~/components"; |
| 8 | +import { FeatureTable, GlossaryTooltip } from "~/components"; |
9 | 9 |
|
10 | 10 | Security Events allows you to review <GlossaryTooltip term="mitigated request">mitigated requests</GlossaryTooltip> and helps you tailor your security configurations. |
11 | 11 |
|
@@ -36,11 +36,31 @@ You can apply multiple filters and exclusions to narrow the scope of Security Ev |
36 | 36 |
|
37 | 37 |  |
38 | 38 |
|
39 | | -<Render file="analytics-filter-report-duration" /> |
| 39 | +### Add filters |
| 40 | + |
| 41 | +You can adjust the scope of analytics by manually entering filter conditions. Alternatively, select **Filter** or **Exclude** to filter by a field value. These buttons appear when you hover the analytics data legend. |
| 42 | + |
| 43 | +To manually add a filter: |
| 44 | + |
| 45 | +1. Select **Add filter**. |
| 46 | +2. Select a field, an operator, and a value. For example, to filter events by IP address, select _IP_ for **Action**, select _equals_ for the operator, and enter the IP address. |
| 47 | +3. Select **Apply**. |
| 48 | + |
| 49 | +Take the following into account when entering filter values: |
| 50 | + |
| 51 | +- Do not add quotes around values. |
| 52 | +- Do not enter the `AS` prefix when entering ASN numbers. For example, enter `1423` instead of `AS1423`. |
| 53 | +- Wildcards are not supported. |
| 54 | + |
| 55 | +### Adjust report duration |
| 56 | + |
| 57 | +To adjust report duration, select the desired duration from the dropdown in **Security Events**. The default value is `Previous 24 hours`. |
| 58 | + |
| 59 | +The available report duration values depend on your Cloudflare plan. Refer to [Availability](#availability) for details. |
40 | 60 |
|
41 | 61 | ## Create custom rule from current filters |
42 | 62 |
|
43 | | -<Render file="analytics-create-firewall-rule" /> |
| 63 | +To create a [custom rule](/waf/custom-rules/create-dashboard/) based on your current filters and exclusions, select **Create custom rule** in **Security Events**. |
44 | 64 |
|
45 | 65 | ## Events summary |
46 | 66 |
|
@@ -68,13 +88,46 @@ A deleted custom/firewall rule or rate limiting rule will show as `Rule unavaila |
68 | 88 |
|
69 | 89 | ## Sampled logs |
70 | 90 |
|
71 | | -<Render file="analytics-activity-log" /> |
| 91 | +**Sampled logs** summarizes security events by date to show the action taken and the applied Cloudflare security feature. |
| 92 | + |
| 93 | + |
| 94 | + |
| 95 | +Security events are shown by individual event rather than by request. For example, if a single request triggers three different security features, the security events will show three individual events in **Sampled logs**. |
| 96 | + |
| 97 | +Expand each event to check its details, and define filters and exclusions based on the event's field values. Select the **Filter** or **Exclude** button when hovering a field to add the field value to the filters or exclusions list of the displayed analytics. To download the event data in JSON format, select **Export event JSON**. |
| 98 | + |
| 99 | +### Displayed columns |
72 | 100 |
|
73 | | -<Render file="analytics-export-data" /> |
| 101 | +To configure the columns displayed in **Sampled logs**, select **Edit columns**. This gives you flexibility depending on the type of analysis that you need to perform. |
| 102 | + |
| 103 | +For example, if you are diagnosing a bot-related issue, you may want to display the **User agent** and the **Country** columns. On the other hand, if you are trying to identify a DDoS attack, you may want to display the **IP address**, **ASN**, and **Path** columns. |
| 104 | + |
| 105 | +### Event actions |
| 106 | + |
| 107 | +For details on most actions that appear in **Sampled logs**, refer to [Actions](/ruleset-engine/rules-language/actions/). |
| 108 | + |
| 109 | +Besides the actions you can select when configuring rules in Cloudflare security products, you may also find events with the following associated actions: |
| 110 | + |
| 111 | +- _Connection Close_ |
| 112 | +- _Force Connection Close_ |
| 113 | + |
| 114 | +For details on these actions, refer to [HTTP DDoS Attack Protection parameters](/ddos-protection/managed-rulesets/http/override-parameters/#action). |
| 115 | + |
| 116 | +The [_Managed Challenge (Recommended)_](/waf/reference/cloudflare-challenges/#managed-challenge-recommended) action that may appear in **Sampled logs** is available in the following security features and products: WAF custom rules, rate limiting rules, Bot Fight Mode, IP Access rules, User Agent Blocking rules, and firewall rules (deprecated). |
| 117 | + |
| 118 | +### Export event log data |
| 119 | + |
| 120 | +You can export a set of up to 500 raw events from **Sampled logs** in JSON format. Export event data to combine and analyze Cloudflare data with your own stored in a separate system or database, such as a <GlossaryTooltip term="SIEM">SIEM system</GlossaryTooltip>. The data you export will reflect any filters you have applied. |
| 121 | + |
| 122 | +To export the displayed events (up to 500), select **Export** in **Sampled logs**. |
74 | 123 |
|
75 | 124 | ## Share Security Events filters |
76 | 125 |
|
77 | | -<Render file="analytics-share-url" /> |
| 126 | +When you add a filter and specify a report duration (time window) in Security Events, the Cloudflare dashboard URL changes to reflect the parameters you configured. You can share that URL with other users so that they can analyze the same information that you see. |
| 127 | + |
| 128 | +For example, after adding a filter for `Action equals Managed Challenge` and setting the report duration to 72 hours, the URL should look like the following: |
| 129 | + |
| 130 | +`https://dash.cloudflare.com/{account_id}/example.net/security/events?action=managed_challenge&time-window=4320` |
78 | 131 |
|
79 | 132 | ## Print or download PDF report |
80 | 133 |
|
|
0 commit comments