LastPass Privileged Access Review
Overview
A LastPass admin can change policies, reset or remove users, and
manage shared folders, so admin membership is the access worth
reviewing most often. LastPass models admin rights as admin levels:
named roles with a permission set. Each user has at most one
adminLevelId.
Every tool here is tier read in Conduit; none is admin-gated.
Removing an admin level happens in the LastPass Admin Console.
Anti-triggers
- MFA and score coverage for all users - use
security-posture; this skill only
looks at admins.
- One departing admin - use
offboarding-review, which covers the
rest of their access too.
Common Workflows
Whole client book (MSP key)
- Pull
lastpass_reports_admin_users_list with max_results: 500,
paging with page_token. Each row is userEmail, adminLevel and
company, across every child and grandchild company. This is the
fastest view of every admin the MSP is responsible for.
- Group by company. Flag companies with zero admins (nobody can manage
them except the MSP) and companies with an unusually high admin
count.
- Flag admins whose email domain does not match the client's domain.
MSP technicians are expected; anyone else (a former vendor, a
personal address) needs an owner.
- For any company that needs detail, run the single-company workflow.
One company
- List the roles:
lastpass_managed_company_admin_levels_list (or
lastpass_admin_levels_list for the key's own company).
- For each level, read its permissions with
lastpass_managed_company_admin_level_get (or
lastpass_admin_level_get) and its holders with
lastpass_managed_company_admin_level_users_list (or
lastpass_admin_level_users_list). Page members with page_token.
- For each holder, read the user with
lastpass_managed_company_user_get (or lastpass_user_get) and
check accountStatus, advancedMfaStatus, lastLoginTime and
masterPasswordScore.
- Record the review.
What to Flag
| Finding |
Why it matters |
| Admin without MFA |
One phished master password exposes the whole tenant |
Admin with a weak masterPasswordScore |
Same exposure |
| Admin not logged in for 90+ days |
Standing privilege nobody uses; remove it |
Admin who is disabled but still holds the level |
Clean-up was half done |
| Custom level with broad permissions held by many users |
Role sprawl |
Shared or generic admin mailbox (it@, admin@) |
No individual accountability |
| Admin outside the client's domain and not MSP staff |
Unknown third party |
Output
An access-review record per company: date of review, reviewer, each
admin level with its permissions summarised, each holder with status,
MFA, last login and a keep or remove recommendation, and the list of
Admin Console changes to make. Keep it factual so it can be filed as
audit evidence; note that the review was read-only and no changes were
made by the reviewer.
Gotchas
- Business key:
lastpass_reports_admin_users_list and the
lastpass_managed_company_* tools need an MSP key (403 otherwise).
With a Business key, use the own-company admin-level tools.
- The cross-tenant report has no MFA data. It names the admin and
level only. Pull the user record for MFA and last login.
- Level names are tenant-defined. Read the permissions, not just the
name; a level called "Helpdesk" can hold super-admin rights.
- Page every list. Admin level member lists cap at 50 per page.
Related Skills
1---2name: lastpass-privileged-access-review3description: >4 Reviewing who holds LastPass admin rights: admin levels (RBAC roles)5 and their permissions, the users in each level, the MSP cross-tenant6 admin-user report, and how to cross-check admins for MFA, dormancy and7 leaver status. Produces an access-review record suitable for SOC 2,8 ISO 27001 or cyber-insurance evidence.9when_to_use: >-10 When running a periodic access review of LastPass admins for one11 client or across the whole client book, or answering "who can12 administer this client's LastPass". Use when: lastpass admins,13 lastpass admin levels, lastpass rbac, privileged access review14 lastpass, who is a lastpass admin, super admin lastpass, or access15 review evidence password manager.16metadata:17 source: https://skillmd.com/skills/wyre-ai/lastpass-privileged-access-review18---1920# LastPass Privileged Access Review2122## Overview2324A LastPass admin can change policies, reset or remove users, and25manage shared folders, so admin membership is the access worth26reviewing most often. LastPass models admin rights as **admin levels**:27named roles with a permission set. Each user has at most one28`adminLevelId`.2930Every tool here is tier **read** in Conduit; none is admin-gated.31Removing an admin level happens in the LastPass Admin Console.3233## Anti-triggers3435- **MFA and score coverage for all users** - use36 [security-posture](../security-posture/SKILL.md); this skill only37 looks at admins.38- **One departing admin** - use39 [offboarding-review](../offboarding-review/SKILL.md), which covers the40 rest of their access too.4142## Common Workflows4344### Whole client book (MSP key)45461. Pull `lastpass_reports_admin_users_list` with `max_results: 500`,47 paging with `page_token`. Each row is `userEmail`, `adminLevel` and48 `company`, across every child and grandchild company. This is the49 fastest view of every admin the MSP is responsible for.502. Group by company. Flag companies with zero admins (nobody can manage51 them except the MSP) and companies with an unusually high admin52 count.533. Flag admins whose email domain does not match the client's domain.54 MSP technicians are expected; anyone else (a former vendor, a55 personal address) needs an owner.564. For any company that needs detail, run the single-company workflow.5758### One company59601. List the roles: `lastpass_managed_company_admin_levels_list` (or61 `lastpass_admin_levels_list` for the key's own company).622. For each level, read its permissions with63 `lastpass_managed_company_admin_level_get` (or64 `lastpass_admin_level_get`) and its holders with65 `lastpass_managed_company_admin_level_users_list` (or66 `lastpass_admin_level_users_list`). Page members with `page_token`.673. For each holder, read the user with68 `lastpass_managed_company_user_get` (or `lastpass_user_get`) and69 check `accountStatus`, `advancedMfaStatus`, `lastLoginTime` and70 `masterPasswordScore`.714. Record the review.7273## What to Flag7475| Finding | Why it matters |76|---------|----------------|77| Admin without MFA | One phished master password exposes the whole tenant |78| Admin with a weak `masterPasswordScore` | Same exposure |79| Admin not logged in for 90+ days | Standing privilege nobody uses; remove it |80| Admin who is `disabled` but still holds the level | Clean-up was half done |81| Custom level with broad permissions held by many users | Role sprawl |82| Shared or generic admin mailbox (`it@`, `admin@`) | No individual accountability |83| Admin outside the client's domain and not MSP staff | Unknown third party |8485## Output8687An access-review record per company: date of review, reviewer, each88admin level with its permissions summarised, each holder with status,89MFA, last login and a keep or remove recommendation, and the list of90Admin Console changes to make. Keep it factual so it can be filed as91audit evidence; note that the review was read-only and no changes were92made by the reviewer.9394## Gotchas9596- **Business key**: `lastpass_reports_admin_users_list` and the97 `lastpass_managed_company_*` tools need an MSP key (403 otherwise).98 With a Business key, use the own-company admin-level tools.99- **The cross-tenant report has no MFA data.** It names the admin and100 level only. Pull the user record for MFA and last login.101- **Level names are tenant-defined.** Read the permissions, not just the102 name; a level called "Helpdesk" can hold super-admin rights.103- **Page every list.** Admin level member lists cap at 50 per page.104105## Related Skills106107- [api-patterns](../api-patterns/SKILL.md) - pagination, filters, errors