This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.
« Conhost Spawned By Suspicious Parent Process Third-party Backup Files Deleted via Unexpected Process »
Elastic Docs ›Elastic Security Solution [8.16] ›Downloadable rule update v1.0.2

Execution via MSSQL xp_cmdshell Stored Procedure

edit

Execution via MSSQL xp_cmdshell Stored Procedure

edit

Identifies execution using the MSSQL stored procedure xp_cmdshell. Malicious users may attempt to elevate their privileges by using xp_cmdshell, which is disabled by default; thus, it’s important to review the context of its use.

Rule type: eql

Rule indices:

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

Severity: high

Risk score: 73

Runs every: 5m

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

Maximum alerts per execution: 100

References: None

Tags:

  • Elastic
  • Host
  • Windows
  • Threat Detection
  • Execution

Version: 5

Rule authors:

  • Elastic

Rule license: Elastic License v2

Investigation guide

edit
## 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.

Rule query

edit
process where event.type in ("start", "process_started") and
  process.name : "cmd.exe" and process.parent.name : "sqlservr.exe"

Framework: MITRE ATT&CKTM

« Conhost Spawned By Suspicious Parent Process Third-party Backup Files Deleted via Unexpected Process »