Detection rules › Panther
A User from the company domain(s) Logged in without SAML
A User from the company domain(s) Logged in without SAML
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Stealth | T1562 Impair Defenses |
Rule body yaml
AnalysisType: rule
Filename: teleport_company_domain_login_without_saml.py
RuleID: Teleport.CompanyDomainLoginWithoutSAML
DisplayName: "A User from the company domain(s) Logged in without SAML"
Enabled: true
LogTypes:
- Gravitational.TeleportAudit
Tags:
- Teleport
Severity: Medium
Description: "A User from the company domain(s) Logged in without SAML"
DedupPeriodMinutes: 60
Reports:
MITRE ATT&CK:
- TA0005:T1562
Reference: https://goteleport.com/docs/management/admin/
Runbook: >
A User from the company domain(s) Logged in without SAML
SummaryAttributes:
- event
- code
- user
- method
- mfa_device
Tests:
- Name: A User from the company domain(s) logged in with SAML
ExpectedResult: false
Log:
{
"attributes": { "firstName": [""], "groups": ["employees"] },
"cluster_name": "teleport.example.com",
"code": "T1001I",
"ei": 0,
"event": "user.login",
"method": "saml",
"success": true,
"time": "2023-09-18 00:00:00",
"uid": "88888888-4444-4444-4444-222222222222",
"user": "jane.doe@example.com",
}
- Name: A User from the company domain(s) logged in without SAML
ExpectedResult: true
Log:
{
"cluster_name": "teleport.example.com",
"code": "T1001I",
"ei": 0,
"event": "user.login",
"method": "local",
"success": true,
"time": "2023-09-18 00:00:00",
"uid": "88888888-4444-4444-4444-222222222222",
"user": "jane.doe@example.com",
}
Detection logic
Condition
event eq "user.login"
success eq "True"
method ne "saml"
This rule also runs imperative logic the parser cannot express as a filter; the conditions above are the structured part it could extract.
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 |
cluster_name |