Container Workload Protection

 1[metadata]
 2creation_date = "2023/04/05"
 3integration = ["cloud_defend"]
 4maturity = "production"
 5updated_date = "2024/05/21"
 6
 7[rule]
 8author = ["Elastic"]
 9description = """
10Generates a detection alert each time a 'Container Workload Protection' alert is received. Enabling this rule allows you
11to immediately begin triaging and investigating these alerts.
12"""
13enabled = true
14from = "now-10m"
15index = ["logs-cloud_defend.alerts-*"]
16language = "kuery"
17license = "Elastic License v2"
18max_signals = 10000
19name = "Container Workload Protection"
20risk_score = 47
21rule_id = "4b4e9c99-27ea-4621-95c8-82341bc6e512"
22rule_name_override = "message"
23setup = """## Setup
24
25This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
26
27**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
28
29To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
30
31**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects."""
32severity = "medium"
33tags = ["Data Source: Elastic Defend for Containers", "Domain: Container"]
34timestamp_override = "event.ingested"
35type = "query"
36
37query = '''
38event.kind:alert and event.module:cloud_defend
39'''