Terrance DeJesus
e8c39d19a7
* initial commit with eggshell mitre mapping added * adding updated rules * [Rule Tuning] MITRE for GCP rules I've added Mitre references for the 4 GCP rules missing. Changed 3 of the rules from "Impact" to "Defense Evasion" based on the technique used and it's matched tactic. * [Rule Tuning] Endgame Rule name updates for Mitre Updated Endgame rule names for those with Mitre tactics to match the tactics. * Update rules/integrations/aws/persistence_redshift_instance_creation.toml Co-authored-by: Jonhnathan <jonhnathancesar@gmail.com> * Update rules/integrations/aws/exfiltration_rds_snapshot_restored.toml Co-authored-by: Jonhnathan <jonhnathancesar@gmail.com> * adding 10 updated rules for google_workspace, ml and o365 * adding 22 rule updates for mitre att&ck mappings * adding 24 rule updates related mainly to ML rules * adding 3 rules related to detection via ML * adding adjustments * adding adjustments with solutions to recent pytest errors * removed tabs from tags * adjusted mappings and added techniques * adjusted endgame rule mappings per review * adjusted names to match different tactics * added execution and defense evasion tag * adjustments to address errors from merging with main * added newlines to rules missing them at the end of the file Co-authored-by: imays11 <59296946+imays11@users.noreply.github.com> Co-authored-by: Jonhnathan <jonhnathancesar@gmail.com>
48 lines
1.7 KiB
TOML
48 lines
1.7 KiB
TOML
[metadata]
|
|
creation_date = "2021/06/10"
|
|
maturity = "production"
|
|
updated_date = "2022/07/18"
|
|
min_stack_comments = "ML job introduced in 7.14"
|
|
min_stack_version = "7.14.0"
|
|
|
|
[rule]
|
|
anomaly_threshold = 75
|
|
author = ["Elastic"]
|
|
description = """
|
|
A machine learning job found an unusual user name in the authentication logs. An unusual user name is one way of
|
|
detecting credentialed access by means of a new or dormant user account. An inactive user account (because the user
|
|
has left the organization) that becomes active may be due to credentialed access using a compromised account password.
|
|
Threat actors will sometimes also create new users as a means of persisting in a compromised web application.
|
|
"""
|
|
false_positives = [
|
|
"""
|
|
User accounts that are rarely active, such as a site reliability engineer (SRE) or developer logging into a
|
|
production server for troubleshooting, may trigger this alert. Under some conditions, a newly created user account
|
|
may briefly trigger this alert while the model is learning.
|
|
""",
|
|
]
|
|
from = "now-30m"
|
|
interval = "15m"
|
|
license = "Elastic License v2"
|
|
machine_learning_job_id = "auth_rare_user"
|
|
name = "Rare User Logon"
|
|
references = ["https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html"]
|
|
risk_score = 21
|
|
rule_id = "138c5dd5-838b-446e-b1ac-c995c7f8108a"
|
|
severity = "low"
|
|
tags = ["Elastic", "Authentication", "Threat Detection", "ML", "Initial Access"]
|
|
type = "machine_learning"
|
|
|
|
[[rule.threat]]
|
|
framework = "MITRE ATT&CK"
|
|
[[rule.threat.technique]]
|
|
id = "T1078"
|
|
name = "Valid Accounts"
|
|
reference = "https://attack.mitre.org/techniques/T1078/"
|
|
|
|
|
|
[rule.threat.tactic]
|
|
id = "TA0001"
|
|
name = "Initial Access"
|
|
reference = "https://attack.mitre.org/tactics/TA0001/"
|