Identifies the execution of a Chromium based browser with the debugging process argument, which may indicate an attempt to steal authentication cookies. An adversary may steal web application or service session cookies and use them to gain access web applications or Internet services as an authenticated user without needing credentials.
Rule type: eql
Risk score: 47
Runs every: 5 minutes
Maximum alerts per execution: 33
- Threat Detection
- Credential Access
Version: 2 (version history)
Added (Elastic Stack release): 7.12.0
Last modified (Elastic Stack release): 8.2.0
Rule authors: Elastic
Rule license: Elastic License v2
Developers performing browsers plugin or extension debugging.
## Config If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2, events will not define `event.ingested` and default fallback for EQL rules was not added until 8.2, so you will need to add a custom pipeline to populate `event.ingested` to @timestamp for this rule to work.
process where event.type in ("start", "process_started", "info") and process.name in ( "Microsoft Edge", "chrome.exe", "Google Chrome", "google- chrome-stable", "google-chrome-beta", "google-chrome", "msedge.exe") and process.args : ("-- remote-debugging-port=*", "--remote-debugging- targets=*", "--remote-debugging-pipe=*") and process.args : "--user-data-dir=*" and not process.args:"--remote- debugging-port=0"
Framework: MITRE ATT&CKTM
- Version 2 (8.2.0 release)
- Formatting only