Does Key2XS replace SailPoint or iLOQ?

No. Key2XS is middleware. SailPoint remains the source of truth for identity and policy, iLOQ remains the locking system. Key2XS connects the two.

Do we need to modify our iLOQ installation to use Key2XS?

No. Key2XS works with the existing iLOQ environment through its standard interfaces. Locks, keys and the locking plan stay as they are.

What happens to physical keys when an employee leaves?

When the leaver process runs in SailPoint, Key2XS revokes the person's key rights in iLOQ as part of the same flow. Physical and digital access are withdrawn together, and the revocation is logged.

Which SailPoint products does Key2XS support?

The certified integration supports SailPoint Identity Security Cloud, SailPoint's SaaS identity governance platform, formerly known as IdentityNow.

How long does a SailPoint iLOQ integration take?

A standard integration is live in under two hours. Key2XS connects to SailPoint Identity Security Cloud and iLOQ through pre-built, certified connectors, so no custom development is required.

Is the Key2XS integration certified by SailPoint?

Yes. Key2XS is a SailPoint Technology Alliance Partner (TAP) and the integration is certified by SailPoint. The Key2XS platform is also certified by ASSA ABLOY.

Is the SailPoint iLOQ integration suitable for NIS2 and CER compliance?

Yes. Both directives require governed, auditable control over physical access to premises. Key2XS provides the policy enforcement and audit trail that connects SailPoint governance to physical keys.

SailPoint iLOQ Integration | Key2XS Physical Access Governance

The problem: SailPoint governs identities, but not your keys

Your organization uses SailPoint to control who has access to which systems. Joiners, movers and leavers are processed automatically, access requests follow approval flows, and every decision is auditable.

Physical keys rarely work that way. Key handout is administered in spreadsheets or a standalone key management tool, disconnected from identity governance. The result:

Employees who left months ago still hold active keys
Key rights that no longer match the person's current role
No approval flow for handing out physical access
Audit questions about physical access take days to answer

For organizations covered by NIS2 and the CER Directive this is more than an inconvenience. Both frameworks expect physical access to premises to be governed with the same rigor as digital access.

The solution: identity-driven key management

Key2XS is middleware that sits between SailPoint and the iLOQ locking system. It reads identity and entitlement data from SailPoint and orchestrates the corresponding key rights in iLOQ.

How it works

Connect. Key2XS connects to your SailPoint Identity Security Cloud tenant and to your iLOQ environment through their standard APIs. Your existing iLOQ locks and keys stay in place, nothing is replaced.
Map. Roles and entitlements in SailPoint are mapped to key rights and lock groups in iLOQ. A field engineer role in SailPoint can correspond to a defined set of substations, technical rooms or sites in iLOQ.
Orchestrate. When SailPoint provisions, changes or revokes an entitlement, Key2XS applies the matching change to the person's iLOQ key rights. When someone leaves the organization, their physical access is revoked in the same movement as their digital access.
Prove. Every key right, every change and every approval is logged. Compliance questions about physical access are answered in minutes instead of days.

What synchronizes between SailPoint and iLOQ

From SailPoint	To iLOQ via Key2XS
Identities (joiners, movers, leavers)	Key holders created, updated or deactivated
Roles and entitlements	Key rights and access to lock groups
Revocations and expirations	Immediate withdrawal of key rights
Approval decisions	Documented authorization behind every key

Changes flow through in near real-time, so a revocation in SailPoint does not wait for a nightly batch to reach your keys.

Built for critical environments

Key2XS is used in environments where physical access affects public safety, service continuity or regulatory compliance: utilities, government, transport, healthcare and industry.

NIS2 and CER ready. The integration produces a continuous, tamper-evident audit trail linking every physical access right to an identity and a policy decision.
Built for continuity. The Key2XS platform is engineered for 99.99% availability, matching the uptime expectations of critical infrastructure operations.
Security by design. All communication between Key2XS, SailPoint and iLOQ is encrypted in transit with TLS 1.3, and data at rest is protected with AES-256.
Non-disruptive. Key2XS orchestrates access rights through the iLOQ management interface. Your locking plan, locks and keys remain untouched.

Why organizations choose Key2XS over custom integration

Building a direct SailPoint to iLOQ integration in-house means developing and maintaining connector code against two evolving APIs, handling schema differences, building an audit layer and keeping it all compliant. Key2XS delivers this as a maintained platform:

SailPoint-certified. Key2XS is a SailPoint Technology Alliance Partner and the connector is certified by SailPoint, so it is validated against the platform you already run
Live in under 2 hours. A standard SailPoint to iLOQ integration is up and running in under two hours, not weeks or months
Maintained connectors that absorb API changes on both sides
Purpose-built audit and reporting for physical access governance
Support for additional IAM systems (Microsoft Entra ID, Okta, One Identity, OpenText) and key systems (ASSA ABLOY eCLIQ and PROTEC) from the same platform, so your architecture is not locked to one vendor pairing

Connect SailPoint to iLOQ