Template -- Administrative-share file transfer through copy tooling

SIGMA detection rule by WinstonRedGuard -- sigma plugin canonical templates · Unknown

Canonical Sigma detection template for MITRE ATT&CK T1570 (Lateral Tool Transfer). Detects common copy utilities targeting an administrative SMB share. Synthetic exemplar from the WinstonRedGuard threat-intel corpus -- no actor binding; review and bind to your environment before deployment.

title: Template -- Administrative-share file transfer through copy tooling
id: 08cdefb6-346c-579f-b94d-4754d4ec6c44
status: experimental
description: >-
  Canonical Sigma detection template for MITRE ATT&CK T1570 (Lateral Tool
  Transfer). Detects common copy utilities targeting an administrative SMB
  share. Synthetic exemplar from the WinstonRedGuard threat-intel corpus -- no
  actor binding; review and bind to your environment before deployment.
references:
- https://attack.mitre.org/techniques/T1570/
author: WinstonRedGuard -- sigma plugin canonical templates
date: '2026-09-16'
logsource:
  category: process_creation
  product: windows
detection:
  selection_copy_tool:
    Image|endswith:
    - '\copy.exe'
    - '\xcopy.exe'
    - '\robocopy.exe'
  selection_admin_share:
    CommandLine|contains:
    - '\ADMIN$\'
    - '\C$\'
  condition: selection_copy_tool and selection_admin_share
falsepositives:
- Approved software deployment, backup, or endpoint-management distribution
- Administrator file transfer during an authorized incident response
level: medium
tags:
- attack.t1570
- wrg.template
- wrg.tactic.lateral_movement

[[ currentRule.title && currentRule.title.length > 60 ? currentRule.title.slice(0, 60) + '…' : currentRule.title ]]

c81f6ff0-c9f5-4e1a-8ddb-8b133653ab65

Propose edits, view related rules, and engage with the community through comments.

Executable code, not a declarative rule

This submission is arbitrary [[ currentRule.format ? currentRule.format.toUpperCase() : '' ]] code, not a declarative detection rule — review it as you would any script before running it, and note that it cannot be safely aggregated or auto-executed alongside YARA/Sigma/Suricata/CRS rules.

Rejected pattern present

[[ reason ]]

What does this mean?

Format & documentation suggestions

Not a security issue — this rule is valid and was accepted as-is. These are optional fields/conventions its own format recommends, mainly affecting its quality score and how well it documents itself for other reviewers.

[[ reason ]]

What do these messages mean?

[[ currentRule.title && currentRule.title.length > 60 ? currentRule.title.slice(0, 60) + '…' : currentRule.title ]]

[[ currentRule.title ]]

Community Discussion