Detection rules › Splunk

Windows C$ Share Access (EDR)

Group by
_time, host
Source
github.com/anvilogic-forge/armory

Windows systems have hidden network shares that are accessible only to administrators and provide the ability for remote file copy and other administrative functions. This Use case identifies when network shares C$, ADMIN$, and IPC$ have had an object call. Adversaries may use this technique in conjunction with administrator-level Valid Accounts to remotely access a networked system

MITRE ATT&CK coverage

References

Event coverage

Rule body yaml

id: '5709.13820'
title: Windows C$ Share Access
description: 'Windows systems have hidden network shares that are accessible only
  to administrators and provide the ability for remote file copy and other administrative
  functions. This Use case identifies when network shares C$, ADMIN$, and IPC$ have
  had an object call. Adversaries may use this technique in conjunction with administrator-level
  Valid Accounts to remotely access a networked system. -- Threat Actor Association:
  APT29, APT31, Blackmatter, Darkside, FIN8 (Syssphinx), OilRig, Volt Typhoon, Wizard
  Spider -- Software Association: Bazar, Black Basta, Clop, Conti, GhostShell, Hafnium,
  Qakbot, Ryuk, SamSam, Vice Society -- Atomics T1021.002 Test#1 Atomics T1021.002
  Test#2 Atomics T1021.002 Test#4'
logic_format: Splunk
logic: '`get_endpoint_data` `get_endpoint_data_edr` ((event_type IN ("childproc","netconn","proc"))
  OR (TERM(ProcessRollup2) OR Type=Process) OR TERM(DeviceProcessEvents)) AND ((event_simpleName="SmbClientShareOpenedEtw"
  OR TERM(SmbClientShareOpenedEtw)) OR (event_simpleName="SmbServerShareOpenedEtw"
  OR TERM(SmbServerShareOpenedEtw))) TERM(admin) | regex object="(?i)admin\$" | table
  _time, host, user signature_id, object, share_*, src_ip, relative_target_name |
  bin span=1s | stats values(*) as * by _time, host '
techniques:
- lateral-movement:remote services:smb/windows admin shares
technique_id:
- T1021.002
data_category:
- EDR Logs
references:
- https://support.malwarebytes.com/hc/en-us/articles/360038524714

Stages and Predicates

Stage 1: search

`get_endpoint_data` `get_endpoint_data_edr` ((event_type IN ("childproc","netconn","proc")) OR (TERM(ProcessRollup2) OR Type=Process) OR TERM(DeviceProcessEvents)) AND ((event_simpleName="SmbClientShareOpenedEtw" OR TERM(SmbClientShareOpenedEtw)) OR (event_simpleName="SmbServerShareOpenedEtw" OR TERM(SmbServerShareOpenedEtw))) TERM(admin)

Stage 2: regex

| regex object="(?i)admin\$"

Stage 3: table

| table _time, host, user signature_id, object, share_*, src_ip, relative_target_name

Stage 4: bucket

| bin span=1s

Stage 5: stats

| stats values(*) as * by _time, host

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
event_simpleNameeq
  • "SmbClientShareOpenedEtw"
  • "SmbServerShareOpenedEtw"
event_typein
  • "childproc"
  • "netconn"
  • "proc"
objectregex_match
  • "(?i)admin$"

Search terms

Bare-string tokens in the SPL search body. Splunk matches each token against _raw (the untyped raw event text) anywhere it appears, not against a specific field. These don't surface in the Indicators table because they aren't predicates on a known field.

StageTerm
1TERM
1ProcessRollup2
1TERM
1DeviceProcessEvents
1TERM
1SmbClientShareOpenedEtw
1TERM
1SmbServerShareOpenedEtw
1TERM
1admin