Transcript
Let's suppose we have a parent company that acquires a target company. During this use case, we are faced with various problems that we are going to encounter. The problems we usually encounter are related to the overlapping IP, to the diversity of hardware that each company has, and to the time that the two companies use to converge at the architectural level. Another problem is related to the risks that are encountered during this acquisition phase. How does Zscaler solve all of this? By applying the Cloud First concept. By directing all of our traffic to our Zero Trust Exchange. I'll abbreviate it as ZTE. Within the Zero Trust Exchange, we will have all the capabilities and all the potential to apply our Zero Trust principles. Let's start with an example. I will have my workers, work from anywhere, and I will go to apply and install our Client Connector. Both for the users of the parent company and for the users of the target company. What they will do is simply a connection to the Zero Trust Exchange. At this point, to respect the Zero Trust framework, the first thing we have to ask ourselves is who is the user, what is the department, what is the location. To do this, we must integrate with an Identity Provider. Let's imagine that the target company uses Octa as an Identity Provider. While the parent company is free to use, for example, Entra ID. First of all, notice how Zscaler can support different Identity Providers simultaneously within the same tenant. This allows us to authenticate different users who come from different Identity Providers. These users want to reach the applications both in the parent datacenter and in the target datacenter. To do this, how do we do it? Let's install a virtual machine here too, which we will call App Connector. And this too will make its connection to the Zero Trust Exchange. The two connections made by the App Connector are two output connections. This allows us to make our datacenters invisible to the outside world, but allows our users to access the applications they can actually access. Let's now imagine using a Cloud Provider. We will install an App Connector on one of our Cloud Providers. The App Connector will make its output call to the Zero Trust Exchange and will allow us to reach our Cloud Applications within a Cloud Provider. In this scenario, we also find ourselves in the use case where the Branch Connectors have to start working together. As for the Branch Sites, what we can do is put a Branch Connector inside our Branches, which will make an output call to our Zero Trust Exchange. In addition to regulating access to OT and IoT devices, I can also have visibility of those that are actually the OT and IoT devices within my Branches. In this case, the Zero Trust Exchange will therefore proxy our requests to those that can be SaaS Applications or Internet traffic. Here too, of course, regulating what access is for our OT and IoT devices, both for those that can be Workload and for those that can be Server or Client. So what are the advantages that Zscaler introduces? Certainly simplify your architecture, make a scenario like this more agile and mitigate and control all the risks we are exposed to during, for example, a scenario like a Merchant Acquisition. With this I have finished, thank you for your attention and I invite you, if you are interested, to contact our Account Team through Zscaler. Thank you very much, goodbye. Microsoft Mechanics www.microsoft.com
