Reviewing Cloud Applications, Integrations and Vendor Access
Assess the access granted to connected accounting applications and the responsibilities shared with cloud service providers.

Xian Hui
9 November 2026 · 5 min read

In brief
How should an accounting practice review cloud applications and vendor access?
List the firm's approved systems and connected applications, then record each connection's owner, purpose, data, permissions and removal path. Check why each permission is needed and how security duties are shared with the provider. Narrow or remove unnecessary access, and review vendor arrangements in proportion to the data and permissions involved.
What you'll learn
- Identify the risks of broad app permissions
- Explain the shared-responsibility idea in cloud services
- Plan a practical vendor and integration access review
Reviewing Cloud Applications, Integrations and Vendor Access
An accounting firm connects a new reporting application to its client document repository. The app requests permission to read and modify all files. The supplier may be reputable, but the permission request is broader than the firm's immediate reporting need.
Cloud tools can improve accounting efficiency. They also create new paths to data. A connected application, external administrator or service-provider account may retain access after the original project has ended.
What does 'shared responsibility' mean?
Using a cloud service does not transfer every security decision to the provider. The provider may operate underlying infrastructure, but the accounting firm generally remains responsible for choices such as which people can sign in, how client records are classified and shared, and which integrations are approved.
The PDPC's data protection resources discuss governance of personal information in information and communications technology systems. The CSA's Cyber Essentials programme also includes cloud security in its expanded coverage.
The exact split of duties varies by service. Staff should not assume either that the provider is responsible for everything or that the firm must manage the provider's infrastructure itself.
Why do application permissions matter?
An integration may use a token or delegated authority to perform actions after the employee closes their browser. A permission that covers all client folders can increase the impact of a compromised integration or accidental misuse.
Before approving an application, ask what task it performs and why each requested permission is required. Record whether it can read, create, modify, delete or export information. If access is not needed after the project, remove it using the supported administrative controls.
The CSA's April 2026 software supply-chain advisory warns that external tools and software dependencies can become routes into internal systems. This is especially relevant to automation projects that join multiple systems together.
Who should be allowed to grant an integration access?
Granting an integration permission is riskier than it used to be. AI agents, automation tools and browser add-ons now ask to connect to email, files and accounting systems as a matter of routine. One click on Allow can give a third party standing access to client records. That access usually continues after the employee closes the window, and it can include reading, sending, changing or deleting data.
Examine the rights carefully before granting them. Read every permission on the consent screen, not just the app's name and logo. Be cautious when an app asks to:
- Read, change or delete all files, mailboxes or client workspaces, rather than one folder or one client.
- Send email or messages as you.
- Keep access when you are not signed in.
- Manage other users, settings or permissions.
If the request is wider than the task, do not approve it. Ask the supplier whether a narrower permission is available, or ask the person who manages the firm's systems.
Control it at admin level where you can. Microsoft 365 and Google Workspace both let administrators restrict which apps staff can connect, or require an administrator to approve a request first. For a small practice, the safest default is that only a named administrator can approve new integrations.
If staff are allowed to grant access, train them first. Delegate that authority only to people who know how to read a permission request, know which data is in scope and know who to ask. Keep a record of what each person approved, so the access can be reviewed and removed later.
What should the vendor review cover?
Use a proportionate review based on the sensitivity of data and the permissions involved. A practical checklist can cover:
| Review area | What to check |
|---|---|
| Provider and support | Which entity provides the service and who supports it |
| Security responsibilities | Where the firm and vendor each bear responsibility |
| Data processed | What categories of client or personal data are involved |
| Access | What access staff, support personnel and subcontractors may receive |
| Incidents | How security incidents are reported and handled |
| End of engagement | Whether access and data can be removed |
| Assurance | What independent assurance or relevant certification can be verified |
The ISO/IEC 27001:2022 overview provides the context for risk management and information-security management systems. A certification may be useful evidence, but does not eliminate the need to assess how the service is actually configured for the firm.
How can the firm review existing connections?
Start with a list of approved systems and the integrations attached to them. For each, capture the business owner, data involved, permissions, connection method, review date and exit plan. Find integrations with no active owner, no documented purpose or access wider than the task requires.
For the wider access review, see Securing Shared Devices, Access Rights and Staff Offboarding.
For example, a spreadsheet connector created for one audit engagement should not quietly retain access to every client workspace indefinitely. A successful review may result in narrower permissions, a separate service identity or complete removal.
Key takeaways
- Cloud use still requires decisions about identities, permissions and data.
- Application integrations can retain broad access beyond the original task.
- Examine every permission before clicking Allow, and let only an administrator or trained staff approve integrations.
- Review vendors and integrations according to their actual risk and permissions.
- Maintain an owner, review date and removal path for each connection.
Last source check: 12 November 2026.
Next in the course: Using Generative AI Without Exposing Client Data
Sources
Frequently asked questions
This information has been prepared for general informational purposes only and is not intended to be relied upon as accounting, tax, or other professional advice.


