---
{
  "title": "Data Staged",
  "summary": "Data staging collects information in a location convenient for later transfer.",
  "topic": "soc",
  "level": "Intermediate",
  "updated": "2026-10-12",
  "published": "2026-10-04",
  "units": [
    6
  ],
  "aliases": [
    "T1074"
  ],
  "sources": [
    {
      "title": "MITRE ATT&CK T1074: Data Staged",
      "url": "https://attack.mitre.org/techniques/T1074"
    }
  ],
  "editorialVersion": 2
}
---

## Preparation creates a collection point

Data staging places collected information in a location convenient for later use or transfer. An actor may aggregate files locally or on another reachable system. The staging location can reduce repeated access to the original sources and make a later transfer easier to manage.

Staging is not the same as exfiltration. A folder containing copied documents demonstrates a different stage from a verified transfer to an unauthorized destination. Investigators should describe the observed preparation without assuming every later objective was completed.

## An unusual aggregation folder

In a fictional organization, a temporary directory contains copies of documents from several unrelated shares. The analyst checks creation times, file provenance where available, the process or identity creating the copies, and the relationship to recent access activity.

A legitimate migration or project-delivery task may explain the aggregation. The team checks the owner, approved purpose, expected dataset, and intended destination. A folder's name or location alone is weak evidence because legitimate tools also use temporary workspaces.

The investigator looks for packaging, encryption, compression, or subsequent transfers, but treats each as a separate event. A prepared archive supports a conclusion about packaging; it does not establish that an external recipient received it.

## Bound the dataset

Identify which original resources are represented and whether the staged copies are complete, partial, or transformed. File counts and sizes may not directly equal the number of source documents because duplicates, temporary files, and archives can alter those measures.

Preserve relevant metadata and artifacts through controlled handling. Staged data may include confidential information, so the investigation storage needs appropriate access restrictions. Copying the entire folder into an open chat or ticket creates an avoidable additional exposure.

[[archive-collected-data]] explains packaging, while [[data-from-network-shared-drive]] and [[data-from-local-system]] describe possible collection sources. [[exfiltration]] addresses the separate boundary-crossing question.

## Contain more than the directory

If staging is unauthorized and ongoing, restrict the responsible process, identity, or transfer path as justified. Removing the staging directory alone may leave access to all the original material available. Review how the actor gathered the information and whether other staging locations exist within the supported scope.

For practice, compare an approved migration workspace with a fictional collection folder created by an unexplained process. Identify the source, creator, purpose, and destination evidence needed to distinguish them. Write one conclusion when only the folder exists and another when a linked transfer record is available. [[incident-response]] coordinates the actions, while [[incident-reporting]] preserves what is confirmed and what remains uncertain.

## Related concepts

- [[mitre-attack]]
- [[logs-and-telemetry]]
- [[modify-cloud-compute-infrastructure]]