MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Execution | T1059 Command and Scripting Interpreter |
Rule body yaml
AnalysisType: rule
Filename: teleport_root_login.py
RuleID: Teleport.RootLogin
DisplayName: User Logged in as root
Enabled: true
LogTypes:
- Gravitational.TeleportAudit
Tags:
- SSH
- Execution:Command and Scripting Interpreter
- Teleport
Severity: Medium
Description: A User logged in as root
DedupPeriodMinutes: 60
Reports:
MITRE ATT&CK:
- TA0002:T1059
Reference: https://goteleport.com/docs/management/admin/
Runbook: >
Use user accounts and policies, rather than root when logging in. With access to root, it is possible to evade auditing and logging.
SummaryAttributes:
- event
- code
- user
- login
- server_hostname
- server_labels
Tests:
- Name: User logged in as root
ExpectedResult: true
Log:
{
"addr_remote": "192.0.2.1:35194",
"cluster_name": "teleport.example.com",
"code": "t2000i",
"ei": 0,
"event": "session.start",
"initial_command": [""],
"login": "root",
"namespace": "default",
"proto": "ssh",
"server_hostname": "ip-10-0-0-1.us-west-2.compute.internal",
"server_id": "12345678-1111-2222-3333-54e9467ff0e6",
"server_labels": { "env": "prod", "role": "project123" },
"session_recording": "node-sync",
"sid": "12345678-1111-2222-3333-54e9467ff0e6",
"size": "80:25",
"time": "2023-09-18 11:22:33",
"uid": "12345678-1111-2222-3333-54e9467ff0e6",
"user": "max.mustermann@zumbeispiel.example",
}
Detection logic
Condition
event eq "session.start"
login eq "root"
Indicators
Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.
Output fields
Fields the rule emits when it matches. Chronicle authors list these in the outcome block; they appear on the detection and $risk_score drives alerting. Sentinel / Defender XDR rules build them up through project / summarize / extend stages. Sentinel maps these into alert fields via entityMappings and customDetails; Defender XDR custom detections surface them as alert fields directly.
| Field |
|---|
user |
server_hostname |
cluster_name |