The following analytic identifies suspicious PowerShell command to allow inbound traffic inbound to a specific local port within the public profile. This technique was seen in some attacker want to have a remote access to a machine by allowing the traffic in firewall rule.
- Type: TTP
- Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Datamodel: Endpoint
- Last Updated: 2021-05-19
- Author: Teoderick Contreras, Splunk
- ID: a5d85486-b89c-11eb-8267-acde48001122
|T1021.001||Remote Desktop Protocol||Lateral Movement|
`powershell` EventCode=4104 Message = "*firewall*" Message = "*Inbound*" Message = "*Allow*" Message = "*-LocalPort*" | stats count min(_time) as firstTime max(_time) as lastTime by EventCode Message ComputerName User | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `allow_inbound_traffic_in_firewall_rule_filter`
Associated Analytic Story
How To Implement
To successfully implement this search, you need to be ingesting logs with the powershell logs from your endpoints. make sure you enable needed registry to monitor this event.
Kill Chain Phase
Known False Positives
administrator may allow inbound traffic in certain network or machine.
|3.0||10||30||Suspicious firewall modification detected on endpoint $ComputerName$ by user $user$.|
source | version: 1