This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have an account, create one now for free!
this post will show a use case for my past post about ID-Sharing.
Customer with VDI solution uses our MUH agent to identify users behind the same machine and apply rules based on their identity, this is great and uses the agent to communicate with a GW that stores the identity and ports used by a specific user, the issue is when we are in the Cloud and a VMSS, the agent can communicate only to one GW so VMSS environments are an issue, so we can use the ID Sharing mechanism to connect the MUH agent to one GW that only will serve as Collector and Share the learned Identities from this one to the VMSS members, this can be automated with a simple script that I shared in the past (past post).
Here a simple diagram from my demo.
and a video showing all the stuffs
To view this video, you must Accept and consent to the use of cookies.
wouldn't it be better to have simple gateway deployed in same backend subnet as VMSS and use it ? instead of going back to on-prem via vpn/express route.
meanwhile there is connectivity the place of the collector/sharing GW is not relevant, in this scenario I place on-prem to avoid the use of rented compute in the cloud, since will be static and no benefit from any cloud feature, also because normally the customer will have some on-prem devices, in case this is not true or they are allowed to pay for a collector machine in the cloud, they can place it.