Anti-Forensics Field Manual

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Alternate Data Stream Abuse ======

===== Definition =====
Alternate Data Stream Abuse is an anti-forensics-related concept analysts may encounter when files, metadata, storage remnants, or recovery results do not behave as a simple report wants them to behave.
In a forensic report, alternate data stream abuse should be treated as a source of evidence and uncertainty, not as a shortcut to intent. The useful question is what the record supports, what it does not support, and what another source says when asked the same question.

===== Background =====
Anti-forensics work is mostly disciplined suspicion. Sometimes the data was deliberately removed. Sometimes the drive did normal drive things. Sometimes the examiner is staring at unallocated space like it owes him a confession.
Good analysis keeps the artifact in its lane: useful, limited, and not allowed to perform intent for the room. A wiped-looking area should make the analyst careful, not poetic.

===== Technical Description =====
The review compares recovered data, deletion artifacts, allocation state, metadata changes, tool output, storage media behavior, and ordinary explanations.
Version, platform, retention, and collection scope should be documented before the artifact is promoted to a finding.

===== Forensic Relevance =====
  * **Recovery analysis:** It can explain why data was recovered, missed, corrupted, or only partially reconstructed.
  * **User activity review:** It may support account or profile context, but only when independent artifacts point the same direction.
  * **Contradiction testing:** It is useful for finding places where logs, metadata, storage behavior, or accounts disagree.
  * **Reporting decisions:** It helps decide how narrow the finding should be when alternate data stream abuse looks interesting but not conclusive.
  * **Timeline reconstruction:** Alternate Data Stream Abuse can help place activity in sequence when the time source and collection conditions are understood.

===== Evidence Sources =====
^ Evidence source ^ What it may show ^ Reliability limits ^ What it cannot prove alone ^
| Deletion and recovery traces | May show removed files, failed carving, overwritten areas, or surviving fragments. | Recovery depends on media, timing, fragmentation, and tool limits. | Does not independently prove intentional destruction. |
| File-system metadata | May show rename, move, deletion, timestamp, or allocation changes. | Can be stale, reused, or changed by normal operations. | Does not prove motive. |
| Storage behavior | May explain recovery limits, especially with SSD TRIM and wear leveling. | Often sits below application logs. | Does not identify a user. |
| Corroborating logs | May support timing and account context. | Can be missing for ordinary reasons. | Do not turn suspicion into proof alone. |

===== Interpretation Limits =====
The most common error is treating alternate data stream abuse as proof of motive. It may support a technical event, a sequence, or a contradiction, but motive needs stronger ground.
Another bad leap is treating absence as intent. Missing data can come from retention, configuration, collection scope, sync behavior, overwriting, media behavior, or ordinary use.
A tool result should be described as a parsed or recovered record, not as the tool's opinion about what happened. Tools surface evidence; they do not understand it.
Unallocated space can be empty because of wiping, storage behavior, or the examiner arriving after the useful bytes left town.

===== Common Misinterpretations =====
  * Treating empty unallocated space as proof of deliberate wiping.
  * Treating secure deletion tool presence as proof of tool use.
  * Treating tool use as proof of targeted evidence destruction.
  * Ignoring media behavior because deliberate wiping makes a cleaner paragraph.
  * Treating alternate data stream abuse as proof that a specific user acted, when the artifact only supports system or account context.

===== Example Scenario =====
A responder notices deletion and recovery traces that appear to line up with a disputed timeline.
The record may be meaningful, but it has to be compared with file-system metadata before the report gets confident.
The careful next step is to normalize the time source, compare independent artifacts, and write the finding as support rather than proof.

===== Analysis Workflow =====
  - Define the question before opening another parser: what should Alternate Data Stream Abuse help answer?
  - Preserve the source evidence and document how the deletion and recovery traces were collected.
  - Record tool versions, input paths, output paths, time settings, and errors.
  - Identify observed facts before writing any interpretation.
  - Normalize time sources and document timezone, clock drift, and collection-time effects.
  - Compare at least two independent artifact families before raising confidence.
  - Consider benign explanations, automated behavior, retention, sync, and storage-device behavior.
  - Write conclusions proportionally: observed fact first, inference second, uncertainty always visible.

===== Reporting Guidance =====
Reporting on alternate data stream abuse should be precise enough that another analyst can retrace the claim without inheriting the original examiner's confidence.
Avoid wording that converts possibility into intent. The report should not say a user deliberately deleted, hid, wiped, or tampered with evidence unless the evidence actually supports that conclusion.
Report-ready wording:
  * The available deletion and recovery traces are consistent with activity related to alternate data stream abuse, but they do not independently establish motive or user intent.
  * Recovery was limited under the examined conditions; additional corroboration would be required before concluding deliberate destruction.
  * The finding should be read with the collection scope, time-source limits, and alternate explanations described in this report.

===== Confidence and Reliability =====
^ Confidence level ^ What it looks like for this topic ^ How to report it ^
| Low | Deletion and recovery traces exist, but collection scope, time source, or surrounding context is limited. | State the observation and keep interpretation narrow. |
| Moderate | Deletion and recovery traces align with File-system metadata, but attribution or intent remains unresolved. | Say the artifacts support the finding, not that they prove it. |
| High | Multiple independent sources agree on sequence, source system, account context, and collection conditions. | Use stronger language, but still separate observed facts from inference. |

===== Related Concepts =====
  * [[wiki:anti_forensics:detection:anti_forensic_file_wiping|Anti-Forensic File Wiping]] - Often appears nearby in reviews of the same system or behavior.
  * [[wiki:anti_forensics:detection:anti_forensics|Anti-Forensics]] - Compare this concept when testing sequence and corroboration.
  * [[wiki:anti_forensics:detection:artifact_deletion|Artifact Deletion]] - Useful when checking whether another artifact supports the same interpretation.
  * [[wiki:anti_forensics:detection:artifact_gaps|Artifact Gaps]] - Useful when checking whether another artifact supports the same interpretation.
  * [[wiki:anti_forensics:detection:benign_explanations_in_anti_forensics|Benign Explanations in Anti-Forensics]] - Compare this concept when testing sequence and corroboration.
  * [[wiki:anti_forensics:detection:cleanup_utility_artifacts|Cleanup Utility Artifacts]] - Compare this concept when testing sequence and corroboration.

===== Tools =====
  * [[https://www.autopsy.com/|Autopsy]] - Case review, file-system browsing, timelines, term search, and recovered artifact review.
  * [[https://www.sleuthkit.org/sleuthkit/|The Sleuth Kit]] - Command-line file-system analysis and evidence inspection.
  * [[https://github.com/log2timeline/plaso|Plaso]] - Timeline extraction and normalization across many artifact types.
  * [[https://github.com/google/timesketch|Timesketch]] - Collaborative timeline analysis and event tagging.
  * [[https://www.cgsecurity.org/|PhotoRec and TestDisk]] - File recovery and partition recovery utilities.
  * [[https://foremost.sourceforge.net/|Foremost]] - File carving by headers, footers, and simple signatures.
  * [[https://www.exterro.com/ftk-product-downloads|FTK Imager]] - Forensic imaging, preview, and export workflows.
  * [[https://guymager.sourceforge.io/|Guymager]] - Linux forensic imaging with hashing and acquisition logs.
  * [[https://sourceforge.net/projects/dc3dd/|dc3dd]] - Disk imaging and hashing utility.
  * [[https://www.gnu.org/software/ddrescue/|GNU ddrescue]] - Imaging damaged media while preserving recovery logs.
  * [[wiki:tools:start|Forensic Tools]] - Full tool directory for the wiki.

===== Limitations of Tools =====
Tools parse, surface, and organize evidence. They do not create conclusions.
Parser output can be affected by version differences, unsupported formats, corrupted records, timezone handling, partial collection, and storage behavior outside the tool's view.
When a tool produces a strong-looking result, validate it against another tool or source where the stakes justify it. A parser can recover a fragment; it cannot tell you whether the fragment deserves a paragraph in the report.

===== References and Further Reading =====
  * [[https://csrc.nist.gov/publications/detail/sp/800-86/final|NIST SP 800-86]] - Forensic and incident response handling guidance.
  * [[https://www.forensicfocus.com/articles/countering-anti-forensic-efforts-part-1/|Forensic Focus: Countering Anti-Forensic Efforts]] - Defensive anti-forensics discussion.
  * [[https://www.forensicfocus.com/articles/browser-anti-forensics/|Forensic Focus: Browser Anti Forensics]] - Browser anti-forensics context.
  * [[https://learn.microsoft.com/en-us/windows-server/storage/file-server/ntfs-overview|Microsoft NTFS overview]] - NTFS technical reference.
  * [[https://www.sleuthkit.org/sleuthkit/docs.php|The Sleuth Kit documentation]] - File-system analysis documentation.

===== See Also =====
  * [[wiki:anti_forensics:detection:start|Detection]]
  * [[wiki:anti_forensics:detection:anti_forensic_file_wiping|Anti-Forensic File Wiping]]
  * [[wiki:anti_forensics:detection:anti_forensics|Anti-Forensics]]
  * [[wiki:anti_forensics:detection:artifact_deletion|Artifact Deletion]]
  * [[wiki:anti_forensics:detection:artifact_gaps|Artifact Gaps]]
  * [[wiki:anti_forensics:detection:benign_explanations_in_anti_forensics|Benign Explanations in Anti-Forensics]]
  * [[wiki:anti_forensics:detection:cleanup_utility_artifacts|Cleanup Utility Artifacts]]
  * [[wiki:anti_forensics:detection:compression_as_concealment|Compression as Concealment]]
  * [[wiki:anti_forensics:detection:encrypted_containers_in_investigations|Encrypted Containers in Investigations]]
  * [[wiki:anti_forensics:detection:evidence_destruction_claims|Evidence Destruction Claims]]
  * [[wiki:anti_forensics:detection:extension_mismatch|Extension Mismatch]]
  * [[wiki:tools:start|Forensic Tools]]
  * [[wiki:resources:start|Project Resources]]

===== Reader Takeaway =====
Alternate Data Stream Abuse is useful when it helps explain what the evidence can support and where the limits begin. Treat alternate data stream abuse as one part of a corroborated record, not a shortcut to intent. Recovery failure is not a motive. It is a technical condition that needs witnesses.

===== Use Notes =====
This article is for defensive education and technical reference. It should not be treated as legal, forensic, investigative, compliance, or operational advice without qualified professional judgment.
Do not use this material to destroy, conceal, or tamper with evidence.