IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
Elastic Docs ›Elastic Security Solution [8.5] ›Detections and alerts ›Prebuilt rule reference
« Potential Command and Control via Internet Explorer Potential Credential Access via DCSync »

Potential Cookies Theft via Browser Debuggingedit

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

Rule indices:

  • auditbeat-*
  • winlogbeat-*
  • logs-endpoint.events.*
  • logs-windows.*

Severity: medium

Risk score: 47

Runs every: 5 minutes

Searches indices from: now-9m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 33

References:

Tags:

  • Elastic
  • Host
  • Linux
  • Windows
  • macOS
  • Threat Detection
  • Credential Access

Version: 100 (version history)

Added (Elastic Stack release): 7.12.0

Last modified (Elastic Stack release): 8.5.0

Rule authors: Elastic

Rule license: Elastic License v2

Potential false positivesedit

Developers performing browsers plugin or extension debugging.

Investigation guideedit












Rule queryedit








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"











Threat mappingedit




Framework: MITRE ATT&CKTM














Rule version historyedit










Version 100 (8.5.0 release)








    

  • 
Formatting only

    • 









Version 4 (8.4.0 release)








    

  • 

    Updated query, changed from:
    

    

    

    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"
    

    

    • 









Version 2 (8.2.0 release)








    

  • 
Formatting only

    • 


















« Potential Command and Control via Internet Explorer


Potential Credential Access via DCSync »