research
Auditing password manager use across browser profiles
A method for measuring how many browser profiles use the approved password manager for company credentials and where saved passwords still sit outside it.
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
On this pageJump to section
Key stats
Key takeaways
Browsers offer to save passwords because it is convenient, and users accept because nobody has given them a safer habit. The result is a set of credentials spread across personal and work profiles, often protected by the same login that opens the laptop. This study measures how many browser profiles use the approved password manager and where company credentials still sit outside it. The aim is a migration plan, not a blame list.
Question and scope
The study asks what share of browser profiles on staff devices use the approved password manager for company credentials. The unit is one browser profile on one device. The population is every profile that can sign in to a company application during the study window. Record the browser, the profile type, and the device owner. Record the result in the study file with the date and the reviewer.
Include work profiles, personal profiles used for work, and profiles on mobile devices. Exclude shared kiosk profiles that cannot store credentials by policy, but record how many exist. Note the password manager products in use. A study that counts only the managed browser will miss the profile where the risk often sits. Keep the evidence beside the case reference so another reviewer can check it.
Define approved use
Define approved use as a company credential stored in the approved vault and protected by multi-factor authentication. A browser profile that only remembers a username does not meet the definition. A personal password manager used without company approval does not meet it either. Write the definition before collecting so the count is consistent. Apply the same rule to every item in the sample before summarising the result.
Decide how to treat a credential that exists in both the browser and the vault. Count the profile as migrated only when the browser copy is removed after the vault entry is confirmed. Note the profiles that still have a saved password for a company domain. A duplicate copy keeps the risk even when the vault is in use. Note any exception and the name of the person who approved it.
Build the profile frame
Export the browser profiles from the management console and match them to the device register. Include the profile name, the signed-in account, the sync status, and the last activity date. Remove the profiles that belong to devices no longer in service. A stale profile can inflate the denominator and hide the real adoption rate. Store the raw export with the query that produced it.
Add the devices that are missing from the console but still in use. Ask the user which browser and profile they use for work. Record the answer and the date. List the profiles that could not be inspected and the reason, so the frame shows what was measured and what was not. Compare the result with the previous period before drawing a conclusion.
Inspect the browser settings
Check whether the browser is allowed to save passwords for company domains; open the password settings and count the saved entries for the company domain. Record whether the browser syncs the password store to a personal account. A sync setting can move company credentials outside the managed device. Write the decision into the method note for the next reviewer. Record the result in the study file with the date and the reviewer.
Check the password manager extension or the native vault integration; confirm that the approved vault is signed in and that the browser is configured to use it. Record the version and the policy that applies. A vault that is installed but not connected is not in use. Check the record against the source system before closing the item. Keep the evidence beside the case reference so another reviewer can check it.
Check the vault records
Ask the password manager administrator for a report of active users and the last activity date. Compare the report with the profile frame. A user who has a vault account but has not opened it in ninety days is unlikely to be using it. Record the report date and the filter used. Keep the sample sheet with the report so the count can be reproduced.
Check whether the vault contains the company domains that appear in the browser. A vault with only personal logins does not replace the browser store for work. Note the shared credentials that are stored in a team vault rather than a personal one. The report should distinguish personal, team, and company vaults. Name the owner of the next action in the review note.
Sample and verify
Select at least ten profiles and inspect them directly with the user present; compare the live browser settings with the exported data. Record any difference and the likely cause, such as a policy change or a new profile. The sample tests whether the collection method is trustworthy. Record the date of the check beside the evidence file. Apply the same rule to every item in the sample before summarising the result.
Choose the sample across departments, browsers, and device types. Include at least two profiles that reported full adoption. Ask the user to show how they retrieve a password for a company site. A user who cannot find the vault entry is not using the approved route, even if the account exists. Use the same definition for every item in the population.
Measure adoption
Report the share of profiles that use the approved vault for company credentials; split the result by browser, department, and device type. Report the profiles that still save company passwords in the browser as a separate line. Do not collapse the two numbers into one adoption percentage. Note the systems that could not be measured in the report. Note any exception and the name of the person who approved it.
Add the count of profiles that sync the browser store to a personal account. Note the profiles where the user could not demonstrate a vault lookup. These categories carry different risk and should be visible in the report. The total should include the denominator and the number of profiles not inspected. Ask the technical owner to confirm the finding before publication.
Report the gaps
Write a short report with the method, the measured population, the adoption share, and the exceptions. Use profile identifiers rather than user names in the summary. Attach the raw export and the sample sheet. Send the draft to the technical owner and give them two working days to correct the facts. Keep the previous result beside the new one for comparison.
Group the findings by cause, such as no vault licence, a browser policy that allows saving, or a user who was never shown the vault. Assign an owner and a due date to each cause. A finding that only names a user does not fix the process that produced it. File the export with the method note at the end of the study.
Interview users
Ask five users how they store the password for a company application. Record the answer without judging the person, because the answer explains the habit. Ask whether they have been shown the approved vault and whether it works on their phone. Compare the answers with the profile data. Record the result in the study file with the date and the reviewer.
Ask the person who supports the browser and the person who owns the password manager. Confirm whether the policy blocks browser saving for company domains. Check whether the vault is available on the devices people actually use. Record the name of the person who owns the next change. Keep the evidence beside the case reference so another reviewer can check it.
Repeat after browser changes
Rerun the study after a browser update, a policy change, or a password manager rollout. A new browser version can change the default saving behavior. A new policy can block the store without migrating the existing entries. Compare the new share with the previous result and investigate any drop. Apply the same rule to every item in the sample before summarising the result.
Keep the query, the export, and the sample sheet with the endpoint documentation; set a quarterly review and a monthly check of new devices. Record the date and the reviewer. A stable adoption share with a short exception list is a better result than a one-time cleanup. Note any exception and the name of the person who approved it. Store the raw export with the query that produced it.
Limits of the study
The study sees the profiles that the management tool can inspect. It cannot see a personal device that is used for work without management. It also cannot prove that a credential in the vault is unique or strong. State these limits so the report is read as a configuration review. Store the raw export with the query that produced it.
A user may move a password after the collection date; repeat the study after a large rollout or a staff change. The method measures where credentials are stored, not whether they have been shared. Use the interviews to interpret the number and keep the raw export for review. Compare the result with the previous period before drawing a conclusion. Write the decision into the method note for the next reviewer.
Keep evidence usable
Store the export, the sample sheet, and the report in one folder with the study date. Name the files by date and scope rather than by the person who ran the study. Give read access to the technical owner and the next reviewer. A folder that only one person can open will not survive a staff change. Write the decision into the method note for the next reviewer.
Write a one-page method note that explains how to repeat the inspection and where to find the definitions. Add the limitations and the profiles that were out of scope. Include the last run date and the next planned date. The note should let a new reviewer reproduce the result without asking the original author. Check the record against the source system before closing the item.
Sources and next step
Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the laptop support, password manager, vendor response, ticket triage, and access removal measures discussed here. The NIST SP 800-63B digital identity guidance supports the credential checks, NIST SP 800-53 Rev. 5 supports the access and audit records, 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 laptop support end date measure and the access removal completeness 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
A practical estimate for volume, review time, escalation rate, and assistant capacity.
A clear split between routine support, preparation work, and technical ownership.
What the auditing password manager use across browser profiles 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
Collect a baseline
Pull the last 30 to 90 days of examples related to auditing password manager use across browser profiles, including completed work and unresolved exceptions.
Classify the work
Tag each item by routine admin, manager approval, technical decision, security risk, or vendor dependency.
Set the operating number
Use the median weekly volume and review time to decide how many assistant hours the workflow deserves.
Refresh the benchmark
Recheck the numbers quarterly so tool growth, new systems, and security requirements do not silently change the scope.
Decision rules
| Metric | Use it to decide | Manager action |
|---|---|---|
| Weekly volume | Whether the workflow is worth assigning as recurring assistant work. | Approve a weekly capacity target and backlog threshold. |
| Access sensitivity | Whether the assistant can work directly or only prepare review notes. | Set least-privilege permissions and removal dates. |
| Escalation rate | Whether the workflow is stable enough to delegate. | Rewrite the SOP when exceptions exceed the agreed threshold. |
Consolidated statistics
| Statistic | Figure | Source |
|---|---|---|
| Unit | One browser profile | Study protocol |
| Verification sample | 10 profiles | Study protocol |
| Review cadence | Quarterly | Study protocol |
Sources
- NIST SP 800-63B, Digital Identity GuidelinesAuthenticator storage and lifecycle guidance used to frame the credential review.
- NIST SP 800-53 Rev. 5, Security and Privacy ControlsCredential management and access control language for the policy comparison.
- CISA Cross-Sector Cybersecurity Performance GoalsBaseline credential and authentication controls for small organisations.
- Mozilla Support: Password ManagerBrowser password storage and sync behavior referenced during inspection.
Measurement checklist
| Field | What to capture | Owner |
|---|---|---|
| Volume | Weekly request count, backlog age, and repeat issue patterns | Assistant prepares, manager reviews |
| Risk | Access level, customer impact, security sensitivity, and approval needs | Technical owner |
| Cadence | Daily, weekly, monthly, or quarterly review rhythm | Manager |
| Evidence | Sample tickets, logs, screenshots, and before-after examples | Assistant collects, owner validates |
| Escalation | Triggers, approval path, response time, and stop-work rules | Technical 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