Detection rules › YARA-L
sap suspected data exfiltration
Detects high-volume data downloads (AUY) from SAP to a local frontend file, potentially indicating exfiltration.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Exfiltration |
Rule body
// Copyright 2026 Google LLC. Licensed under Apache-2.0.
rule sap_suspected_data_exfiltration {
meta:
author = "Google Cloud Security"
description = "Detects high-volume data downloads (AUY) from SAP to a local frontend file, potentially indicating exfiltration."
severity = "Medium"
tactic = "TA0010"
technique = "T1041"
events:
$e.metadata.product_name = "SAP security audit"
$e.additional.fields["msg_1"] = "AUY"
$user = $e.principal.user.userid
match:
$user over 5m
outcome:
$event_count = count($e.metadata.product_log_id)
$report_used = array_distinct($e.principal.process.file.names)
$file_paths = array_distinct($e.additional.fields["param3_1"])
$total_bytes_approx = array_distinct($e.additional.fields["param1_1"])
$terminal_ip = array_distinct($e.principal.ip)
$system_id = array_distinct($e.target.application)
condition:
$e and $event_count >= 10
}
YARA-L rule structure
Condition
Fires when at least one $e event in the 5m window and $event_count ≥ 10.
Events
$e
additional.fields["msg_1"] = "AUY"
Match and correlation
Outcome
Outcome variables add context to a detection. When the rule generates an alert, $risk_score is displayed with it.
| Field | Expression |
|---|---|
event_count | count($e.metadata.product_log_id) |
report_used | array_distinct($e.principal.process.file.names) |
file_paths | array_distinct($e.additional.fields["param3_1"]) |
total_bytes_approx | array_distinct($e.additional.fields["param1_1"]) |
terminal_ip | array_distinct($e.principal.ip) |
system_id | array_distinct($e.target.application) |