====== Wear Leveling ======

===== Definition =====
Wear Leveling is a file-system concept for understanding how storage structures record, organize, name, allocate, or retain data.
In a forensic report, wear leveling 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 =====
File systems were designed to store data efficiently, not to write detective novels for examiners. That tension is why the artifacts are useful and why they keep ruining clean theories.
A reviewer should be able to follow the claim from source evidence to cautious conclusion without spelunking through unsupported confidence. Unallocated space is not a witness. It is a room where furniture used to be.

===== Technical Description =====
The technical review usually compares allocation records, directory structures, metadata timestamps, object identifiers, and storage-layer behavior.
A careful review starts with the source format and collection method before it argues about meaning.

===== Forensic Relevance =====
  * **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 wear leveling looks interesting but not conclusive.
  * **Timeline reconstruction:** Wear Leveling can help place activity in sequence when the time source and collection conditions are understood.
  * **Recovery analysis:** It can explain why data was recovered, missed, corrupted, or only partially reconstructed.

===== Evidence Sources =====
^ Evidence source ^ What it may show ^ Reliability limits ^ What it cannot prove alone ^
| Storage-device behavior | May explain why recovery returns little or nothing. | SSD firmware behavior is often below file-system visibility. | Does not prove deliberate wiping. |
| File-system allocation records | May show deletion or allocation state. | Can be reused or overwritten. | Does not explain motive. |
| Recovery output | Shows what could be recovered under examined conditions. | Depends on tools, timing, and media. | Does not prove data never existed. |
| Collection notes | May record media type, imaging method, errors, and timing. | Weak notes weaken every recovery claim. | Do not replace technical evidence. |

===== Interpretation Limits =====
The most common error is treating wear leveling 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.
Cold sectors do not care what theory needed them to say.

===== Common Misinterpretations =====
  * Ignoring benign explanations because the suspicious explanation is easier to write.
  * Treating wear leveling as proof that a specific user acted, when the artifact only supports system or account context.
  * Treating a timestamp as exact truth without checking timezone, clock drift, and source semantics.

===== Example Scenario =====
A reviewer sees storage-device behavior in the case file and asks whether it actually supports the written conclusion.
The record may be meaningful, but it has to be compared with file-system allocation records before the report gets confident.
The analyst preserves the source, exports the relevant records, checks file-system allocation records, and documents what remains unresolved.

===== Analysis Workflow =====
  - Define the question before opening another parser: what should Wear Leveling help answer?
  - Preserve the source evidence and document how the storage-device behavior was 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 wear leveling 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 storage-device behavior is consistent with activity related to wear leveling, but it does 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 | Storage-device behavior exists, but collection scope, time source, or surrounding context is limited. | State the observation and keep interpretation narrow. |
| Moderate | Storage-device behavior aligns with File-system allocation records, 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:digital_forensics:file_systems:alternate_data_streams|Alternate Data Streams]] - Helps keep the finding grounded in a wider evidence pattern.
  * [[wiki:digital_forensics:file_systems:apfs|APFS]] - Helps keep the finding grounded in a wider evidence pattern.
  * [[wiki:digital_forensics:file_systems:archive_files|Archive Files]] - Useful when checking whether another artifact supports the same interpretation.
  * [[wiki:digital_forensics:file_systems:bad_sectors|Bad Sectors]] - Often appears nearby in reviews of the same system or behavior.
  * [[wiki:digital_forensics:file_systems:btrfs|Btrfs]] - Often appears nearby in reviews of the same system or behavior.
  * [[wiki:digital_forensics:file_systems:cluster_allocation|Cluster Allocation]] - Often appears nearby in reviews of the same system or behavior.

===== 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://www.exterro.com/ftk-product-downloads|FTK Imager]] - Forensic imaging, preview, and export workflows.
  * [[https://www.magnetforensics.com/products/magnet-axiom/|Magnet AXIOM]] - Commercial forensic suite for computer, mobile, and cloud evidence review.
  * [[https://www.x-ways.net/forensics/|X-Ways Forensics]] - Commercial forensic suite for file systems, carving, and case analysis.
  * [[https://exiftool.org/|ExifTool]] - Metadata extraction across images, documents, and many file formats.
  * [[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.
  * [[https://arsenalrecon.com/products/arsenal-image-mounter|Arsenal Image Mounter]] - Mount forensic images for controlled review.
  * [[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://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.
  * [[https://www.nist.gov/itl/ssd/software-quality-group/computer-forensics-tool-testing-program-cftt|NIST CFTT]] - Tool testing context.
  * [[https://csrc.nist.gov/publications/detail/sp/800-86/final|NIST SP 800-86]] - Guide to integrating forensic techniques into incident response.
  * [[https://www.forensicfocus.com/articles/what-is-digital-forensics/|Forensic Focus: What is digital forensics?]] - Practitioner-facing overview.

===== See Also =====
  * [[wiki:digital_forensics:file_systems:start|File Systems]]
  * [[wiki:digital_forensics:file_systems:alternate_data_streams|Alternate Data Streams]]
  * [[wiki:digital_forensics:file_systems:apfs|APFS]]
  * [[wiki:digital_forensics:file_systems:archive_files|Archive Files]]
  * [[wiki:digital_forensics:file_systems:bad_sectors|Bad Sectors]]
  * [[wiki:digital_forensics:file_systems:btrfs|Btrfs]]
  * [[wiki:digital_forensics:file_systems:cluster_allocation|Cluster Allocation]]
  * [[wiki:digital_forensics:file_systems:copy_operation_artifacts|Copy Operation Artifacts]]
  * [[wiki:digital_forensics:file_systems:created_modified_accessed_times|Created Modified Accessed Times]]
  * [[wiki:digital_forensics:file_systems:directory_entries|Directory Entries]]
  * [[wiki:digital_forensics:file_systems:disk_images|Disk Images]]
  * [[wiki:tools:start|Forensic Tools]]
  * [[wiki:resources:start|Project Resources]]

===== Reader Takeaway =====
Wear Leveling is useful when it helps explain what the evidence can support and where the limits begin. Treat wear leveling as one part of a corroborated record, not a shortcut to intent. Cold sectors do not care what theory needed them to say.

===== 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.