1Password Sign-in Triage
Overview
A 1Password account is a high-value target: one compromised member can expose every shared
vault they can open. The sign-in attempts feed records every attempt with its outcome, so an
MSP can spot password guessing, MFA fatigue, and sign-ins from places the client does not
operate. This skill reads that feed and produces a triage list. It cannot lock accounts or
change policy; those are console actions.
Tools used
| Tool |
Purpose |
Conduit tier |
1password_events_introspect |
Confirm the account and that the token has signinattempts |
read |
1password_signin_attempts_list |
The sign-in feed |
admin |
1password_users_list |
Resolve targets to users and their state |
read |
1password_audit_events_list |
Optional: what a suspicious session did next |
admin |
The sign-in feed is admin-gated in Conduit. Without the admin tier, stop and say so.
Key fields
Each attempt carries a category (the outcome), a more specific type, the target user,
the client app and the location (including country). 1Password documents categories such as
success, credentials_failed, mfa_failed, sso_failed, firewall_failed and
modern_version_failed. Group on the values the feed actually returns rather than assuming
this list is complete.
| Pattern |
Likely meaning |
Many credentials_failed on one user, few countries |
Forgotten password, or guessing from one source |
credentials_failed across many users from one country |
Password spraying |
mfa_failed on a user who also has success on credentials |
The password is known to someone; the second factor stopped them |
firewall_failed |
The client's 1Password firewall rules blocked the attempt; the control worked |
modern_version_failed |
An outdated 1Password app; a support issue, not a security one |
success from a country with no prior activity |
Travel, VPN, or compromise; needs confirmation |
Workflow
- Introspect. Call
1password_events_introspect; confirm the account and that
signinattempts is among the features.
- Pull the window. Call
1password_signin_attempts_list with start_time (default:
7 days ago for a routine check, 24 hours for an active alert) and limit 200. Page with
cursor while has_more is true.
- Group. Count by category, then by target user and country within each failure
category.
- Baseline countries. From the
success attempts in the window, list each user's usual
countries. A success outside that set is a finding; a failure outside it is context.
- Correlate. For a user with
mfa_failed, or failures followed by a success from a new
country, pull 1password_audit_events_list for the same period and look for actions by
that user after the success (invites, vault sharing, group changes).
- Resolve users. Check flagged users against
1password_users_list to see whether they
are ACTIVE or SUSPENDED. Attempts against a suspended user are someone trying an old
account.
- Report.
Report format
- Verdict: quiet, noisy-but-benign, or needs client contact.
- Needs client contact: successes from unexpected countries,
mfa_failed on a known
password, spraying across users. Give user, times (in the client's time zone), country,
client app and count.
- Benign noise: forgotten passwords, outdated apps, firewall blocks working as intended.
- Console actions (manual): ask the user to change their account password, review their
trusted devices, sign out sessions, tighten firewall rules or MFA policy.
- Coverage: window, events read, and whether paging was cut short.
Gotchas
- One hour by default. Without
start_time the feed covers only the last hour.
- No user filter. The feed returns all users; filter locally and keep windows short on
large accounts.
- Policy is not readable. No tool returns whether MFA is enforced. Do not infer the
policy from the feed; recommend the client confirm it in the console.
- Times are UTC. Convert before comparing with the client's working hours.
1---2name: "1password-sign-in-triage"3description: >4 Triage of 1Password sign-in attempts for one client account: pulling the5 sign-in feed over a window, grouping failures by user, category and country,6 separating password-guessing from MFA failures and firewall blocks, spotting7 successes from new countries after a run of failures, and deciding what is8 noise and what goes to the client. The sign-in feed is admin-gated in9 Conduit and read-only.10when_to_use: >-11 When an MSP needs to investigate failed or suspicious sign-ins to a client's 1Password12 account, or wants a periodic sign-in health check. Use when: 1password failed sign-in,13 1password brute force, 1password mfa failure, 1password suspicious login, 1password sign-in14 report, or password manager login alerts.15metadata:16 source: https://skillmd.com/skills/wyre-ai/1password-sign-in-triage17---1819# 1Password Sign-in Triage2021## Overview2223A 1Password account is a high-value target: one compromised member can expose every shared24vault they can open. The sign-in attempts feed records every attempt with its outcome, so an25MSP can spot password guessing, MFA fatigue, and sign-ins from places the client does not26operate. This skill reads that feed and produces a triage list. It cannot lock accounts or27change policy; those are console actions.2829## Tools used3031| Tool | Purpose | Conduit tier |32|---|---|---|33| `1password_events_introspect` | Confirm the account and that the token has `signinattempts` | read |34| `1password_signin_attempts_list` | The sign-in feed | admin |35| `1password_users_list` | Resolve targets to users and their state | read |36| `1password_audit_events_list` | Optional: what a suspicious session did next | admin |3738The sign-in feed is admin-gated in Conduit. Without the admin tier, stop and say so.3940## Key fields4142Each attempt carries a `category` (the outcome), a more specific `type`, the target user,43the client app and the location (including country). 1Password documents categories such as44`success`, `credentials_failed`, `mfa_failed`, `sso_failed`, `firewall_failed` and45`modern_version_failed`. Group on the values the feed actually returns rather than assuming46this list is complete.4748| Pattern | Likely meaning |49|---|---|50| Many `credentials_failed` on one user, few countries | Forgotten password, or guessing from one source |51| `credentials_failed` across many users from one country | Password spraying |52| `mfa_failed` on a user who also has `success` on credentials | The password is known to someone; the second factor stopped them |53| `firewall_failed` | The client's 1Password firewall rules blocked the attempt; the control worked |54| `modern_version_failed` | An outdated 1Password app; a support issue, not a security one |55| `success` from a country with no prior activity | Travel, VPN, or compromise; needs confirmation |5657## Workflow58591. **Introspect.** Call `1password_events_introspect`; confirm the account and that60 `signinattempts` is among the features.612. **Pull the window.** Call `1password_signin_attempts_list` with `start_time` (default:62 7 days ago for a routine check, 24 hours for an active alert) and `limit` 200. Page with63 `cursor` while `has_more` is true.643. **Group.** Count by category, then by target user and country within each failure65 category.664. **Baseline countries.** From the `success` attempts in the window, list each user's usual67 countries. A success outside that set is a finding; a failure outside it is context.685. **Correlate.** For a user with `mfa_failed`, or failures followed by a success from a new69 country, pull `1password_audit_events_list` for the same period and look for actions by70 that user after the success (invites, vault sharing, group changes).716. **Resolve users.** Check flagged users against `1password_users_list` to see whether they72 are `ACTIVE` or `SUSPENDED`. Attempts against a suspended user are someone trying an old73 account.747. **Report.**7576## Report format7778- **Verdict**: quiet, noisy-but-benign, or needs client contact.79- **Needs client contact**: successes from unexpected countries, `mfa_failed` on a known80 password, spraying across users. Give user, times (in the client's time zone), country,81 client app and count.82- **Benign noise**: forgotten passwords, outdated apps, firewall blocks working as intended.83- **Console actions** (manual): ask the user to change their account password, review their84 trusted devices, sign out sessions, tighten firewall rules or MFA policy.85- **Coverage**: window, events read, and whether paging was cut short.8687## Gotchas8889- **One hour by default.** Without `start_time` the feed covers only the last hour.90- **No user filter.** The feed returns all users; filter locally and keep windows short on91 large accounts.92- **Policy is not readable.** No tool returns whether MFA is enforced. Do not infer the93 policy from the feed; recommend the client confirm it in the console.94- **Times are UTC.** Convert before comparing with the client's working hours.