Cloud Application Integration
- ID
- T1671
- Tactics
- TA0003 Persistence
- Platforms
- Office Suite, SaaS
- Data sources
- Active Directory Object Modification, Cloud Service Modification, Application Log Content
- Source
- attack.mitre.org
- MITRE last modified
- 16 Apr 2025
Adversaries may achieve persistence by leveraging OAuth application integrations in a software-as-a-service environment. Adversaries may create a custom application, add a legitimate application into the environment, or even co-opt an existing integration to achieve malicious ends.[2][3]
OAuth is an open standard that allows users to authorize applications to access their information on their behalf. In a SaaS environment such as Microsoft 365 or Google Workspace, users may integrate applications to improve their workflow and achieve tasks.
Leveraging application integrations may allow adversaries to persist in an environment – for example, by granting consent to an application from a high-privileged adversary-controlled account in order to maintain access to its data, even in the event of losing access to the account.[4][5][6] In some cases, integrations may remain valid even after the original consenting user account is disabled.[7] Application integrations may also allow adversaries to bypass multi-factor authentication requirements through the use of Application Access Tokens. Finally, they may enable persistent Automated Exfiltration over time.[8]
Creating or adding a new application may require the adversary to create a dedicated Cloud Account for the application and assign it Additional Cloud Roles – for example, in Microsoft 365 environments, an application can only access resources via an associated service principal.[9]
Detection
- DET0539 Detection Strategy for Cloud Application Integration
Data components: Active Directory Object Modification, Cloud Service Modification, Application Log Content
Mitigations (2)
- M1042 Disable or Remove Feature or Program
Do not allow users to add new application integrations into a SaaS environment. In Entra ID environments, consider enforcing the “Do not allow user consent” option.[1]
- M1047 Audit
Periodically review SaaS integrations for unapproved or potentially malicious applications.
References
- Microsoft Entra Configure OAuth Consent
- Push Security SaaS Persistence 2022
- SaaS Attacks GitHub Evil Twin Integrations
- Wiz Midnight Blizzard 2024
- Microsoft Malicious OAuth Applications 2022
- Huntress Persistence Microsoft 365 Compromise 2024
- Push Security Slack Persistence 2023
- Synes Cyber Corner Malicious Azure Application 2023
- Microsoft Entra ID Service Principals
