Remote Access
The person who needs access asks for it, and someone else approves
Nobody needs access in advance. The user requests access to a machine when it is needed. Another person approves the request. Access then applies only for the period the request covers.
How it works
Five steps from request to closed access
- The user signs in to the XMS and requests access to a machine. They state for what period and for what reason.
- The person who approves receives an email.
- The approver decides on the request in the XMS.
- When the period starts, the user connects as usual, with the XoT-Desktop Client or XoT-WebAccess.
- When the period is over, the access ends by itself.
The request, the decision and the connection are logged. Afterwards you can see who asked for access, who approved it and what happened.
Why
Benefits of access approval
No access left lying around
Vendors and engineers have no access between jobs. So there is no access right an attacker can exploit in the meantime.
Two people in every decision
The person who asks for access cannot approve their own request. It always takes two people, which is sometimes called the four-eyes principle.
Less work for the administrator
Users request what they need themselves. The administrator does not need to create a new policy for every service visit.
Traceability for audits
The log shows who asked for access, who approved it, when and why. That is evidence for NIS2, IEC 62443 and GMP.
Common questions
Where does the user request access?
The user signs in to the XMS in the web browser and makes the request there.
How does the approver know there is a request?
They receive an email and decide in the XMS.
Can we still grant access directly, without a request?
Yes. An administrator can also create a policy directly in the XMS. It takes about 20 seconds.
What happens if the work takes longer than planned?
Access ends when the period is over. The user can then request a new period.
See how it works
The video shows the whole flow, from request to approved access.