Thousands of unmanned sites. One governance model. Key2XS connects the IAM you already run to the keys already on your assets.
Nobody checks a badge at a transformer station. Four everyday realities make that model fragile.
Access needs change faster than key administration follows.
People change per project. Keys outlive the contract.
Standby keys open everything, and nobody dares narrow them.
Accounts close centrally. Keys come back eventually, sometimes.
Every one of those keys opens infrastructure whose failure makes the news.
Middleware between your IAM and your locking system. Follow one field engineer through four events.
A role in the IAM becomes access rights for exactly the Region North sites. No ticket, no key desk.
Old rights withdrawn, new ones granted, in one movement, near real time.
Broad access, made explicit: granted by the on-call role, ended with the rotation.
Disabling the accounts closes every door, in the same movement. Logged.
CER names energy and drinking water as critical sectors. NIS2 covers access to premises. Auditors ask three questions.
A substation sees a key long before it sees a network. Rights travel with the key, and a withdrawal is enforced at the next key update.
The next time the key is used or updated it picks up its new rights. Revocation propagates the same way.
Near real time, not instantaneous. Each key system closes the window with its own mechanism; Key2XS makes the decision centrally and logs the change.
Middleware through standard interfaces. Locks, keys and the locking plan stay as they are.
Identity decisions become access rights, with evidence.
No. Key2XS governs access rights centrally, regardless of how dispersed the locks are. Digital key systems like iLOQ, CLIQ and Traka are designed for exactly such estates, and Key2XS adds the identity layer on top.
Yes. Access follows the assignments and end dates in your IAM system. When the contract or project assignment ends, the corresponding access rights are withdrawn automatically and the change is logged.
Yes. Key2XS produces a continuous, tamper-evident audit trail linking every physical access right to an identity and a policy decision, so audit questions about physical access are answered in minutes instead of days.
No. Key2XS is middleware. It orchestrates access rights through the standard interfaces of your existing key systems: iLOQ, ASSA ABLOY CLIQ, ASSA ABLOY Access or Traka. Locks, keys and the locking plan stay as they are.
A standard integration is live in under two hours, through pre-built connectors, with no custom development required from your team.
A guided walkthrough of how identity, policy and physical keys come together across a dispersed estate.
