CyberKit

Network Connection Artifacts

Also called Socket Objects, In-Memory Connections.

Active and recent network endpoints recovered from kernel memory.

What it is

The kernel structures that track sockets and TCP/UDP endpoints, recording local and remote addresses, ports, state, and the owning process. Memory analysis recovers these to reconstruct a host's network activity.

Why it matters

These artifacts tie a suspicious remote address to the exact process that owned the connection, linking network indicators to a process in memory, including connections that closed before any flow logging caught them. They are central to identifying command-and-control from a capture.

In practice

Recovering a connection object that mapped a beaconing remote address back to an injected thread inside an otherwise trusted process.

What to look for

  • Connections owned by processes that should not talk to the network.
  • Listening sockets on unusual ports.
  • Recently closed connections still in memory.

Common mistake

Trusting netstat on the live host. A rootkit can hide connections from it.

Use it in CyberKit

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Volatility 3 Open source

    A widely used open source framework for analyzing memory images with plugins. Our notes.

  • Velociraptor Open source

    Can collect memory and query live process memory across many hosts. Our notes.

  • CrowdStrike Falcon Commercial

    EDR agents watch memory activity on the host, such as injection and unbacked code.

Read next

Sources