Per the order-of-volatility principle used in incident response, the most ephemeral evidence must be preserved before it changes or disappears. Netstat output reflects the server's currently active network connections and sessions, which are live, in-memory state that is destroyed the moment the server is taken off the network. Because the analyst's very next action is to disconnect the server from the network, this connection data must be captured first, before that state is irrecoverably lost. ShellBags and the hard disk are non-volatile, disk-resident artifacts that remain available for later imaging and analysis even after the server is disconnected, and the ARP cache, while volatile, does not depend directly on active network connectivity the way netstat's session data does, making it less time-critical in this specific scenario.
Community Discussion