New

The executive guide to generative AI

Read more
About usPartnersSupport|Login
IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Network Connection via Compiled HTML File Network Connection via Registration Utility »
Elastic Docs ›Elastic Security Solution [7.12] ›Detections and alerts ›Prebuilt rule reference

Network Connection via MsXsl

edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Network Connection via MsXsl

edit

Identifies msxsl.exe making a network connection. This may indicate adversarial activity as msxsl.exe is often leveraged by adversaries to execute malicious scripts and evade detection.

Rule type: eql

Rule indices:

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

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
  • Host
  • Windows
  • Threat Detection
  • Defense Evasion

Version: 6 (version history)

Added (Elastic Stack release): 7.7.0

Last modified (Elastic Stack release): 7.12.0

Rule authors: Elastic

Rule license: Elastic License v2

Rule query

edit
sequence by process.entity_id [process where process.name :
"msxsl.exe" and event.type == "start"] [network where process.name :
"msxsl.exe" and not cidrmatch(destination.ip, "10.0.0.0/8",
"172.16.0.0/12", "192.168.0.0/16")]

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 6 (7.12.0 release)
  • Formatting only
Version 5 (7.11.0 release)
  • Formatting only
Version 4 (7.10.0 release)

  • Updated query, changed from:

    event.category:network and event.type:connection and
process.name:msxsl.exe and not destination.ip:(10.0.0.0/8 or
172.16.0.0/12 or 192.168.0.0/16)
Version 3 (7.9.1 release)
  • Formatting only
Version 2 (7.9.0 release)

  • Updated query, changed from:

    process.name:msxsl.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)
« Network Connection via Compiled HTML File Network Connection via Registration Utility »
Was this helpful?
Feedback