Detection rules › Panther
A Teleport Role was modified or created
A Teleport Role was modified or created
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Persistence | T1098.001 Account Manipulation: Additional Cloud Credentials |
Rule body yaml
AnalysisType: rule
Filename: teleport_role_created.py
RuleID: Teleport.RoleCreated
DisplayName: A Teleport Role was modified or created
Enabled: true
LogTypes:
- Gravitational.TeleportAudit
Tags:
- Teleport
Severity: Medium
Description: A Teleport Role was modified or created
DedupPeriodMinutes: 60
Reports:
MITRE ATT&CK:
- TA0003:T1098.001
Reference: https://goteleport.com/docs/management/admin/
Runbook: >
A Teleport Role was modified or created. Validate its legitimacy.
SummaryAttributes:
- event
- code
- user
- name
Tests:
- Name: A role was created
ExpectedResult: true
Log:
{
"cluster_name": "teleport.example.com",
"code": "T9000I",
"ei": 0,
"event": "role.created",
"expires": "0001-01-01T00:00:00Z",
"name": "teleport-event-handler",
"time": "2023-09-20T23:00:000.000000Z",
"uid": "88888888-4444-4444-4444-222222222222",
"user": "max.mustermann@example.com",
}
Detection logic
Condition
event eq "role.created"
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.
| Field | Kind | Values |
|---|---|---|
event | eq |
|
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 |
name |
cluster_name |