Detection rules › YARA-L
sap multi terminal logon
Identifies successful logons for the same User ID from multiple different terminal IDs or client hostnames in a short timeframe, indicating potential credential sharing or session theft.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Initial Access | T1078 Valid Accounts |
| Persistence | T1078 Valid Accounts |
| Privilege Escalation | T1078 Valid Accounts |
| Stealth | T1078 Valid Accounts |
Event coverage
| Provider | Event | Title |
|---|---|---|
| Security-Auditing | Event ID 4624 | An account was successfully logged on. |
| Security-Auditing | Event ID 4625 | An account failed to log on. |
| Security-Auditing | Event ID 4648 | A logon was attempted using explicit credentials. |
Rule body yaral
/*
* Copyright 2026 Google LLC
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* https://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
rule sap_multi_terminal_logon {
meta:
author = "Google Cloud Security"
description = "Identifies successful logons for the same User ID from multiple different terminal IDs or client hostnames in a short timeframe, indicating potential credential sharing or session theft."
severity = "medium"
tactic = "TA0006"
technique = "T1078"
events:
$e.metadata.log_type = "SAP_SECURITY_AUDIT"
(
$e.metadata.event_type = "USER_LOGIN" or
$e.additional.fields["msg_1"] = /^AU1$|^AU5$/
)
// Ensure we only check events that actually have a terminal/hostname recorded
$e.principal.hostname != ""
$terminal = $e.principal.hostname
$user = $e.principal.user.userid
match:
// You can reduce this window to 15m or 30m if 1h is too broad for direct terminal switches
$user over 15m
outcome:
$terminals = array_distinct($terminal)
$count_of_terminals = count_distinct($terminal)
// Give a high risk score if they switch terminals
$risk_score = 60
$sap_instance = array_distinct($e.target.resource.name)
condition:
// Trigger if the user is seen on 2 or more distinct terminals
#terminal >= 2
}
Detection logic
Fires when $terminal occurs at least 2 times in the 15m window.
Events
$e
metadata.log_type = "SAP_SECURITY_AUDIT"additional.fields["msg_1"] matches "^AU1$|^AU5$"principal.hostname is not null
Correlation
Outcome
Fields the detection emits on a match. $risk_score drives alerting; Chronicle surfaces the rest on the detection.
| Field | Expression |
|---|---|
terminals | array_distinct($terminal) |
count_of_terminals | count_distinct($terminal) |
risk_score | 60 |
sap_instance | array_distinct($e.target.resource.name) |