Detection rules › Sigma

First Time Seen Remote Named Pipe

Severity
high
Author
Samir Bousseaden
Source
upstream

This detection excludes known namped pipes accessible remotely and notify on newly observed ones, may help to detect lateral movement and remote exec using named pipes

MITRE ATT&CK coverage

TacticTechniques
Lateral MovementT1021.002 Remote Services: SMB/Windows Admin Shares

Event coverage

ProviderEvent IDTitle
Security-Auditing5145A network share object was checked to see whether client can be granted desired access.

Stages and Predicates

Stage 1: selection1

ShareName: '\\\\\*\\IPC$'

Stage 2: not false_positives

RelativeTargetName: [HydraLsPipe, LSM_API_service, MsFteWds, TermSrv_API_service, atsvc, browser, eventlog, lsarpc, lsass, netdfs, netlogon, ntsvcs, protected_storage, samr, spoolss, 'sql\query', srvsvc, svcctl, winreg, wkssvc]

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

FieldKindValues
RelativeTargetNameeq
  • HydraLsPipe
  • LSM_API_service
  • MsFteWds
  • TermSrv_API_service
  • atsvc corpus 2 (sigma 2)
  • browser
  • eventlog
  • lsarpc corpus 3 (sigma 2, splunk 1)
  • lsass
  • netdfs
  • netlogon
  • ntsvcs
  • protected_storage corpus 2 (sigma 2)
  • samr
  • spoolss corpus 2 (sigma 2)
  • sql\query
  • srvsvc
  • svcctl corpus 2 (sigma 2)
  • winreg
  • wkssvc
ShareNameeq
  • \\\\\*\\IPC$ corpus 6 (sigma 6)

Neighbors

Stricter alternatives (narrower than this rule)

The rules below may be useful if you find the current rule is too noisy / lacks specificity.

Broader alternatives (more inclusive than this rule)

These rules match a superset of what this rule catches. They cover the same events plus more. Use them if you want wider coverage and can absorb more false positives.