Detection rules › YARA-L
sap sensitive tables direct access by rfc logon data table
Detects direct access to sensitive SAP tables (e.g., USR02, T000) specifically via RFC logon. This identifies potential data exfiltration or unauthorized inspection of security-critical data tables.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Collection |
Rule body
// Copyright 2026 Google LLC. Licensed under Apache-2.0.
rule sap_sensitive_tables_direct_access_by_rfc_logon_data_table {
meta:
author = "Google Cloud Security"
description = "Detects direct access to sensitive SAP tables (e.g., USR02, T000) specifically via RFC logon. This identifies potential data exfiltration or unauthorized inspection of security-critical data tables."
severity = "High"
tactic = "TA0009"
technique = "T1005"
events:
$e.metadata.log_type = "SAP_SECURITY_AUDIT"
$e.additional.fields["msg_1"] = "CUZ"
$SID = $e.target.application
$table = $e.additional.fields["param1_1"]
$table in %sap_sensitive_tables.name
match:
$table over 1h
outcome:
$user_list = array_distinct($e.principal.user.userid)
$source_ips = array_distinct($e.principal.ip)
$system_ids = array_distinct($SID)
$event_count = count($e.metadata.id)
$terminal_names = array_distinct($e.principal.hostname)
condition:
$e
}
YARA-L rule structure
Condition
Fires when at least one $e event in the 1h window.
Events
$e
metadata.log_type = "SAP_SECURITY_AUDIT"additional.fields["msg_1"] = "CUZ"additional.fields["param1_1"] in "%sap_sensitive_tables.name"
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 |
|---|---|
user_list | array_distinct($e.principal.user.userid) |
source_ips | array_distinct($e.principal.ip) |
system_ids | array_distinct($SID) |
event_count | count($e.metadata.id) |
terminal_names | array_distinct($e.principal.hostname) |