| name | T1671_cloud-application-integration |
| description | Adversaries may achieve persistence by leveraging OAuth application integrations in a software-as-a-service environment. |
| category | configuration |
| version | 18.1 |
| author | cyberstrike-official |
| tags | ["mitre-attack","enterprise","t1671","persistence","office-suite","saas"] |
| technique_id | T1671 |
| tactic | persistence |
| all_tactics | ["persistence"] |
| platforms | ["Office Suite","SaaS"] |
| mitre_url | https://attack.mitre.org/techniques/T1671 |
| tech_stack | ["office","saas"] |
| cwe_ids | ["CWE-276"] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
T1671 Cloud Application Integration
High-Level Description
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.
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. In some cases, integrations may remain valid even after the original consenting user account is disabled. 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.
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.
Kill Chain Phase
Platforms: Office Suite, SaaS
What to Check
How to Test
Manual Testing
-
Identify Attack Surface: Determine if the target environment is susceptible to Cloud Application Integration by examining the target platforms (Office Suite, SaaS).
-
Assess Existing Defenses: Review whether mitigations for T1671 are in place. If defenses are absent or misconfigured, this technique may be exploitable.
-
