Which apps still use a password? Finding the logins that skip your SSO
Single sign-on protects the apps that are connected to it. The rest, where people still type a username and a password, are usually the ones nobody approved. Here is why they are hard to see, and how Browser Security lists them.
Single sign-on only covers the apps that use it
Most organisations put their main applications behind an identity provider such as Microsoft Entra ID, Okta or Google Workspace. Sign-in goes through one place, your MFA rules apply everywhere, and when someone leaves, one switch closes every door.
That only holds for the applications connected to the identity provider. Every week people sign up for tools with their work email and a password of their own: a trial of a design tool, a supplier’s portal, a webinar platform, the file-sharing site a customer prefers. None of these accounts goes through single sign-on, and each one is a gap.
- Your MFA and sign-in rules don’t apply. The account is protected by whatever the app offers, often a password alone.
- Leavers keep access. Disabling someone in the directory doesn’t close an account the directory never knew about.
- The work password gets reused. People pick a password they remember, often the one they use for work, so a breach at that app becomes a breach of yours.
- Company data sits where nobody looks. Files, customer details and conversations end up in accounts no one reviews.
Why these logins are hard to find
The identity provider records the sign-ins that go through it, so it can’t list the ones that don’t. Firewall and DNS logs show which sites were visited, not whether anyone typed a password there. Asking people produces a partial list, and the riskiest accounts are the ones they forget.
The one place that sees a password being entered into a site is the browser, at the moment it happens.
A second blind spot: apps people grant access to
Some apps don’t need a password at all. In consent phishing, a person signs in on the real Microsoft or Google page, passes MFA, and is asked to let an app read their mailbox or files. If they accept, the app holds a token that keeps working after a password reset. The sign-in page is genuine, so phishing filters see nothing wrong.
Microsoft and Google show who published an app and whether that publisher is verified. An app from an unverified publisher, or one you never approved, asking for mailbox or files access is exactly the request worth stopping.
How Browser Security shows you every one
SafeToOpen Browser Security runs in the browser on every managed device, so it sees each sign-in as it happens. Three features work together.
The Password logins report
Whenever a password is submitted to a site that isn’t one of your identity-provider hosts, the extension counts it for that site and that person. In the console, Security → Password logins turns the counts into a list for the last 7, 30 or 90 days, for one workspace or all of them:
- every site that takes a password of its own, with how many people use it and how many sign-ins it had;
- new accounts: a page with two password fields counts as a sign-up, so you see where accounts are being created;
- whether the work password was reused there, from Password Alert;
- when each site was last seen, and the same view per person and per workspace.
Login forms inside embedded frames and pop-up sign-in windows count too, and the site recorded is the one that actually took the password. Counts reach the console within seconds of the sign-in. Only the host name and the counts are sent: usernames and passwords are never collected. The whole list exports as CSV.

Password Alert
When someone signs in on your identity provider, the extension keeps a salted fingerprint of the password on that device. If the same password is then typed into any other site, whether a proxy phishing page that mirrors your login or a personal account, the extension catches it before the form is sent. It can warn or block, and the console records a PASSWORD_REUSE incident naming the site. The fingerprint never leaves the device and can’t be turned back into the password.
The OAuth consent guard
On Microsoft and Google consent screens, the extension reads the app name, the client ID, whether the publisher is verified and the permissions requested. In a managed workspace, any app that isn’t on your approved list and asks for mailbox, files, contacts, calendar, directory or offline access is treated as risky: the person sees a warning, or the Accept button is disabled if you choose Block. Either way the console records the app and its permissions as an OAUTH_CONSENT_RISKY incident. Apps your tenant has already granted admin consent never show a consent screen, so they are not affected.
What to do with the list
Start with the busiest sites. The apps with the most people and sign-ins are your best candidates for single sign-on. Many vendors offer SAML or OpenID Connect sign-in, sometimes on a business plan. Once an app is connected, its sign-ins go through your identity provider and it drops off the list.
Look at new accounts. Sign-ups show tools being adopted right now. Decide whether to approve each one, replace it with something you already pay for, or block it.
Act on reused work passwords. A site flagged for reuse means your directory password exists outside the directory. Ask those people to change it, and consider a response rule that signs the person out everywhere and forces a password change in Entra ID, Okta or Google Workspace whenever Password Alert fires.
Build your approved apps list. Run the consent guard in Warn mode for the first few weeks, add the apps you trust to the approved list, then switch to Block.
Keep the evidence. Export the CSV for access reviews and audits, so your list of applications outside single sign-on is a document rather than a guess.
None of the three features sends a username or a password. The report sends host names and counts, Password Alert compares a fingerprint on the device and reports only the site, and the consent guard records the app, its client ID, the publisher status and the permissions it asked for.
Getting started
In Browser Security Business Plus, all three are set per workspace under Policies → Security. The Password logins report and the OAuth consent guard are on by default; Password Alert stays off until you switch it on. Every setting is explained in the modern threat guards guide.
See which apps skip your SSO
Business Plus has a 28-day free trial. Deploy the extension and the list starts filling in from the first sign-in.
Start a free trial →