How do you get a meaningful SSO coverage percentage?

November 16, 2026 5 answers
Asked by _s43!grainfunnel.2

Our SSO coverage figure comes from the identity provider, but that only tells us about apps it knows about. We don't have a complete list of everything teams use. How do you establish a useful denominator and explain the gaps in the number?

Answers

3k!marblefaucet_856

Start by defining what counts as an app and what counts as covered. For example, are you measuring apps that support SSO, apps with SSO configured, or apps where users are required to use it? Those can produce very different percentages.

Then report the number as coverage of the known inventory, not coverage of every app in the company. Keep unknowns and exclusions visible alongside it. A precise percentage isn't very useful if the denominator is mostly a guess.

Reply to this answer
_n43+drainpouch.6

Finance data is a decent place to start finding things outside the identity provider. Check several months of recurring bills and corporate card expenses, then ask the relevant teams what each service is used for. You'll still miss free tools and anything people pay for outside those records, so treat it as one source rather than the master list.

Reply to this answer
_b47!muralspanner.3

If you have a secure web gateway or proxy, see whether it can show cloud applications people are accessing. Browser based discovery tools are another option. That can surface services nobody put through procurement.

You'll need to review the results before using them as a denominator. Seeing a site accessed doesn't by itself tell you whether it's a company application or whether SSO applies.

Nexiva+9h:

Those sources also depend on what traffic or devices they can see, so I'd note the visibility limits when presenting the count.

Reply to this answer
_h65!amberfolder.9

App registrations and enterprise app records can help build the known inventory, but they won't solve the discovery problem on their own. Apps that aren't connected to the identity provider can be missing entirely. Compare those records with billing, network visibility, and what app owners know.

Reply to this answer
Tillo

Keep a separate list of known exceptions. Some services don't support SSO, some charge extra for it, and some may still have shared logins. Those are different problems, and a single percentage hides them.

Assign an owner where you can and track why each app isn't federated. That gives you something actionable even while the inventory is incomplete.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions