Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Anti-forensic techniques are the methods attackers use to destroy, falsify, or hide the evidence an investigation depends on, from clearing event logs to timestomping files and attacking analysis tools.

What Are Anti-Forensic Techniques?
Anti-forensics is everything an intruder does to make the investigation that follows harder. Some of it is deliberate and sophisticated; much of it is ordinary operational hygiene on the attacker’s side, such as deleting a tool after use. The effect is the same: the record an examiner relies on is incomplete, misleading, or absent, and the organisation ends up paying for a longer engagement with a weaker conclusion.
Clearing Windows event logs remains the most common move. It is also self-defeating, because the act of clearing writes event ID 1102 to the Security log and event ID 104 to System or Application. More careful tooling removes individual records instead: the DanderSpritz framework leaked in 2017 included a module that could excise selected entries from an EVTX file, which leaves no 1102 but does leave gaps in the sequential record identifiers. Other variations kill the event log service threads so that nothing is written in the first place, delete the USN change journal with fsutil usn deletejournal, or disable Prefetch through the registry so that execution artefacts stop being created.
On Linux the equivalents are truncating /var/log/wtmp, unsetting the shell history file, and selectively editing auth.log. Systemd journals can be sealed with Forward Secure Sealing, which does not stop deletion but makes tampering detectable.
Timestomping rewrites file timestamps so that a web shell appears to date from the original installation of the application. On NTFS it is usually only partly successful, because the $STANDARD_INFORMATION attribute is trivially writable while the $FILE_NAME attribute in the directory index is not updated by the same API calls. A file whose creation time in one attribute precedes the other by years is a strong signal, which is why master file table analysis is a routine part of web shell hunts. Nanosecond fields set to zero are another giveaway, since genuine Windows timestamps rarely end in round numbers.
Concealment ranges from the mundane to the elaborate. NTFS alternate data streams attach content to an innocuous file and do not show in a directory listing. Steganography buries payloads in images and audio. Encrypted containers, including hidden volumes designed to give plausible deniability, keep data unreadable even once it has been found, and detecting encrypted containers is a specialist task in itself. Fileless intrusions avoid the disk altogether, holding payloads in memory or in registry values so that there is nothing to carve once the host reboots.
A smaller class of technique targets the investigation directly. Malware checks for virtual machines, debuggers, and sandbox artefacts and behaves innocently when it finds them. Archive bombs and deliberately corrupted file headers crash parsers. Enormous sparse files inflate acquisition times. None of these is common in routine intrusions, but they appear in targeted operations where the attacker expects scrutiny.
The answer is not a clever counter-tool; it is making the evidence live somewhere the attacker cannot reach. Forward event logs to a collector or SIEM in near real time, so clearing the local log destroys only the copy. Write cloud audit trails to immutable storage with object lock. Deploy Sysmon or equivalent telemetry so that process creation, file deletion, and raw disk access are recorded independently of the application logs. Keep endpoint detection data server-side rather than on the endpoint. The NCSC’s guidance on mitigating malware and ransomware makes the same point about backups: anything an administrator can delete, an intruder with administrator rights can delete too.
Then look for the absence. Record identifier gaps, a Security log that starts on the day of the incident, a Prefetch folder with twelve entries on a three-year-old workstation, a timestamp that sits outside the window the file system journal supports — each one is an artefact of the clean-up rather than of the attack, and each one is worth more than the evidence it replaced. At Privia Security, we treat those anomalies as findings in their own right during investigation and incident response services.
Yes, in two ways. Clearing the Security log writes event ID 1102, and clearing System or Application writes event ID 104, so the act itself is logged. If records are removed selectively instead, the remaining entries show gaps in their sequential record identifiers. A forwarded copy on a collector or SIEM is the most reliable check, because it is written before the local log is touched.
Often, though not always. NTFS stores timestamps in two places, and many tools only alter the easily writable set, leaving a discrepancy between them. Nanosecond values of exactly zero, a creation time earlier than the file system journal supports, and a file that is newer than its parent directory index entry all point the same way. Combine the master file table, the USN journal, and the log file for confidence.
Not when a business deploys it. The distinction is intent: encryption used to protect data at rest is a security control, while a hidden volume created to defeat a lawful examination is an anti-forensic measure. Investigators treat them differently, although the practical obstacle is identical, which is why acquisition should happen on a running system wherever the keys are still in memory.
Off-host logging. Once event data leaves the endpoint within seconds, an attacker who later gains administrator rights can destroy only the local copy. Combine forwarding with immutable storage for cloud audit trails and a retention period that outlasts typical dwell time, and most clean-up attempts become an indicator rather than an obstacle.
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.