let threshold = 1000;
Infoblox
| where ProcessName =~ "dhcpd" and Log_Type =~ "DHCPREQUEST"
| summarize count() by SrcIpAddr, bin(TimeGenerated,5m)
| where count_ > threshold
| join kind=inner (Infoblox
| where ProcessName =~ "dhcpd" and Log_Type =~ "DHCPREQUEST"
) on SrcIpAddr
query: |
let threshold = 1000;
Infoblox
| where ProcessName =~ "dhcpd" and Log_Type =~ "DHCPREQUEST"
| summarize count() by SrcIpAddr, bin(TimeGenerated,5m)
| where count_ > threshold
| join kind=inner (Infoblox
| where ProcessName =~ "dhcpd" and Log_Type =~ "DHCPREQUEST"
) on SrcIpAddr
entityMappings:
- fieldMappings:
- identifier: Address
columnName: SrcIpAddr
entityType: IP
triggerOperator: gt
description: |
'This creates an incident in the event that an excessive amount of DHCPREQUEST have been recieved by a DHCP Server and could potentially be an indication of a DHCP Starvation Attack.'
tactics:
- InitialAccess
severity: Medium
queryFrequency: 1h
kind: Scheduled
name: Potential DHCP Starvation Attack
triggerThreshold: 0
status: Available
id: 57e56fc9-417a-4f41-a579-5475aea7b8ce
requiredDataConnectors:
- connectorId: SyslogAma
datatypes:
- Syslog
relevantTechniques:
- T1200
version: 1.0.5
OriginalUri: https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/Infoblox NIOS/Analytic Rules/PotentialDHCPStarvationAttack.yaml
queryPeriod: 1h