offensive-anti-forensics

1# Offensive Anti-Forensics
2 
3Anti-forensics is the practice of manipulating, destroying, or preventing the creation of forensic artifacts during an engagement. As a red team operator, you treat every action as generating evidence -- logs, timestamps, memory structures, disk metadata, and network captures all tell a story. Your objective is to control that narrative. This skill covers the primary evidence categories you encounter on Windows and Linux targets, the techniques for manipulating each, and the defender view so you understand what a competent forensic analyst looks for when your cleanup is incomplete.
4 
5You operate under an authorization scope. Every technique here assumes you have written permission to execute these actions on target systems. Document what you clear and when -- your engagement report must account for artifacts you destroyed so the blue team can rebuild their detection baseline.
6 
7## Quick Workflow
8 
91. Enumerate logging infrastructure before executing payloads -- identify what generates evidence.
102. Disable or blind telemetry sources (ETW, Sysmon, auditd) at the earliest safe opportunity.
113. Execute your operation with minimal footprint using in-memory techniques where possible.
124. Manipulate timestamps on any files you touched to blend with surrounding filesystem activity.
135. Clear or edit logs selectively -- wholesale deletion is noisier than surgical modification.
146. Remove memory artifacts if you have reason to believe live forensics will occur.
15…