Windows Security: Network Access to protected_storage (IPC)

Flags Windows network share access to protected_storage through IPC from Security event 5145.

FreeReviewedSigma · High · v2
Product
windows
Service
security
Author
Roberto Rodriguez @Cyb3rWard0g (SigmaHQ), DRL 1.1
Published
2019-08-10
Updated
2026-07-31

ATT&CK techniques

Lateral Movement
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags Windows Security event 5145 where a client accesses the protected_storage resource via an IPC share path. Attackers may use protected storage access to facilitate credential and key material theft or lateral movement by reaching sensitive backups on domain systems. The detection relies on event-based SMB/Share access telemetry, including ShareName content containing IPC and the RelativeTargetName matching protected_storage.

Related detections9 linkedT1021.002 — drag to rearrange
Malicious NetExec SMB Enumeration Execution (via process_creation)
Malicious WMIexec Style Command Output Redirection to Local Admin Share
Malicious Cobalt Strike Default Named Pipe Activity
Suspicious PsExec Service Launching Encoded PowerShell Payload
Suspicious Impacket Style Command Execution with ADMIN Share Output Redirect
Suspicious Active Directory Reconnaissance via In-Memory Offensive PowerShell (via ps_script)
Suspicious NetExec Post-Exploitation Tool Execution via nxc (via process_creation)
Suspicious SMB Admin Share Mapping for Lateral Tool Transfer (via process_creation)
Suspicious Impacket Remote Execution Tool Usage via process_creation
Windows Security: Network Access to protected_storage (IPC)
Pivot detection · T1021.002 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.