Waterschappen and water authorities run pump stations, sluices, weirs and treatment works, dispersed across the region and unmanned. Key2XS connects the IAM you already run to the keys already on those doors.
Whoever can open a pump station, a sluice house or a telemetry cabinet is close to the systems that keep the water out. Four realities work against knowing who that is.
Field crews cover different districts in different weeks; keys lag behind.
Mowing, dredging and inspection crews change per season; keys outlive the contract.
Storm duty needs many doors at once, so keys are cut wide.
Accounts close centrally; keys return by internal mail, eventually.
Flood defence is publicly accountable, down to the last sluice key.
Middleware between your IAM and the key systems on your assets. Follow one field operator through four events.
The team assignment becomes access rights for exactly the sluices, weirs and cabinets in the district. No key desk, no spreadsheet.
Old rights withdrawn, new ones granted, in one movement, near real time.
High water needs many doors at once. The duty role grants that breadth explicitly: bounded to the rotation, visible in the audit trail.
Disabling the accounts closes every sluice house and pump station door in the same movement, and logs it.
CER names drinking water and waste water as critical sectors. NIS2 requires policies for access to premises. For a waterschap the question is concrete: who can reach the water infrastructure, and can you prove it?
A weir in the polder 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.
Yes. Access follows the assignments and end dates in your IAM system. When the mowing, dredging or inspection contract ends, the corresponding access rights are withdrawn automatically and the change is logged.
Yes. Broad access can be granted explicitly through a duty role: bounded to the rotation, visible in the audit trail, and withdrawn when the duty ends.
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, from pump station to sluice.
