Colour theme
Book a consultation

Finding cloud apps outside your IT inventory

Build a cloud-app inventory from staff input and existing business records, assign owners, and verify how approval or blocking decisions take effect.

An illustrated laptop displaying cloud symbols against a network of circles.

The list of software your business buys may miss a free file-sharing account, a contractor’s project tool or a subscription paid through a department. These services can hold business records even when IT has never been asked to manage them.

An unsanctioned app is one your organization hasn’t signed off for the way it’s being used. Discovery should find out the business need, the data involved and who can administer the account. An unfamiliar service may be fine, and a familiar one may be set up badly.

Start with records you already have

Compare subscription invoices, purchasing records, the browser extensions you already allow, application integrations and business sign-in logs. Ask each department which services it uses to share files, schedule work, collect information or collaborate with suppliers.

Include free services and tools used by contractors. Ask staff to name the tool and the job it supports without submitting passwords or copies of sensitive records. Explain how to report a tool that needs urgent review.

Technical discovery can add another view. Microsoft’s shadow IT tutorial describes endpoint and network-log discovery methods. Their coverage depends on the devices, traffic and data sources included. A service absent from a report may still be used through personal accounts or unmonitored devices.

Record ownership and the information involved

Use a simple register with an entry for each service:

  • The task it supports and the team using it.
  • A business owner and someone who can administer it.
  • Account type, sign-in method and current users.
  • Information categories, sharing settings and connected applications.
  • Subscription owner, renewal date and export or deletion options.

Distinguish a business-owned workspace from a staff member’s personal account. If the only administrator leaves, the subscription may continue while the organization loses the ability to manage its records.

The SaaS departure-access audit covers checking former users. Include any gaps it identifies in this register.

Review the use, then decide

Check the vendor’s terms and the settings available on your subscription. Consider authentication, logging, support, data handling and whether permissions can be limited to the work required. Ask the owner to explain what would break if the app were unavailable.

Record the conditions for keeping it, a replacement plan or a decision to stop using it. Assign an owner to unanswered questions. A catalogue risk score can help, but it can’t tell you whether your configuration meets your contracts or privacy obligations.

For AI features and connectors, use the shadow AI review alongside this inventory. Accepting the core service doesn’t cover every new way it processes information.

Verify what a blocking decision does

Microsoft’s app-governance documentation explains that marking an app unsanctioned doesn’t itself block access. Enforcement needs a supported integration or configured network control. Check the required licences, integrations and device coverage before describing a decision as enforced.

Test from the locations and devices used for work. Confirm what happens to existing sessions and connected integrations, as well as new browser visits. Blocking network access doesn’t close an account, revoke every token or retrieve records already copied out.

Before replacing a service, preserve required records and check the cloud-exit process. Provide staff with the replacement workflow and a clear change date.

Keep discovery limited and repeatable

If you need new employee monitoring, first decide its purpose, scope, retention and access. The OPC’s workplace privacy guidance supports transparent, proportionate collection. Review the applicable province and sector requirements; don’t begin by collecting everyone’s personal browser history.

Revisit the register during purchases, departures and renewals. Keep the request process short so a team can get a needed tool reviewed before its records end up in an unmanaged account. Contact us if you need help establishing that inventory and ownership process.


Featured Image Credit