Network Connection via Signed Binary

edit

Binaries signed with trusted digital certificates can execute on Windows systems protected by digital signature validation. Adversaries may use these binaries to live off the land and execute malicious files that could bypass application allowlists and signature validation.

Rule type: query

Rule indices:

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

Severity: low

Risk score: 21

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
  • Windows

Version: 4 (version history)

Added (Elastic Stack release): 7.6.0

Last modified (Elastic Stack release): 7.9.1

Rule authors: Elastic

Rule license: Elastic License

Rule query

edit
event.category:network and event.type:connection and
process.name:(expand.exe or extrac.exe or ieexec.exe or makecab.exe)
and not destination.ip:(10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16)

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 4 (7.9.1 release)
  • Formatting only
Version 3 (7.9.0 release)
  • Updated query, changed from:

    process.name:(expand.exe or extrac.exe or ieexec.exe or makecab.exe)
    and event.action:"Network connection detected (rule: NetworkConnect)"
    and not destination.ip:(10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16)
Version 2 (7.7.0 release)
  • Updated query, changed from:

    (process.name:expand.exe or process.name:extrac.exe or
    process.name:ieexec.exe or process.name:makecab.exe) and
    event.action:"Network connection detected (rule: NetworkConnect)" and
    not destination.ip:10.0.0.0/8 and not destination.ip:172.16.0.0/12 and
    not destination.ip:192.168.0.0/16