Mast sites, exchanges, street cabinets and data centres: a network is only as closed as its most remote door. Key2XS connects the IAM you already run to the keys already on your sites.
Tower crews, fibre contractors and facilities firms all carry keys. Sites are shared, work is subcontracted, and every handover multiplies who can open what.
The operator contracts the tower firm; the tower firm hires the crew. The key does not know that.
Co-location means more parties at the door than any one registry shows.
Night call-outs need doors open now, so keys are cut broad.
Riggers change per job; site keys outlive the work order.
The network carries everyone's traffic. The question a regulator asks is simple: who can open your sites, right now?
Middleware between your IAM and the key systems on your sites. Follow one tower crew through four events.
The work order in your IAM becomes access rights for exactly the sites on it. Every right traces to the order, through the whole subcontractor chain.
The crew moves to core work; the rights move with them, in one movement, near real time.
A fault at two in the morning needs doors open now. The on-call role grants broad access, bounded to the rotation, visible in the audit trail.
When the order closes or the contract ends, every site door closes with it, in the same movement. Logged.
NIS2 puts providers of public electronic communications networks in scope. CER names digital infrastructure a critical sector. Both ask who can physically reach the network.
A street cabinet has no badge reader and a mast site has no receptionist. 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.
Yes. Key2XS governs access rights centrally regardless of site type. Masts, street cabinets, exchanges and data centres are all mapped to roles in the same flow.
Yes. Access follows the assignments and end dates in your IAM system. When the order or contract 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 masts, cabinets and core sites.
