Skip to main content
Signal data sources are the systems that supply activity for human risk signals. Living Security normalizes records from each source into a shared activity vocabulary. This gives teams one way to analyze related behavior across different tools.

​
Common source categories

The activity available from a provider depends on its products, enabled APIs, permissions, and the Living Security connector.

​
Supported and reporting sources

Living Security separates compatibility from current data flow:
  • A supported source has a reviewed mapping that can supply the activity used by a signal.
  • A reporting source has recently sent matching activity for a customer’s environment.
This distinction helps a team answer two different questions: “Which systems can supply this signal?” and “Which systems supply it now?” A compatible source can be connected without reporting a specific activity, and a custom source can report an activity without a built-in provider mapping.

​
Dormant signals

A signal with no listed built-in source is dormant, not broken. Its definition is ready, but no built-in mapping currently supplies matching activity. A future connector, mapping update, or Custom Push Source can activate it without changing the signal’s meaning. This model lets Living Security keep a stable signal vocabulary while integration coverage grows.

​
Choose and prepare a source

Use this sequence when you assess an integration:
1

Start with the behavior

Define the risk or protective behavior you want to observe. Then identify the activity that provides evidence for it.
2

Review provider coverage

Check the provider guide for supported activity, prerequisites, permissions, and known limits. Similar products can expose different records or API access.
3

Connect and verify

Complete the provider setup, then confirm that records arrive and map to the expected people and activity types.
4

Use custom push when needed

If a built-in connector is not available, evaluate a Custom Push Source for supported JSON or CSV data.

​
Privacy and public documentation

Public provider and signal pages describe reviewed capabilities. They do not show whether a specific customer connected a provider, which people have matching activity, or how a customer’s scorecards use a signal. That organization-specific state stays in the authenticated platform.

Integration Overview

Explore integration types and the connection workflow.

Set Up an Integration

Prepare credentials, connect a provider, and verify data flow.

Human Risk Signals

Learn how signal definitions turn activity into reusable indicators.

Human Risk Index

Learn how selected signals contribute to a human risk model.