Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
KAPE collects and parses forensic artefacts from a live Windows system in minutes, producing a triage data set that answers most incident questions without a full disk image.

What Is KAPE?
KAPE, the Kroll Artifact Parser and Extractor, is a Windows triage tool written by Eric Zimmerman and distributed free by Kroll. It collects the specific files that hold forensic value from a running system, then runs parsers over them to produce readable output. A collection that would take hours by hand finishes in minutes, and the result is usually a few hundred megabytes rather than the several terabytes a full disk image would be.
It exists because the old model stopped scaling. Imaging one laptop is reasonable. Imaging the forty endpoints that an incident touched, several of them cloud virtual machines and some of them in another country, is not, and by the time the images arrive the question has usually moved on. Triage answers the urgent questions first, and full imaging is reserved for the systems that genuinely justify it.
KAPE separates collection from parsing, which is the design decision that makes it reliable.
Targets define which files to collect. A target is a list of paths and file masks, and compound targets group many together. The commonly used !SANS_Triage compound target gathers the standard evidence set in one pass. The important technical detail is that KAPE reads through raw disk access rather than the file system API, so it collects files that Windows holds locked, including the master file table, the USN journal, registry hives, and event logs on a running system.
What a triage collection contains, and what each part answers:
Modules run tools over the collected files. Most of them invoke Eric Zimmerman’s own parsers, producing CSV output ready for review in Timeline Explorer, with others calling Hayabusa for event log analysis or a hash utility for file identification. Because modules operate on collected copies rather than on the live system, parsing can be repeated with different tools later without going back to the endpoint.
In a real incident, KAPE is rarely run by hand on one machine. The practical patterns are to push it through the endpoint detection platform’s remote execution feature, deploy it by Group Policy or a configuration management tool, or run it from a share with output written to a central collection point. Collections from many hosts are then processed centrally and compared, which is how an analyst finds the one machine out of two hundred with an unexpected scheduled task.
Two operational cautions. First, running KAPE modifies the system, because any execution does: it creates prefetch entries and writes to the event log. Record what was run, when, and by whom, and include it in the chain of custody notes, so that the analyst’s own footprint is not later mistaken for the intruder’s. Second, memory is not collected by KAPE and is the most volatile evidence on the system. Capture it first with a dedicated tool if it matters, as described under memory forensics.
Triage collects known artefact locations. It does not recover deleted files from unallocated space, carve fragments from slack space, or capture anything hidden outside the paths a target describes. Where the matter is likely to reach court, where deliberate anti-forensic activity is suspected, or where the question is what a specific deleted file contained, a full image taken with FTK Imager and examined in Autopsy or a commercial suite remains the right approach.
The sensible sequence is triage first on everything in scope, then full imaging on the small number of systems the triage results point to. That order answers the business questions quickly while preserving the evidential option where it matters.
At Privia Security, our Digital Forensic Incident Response Services use estate-wide triage collection to scope an incident quickly before deciding where full acquisition is justified.
No, it changes when imaging is needed. Triage collects known artefact locations and answers most incident questions in minutes across many hosts. It does not recover deleted files from unallocated space or carve data from slack space. Collect triage data from everything in scope, then take full images of the small number of systems the triage results identify as significant.
Yes, and that is its main purpose. It reads through raw disk access rather than the file system API, so it retrieves files Windows holds locked, including the master file table, the USN journal, registry hives, and event logs. The system stays online, which matters when taking a production server down is not an option.
It leaves a footprint, as any execution on a live system does: prefetch entries, event log records, and file access times. That is acceptable in incident response provided it is documented. Record what was run, when, by whom, and from where, so the analyst’s own activity is never mistaken for the intruder’s during later examination.
Memory, which must be captured separately with a dedicated tool before anything else because it is the most volatile evidence present. Also deleted file content from unallocated space, carved fragments from slack space, and anything stored outside the paths the chosen targets describe. If deliberate anti-forensic activity is suspected, triage alone is not sufficient.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.