> ## Documentation Index
> Fetch the complete documentation index at: https://docs.livingsecurity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# LastPass Enterprise integration setup

> Connect LastPass Enterprise to Living Security for account, authentication, administrative, and credential-vault activity.

export const PublicIntegrationNextSteps = () => <>
    <hr />
    <h2>Related resources</h2>
    <ul>
      <li>
        <a href="/signals/data-sources">Learn how integration data becomes Human Risk Management signals</a>
      </li>
      <li>
        <a href="https://www.livingsecurity.com/integrations">Explore Living Security integrations</a>
      </li>
      <li>
        <a href="https://app.livingsecurity.ai/">Open the Living Security Platform</a>
      </li>
      <li>
        <a href="https://www.livingsecurity.com/request-demo/">Request a Living Security demo</a>
      </li>
    </ul>
  </>;

export const ConnectInPlatform = ({tile, children}) => <Step title="Enter the credentials in the Living Security Platform">
    <p>
      Completed by whoever holds Living Security access — the program owner, or the system
      admin if they've been invited (delegated setup).
    </p>
    <ol>
      <li>
        Go to <strong>Settings → Integrations → Catalog</strong>, find the{' '}
        <strong>{tile}</strong> tile, click <strong>Connect</strong>.
      </li>
      <li>
        Fill in the fields below, then click <strong>Connect</strong>.
      </li>
    </ol>
    {children}
  </Step>;

export const SystemAdminBanner = ({system, recommendDelegated}) => <Note>
    <p>
      <strong>This guide is for your {system} administrator.</strong> It covers creating API
      credentials inside {system}, which requires admin access to {system} — not to the
      Living Security Platform.
    </p>
    <p>
      If you're the Living Security <strong>program owner</strong> and don't administer {system},
      send this page to whoever does. They complete Part A and hand the credentials back to you
      (or enter them directly if you've invited them into the platform).
      {recommendDelegated && <>
          {' '}Because setup produces sensitive key material, we recommend the{' '}
          <strong>delegated setup</strong> path so the secret is never sent back to you.
        </>}
    </p>
  </Note>;

<SystemAdminBanner system="LastPass Enterprise" recommendDelegated={true} />

## 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](/signals/data-sources).

## What Living Security needs

| Credential            | Description                                                    |
| --------------------- | -------------------------------------------------------------- |
| **CID**               | Your LastPass Enterprise account number.                       |
| **Provisioning hash** | The `provhash` credential used by the LastPass Enterprise API. |

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

<Steps>
  <Step title="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.
  </Step>

  <ConnectInPlatform tile="LastPass Enterprise">
    Enter the CID in the account-ID field and the provisioning hash in the secret field, then connect.
  </ConnectInPlatform>
</Steps>

## Verify and troubleshoot

Verify that the first connection test succeeds and that user data begins synchronizing.

<AccordionGroup>
  <Accordion title="Authentication failed">
    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.
  </Accordion>

  <Accordion title="Users load but reports do not">
    Confirm that Enterprise reporting is enabled for the account and that the credential belongs to the same LastPass Enterprise tenant.
  </Accordion>

  <Accordion title="Credential rotation">
    Generate or retrieve the replacement provisioning hash, reconnect in Living Security, and then retire the previous credential.
  </Accordion>
</AccordionGroup>

<PublicIntegrationNextSteps />