research

Auditing which browser profiles still store company passwords

A method for counting browser profiles that hold saved company credentials, separating personal accounts, and moving shared passwords into the approved vault.

Short answer

Use this benchmark to size repeatable IT work, set the review cadence, and decide what stays with the technical owner before assigning the workflow to an IT virtual assistant.

Research playbook

MeasureVolume and handling time
OwnerTechnical manager validates
Risk ruleName sensitive access
RefreshQuarterly benchmark review
On this pageJump to section

Key stats

UnitOne browser profileStudy protocol
Verification sample10 devicesStudy protocol
Review cadenceQuarterlyStudy protocol

Key takeaways

A browser that offers to save a password is convenient, and on a shared or poorly managed laptop it becomes an unmanaged credential store. The saved password may belong to a company application, a personal account, or a former employee. The browser profile can sync that store to a consumer account outside the company's control. This audit counts the profiles that still hold company passwords and checks whether the practice is documented.

Question and scope

The audit asks which browser profiles on company devices contain saved passwords for company applications, and whether those credentials are also stored in the approved password manager. The unit is one browser profile. The population is every managed laptop and desktop assigned to a named user. The result describes the saved credential state at the audit date. Record the audit date and the browser versions included in the scan.

Include the browsers installed by the company and any browser the user installed with permission. Exclude personal devices that are not managed, but record how many exist. Note the browser versions and whether sync is enabled. A profile that syncs to a personal account can hold company passwords outside the company's reach. Note the browsers that are installed but not supported by the company.

Define a stored credential

Treat a credential as stored when the browser's password manager contains a username and password for a company domain. Include credentials saved for single sign-on pages, vendor portals, and internal tools. Exclude form autofill entries that contain no password. Record the domain and the username where the tool exposes them. Record the count of credentials without exposing the password or the username.

Decide how to treat a credential that is saved but no longer valid. Count it separately as stale because it still reveals the account naming pattern and may be reused. Note whether the browser has a password export or a sync account linked. A saved password that syncs is a copy that the company cannot delete from the other device.

Build the profile list

Use the device management console to list the browsers and profiles on each device. Add the profile names and the signed-in sync account where the tool reports them. Record the device owner and the department. Export the list on one day so the count is consistent. Add the profile name and the sync account type to the inventory. Check that the inventory includes the browser used for the company intranet.

Check the browsers that are not covered by the console, such as a portable browser or a second profile created by the user. Ask the user which browsers they use for work. Record the answer and the date. A profile that is missing from the tool is a gap in the audit frame. Ask the user to open the browser profile menu and confirm the profiles they use.

Check each browser

Inspect the browser password settings on a sample of devices and record whether any company domains appear. Do not export or copy the passwords. Note the count and the domains only. For the full fleet, use a management report or a script that returns the domain list without the secret. Save only the domain list, never the password export, in the audit folder.

Check whether the browser is signed in to a sync account and whether the sync includes passwords. Record the account type, such as a company account or a personal account. Check the browser's save-password setting and whether the user can override it. A policy that relies on the user declining the prompt is not a control. Note whether the setting is enforced by policy or left to the user.

Distinguish personal from company

Separate credentials for company domains from personal shopping, banking, and social accounts. Use the company domain list to classify each entry. Ask the user to confirm any ambiguous domain. A personal account on a company device is a policy question, but it is not the same finding as a company password outside the vault. Record the policy reference that defines a personal account on a company device.

Check whether the company allows personal use of the device and what the acceptable use policy says. Record the policy reference. If personal use is allowed, state how personal credentials should be stored and whether the browser may sync them. The audit should not create a rule that the company has not agreed to. Add the acceptable use policy date so the rule can be checked later.

Sample and verify

Select at least ten devices across departments and inspect the browser settings directly. Compare the result with the management report. Record any difference and the likely cause. The sample tests whether the report is complete and whether users have created profiles the tool cannot see. Record the browser version and the profile name for each device checked. Repeat the inspection on a second device when the report and the screen disagree.

Ask two users to show where they save work passwords and whether they know the approved vault. Record the answer without collecting the password. A user who saves passwords in the browser because the vault is hard to use is telling you why the practice persists. Note the reason the user gave for avoiding the vault, such as access or habit.

Measure the share

Report the number of profiles with at least one company credential and the share of the measured fleet. Split the count by browser, by sync status, and by whether the credential is also in the vault. Do not report the number of passwords as a headline because one profile can hold many. Add the count of profiles that hold only stale credentials as a separate line.

Add the number of profiles that sync to a personal account and the number that hold stale credentials. These are the highest-risk groups because the company cannot remove the copy. Report the count of users who could not access the vault during the audit. The measure should point to the fix, not only the size of the problem. Record the number of users who needed a vault reset during the cleanup.

Report and clean

Write a short report with the method, the share, the domain categories, and the exceptions. Avoid listing actual passwords or usernames in the summary. Send the report to the device owner and the technical manager. Attach the domain list without the secrets. Send the report to the technical manager before the cleanup starts. Add the cleanup owner and the completion date to the report.

For each affected profile, confirm that the company credential is in the vault before removing it from the browser. Record the removal and the verification. If the credential is not in the vault, add it first so the user is not locked out. A cleanup that removes access without a replacement creates a support incident. Record the date and the person who confirmed the vault entry.

Set a policy

Write a rule that names the approved password manager, the browser settings the company enforces, and the process for personal accounts. Explain why browser storage is not allowed for company credentials. Publish the rule where users see it during onboarding and device setup. Give the rule to the onboarding team so new devices start in the right state. Record the date the rule was published and where users can find it.

Configure the browser policy to disable password saving for company domains where the platform allows it. Test the setting on a managed device before rolling it out. Provide a short guide for moving a saved password into the vault. A policy without a migration path will be bypassed. Record the policy setting and the test result on a managed device.

Limits of the audit

The audit sees the profiles that the management tool can inspect and the users who agreed to show their settings. It cannot see a portable browser on a USB drive or a personal device used for work. It also cannot prove that a credential was never exported. State these limits so the report is read as a configuration review. Note the browsers and devices that were out of scope in the report.

The sample describes the devices checked, not every device in the company. Repeat the audit after a browser update, a policy change, or a device refresh. Keep the domain list and the report with the endpoint documentation. Use the result to improve the vault experience, not only to remove access. Set the next review date and the person who will run it.

Check the sync account

For each profile with saved passwords, record whether sync is enabled and which account it uses. A company-managed account is different from a personal account because the company can control the former. Check whether the sync includes passwords or only bookmarks and settings. Note the device where the account was first signed in. Ask the user to sign out of the sync account after the company credentials are moved.

Ask the user whether they signed in for convenience or because the browser required it. Record the answer and the date. If the account is personal, explain the risk and help the user move company credentials to the vault before disconnecting sync. A sync account that stays connected will restore the saved passwords after a cleanup. Confirm the sync account is disconnected on every device the user uses for work.

Help users move to the vault

Write a short guide that shows how to save a password in the approved vault and how to remove it from the browser. Test the guide on a managed device with a test account. Include the steps for the browser versions the company supports. A guide that assumes one browser will confuse the rest of the fleet. Add the guide link to the password prompt message where the platform allows it.

Offer a short help session during the first week and record who attends. Ask users what made the vault hard to use and fix the top two issues. Check the browser setting again after a month to see whether the practice returned. The goal is a habit that survives the next password prompt. Record the follow-up date and the number of profiles that still hold company credentials.

Sources and next step

Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the local administrator, password reset, vendor case, file restore, and browser credential measures discussed here. The NIST SP 800-63B digital identity guidance supports the verification and credential checks, NIST SP 800-34 contingency planning guidance supports the restore measure, and the GAO data reliability guidance supports the sampling approach. Apply your own policies, contracts, and system documentation when adapting the method.

Compare this study with the local administrator audit and the file restore timing study before combining them into one review cycle. If the measurement work is recurring and your technical owner can define the scope, review the service areas and contact ITVirtualAssistant to discuss a limited pilot.

Benchmark brief

What this research page must produce

Working number

A practical estimate for volume, review time, escalation rate, and assistant capacity.

Operating boundary

A clear split between routine support, preparation work, and technical ownership.

What the auditing which browser profiles still store company passwords data shows

Treat this as a planning benchmark, not a universal number. Compare the benchmark against your ticket volume, SaaS stack, documentation backlog, and support risk before assigning recurring work.

The useful output is a decision about capacity, not a static statistic. If the workflow is high volume and low judgment, an IT virtual assistant can absorb coordination and upkeep. If the workflow is low volume but high risk, keep it with the technical owner and use the assistant only for preparation, reminders, and documentation.

Workflow

Recommended operating workflow

1

Collect a baseline

Pull the last 30 to 90 days of examples related to auditing which browser profiles still store company passwords, including completed work and unresolved exceptions.

2

Classify the work

Tag each item by routine admin, manager approval, technical decision, security risk, or vendor dependency.

3

Set the operating number

Use the median weekly volume and review time to decide how many assistant hours the workflow deserves.

4

Refresh the benchmark

Recheck the numbers quarterly so tool growth, new systems, and security requirements do not silently change the scope.

Decision rules

MetricUse it to decideManager action
Weekly volumeWhether the workflow is worth assigning as recurring assistant work.Approve a weekly capacity target and backlog threshold.
Access sensitivityWhether the assistant can work directly or only prepare review notes.Set least-privilege permissions and removal dates.
Escalation rateWhether the workflow is stable enough to delegate.Rewrite the SOP when exceptions exceed the agreed threshold.

Consolidated statistics

StatisticFigureSource
UnitOne browser profileStudy protocol
Verification sample10 devicesStudy protocol
Review cadenceQuarterlyStudy protocol

Sources

  1. NIST SP 800-63B, Digital Identity GuidelinesAuthenticator storage and lifecycle guidance used to frame the credential review.
  2. NIST SP 800-53 Rev. 5, Security and Privacy ControlsCredential management and access control language for the policy.
  3. CISA Cross-Sector Cybersecurity Performance GoalsBaseline credential and authentication controls for small organisations.
  4. SBA: Strengthen Your CybersecuritySmall business guidance on passwords and account protection.

Measurement checklist

FieldWhat to captureOwner
VolumeWeekly request count, backlog age, and repeat issue patternsAssistant prepares, manager reviews
RiskAccess level, customer impact, security sensitivity, and approval needsTechnical owner
CadenceDaily, weekly, monthly, or quarterly review rhythmManager
EvidenceSample tickets, logs, screenshots, and before-after examplesAssistant collects, owner validates
EscalationTriggers, approval path, response time, and stop-work rulesTechnical owner

How to read the result

A good research page should leave the manager with a working number and a clear boundary: what the assistant can do every week, what the assistant can prepare for review, and what must never move without the accountable technical owner.

Source and refresh note

This planning page is dated for 2026 and should be refreshed quarterly as tool stacks, ticket patterns, and security expectations change.

How should teams use this benchmark?

Use it to define task volume, access limits, review cadence, and escalation rules before assigning work.

Get free benchmark review