How Identity Links work
Panaptico reads entity data from each connected system via System Sensors. It matches records using correlation keys: email, device ID, serial number, IP address, or other stable identifiers. When a match is confident, the records are linked. When confidence is low, the Atlas flags the candidate for review. Once linked, the entity carries all of its attributes from every source. A single device record might include:- Okta: user assignment and MFA status
- Intune: compliance state and OS version
- Cloudflare: network location and WARP enrollment
- MDM: encryption and patch level
Groups as verifiable scopes
Groups turn populations into named, reusable scopes for verification. Examples include:- Japan Office — all devices and users physically located in the Tokyo office
- Main Admin Users — all accounts with super-admin privileges across identity systems
- Production Databases — all database instances tagged in cloud provider consoles
When to use Identity Links
Use Identity Links when your verification must span multiple systems and you need to reason about real entities, not siloed records. They are required for any cross-system Signal, Enriched Signal, or Initiative that involves identity, device, or network scope.Atlas
The live map of entities, relationships, and dependencies that powers linking.
System Sensor
The readers that ingest the raw entity data used for linking.
Initiatives
Apply verification to named Groups as part of budget-level programs.