Network Sniffing
https://attack.mitre.org/techniques/T1040/
Last updated
Was this helpful?
https://attack.mitre.org/techniques/T1040/
Last updated
Was this helpful?
ATT&CK ID:
Required Permissions: Network interface access and packet capture driver
Description
Adversaries may sniff network traffic to capture information about an environment, including authentication material passed over the network. Network sniffing refers to using the network interface on a system to monitor or capture information sent over a wired or wireless connection. An adversary may place a network interface into promiscuous mode to passively access data in transit over the network, or use span ports to capture a larger amount of data.
Data captured via this technique may include user credentials, especially those sent over an insecure, unencrypted protocol. Techniques for name service resolution poisoning, such as LLMNR/NBT-NS Poisoning and SMB Relay, can also be used to capture credentials to websites, proxies, and internal systems by redirecting traffic to an adversary.
Network sniffing may also reveal configuration details, such as running services, version numbers, and other network characteristics (e.g. IP addresses, hostnames, VLAN IDs) necessary for subsequent Lateral Movement and/or Defense Evasion activities.
The empire module essentially runs the same command as the Netsh binary shown further below on this page.
After capture has been stopped the capture.etl file can be converted to a PCAP with etl2pcapng (Windows required).
After converting to PCAP we are able to view the results in Wireshark. Whilst we did not capture any credentials we have discovered \\Srv01\Share through SMB analysis.
After capture has been stopped the trace.etl file can be converted to a PCAP with etl2pcapng (Windows required).
Or the .etl file can be opened directly in event viewer.
Github:
Github:
