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