IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« Adversary Behavior - Detected - Elastic Endgame Agent Spoofing - Multiple Hosts Using Same Agent »

› › ›

Agent Spoofing - Mismatched Agent ID

edit

Agent Spoofing - Mismatched Agent ID

edit

Detects events which have a mismatch on the expected event agent ID. The status "agent_id_mismatch" occurs when the expected agent ID associated with the API key does not match the actual agent ID in an event. This could indicate attempts to spoof events in order to masquerade actual activity to evade detection.

Rule type: query

Rule indices:

logs-*
metrics-*
traces-*

Severity: high

Risk score: 73

Runs every: 5 minutes

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

Maximum alerts per execution: 100

Tags:

Elastic
Threat Detection
Defense Evasion

Version: 2 (version history)

Added (Elastic Stack release): 7.14.0

Last modified (Elastic Stack release): 8.1.0

Rule authors: Elastic

Rule license: Elastic License v2

Potential false positives

edit

This is meant to run only on datasources using Elastic Agent 7.14+ since versions prior to that will be missing the necessary field, resulting in false positives.

Rule query

edit

event.agent_id_status:agent_id_mismatch

Threat mapping

edit

Framework: MITRE ATT&CK^TM

Tactic:
- Name: Defense Evasion
- ID: TA0005
- Reference URL: https://attack.mitre.org/tactics/TA0005/
Technique:
- Name: Masquerading
- ID: T1036
- Reference URL: https://attack.mitre.org/techniques/T1036/

Rule version history

edit

Version 2 (8.1.0 release)

Formatting only

« Adversary Behavior - Detected - Elastic Endgame Agent Spoofing - Multiple Hosts Using Same Agent »