Nuage Solutions All articles
Cloud Strategy

Consent That Outlives the Project: A Quarterly Audit of Third-Party App Access

Nuage Solutions
Consent That Outlives the Project: A Quarterly Audit of Third-Party App Access

Photo: US Embassy, Public domain, via Wikimedia Commons

The grant nobody remembers approving

Somewhere in your tenant, an application is reading mail. It may be a meeting scheduler, a CRM connector, a document e-signing tool, or something a former employee installed for a six-week pilot in 2023. The project ended. The subscription may even have been cancelled. The consent did not.

OAuth changed how SaaS tools integrate. Rather than sharing a password, a user or administrator grants an application a scoped token. That token can persist indefinitely, refresh automatically, and carry permissions that were broad at the outset. For UK SMEs, the result is a quiet accumulation of access that sits outside the usual joiners, movers, and leavers process.

The blind spot is not technical. It is procedural. Most organisations review user accounts; few review the applications those accounts have authorised.

Why the permission estate drifts

Three forces drive accumulation. First, delegated consent: any user can often approve an app that requests access to their mail, files, or calendar. Second, admin consent: a single click can grant tenant-wide access to directory data or all mailboxes. Third, integrations multiply: SaaS tools connect to each other, and each connection is another grant.

Procurement rarely sees these grants. A team can adopt a tool on a departmental budget, connect it to Microsoft 365 or Google Workspace, and never raise a purchase order. The tool becomes part of the workflow. The grant becomes part of the estate. When the project ends, the tool may be removed from the browser bookmarks but not from the identity provider.

What the risk actually looks like

Over-privileged tokens are attractive to attackers because they can bypass multi-factor authentication. If a token is stolen, or a vendor is compromised, the attacker inherits the granted scopes. A mail-reading grant becomes a route to invoice fraud. A file-reading grant becomes a route to client data. A directory-reading grant becomes a route to user enumeration and phishing.

For UK organisations, the regulatory dimension is direct. A mailbox compromise is not merely an IT incident; it may be a personal data breach requiring assessment under UK GDPR and, where appropriate, notification to the ICO within 72 hours. NCSC guidance on supply chain security is also relevant: your suppliers include the applications your staff have authorised, not only the ones with contracts.

A quarterly review that fits a UK SME

The review does not need a dedicated security team. It needs an owner, a cadence, and a record. Quarterly is usually sufficient for an SME; monthly is better for regulated firms or those with high staff turnover. The review should answer four questions: Which apps have access? What can each app read or change? Who approved it? Does it still have a business owner?

Microsoft 365

In the Microsoft Entra admin centre, open Enterprise applications and review the All applications list. Filter by consent type to separate admin-consented apps from user-consented ones. For each app, inspect the Permissions tab and compare the requested scopes with what the business actually uses. A reporting tool that asks for Mail.ReadWrite when it only needs Mail.Read is over-privileged.

Use PowerShell or Microsoft Graph to export grants for a durable record: Get-MgOauth2PermissionGrant and Get-MgServicePrincipal provide the raw data. Review user consent settings under Enterprise applications > Consent and permissions. If users can consent to apps that request sensitive scopes, consider restricting that setting and enabling the admin consent workflow so requests are reviewed rather than auto-approved.

Revocation is more than deleting the app. Revoke the app's sign-in sessions, remove the oauth2PermissionGrant, disable the enterprise application, and, where appropriate, delete the app registration. Check whether the app is still used before you act; a broken workflow is a business interruption, not a security win.

Google Workspace

In the Google Admin console, go to Security > API controls > App access control. Review third-party apps with access to Google services. The tokens list shows which users have authorised which apps and which scopes are in play. Look for apps with broad scopes such as Gmail read, Drive full access, or directory access.

Set a default posture: block apps that have not been reviewed, and allowlist those that have. Revoke tokens for apps that are no longer needed, and remove user-level grants where an app should be admin-managed only. As with Microsoft 365, communicate before revocation and record the decision.

Revocation is a process, not a button

Revoking a grant can break an integration that a team depends on. Treat revocation as a change: identify the business owner, confirm the dependency, agree a date, notify users, revoke, verify, and record the outcome. If the app is still needed, re-consent with narrower scopes rather than restoring the original grant.

Keep a simple register: application name, vendor, business owner, scopes, consent type, approval date, last review date, and exit plan. The register is the evidence that the review happened. It also makes the next review faster.

Procurement controls that stop the next grant

The quarterly review cleans up the past. Procurement controls prevent the next problem. Add an application onboarding checklist: purpose, data touched, minimum scopes, owner, review date, and offboarding steps. Require admin approval for any app requesting mail, file, or directory access. Include UK GDPR Article 28 processor terms, breach notification, subprocessor disclosure, and data location in the contract.

For managed service providers, make app access part of the monthly service review. The provider should be able to show which third-party apps hold grants, which have been revoked, and which are awaiting review.

Make app access part of the estate

Cloud estates are usually described in terms of workloads, subscriptions, and identities. Third-party grants belong in that description. They are not peripheral. They are the permissions that let other people's software read your mail, your files, and your directory.

A quarterly review will not eliminate the risk. It will make the risk visible, owned, and bounded. For most UK SMEs, that is the difference between a blind spot and a managed control.

All Articles

Related Articles

Custody Before Configuration: A Domain and DNS Control Review for UK Businesses

Custody Before Configuration: A Domain and DNS Control Review for UK Businesses

After the Last Workload Moves: Five Cloud Contract Terms That Shape the Estate

After the Last Workload Moves: Five Cloud Contract Terms That Shape the Estate

When the Status Page Turns Red: A Practical Outage Rehearsal for UK SMEs

When the Status Page Turns Red: A Practical Outage Rehearsal for UK SMEs