Suspicious Web Browser Sensitive File Access
Identifies the access or file open of web browser sensitive files by an untrusted/unsigned process or osascript. Adversaries may acquire credentials from web browsers by reading files specific to the target browser.
Elastic rule (View on GitHub)
1[metadata]
2creation_date = "2020/01/04"
3integration = ["endpoint"]
4maturity = "production"
5min_stack_comments = "New fields added: file_access_events, process.Ext.effective_parent"
6min_stack_version = "8.11.0"
7updated_date = "2024/08/28"
8
9[rule]
10author = ["Elastic"]
11description = """
12Identifies the access or file open of web browser sensitive files by an untrusted/unsigned process or osascript.
13Adversaries may acquire credentials from web browsers by reading files specific to the target browser.
14"""
15from = "now-9m"
16index = ["logs-endpoint.events.file-*"]
17language = "eql"
18license = "Elastic License v2"
19name = "Suspicious Web Browser Sensitive File Access"
20references = ["https://securelist.com/calisto-trojan-for-macos/86543/"]
21risk_score = 73
22rule_id = "20457e4f-d1de-4b92-ae69-142e27a4342a"
23setup = """## Setup
24
25This rule requires data coming in from Elastic Defend.
26
27### Elastic Defend Integration Setup
28Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
29
30#### Prerequisite Requirements:
31- Fleet is required for Elastic Defend.
32- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
33
34#### The following steps should be executed in order to add the Elastic Defend integration on a macOS System:
35- Go to the Kibana home page and click "Add integrations".
36- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
37- Click "Add Elastic Defend".
38- Configure the integration name and optionally add a description.
39- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
40- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. [Helper guide](https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html).
41- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
42- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
43For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/current/agent-policy.html).
44- Click "Save and Continue".
45- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
46For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
47"""
48severity = "high"
49tags = ["Domain: Endpoint", "OS: macOS", "Use Case: Threat Detection", "Tactic: Credential Access", "Data Source: Elastic Defend"]
50timestamp_override = "event.ingested"
51type = "eql"
52
53query = '''
54file where event.action == "open" and host.os.type == "macos" and process.executable != null and
55 file.name : ("cookies.sqlite",
56 "key?.db",
57 "logins.json",
58 "Cookies",
59 "Cookies.binarycookies",
60 "Login Data") and
61 ((process.code_signature.trusted == false or process.code_signature.exists == false) or process.name : "osascript") and
62 not process.code_signature.signing_id : "org.mozilla.firefox" and
63 not Effective_process.executable : "/Library/Elastic/Endpoint/elastic-endpoint.app/Contents/MacOS/elastic-endpoint"
64'''
65
66
67[[rule.threat]]
68framework = "MITRE ATT&CK"
69[[rule.threat.technique]]
70id = "T1539"
71name = "Steal Web Session Cookie"
72reference = "https://attack.mitre.org/techniques/T1539/"
73
74[[rule.threat.technique]]
75id = "T1555"
76name = "Credentials from Password Stores"
77reference = "https://attack.mitre.org/techniques/T1555/"
78[[rule.threat.technique.subtechnique]]
79id = "T1555.003"
80name = "Credentials from Web Browsers"
81reference = "https://attack.mitre.org/techniques/T1555/003/"
82
83
84
85[rule.threat.tactic]
86id = "TA0006"
87name = "Credential Access"
88reference = "https://attack.mitre.org/tactics/TA0006/"
References
Related rules
- Access to Keychain Credentials Directories
- Dumping Account Hashes via Built-In Commands
- Dumping of Keychain Content via Security Command
- Kerberos Cached Credentials Dumping
- Keychain Password Retrieval via Command Line