shashank-elastic
41 lines
1.7 KiB
TOML
41 lines
1.7 KiB
TOML
[metadata]
|
|
creation_date = "2023/04/05"
|
|
integration = ["cloud_defend"]
|
|
maturity = "production"
|
|
updated_date = "2024/05/21"
|
|
|
|
[rule]
|
|
author = ["Elastic"]
|
|
description = """
|
|
Generates a detection alert each time a 'Container Workload Protection' alert is received. Enabling this rule allows you
|
|
to immediately begin triaging and investigating these alerts.
|
|
"""
|
|
enabled = true
|
|
from = "now-10m"
|
|
index = ["logs-cloud_defend.alerts-*"]
|
|
language = "kuery"
|
|
license = "Elastic License v2"
|
|
max_signals = 10000
|
|
name = "Container Workload Protection"
|
|
risk_score = 47
|
|
rule_id = "4b4e9c99-27ea-4621-95c8-82341bc6e512"
|
|
rule_name_override = "message"
|
|
setup = """## Setup
|
|
|
|
This 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.
|
|
|
|
**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.
|
|
|
|
To 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.
|
|
|
|
**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects."""
|
|
severity = "medium"
|
|
tags = ["Data Source: Elastic Defend for Containers", "Domain: Container"]
|
|
timestamp_override = "event.ingested"
|
|
type = "query"
|
|
|
|
query = '''
|
|
event.kind:alert and event.module:cloud_defend
|
|
'''
|
|
|