Skip to content
CyberSimStart training

Theory · 8 min

OAuth apps and consent

Investigate a suspicious app consent and its permissions.

Cloud apps get access to a user’s data through OAuth: the user (or an admin) consents to permissions such as Mail.Read, Files.ReadWrite.All or offline_access, and the app receives tokens. No password is shared.

Consent phishing tricks users into granting that access to an attacker’s app (T1528 Steal Application Access Token). The app keeps working after a password reset, because its tokens are separate.

Signals: an app from an unverified publisher (Microsoft marks verified publishers with a blue badge), broad mail or file permissions, offline_access for persistent access, and consent soon after a phishing email.

Response, as in Microsoft’s app consent playbook: revoke the grant, disable or remove the app’s service principal, check its sign-ins and what it accessed, and look for other users who consented.

T1528

Your turn: select the field that proves it. Select the field that gives the app lasting access even when the user is not signed in.

Do the interactive check Free, in the browser.

Sources

Part of