Hello,
I might have an interesting usecase which i'm not sure there is a solution for yet, if there is I would like to know.
We have saveral vaults, actually a vault for each in-house project we have. Each of these vaults have specific users in them which maintain(create/read/update) the entries. I did it this so so that the projectowner can maintain the vault and I don't have to maintain every vault individually after the inital creation. All these users are synced with Entra ID, but that's not relevant to my issue.
We have three physical offices currently and each office has an on-premise Devolutions Gateway running in the DMZ. This DMZ subnet connects through our company firewall with each seperate subnet(VLAN) which houses a project. This works perfectly but it seems I just made a massive security gap which I missed initially.
Each user can create his/her own entry in their vault, I can limit their gateway selection if I want too but what i cannot seem to limit is which subnet(vlan) the user is able to connect to when he/she establishes a connection.
For example:
Office A houses projects 1, 2 and 3
Office B houses project 4,5
User X works on project 1, which resides physically in office A and uses the Vault for project 1. Because the project is housed in Office A the user must connect to the Devolutions Gateway in Office A. All is fine up until now because what is preventing the user from making records that can make connections to projects 2 and 3?
Our firewall doesn't know which users makes which connection and I don't want to make a gateway for each project because that would create a massive overhead on our systems and management.
It seems to me that there needs to be a security mechanism in place which can limit a user to specific subnets he can connect to.