Techniques for digital forensics and incident response
Footprints

© Photo by Edoardo Busti on Unsplash
When it's too late to stop an attack, the next urgent task is to find out what happened and assess the damage.
Digital Forensics and Incident Response (DFIR) is the art of studying a potentially compromised system to understand the blast radius of an attack. In this article I will look at some of the DFIR steps a security analyst might take following an incident. I will also simulate a couple of attacks and then go through how an analyst might respond after a monitoring system raises an alarm about a potential attack. (See the box entitled "Resources and Tools" for more on the post-incident investigation environment.) A large part of this discussion was inspired by an excellent article by Craig Rowland [1].
For purposes of illustration, I will work with a live, running system, but keep in mind that a real forensic investigation would be more likely to make an exact copy of the compromised system and scrutinize it offline. If you work offline, the offline copy should be a block-for-block carbon copy of the compromised system that contains all the metadata and potentially even live processes (depending on how the copy was created). Many professional investigations will make multiple copies of the original in order to study the problem from multiple viewpoints and still retain the integrity of the original.
Digging Deeper – Attack #1
I will use the opening example in Rowland's excellent article for the first attack. The example involves what's called a bind shell. The more popular version of backdoor access into a remote system is called a reverse shell. A reverse shell causes the compromised system to phone home back to an attacker's computer. Reverse shells are easier to instantiate because, generally, outbound firewalling is much more attacker-friendly than inbound firewall rules. In other words, a process on the system that wants to communicate with the Internet can generally do so by default. Whereas inbound traffic is almost always limited to a select number of network-based services.
[...]
Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.

News
-
Linux Kernel 6.17 is Available
Linus Torvalds has announced that the latest kernel has been released with plenty of core improvements and even more hardware support.
-
Kali Linux 2025.3 Released with New Hacking Tools
If you're a Kali Linux fan, you'll be glad to know that the third release of this famous pen-testing distribution is now available with updates for key components.
-
Zorin OS 18 Beta Available for Testing
The latest release from the team behind Zorin OS is ready for public testing, and it includes plenty of improvements to make it more powerful, user-friendly, and productive.
-
Fedora Linux 43 Beta Now Available for Testing
Fedora Linux 43 Beta ships with Gnome 49 and KDE Plasma 6.4 (and other goodies).
-
USB4 Maintainer Leaves Intel
Michael Jamet, one of the primary maintainers of USB4 and Thunderbolt drivers, has left Intel, leaving a gaping hole for the Linux community to deal with.
-
Budgie 10.9.3 Now Available
The latest version of this elegant and configurable Linux desktop aligns with changes in Gnome 49.
-
KDE Linux Alpha Available for Daring Users
It's official, KDE Linux has arrived, but it's not quite ready for prime time.
-
AMD Initiates Graphics Driver Updates for Linux Kernel 6.18
This new AMD update focuses on power management, display handling, and hardware support for Radeon GPUs.
-
AerynOS Alpha Release Available
With a choice of several desktop environments, AerynOS 2025.08 is almost ready to be your next operating system.
-
AUR Repository Still Under DDoS Attack
Arch User Repository continues to be under a DDoS attack that has been going on for more than two weeks.