LastPass Security Posture
Overview
LastPass rates each user with a Security Challenge score
(securityChallengeScore, the vault hygiene score: weak, reused and old
passwords) and a master password score (masterPasswordScore), and
records their MFA state, last login and last master password change.
Those per-user fields are what this skill turns into a posture review.
Every tool here is tier read in Conduit; none is admin-gated.
Scope limits. The LastPass REST API does not expose company
policies (for example "require MFA"), shared folders, or event logs. A
posture summary from this connector describes what users have done, not
what policy enforces. Say that in the report.
Key Fields
| Field |
Use |
accountStatus |
Only enrolled users count toward coverage |
advancedMfaStatus, enabledMfa |
MFA state and which authenticator |
federatedStatus |
Federated users authenticate through the IdP; judge their MFA there |
securityChallengeScore |
0 to 100; low means weak, reused or old vault passwords |
masterPasswordScore |
0 to 100; low means a weak master password |
lastMasterPasswordChangeTime |
Age of the master password |
lastLoginTime |
Dormant accounts |
creationTime, lastInvitationTime |
Unconverted invites |
Common Workflows
One client
- Resolve the client's
child_company_id with
lastpass_managed_companies_list (MSP key). For a Business key, use
the own-company tools throughout.
- Pull every enrolled user:
lastpass_managed_company_users_list (or
lastpass_users_list) with account_status: "enrolled" and
max_results: 500, paging with page_token until nextPageToken is
gone. You need the full set for honest percentages.
- Pull the weak tail directly with the range filter, e.g.
security_challenge_score: "[:50]", to cross-check your counts.
- Pull unconverted invites:
lastpass_managed_company_invites_list (or
lastpass_invites_list), plus users with account_status of
pending-invitation and expired-invitation.
- Compute the findings below and write the summary.
Across the client book
Use lastpass_managed_companies_list with status: ["active"], then
run the single-client workflow per company. Pace the calls: some
LastPass rate limits are shared by every key in the company, and a 429
tells you how long to wait. For a large book, hand this to the
posture-sweep agent.
Findings and Default Thresholds
Report the threshold you used next to every count. These are starting
points; the MSP should adjust them.
| Finding |
Default rule |
Severity |
| Enrolled user without MFA |
advancedMfaStatus not enabled and not federated |
High |
| Admin without MFA |
Above, and adminLevelId set |
Critical |
| Weak master password |
masterPasswordScore below 50 |
High |
| Poor vault hygiene |
securityChallengeScore below 50 |
Medium |
| Stale master password |
lastMasterPasswordChangeTime older than 365 days |
Low |
| Dormant account |
Enrolled, lastLoginTime older than 90 days |
Medium (likely a missed leaver) |
| Never enrolled |
Invite or pending-invitation older than 14 days |
Low (adoption gap) |
| Expired invite |
expired-invitation |
Low (re-invite or close out) |
Output
Per client:
- Enrolled users, and the share with MFA (excluding federated users from
the denominator if their MFA lives at the IdP; say which you did).
- Median and lowest
securityChallengeScore and masterPasswordScore.
- Counts per finding, then a named list of the High and Critical
findings.
- Adoption: invited but not enrolled.
- A line stating that policies, shared folders and events are not
visible through this connector.
Keep names and scores inside the client's own report. Across the book,
report counts and percentages per client, not names.
Gotchas
- Never report a percentage from one page. The default page size is
- Missing statuses. Awaiting approval users never appear, and some
Staged and Pending invitation users are omitted, so adoption figures
are a floor. Say so.
advancedMfaStatus values are reported as LastPass sends them.
Treat anything other than an enabled state as "no MFA" and quote the
raw value in the detail list rather than guessing.
- Dormancy comes first. A dormant enrolled account is an access
problem before it is a hygiene problem. List it under dormant
accounts, and do not let its score drag the client's median without
saying so.
Related Skills
1---2name: lastpass-security-posture3description: >4 Per-client LastPass account hygiene from user records: MFA coverage5 (`advancedMfaStatus`, `enabledMfa`), weak Security Challenge and6 master-password scores, stale master passwords, dormant enrolled7 accounts, invitations that never converted, and how to roll those into8 a client-facing posture summary. Covers what the API cannot show9 (policies, shared folders, events) so the summary does not overclaim.10when_to_use: >-11 When reviewing how well a client (or the MSP itself) is using12 LastPass: MFA adoption, weak or reused master passwords, low security13 scores, dormant accounts, or unenrolled staff, for a QBR, security14 review or compliance evidence. Use when: lastpass mfa, lastpass15 security score, weak master password, lastpass adoption, lastpass16 posture, lastpass compliance, who has not enrolled in lastpass, or17 lastpass qbr.18metadata:19 source: https://skillmd.com/skills/wyre-ai/lastpass-security-posture20---2122# LastPass Security Posture2324## Overview2526LastPass rates each user with a **Security Challenge score**27(`securityChallengeScore`, the vault hygiene score: weak, reused and old28passwords) and a **master password score** (`masterPasswordScore`), and29records their MFA state, last login and last master password change.30Those per-user fields are what this skill turns into a posture review.3132Every tool here is tier **read** in Conduit; none is admin-gated.3334**Scope limits.** The LastPass REST API does not expose company35policies (for example "require MFA"), shared folders, or event logs. A36posture summary from this connector describes what users have done, not37what policy enforces. Say that in the report.3839## Key Fields4041| Field | Use |42|-------|-----|43| `accountStatus` | Only `enrolled` users count toward coverage |44| `advancedMfaStatus`, `enabledMfa` | MFA state and which authenticator |45| `federatedStatus` | Federated users authenticate through the IdP; judge their MFA there |46| `securityChallengeScore` | 0 to 100; low means weak, reused or old vault passwords |47| `masterPasswordScore` | 0 to 100; low means a weak master password |48| `lastMasterPasswordChangeTime` | Age of the master password |49| `lastLoginTime` | Dormant accounts |50| `creationTime`, `lastInvitationTime` | Unconverted invites |5152## Common Workflows5354### One client55561. Resolve the client's `child_company_id` with57 `lastpass_managed_companies_list` (MSP key). For a Business key, use58 the own-company tools throughout.592. Pull every enrolled user: `lastpass_managed_company_users_list` (or60 `lastpass_users_list`) with `account_status: "enrolled"` and61 `max_results: 500`, paging with `page_token` until `nextPageToken` is62 gone. You need the full set for honest percentages.633. Pull the weak tail directly with the range filter, e.g.64 `security_challenge_score: "[:50]"`, to cross-check your counts.654. Pull unconverted invites: `lastpass_managed_company_invites_list` (or66 `lastpass_invites_list`), plus users with `account_status` of67 `pending-invitation` and `expired-invitation`.685. Compute the findings below and write the summary.6970### Across the client book7172Use `lastpass_managed_companies_list` with `status: ["active"]`, then73run the single-client workflow per company. Pace the calls: some74LastPass rate limits are shared by every key in the company, and a 42975tells you how long to wait. For a large book, hand this to the76`posture-sweep` agent.7778## Findings and Default Thresholds7980Report the threshold you used next to every count. These are starting81points; the MSP should adjust them.8283| Finding | Default rule | Severity |84|---------|--------------|----------|85| Enrolled user without MFA | `advancedMfaStatus` not enabled and not federated | High |86| Admin without MFA | Above, and `adminLevelId` set | Critical |87| Weak master password | `masterPasswordScore` below 50 | High |88| Poor vault hygiene | `securityChallengeScore` below 50 | Medium |89| Stale master password | `lastMasterPasswordChangeTime` older than 365 days | Low |90| Dormant account | Enrolled, `lastLoginTime` older than 90 days | Medium (likely a missed leaver) |91| Never enrolled | Invite or `pending-invitation` older than 14 days | Low (adoption gap) |92| Expired invite | `expired-invitation` | Low (re-invite or close out) |9394## Output9596Per client:9798- Enrolled users, and the share with MFA (excluding federated users from99 the denominator if their MFA lives at the IdP; say which you did).100- Median and lowest `securityChallengeScore` and `masterPasswordScore`.101- Counts per finding, then a named list of the High and Critical102 findings.103- Adoption: invited but not enrolled.104- A line stating that policies, shared folders and events are not105 visible through this connector.106107Keep names and scores inside the client's own report. Across the book,108report counts and percentages per client, not names.109110## Gotchas111112- **Never report a percentage from one page.** The default page size is113 10.114- **Missing statuses.** Awaiting approval users never appear, and some115 Staged and Pending invitation users are omitted, so adoption figures116 are a floor. Say so.117- **`advancedMfaStatus` values** are reported as LastPass sends them.118 Treat anything other than an enabled state as "no MFA" and quote the119 raw value in the detail list rather than guessing.120- **Dormancy comes first.** A dormant enrolled account is an access121 problem before it is a hygiene problem. List it under dormant122 accounts, and do not let its score drag the client's median without123 saying so.124125## Related Skills126127- [api-patterns](../api-patterns/SKILL.md) - pagination, filters, errors128- [privileged-access](../privileged-access/SKILL.md) - admin-level review129- [offboarding-review](../offboarding-review/SKILL.md) - for dormant accounts that turn out to be leavers