Template -- File and Directory Discovery (recon commands)

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

Canonical sigma detection template for MITRE ATT&CK T1083 (File and Directory Discovery (recon commands)). Synthetic exemplar from the WinstonRedGuard threat-intel corpus -- no actor binding; review and bind to your environment before deployment.

title: Template -- File and Directory Discovery (recon commands)
id: 46df2d03-93bb-55e3-89f7-8b77ab9c657d
status: experimental
description: Canonical sigma detection template for MITRE ATT&CK T1083 (File and Directory Discovery (recon commands)). 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/T1083/
author: WinstonRedGuard -- sigma plugin canonical templates
date: '2026-05-21'
logsource:
  category: process_creation
  product: windows
detection:
  selection_discovery_command:
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \pwsh.exe
    CommandLine|contains:
    - dir /s
    - dir /a
    - tree /f
    - Get-ChildItem -Recurse
    - gci -recurse
  condition: selection_discovery_command
falsepositives:
- Backup pre-scans, on-demand antivirus scans and disk-usage tools, all of which enumerate recursively by design
- Interactive administrator and developer use of dir /s and Get-ChildItem -Recurse, which on a workstation is continuous rather than occasional
- Build and installer scripts walking a tree to compute a file list
level: medium
tags:
- attack.t1083
- wrg.template
- wrg.tactic.discovery

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

7d9ed2db-4b15-4fe9-b07a-6d2491d213dd

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