Skip to main content

​
What this integration contributes

LastPass can contribute normalized account, authentication, administrative, and credential-vault activity. Reviewed examples include:
  • credential.vault.created — adds entries to the credential vault
  • auth.login.failed — fails to log in
  • account.privilege.escalated — account privilege escalated
See how integration data becomes signals.

​
What Living Security needs

These credentials allow the connection to read Enterprise user and reporting data. Treat the provisioning hash as a secret and rotate it according to your organization’s credential policy.

​
Setup

1

Obtain Enterprise API credentials

In the LastPass Admin Console, obtain the account CID and provisioning hash for a dedicated integration credential. If your role cannot view them, ask a LastPass administrator or LastPass Support.

​
Verify and troubleshoot

Verify that the first connection test succeeds and that user data begins synchronizing.
Confirm that the CID is the numeric account identifier and that the provisioning hash has not been rotated. Do not enter an administrator email or interactive account password.
Confirm that Enterprise reporting is enabled for the account and that the credential belongs to the same LastPass Enterprise tenant.
Generate or retrieve the replacement provisioning hash, reconnect in Living Security, and then retire the previous credential.