T1074 Google Chronicle · YARA-L

Detect Data Staged in Google Chronicle

Adversaries may stage collected data in a central location or directory prior to exfiltration. Data may be kept in separate files or combined into one file through archiving techniques. Adversaries choose staging to minimize the number of connections made to their C2 server and better evade detection. Staging locations are commonly temp directories, user profile folders, or hidden directories. In cloud environments, adversaries may stage data within a particular instance before exfiltration.

MITRE ATT&CK

Tactic
Collection
Technique
T1074 Data Staged
Canonical reference
https://attack.mitre.org/techniques/T1074/

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule t1074_data_staged_detection {
  meta:
    author = "Argus Detection Engineering"
    description = "Detects T1074 data staging: bulk file creation or archive creation in common staging paths, and bulk copy commands targeting staging locations"
    mitre_attack_tactic = "Collection"
    mitre_attack_technique = "T1074"
    mitre_attack_sub_technique = ""
    severity = "MEDIUM"
    priority = "MEDIUM"
    version = "1.0"

  events:
    (
      // Branch 1: Archive file creation in staging directories
      $e1.metadata.event_type = "FILE_CREATION"
      $e1.principal.hostname = $hostname
      $e1.principal.user.userid = $userid
      (
        re.regex($e1.target.file.full_path, `(?i)\\(Temp|tmp|AppData\\Local\\Temp|AppData\\Roaming|ProgramData|Users\\Public|Windows\\Temp)\\`)
      )
      (
        re.regex($e1.target.file.full_path, `(?i)\.(zip|7z|rar|tar|gz|cab|iso)$`)
      )
    )
    OR
    (
      // Branch 2: Bulk copy process targeting staging paths
      $e1.metadata.event_type = "PROCESS_LAUNCH"
      $e1.principal.hostname = $hostname
      $e1.principal.user.userid = $userid
      (
        re.regex($e1.target.process.command_line, `(?i)(robocopy|xcopy|copy\s+/|Copy-Item|cp\s+-r)`)
      )
      (
        re.regex($e1.target.process.command_line, `(?i)\\(Temp|tmp|Public|ProgramData)\\`)
      )
    )

  match:
    $hostname, $userid over 10m

  outcome:
    $risk_score = max(
      if($e1.metadata.event_type = "FILE_CREATION", 50, 70)
    )
    $staging_path = array_distinct($e1.target.file.full_path)
    $process_name = array_distinct($e1.target.process.file.full_path)
    $command_line = array_distinct($e1.target.process.command_line)
    $event_count = count_distinct($e1.metadata.id)

  condition:
    $e1
}
medium severity medium confidence

Chronicle YARA-L 2.0 rule detecting T1074 data staging by identifying archive file creation in common staging directories and bulk copy command execution targeting staging paths. Correlates events by hostname and user within a 10-minute window using UDM event types FILE_CREATION and PROCESS_LAUNCH.

Data Sources

Google Chronicle SIEM with Windows Sysmon UDM ingestionChronicle Unified Data Model (UDM) with endpoint telemetryChronicle Google Workspace activity (for cloud staging variant)

Required Tables

UDM events (FILE_CREATION, PROCESS_LAUNCH)

False Positives & Tuning

  • Enterprise software packaging workflows where administrators use robocopy or xcopy to distribute application packages to staging directories on endpoints before installation
  • Endpoint security or DLP agents that create archive snapshots of monitored directories in Temp or AppData for forensic preservation or policy enforcement
  • Cloud sync clients (OneDrive, Google Drive, Dropbox) staging large file sets in AppData\Roaming or AppData\Local\Temp before uploading to cloud storage
Download portable Sigma rule (.yml)

Other platforms for T1074


Testing Methodology

Validate this detection against 5 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Stage Sensitive Files to Temp Directory Using Robocopy

    Expected signal: Sysmon Event ID 1: Process Create with Image=robocopy.exe, CommandLine containing source and destination temp paths with /E /COPYALL flags. Sysmon Event ID 11: Multiple FileCreate events in %TEMP%\df00tech-stage\ for each copied file. Security Event ID 4688 (if command line auditing enabled) for robocopy.exe execution. DeviceProcessEvents and DeviceFileEvents will capture this in MDE environments.

  2. Test 2Stage and Compress Data Using 7-Zip from Command Line

    Expected signal: Sysmon Event ID 1: Process Create for cmd.exe with copy command, then 7z.exe with -p flag (password) targeting staging directory. Sysmon Event ID 11: FileCreate events for each copied file in df00tech-collection\, then FileCreate for df00tech-exfil.zip. The -p flag in 7z.exe command line indicates password protection — a high-fidelity indicator of malicious intent.

  3. Test 3Stage Data Using PowerShell Copy-Item to ProgramData

    Expected signal: Sysmon Event ID 1: Process Create for powershell.exe with Copy-Item in CommandLine targeting C:\ProgramData\MicrosoftUpdates. Sysmon Event ID 11: Multiple FileCreate events in C:\ProgramData\MicrosoftUpdates\. Sysmon Event ID 12/13: Registry or attribute change if attrib command is monitored. The directory name 'MicrosoftUpdates' is a common masquerading technique — look for this in DeviceFileEvents FolderPath.

  4. Test 4Linux Data Staging Using cp and tar

    Expected signal: Linux auditd syscall events (if configured): open/creat syscalls for files in /tmp/.df00tech_stage/, execve for cp, find, tar commands. Syslog entries if auditd rules cover /tmp/ writes. If Sysmon for Linux is deployed: Sysmon Event ID 11 for file creations, Event ID 1 for process creation with tar czf command. The hidden directory name (.df00tech_stage with leading dot) indicates deliberate concealment.

  5. Test 5Remote Data Staging via Network Share Copy

    Expected signal: Sysmon Event ID 1: Process Create for net.exe (net use) with UNC path and xcopy.exe with /E /H /Y flags. Sysmon Event ID 3: Network Connection to target host on port 445 (SMB). Sysmon Event ID 11: FileCreate events in staging directory. Security Event ID 4648 (explicit credential logon) if credentials were provided to net use. Security Event ID 5140/5145 (network share access) on the target host if SMB auditing is enabled.

Unlock Pro Content

Get the full detection package for T1074 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections