Techniques › T1213.005 › AN1565
AN1565 Analytic 1565
SaaS · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Atypical access to Slack or Teams conversations via APIs, automation tokens, or bulk message export functionality, particularly after an account takeover or rare sign-in pattern. Often includes mass retrieval of chat history, download of message content, or scraping of workspace/channel metadata.</p>
- Detects
- T1213.005 Messaging Applications
- Part of
- DET0567 Detecting Unauthorized Collection from Messaging Applications in SaaS and Office Environments
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:slack | conversations.history, files.list, users.info, audit_logs | DC0038 Application Log Content |
| m365:signinlogs | UserLoggedIn | 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 |
|---|---|
TimeWindow | Time interval to observe post-login message scraping behavior |
MessageExportThreshold | Number of messages or files accessed/downloaded to flag for review |
UserContext | User privilege level, team membership, or role context to suppress false positives |
AccessMethod | Direct user access vs API token, OAuth app, or bot interaction |