Compliance ConnectorsSetup by categorySecurity Training
Living Security
Connect Living Security to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Living Security connection as security training evidence.
| Category | Security Training |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Living Security:
- Sign in to the Living Security Dashboard as an admin and go to Settings › Integrations & Developers › Developer Hub.
- Open the Service accounts tab and create a service account with a descriptive name (for example safeguard-reader). Grant it only read permissions, such as organization:read and the read permissions for the training and people data Safeguard should see. The account's permissions are the ceiling for every key created under it.
- Open the service account's detail page and create a key. Pick the read permissions this key needs (a subset of the account's) and an expiration: 30, 90 or 365 days, or a custom period (expiration is mandatory).
- Copy the key's secret (it starts with lsk_live_); it is shown once and cannot be retrieved later.
Where to find the other values:
- Base URL (optional): The regional host for your organization's data residency: US https://api.us-east-1.livingsecurity.ai/v1 or EU https://api.eu-west-1.livingsecurity.ai/v1 (uk uses EU, ca uses US; apac/au: ask Living Security Support). Keys work only on their own region's host.
- Account / Org / Workspace (optional): Not needed for /v1 service-account keys; the key belongs to one organization (GET /v1/organization returns its id).
Living Security shows the secret only once, so copy it before you leave the page.
Source: docs.livingsecurity.com, docs.livingsecurity.com, docs.livingsecurity.com, docs.livingsecurity.com, checked 2026-10-07.
-
On Compliance › Connectors, open Living Security, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) - Account / Org / Workspace (optional) - -
Click Connect with token.
Frameworks
No automated compliance test reads Living Security, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.
Related
- Security Training connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks