Investigation playbook · network
Network alert playbook
For firewall, proxy, DNS and VPN alerts: scans, beacons, connections to bad infrastructure.
Answer these before you decide
- Which internal host, and what is it (workstation, server, scanner)?
- Lookup the remote address or domain: reputation, age, hosting, CDN?
- Is it a pattern: beaconing at fixed intervals, many hosts, data volume out of proportion?
- Is there an authorised activity (scanner, backup, CDN) in the handover or change records?
- Did the firewall allow or block it?
When it is an incident: first containment
Block the IP or domain for confirmed C2; isolate the host if it is compromised.
A playbook says what to check. Whether this alert is real is what the logs tell you.
Events to read
- Event ID 4624: An account was successfully logged on.
- Event ID 4625: An account failed to log on.
- Event ID 5145: A network share object was checked to see whether client can be granted desired access.
- Sysmon event 11: FileCreate
ATT&CK techniques these alerts carry
- T1021.001 Remote Services: Remote Desktop Protocol
- T1046 Network Service Discovery
- T1071.001 Application Layer Protocol: Web Protocols
- T1071.004 Application Layer Protocol: DNS
- T1110.001 Brute Force: Password Guessing
- T1133 External Remote Services
- T1190 Exploit Public-Facing Application
- T1195.002 Supply Chain Compromise: Compromise Software Supply Chain
- T1204.002 User Execution: Malicious File
- T1567.002 Exfiltration Over Web Service: Exfiltration to Cloud Storage
Practise it
- Exploit attempts on the VPN appliance: did one get in? Advanced · Network
- SSH switched on for a production hypervisor Advanced · Network
- VPN account brute forced, admin access to file server Advanced · Network
- Web shell on the public web server, pivot to SQL Advanced · Network
Alerts in the shift that use this playbook
- App update pulled from an unexpected host
- Bulk upload to personal cloud storage
- High-volume DNS TXT queries to one domain
- Internal port scan
- Outbound to flagged IP
- RDP logon from the internet after repeated failures
- SQL injection blocked by WAF
- Suspicious long DNS query