Detection rules › Panther
A SAML Connector was created or modified
A SAML connector was created or modified
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Resource Development | T1585 Establish Accounts |
Rule body yaml
AnalysisType: rule
Filename: teleport_saml_created.py
RuleID: Teleport.SAMLCreated
DisplayName: A SAML Connector was created or modified
Enabled: true
LogTypes:
- Gravitational.TeleportAudit
Tags:
- Teleport
Severity: High
Description: A SAML connector was created or modified
DedupPeriodMinutes: 60
Reports:
MITRE ATT&CK:
- TA0042:T1585
Reference: https://goteleport.com/docs/management/admin/
Runbook: >
When a SAML connector is modified, it can potentially change the trust model of the Teleport Cluster. Validate that these changes were expected and correct.
SummaryAttributes:
- event
- code
- user
- name
Tests:
- Name: SAML Auth Connector modified
ExpectedResult: true
Log:
{
"cluster_name": "teleport.example.com",
"code": "T8200I",
"ei": 0,
"event": "saml.created",
"name": "okta",
"time": "2023-09-19 18:00:00",
"uid": "88888888-4444-4444-4444-222222222222",
"user": "max.mustermann@zumbeispiel.example",
}
Detection logic
Condition
event eq "saml.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 |
cluster_name |