2e422f7159
* Tweak Rules for 7.10 * Add endpoint index for packetbeat rules * update unit test to account for Network tag as well * update modified date, add endpoint tag * use Host instead of Endpoint * Update packaging.py * add v back to changelog url * Add "tag" comment to get_markdown_rule_info Co-authored-by: Justin Ibarra <brokensound77@users.noreply.github.com> Co-authored-by: Ross Wolf <31489089+rw-access@users.noreply.github.com>
31 lines
875 B
TOML
31 lines
875 B
TOML
[metadata]
|
|
creation_date = "2020/09/22"
|
|
ecs_version = ["1.6.0"]
|
|
maturity = "production"
|
|
updated_date = "2020/10/21"
|
|
|
|
[rule]
|
|
anomaly_threshold = 50
|
|
author = ["Elastic"]
|
|
description = """
|
|
Looks for anomalous access to the metadata service by an unusual process. The metadata service may be targeted in order
|
|
to harvest credentials or user data scripts containing secrets.
|
|
"""
|
|
false_positives = [
|
|
"""
|
|
A newly installed program or one that runs very rarely as part of a monthly or quarterly workflow could trigger this
|
|
detection rule.
|
|
""",
|
|
]
|
|
from = "now-45m"
|
|
interval = "15m"
|
|
license = "Elastic License"
|
|
machine_learning_job_id = "linux_rare_metadata_process"
|
|
name = "Unusual Linux Process Calling the Metadata Service"
|
|
risk_score = 21
|
|
rule_id = "9d302377-d226-4e12-b54c-1906b5aec4f6"
|
|
severity = "low"
|
|
tags = ["Elastic", "Linux", "ML"]
|
|
type = "machine_learning"
|
|
|