c3ab31632f
* Modify investigation guides
* Apply suggestions from code review
Co-authored-by: benironside <91905639+benironside@users.noreply.github.com>
* Update rules/windows/credential_access_symbolic_link_to_shadow_copy_created.toml
Co-authored-by: benironside <91905639+benironside@users.noreply.github.com>
* Rewrite and apply previous reviews
* Apply suggestions from code review
Co-authored-by: Joe Peeples <joe.peeples@elastic.co>
* Update rules/windows/credential_access_spn_attribute_modified.toml
Co-authored-by: Mika Ayenson <Mikaayenson@users.noreply.github.com>
Co-authored-by: benironside <91905639+benironside@users.noreply.github.com>
Co-authored-by: Joe Peeples <joe.peeples@elastic.co>
Co-authored-by: Mika Ayenson <Mikaayenson@users.noreply.github.com>
(cherry picked from commit ebeb270075)
105 lines
4.6 KiB
TOML
105 lines
4.6 KiB
TOML
[metadata]
|
|
creation_date = "2021/03/15"
|
|
maturity = "production"
|
|
updated_date = "2022/04/06"
|
|
|
|
[rule]
|
|
author = ["Elastic"]
|
|
description = """
|
|
Identifies suspicious startup shell folder modifications to change the default Startup directory in order to bypass
|
|
detections monitoring file creation in the Windows Startup folder.
|
|
"""
|
|
from = "now-9m"
|
|
index = ["logs-endpoint.events.*"]
|
|
language = "eql"
|
|
license = "Elastic License v2"
|
|
name = "Suspicious Startup Shell Folder Modification"
|
|
note = """## Triage and analysis
|
|
|
|
### Investigating Suspicious Startup Shell Folder Modification
|
|
|
|
Techniques used within malware and by adversaries often leverage the Windows registry to store malicious programs for
|
|
persistence. Startup shell folders are often targeted as they are not as prevalent as normal Startup folder paths so this
|
|
behavior may evade existing AV/EDR solutions. These programs may also run with higher privileges which can be ideal for
|
|
an attacker.
|
|
|
|
#### Possible investigation steps
|
|
|
|
- Investigate the process execution chain (parent process tree).
|
|
- Review the source process and related file tied to the Windows Registry entry.
|
|
- Validate the activity is not related to planned patches, updates, network administrator activity or legitimate software
|
|
installations.
|
|
- Determine if activity is unique by validating if other machines in the same organization have similar entries.
|
|
- Retrieve the file and determine if it is malicious:
|
|
- Use a private sandboxed malware analysis system to perform analysis.
|
|
- Observe and collect information about the following activities:
|
|
- Attempts to contact external domains and addresses.
|
|
- File and registry access, modification, and creation activities.
|
|
- Service creation and launch activities.
|
|
- Scheduled tasks creation.
|
|
- Use the PowerShell Get-FileHash cmdlet to get the SHA-256 hash value of the file.
|
|
- Search for the existence and reputation of this file in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
|
|
|
|
### False positive analysis
|
|
|
|
- There is a high possibility of benign legitimate programs being added to shell folders. This activity could be based
|
|
on new software installations, patches, or other network administrator activity. Before entering further investigation,
|
|
it should be verified that this activity is not benign.
|
|
|
|
### Related rules
|
|
|
|
- Startup or Run Key Registry Modification - 97fc44d3-8dae-4019-ae83-298c3015600f
|
|
- Persistent Scripts in the Startup Directory - f7c4dc5a-a58d-491d-9f14-9b66507121c0
|
|
|
|
### Response and remediation
|
|
|
|
- Initiate the incident response process based on the outcome of the triage.
|
|
- Isolate the involved host to prevent further post-compromise behavior.
|
|
- Since this activity is considered post-exploitation behavior, it's important to understand how the behavior was first
|
|
initialized such as through a macro-enabled document that was attached in a phishing email. After understanding the source
|
|
of the attack, you can use this information to search for similar indicators on other machines in the same environment.
|
|
"""
|
|
risk_score = 73
|
|
rule_id = "c8b150f0-0164-475b-a75e-74b47800a9ff"
|
|
severity = "high"
|
|
tags = ["Elastic", "Host", "Windows", "Threat Detection", "Persistence"]
|
|
timestamp_override = "event.ingested"
|
|
type = "eql"
|
|
|
|
query = '''
|
|
registry where
|
|
registry.path : (
|
|
"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\User Shell Folders\\Common Startup",
|
|
"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Shell Folders\\Common Startup",
|
|
"HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\User Shell Folders\\Startup",
|
|
"HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Shell Folders\\Startup"
|
|
) and
|
|
registry.data.strings != null and
|
|
/* Normal Startup Folder Paths */
|
|
not registry.data.strings : (
|
|
"C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\Startup",
|
|
"%ProgramData%\\Microsoft\\Windows\\Start Menu\\Programs\\Startup",
|
|
"%USERPROFILE%\\AppData\\Roaming\\Microsoft\\Windows\\Start Menu\\Programs\\Startup",
|
|
"C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Windows\\Start Menu\\Programs\\Startup"
|
|
)
|
|
'''
|
|
|
|
|
|
[[rule.threat]]
|
|
framework = "MITRE ATT&CK"
|
|
[[rule.threat.technique]]
|
|
id = "T1547"
|
|
name = "Boot or Logon Autostart Execution"
|
|
reference = "https://attack.mitre.org/techniques/T1547/"
|
|
[[rule.threat.technique.subtechnique]]
|
|
id = "T1547.001"
|
|
name = "Registry Run Keys / Startup Folder"
|
|
reference = "https://attack.mitre.org/techniques/T1547/001/"
|
|
|
|
|
|
|
|
[rule.threat.tactic]
|
|
id = "TA0003"
|
|
name = "Persistence"
|
|
reference = "https://attack.mitre.org/tactics/TA0003/"
|