← All integrations
1P
Live integration

1Password Business

Security tooling · API key / service-account token · Daily

Service-account token. Pulls vault count, member count + 2FA enrollment rate, and recent admin activity from the Events API for credential-management evidence.

Authentication
API key / service-account token
Sync cadence
Daily
Stale threshold
Every 2 days
Category
Security tooling

Evidence this connector produces

Every sync writes typed evidence rows linked to the controls below. Evidence is immutable once attached to an approved assessment, fingerprinted for de-dup, and surfaced in the control coverage calculation on your dashboard.

SOC 2 CC6.1

How to connect

Create a service account in 1Password Business with read access. Paste the token + your account hostname.

  1. 1
    Create the service account

    1Password Business → Integrations → Service Accounts → Create. Grant View access on the vaults you want audited.

  2. 2
    Generate the token

    Service account detail page → Generate a service account token. Copy it ONCE — 1Password won't show it again.

  3. 3
    Note your hostname

    Your team's 1Password URL is your-team.1password.com — paste your-team (just the subdomain).

Security model

Every connector ships behind the same auditor-grade primitives — not just RBAC config, but architectural enforcement.

Credentials KMS-encrypted at rest

Tokens, client secrets, and service-account keys are encrypted under a per-tenant AWS KMS data key. The plaintext is never persisted, never logged, and never leaves the FastAPI process boundary.

Tenant-isolated by architecture

Every Connection, ConnectorRun, and emitted Evidence row carries an organization ObjectId. The scheduler never iterates without an org-scoped filter; cross-tenant evidence bleed is impossible at the data layer.

Audit log on every action

Connect, sync, sync-failure, re-auth, and revoke each write a row to the immutable AuditLog. The full lifecycle is reconstructable for any examiner.

Soft-delete on revoke

Revoking a connection sets deletedAt and clears the encrypted credential blob, but the historical evidence + sync log stays queryable for the retention window. Auditors can still trace what was attested when.

Stale-evidence degradation

If this connector hasn't synced in Every 2 days, control coverage degrades automatically and an alert fires. Auditors don't trust stale evidence — neither do we.

Least-privilege scopes only

We request the minimum read-only scopes needed for the listed evidence. No write scopes, no admin scopes, no scopes outside the documented set.

Ready to connect 1Password Business?

Connect from Settings → Integrations — typically under 5 minutes. Or talk to us first.