Techniques › T1697 › AN2077
AN2077 Analytic 2077
SaaS · attack.mitre.org · ATT&CK Enterprise v20.0
<p>Detect successful SaaS authentication through an application-specific or legacy credential mechanism from a source/client not previously associated with that account, correlated with new session establishment or subsequent access inconsistent with ApprovedASPUsage.</p>
- Detects
- T1697 Steal Application Specific Passwords
- Part of
- DET0926 Suspicious Acquisition and Use of Application-Specific Passwords
Log sources and channels
Exactly as MITRE states them in x_mitre_log_source_references. Where a channel is vague, it is vague in the source; kevmap does not tidy it.
| Log source | Channel | Data component |
|---|---|---|
| saas:audit | Successful application-specific/legacy credential authentication where exposed | DC0002 User Account Authentication |
| saas:audit | ASP creation/modification event where supported | DC0010 User Account Modification |
| saas:session | New authenticated session associated with changed source/client context | DC0067 Logon Session Creation |
Mutable elements
Parameters MITRE marks as environment-specific. These are the knobs you are expected to tune; they are why an analytic is not a rule.
| Field | Description |
|---|---|
ApprovedASPUsage | Approved user/application/use-case relationships for ASP authentication—for example, which user or service is expected to use an ASP with which application. Derive from documented integration workflows and service ownership. Broadening permitted relationships reduces FP but increases FN for abused legitimate credentials; narrowing them increases detection sensitivity and FP. |