Cisco Multicloud Defense Overview: Secure the Multicloud

Hello everyone. Thank you very much for joining today's EIS session. I am Jenny, your host and moderator. Today we will talk about the.00:10Review of Cisco multi cloud defense and how it can secure your multi cloud environment.00:20Today we have Alicia as our presenter. She will walk you through the overview and use cases of multi cloud defense. She will also provide demonstrations so you can understand how to deploy multi cloud defense and how to protect your cloud assets using multi cloud defense. And we haven't and myself.00:27Self as a panelists to support Lisa and answer your questions. We are all from customer success team. We help customers to make sure you get maximum value of your investment from multi cloud defense.00:47During our session, if you cannot hear the sound or have any connection issues, please raise your hand. We will contact you individually. And if you have any questions, please type your question in the Q and A panel. In the bottom right corner of your Webex window, you should be able to see.01:04A3.button and if you click this three.button, you will see this Q and A panel.01:23Please use this Q and A panel to ask your questions. Select all panelists. From this dropdown list, type your question and send and click this send button. Our panelists will receive your question and we will answer your questions online. And we will also have a.01:31Take the time for Q and A at the end of this session if timer permits.01:51With this, I'm going to stop my sharing and hand over the ball to our presenter, Lisa. Hi Lisa over to you. Thank you Jenny for the introduction. So let me share my screen.01:57I hope everyone is able to see my slide. So 1st let's take a look at the agenda for today's webinar. So firstly, in the 1st section, we will take a look at the overview for Cisco multi cloud defense.02:15Which is in short MCD solution. So in the 1st section, we will take a look at what exactly the MCD solution is, what features and the capabilities it can provide.02:35And then we will take a closer look at the key use cases that MCD provide, and then we will deep dive into the MCD deployment. So MCD provides very powerful automation features with the setup widget.02:50Customer can simply complete the deployment just with three steps within few hours.03:11So I will combine with the demo to show you how this product looks like and how to deploy the MCD for our public clouds. So if you have any questions, please feel free to ask in the QA panel, our panelists will help answering that.03:18So 1st let's take a look at the main challenges and issues that exist when using the multi cloud infrastructure. So nowadays more and more enterprises are shifting to hybrid and the multi cloud architecture. So application.03:40No longer reside in one single data centers but are distributed across multiple cloud platforms such as the AWS, Azure, Google Cloud, and et cetera, and even span across both on premise data centers and the.03:59Public clouds. So this increases the difficulty and the complexity for our administrators to manage the cloud security.04:182nd challenge is the visibility and the control. So when we are using multiple cloud platforms, different cloud providers have different terminologies and the technologies for the data. So how can we centrally analyze.04:29This and manage this data and the control the potential security risk that may exist in this traffic. The 3rd challenge is the scalability, so many applications are now deployed using auto scaling. So this brings the challenge to the security.04:49This solution, can the security solution also rapidly scale their performance in line with the traffic growth?05:09So these are the three core challenges that MCD owns to solve. So MCD is a security solution, provided by Cisco specifically for multi cloud environment.05:18So it provides three core features. So 1st is 100 % automated. So as I mentioned MCD provides very powerful automation feature, e.g., Hcan automated the deployment of the gateways to the public cloud.05:35And it also provides highly scaled automated process for the integration with the public clouds as well.05:56So with this automated feature, this can significantly reduce the complexity of the deployment and avoid any misconfigurations that may cause when integration with this public clouds.06:04And 2nd feature is the adaptive policy. So MCD provides unified security policy management that can dynamically adjust it based on the threat intelligence and the traffic behaviors.06:20And the 3rd core feature is the centralized across cloud security protection. MCD can connect and protect the workloads and datas across different cloud platforms, including the AWS, Azure, Google Cloud, and the Oracle Cloud.06:37So we can only use one unified policy framework to manage all of the access controls for these public clouds.06:57If we take a look at the right side of the slide, we can see these are the three main use cases that MCD provide. So the 1st use case is the inbound protection. MCD can help prevent and stop the inbound threats or.07:08The Tags for our internal applications that running in the public clouds.07:27And 2nd use case is the outbound security protection. So MCD can help detect to see if there's any existing outgoing traffic that's connecting to the bad and known service such as the command console servers.07:33The bottlenets and MCD can also detect the data as refusion behaviors as well.07:53The 3rd use case is the lateral segmentation. So this is the east west traffic analysis, so with MCD, this can help mitigate the attackers movement in case if there's any workload that is compromised in our.08:01Public clouds. So ultimately mcd's goal is to help us to reduce the overall risk, to enable the agility and also to gain the efficiencies for our entire public infrastructure.08:20So this is the high level introduction for the MCD. And next, let's take a look at the architecture of the MCD. So basically, there's two main components within MCD deployment. So 1st is called as controller.08:39Controller is used to control everything, including the settings, the deployment. So through the controller, we integrate with the public cloud. We through the controller, we can automatically deploy the gateways to the public clouds and.09:00We can centrally manage our policies across different public providers and also to perform the daily operations in the controller.09:19So controller is like the SaaS offering. And 2nd component is the gateways, MCD gateways. So and this MCD gateways is specifically deployed in the public clouds. E.g., it's deployed at.09:31As an EC two instance in the AWS environment.09:51So there's two types of gateways. One is called the ingress gateway, and this is used to protect the ingress security. And 2nd type of gateway is called the egress gateway. So this is protect the egress security as well as the.09:56The east west traffic.10:15And as I mentioned, MCD provides a very powerful automation feature. So through the controller, we can automatically deploy these gateways into our public cloud infrastructure. And MCD will make sure all the.10:20Routings and connectivities.10:38So I will talk more details in the later deployment section to let you better understand the entire deployment process. Okay, so this is about the 1st section about the introduction.10:41For the MCD solution. And next, let's take a closer look at the key use cases that MCD provide.11:01So as I mentioned, these are the three main use cases that MCD provide. So 1st is the ingress protection. So with the ingress protection, this can help us to prevent and stop the inbound threat or attack for.11:12For our internal applications, whether it's the web application or non web applications deployed in the public clouds.11:31MCD can provide the advanced inspection features such as the WAF, IPS, IDS, the antivirus, as well as the malicious security intelligence features that can help detect the norm and bad IPs and domains.11:412nd use case is the egress security. So with this feature use case, we are able to detect any existing outgoing traffic that's connecting to the bed and known servers such as the command control servers.12:02The bottlenet and et cetera. MCD can provide the DLP feature, which can help to detect the data as fortution behaviors for us.12:21The 3rd use case is the segmentation. So this is for the east to west traffic analysis. So in case if there's any, workload in our public clouds that gets compromised. So we can use this segmentation to better.12:35Mitigate the lateral movement in our clouds.12:54So here let's take a look at this topology to better understand about how the traffic pattern looks like. So let's 1st take a look at the right side of the slide. So as I mentioned, there's two main components for the MCD deployment.13:01One is the controller which is used to control everything, including the settings and the deployments of the gateways.13:21So through the controller we will deploy the ingress gateways specifically to our public clouds. So when we deploy the gateways, there's two deployment methods. One is called centralized security deployment model. So in this mod.13:30Total, the controller is going to provision a service VPC that puts all the resources and services within this VPC. So we will deploy the ingress gateways within this service VPC as well as some other important component.13:51Such as the loader balancers, the transit gateways, so MCD will make sure all the routings and the connectivities. So what we needed to do is.14:11Only tell the MCD what application vpcs that we want to protect in our public cloud. And then the MCD will make sure all the traffics that will going through our service VPC and be processed by our ingress gateways.14:24So here let's take a look at the example of the ingress use case. So we have an external user that's trying to access our applications that resides in our public cloud. So with MCD, the traffic will go through the ingress.14:45As gateways for the advanced security inspection. E.g., the IPS detections, the antivirus inspections, as well as other advanced inspection to make sure the traffic does NO malicious behaviors.15:04So in case if there's any malicious behaviors, so with the MCD gateways, we are able to block these behaviors immediately. So this is about the centralized security deployment model.15:23And then we have 2nd deployment model, which is called distributed security model. So in this model, we will deploy the ingress gateway specifically into the application vpcs.15:40So if we have multiple applications that's running across different vpcs, we will deploy the ingress gateway specifically for each of the application vpcs. And this ingress gateway will be used to process the traffic.15:57Specifically for this.16:17Application VPC. So most of customers will choose the centralized security deployments model as this is easier and the easier to manage. Well, some of the customers, they will choose the distributed security.16:20Model because this can provide lower latency and also help some of the meet some of the security compliance requirements.16:40So this is about the traffic patterns for the ingress security use case. And here let's also take a look at the traffic patterns for the egress security. So similarly, we can support both of the.16:51This deployment method for the centralized security deployment method.17:09Through the controller, we will automatically deploy the egress gateways into our public clouds and we will provision a service VPC for these gateways as well as other necessary components.17:16And then we need to tell the MCD what application VPC that we want to protect and all the traffic that's coming from these applications will go through the egress gateway for advancing inspection before it's going to the internet.17:33And for the distributed security deployment model, we will deploy the egress gateway specifically for each of these application vpcs. So the egress gateway will be used to process the traffic specifically.17:53For this application VPC.18:12And this is about the east to west segmentation use case, how the traffic pattern looks like. So for the traffic that inter VPC or intern vpcs, we will deploy the egress gateway to centrally inspect this.18:17Internal traffic. E.g., if the traffic that comes from the VPC one, application VPC one, the, the traffic will go through the egress gateway for centralized inspection before it's getting to the VPC two.18:37And for the distributed security deployment model, the egress gateway will deploy it specifically for this application VPC and used to handle the traffic that's coming from the different subnets and different workloads in our VPC.18:57Okay, so with that, I hope you have a basic understanding about the MCD or product, the features, and the use cases it provide. And then we will deep dive into the MCD deployment.19:20So as I mentioned, MCD provides very powerful automation feature which can help us to simply deploy the MCD within few hours. So I will combine with the demo to show you the entire deployment process.19:38Yeah. So the 1st step is, we need to integrate with the public clouds. So after the integration, we can immediately discover the assets that's deployed in the MCD.19:58So firstly, we need to log into the MCD dashboard. So now MCD is managed through the security cloud control platform. So as you may know, security Cloud control is a centralized platform which can help us to.20:17To manage multiple Cisco security products, including the MCD, the CDF MC, the secure workload, the AI defense, the hyper shield, as well as the secure access solution.20:37So now we can manage all these products in one unified dashboard. So for those of you in case if you haven't have the the MCD account, and if you want to test the MCD features for your public clouds.20:53You can go to this website and request a few trial account for the MCD.21:13Okay, and after we get our MCD account and we complete the account provisioning in the SCCC platforms, and then we can we can we can see the dashboard for the multi cloud.21:21Defense.21:41Okay, so MCD provides the easy setup widget. So this is actually a very powerful setup widget that can help us to complete all the MCD deployment. So firstly, we need to integrate with AWS with the.21:42Public cloud.22:02So we click on the step one to connect the accounts, and we can choose the one that you are using in your environment. So here we will take a look at the AWS as an example. So we click on the.22:03AWS and we start the integration. So MCD provides a AWS cloud formation template that can help us to simplify the integration process with the AWS. So we can simply click on launch stack.22:23And this will navigate to the AWS dashboard. So with this AWS Cloud formation template, this will include all the necessary resources for the integration. So we can simply use this template to create any necessary.22:43Resources that require for integration.23:03So we can simply click create stack option to create this template, and based on this feature, it's going to create all the necessary resources for the integration. E.g., such as the IAM roles and permissions such as.23:06Has the SS three bucket and SS three buckets policies and et cetera. So now we can see all these resources has been created automatically in the AWS environment.23:26And one thing I want to highlight here is MCD follows the list of privilege principle. MCD only creates the necessary resources for the integration, it will not create any unnecessary components in the AWS.23:42Okay, and then we can just copy, copy the resources names that's created and paste it to this box. So we enter the account names, we enter the IAM rules settings that just provisioned in the previous step.24:02Be and paste it here and then we can simply hit next and this will complete the entire integration.24:22And immediately we can discover the assets in the AWS environment. As we can see how many instance that we deployed, how many vpcs, subnets and other configurations in the AWS.24:30So, for us to better understand this integration process, so here let's take a look at the 1st demo. So in this demo, I'm going to show you how we can complete the integration by using.24:50In the setup widget just within few minutes.25:09So here we click to connect the accounts and we take the AWS as an example. So this will navigate to the AWS environment, and we can see what resources that is in provisioned through this template.25:13And we can simply click create stack, and this is going to create all the necessary resources for the AWS integration. So after we complete this creation, we can just copy the.25:32Names about the accounts and the settings about the iam's for the controllers, IAM role for the controllers, IAM role for the, the inventory monitor role.25:50And then we hit next, and this will complete the integration and the immediately MCD is able to discover the asset deployed in the AWS environment. As you can see here, these are all the summarized discovered.26:07Three in the AWS environment. So as you can see, this integration process is very simple and very quickly to complete just within few minutes. We can complete the integration.26:27Okay, so after the integration, the next step is we need to collect the the traffic from the AWS so that we can have a better view for all the traffic patterns in the in the public clouds.26:45So here we will go to the step two, which we will enable the traffic visibility. So the configuration is also simple. We can follow the setup widget. We enter the account information, the ranges.27:02And then we can choose which vpcs that we want to collect this traffic from.27:22And then we can, we choose which access three bucket the storage accounts that we are going to store these VPC floor logs. And then, so this can be the accessory bucket, can be the one that we just created in the previous steps or this can be the one.27:29That you're already using.27:49And then we hit next. So this completes the traffic visibility setup. So with this traffic visibility setup, MCD is going to enable the VPC floor logs for the vpcs that we selected.27:52And we will, and MCD will put all those VPC floor logs in the SS three bucket, the storage storage account, and then share these logs to the MCD for further analysis.28:11And then we can see how the traffic pattern looks like for our all AWS deployment. So this is the glob global view for the AWS and we can even see if there's any malicious traffic that.28:28Within the AWS deployment.28:46Okay, so here let's take a look at 2nd demo to better understand about this process. So.28:48We go to the MCD dashboard and then this time we click on the step two. This is enabled traffic with ability. So we choose the public clouds account, the ranges that our VPC deployed, and then we can filter.29:06And.29:26Choose the vpcs that we want to collect the traffic and the logs. And then we choose the SS three storage bucket account, ok? And then we hit next. So MCD is going to collect the VPC floor logs from the SS.29:27Three storage accounts and immediately we can check the the traffic informations within the MCD cloud.29:47So this process may take few minutes to show the data in the MCD. And then, if we go to the topology, and we can see this is the global view of the AWS deployment.29:57And we can for, we can even see if there's any malicious traffic that's detected.30:17So in this case, some of the workload in the AWS environment, they are trying to visit some bad bad IP addresses. So we can see, we can check the detailed informations in the right side about the IP addresses.30:24About the ports and we can also check the detailed logs about this traffic.30:44So here we can even see more details about the deployment, about this workload, and one thing I want to highlight here is if we take a look at the deny, here.30:51Deny sections here, we can see it's showing as false because we only enabled the traffic visibility. We haven't deployed the gateways to specifically block this traffic. So currently we can only see this malicious traffic.31:06So only after we deploy the gateways, we can block the specific, the malicious traffics. And we can also see the summary information about this traffic, the VPC traffic, what are the top workloads that's sending the traffic and what are the.31:26IP addresses that trigger the malicious event. And we can also check the DMS information as well. We can quickly see what are the top domains URLs that our internal workloads are visiting and also the detailed log information.31:46Okay, so this is about the process for the asset visibility. So with this, with the 1st step, we have successfully integrated with the public cloud and we enable the traffic visibility which give us a better understanding about.32:06How the traffic patterns looks like in our public clouds.32:26And next, 2nd step is we are going to deploy the gateways into our public clouds. So this time we will click on the step three to secure the account.32:31So when we deploy the gateways, as I mentioned, there's two type of deployment method. One is the centralized deployment method, which MCD is going to provision a service with PC and put all the deploy.32:51Avoid the gateways within this specific VPC.33:07And all other necessary components such as the load balancers, the transit gateways, that will be automatically deployed within this service VPC. And the application traffic will go through a service VPC and go through the gateways for the.33:12Keep inspection.33:32And 2nd deployment is the distributed deployment where we will put our gateways specifically into each of these application vpcs for dedicated inspection. So here we will take a look at the example of the centralized deployment method.33:33So there's two steps to deploy the gateways. So this 1st step is we need to specify the service VPC. So here we need to give it a name and we need to choose the specific cloud accounts that we want to provision.33:55And the service VPC, as well as the specific region that we want to deploy. And then we also need to give it IP block. So this is used by the service VPC as well as the gateways.34:14And then we need to choose the available zones. So Cisco recognized to deploy, choose two, at least two availability zones for higher availability purpose. So when we choose two availability zones, MCD.34:31Is going to deploy the service VPC and the gateways into these two availability zones.34:51And next we also need to configure the transit gateways. So the transit gateway is like a hub for all the routings handling. So we can choose either to use the existing transit gateways or create a new transit gateway.35:00And then when we click next, this is going to automatically provision the service vpcs and the transit gateway configurations in the public clouds. And then we move to 2nd step, which is to deploy.35:21The MCD gateways. So 1st we choose the accounts and then which the service VPC that we just provisioned. And then we can also choose the instance types as well based on our requirement, and we can choose whether to deploy both.35:40Ingress and the egress gateways.36:00And, and when we choose this gateways, we need to specify the name and associate the initial access control policies so we can firstly associate with like the template access control policy and then create our own and the cluster.36:03And access control policies.36:23For the public clouds. And also the egress gateway, the name, the policy set for egress gateways, and then the IAM rules for the gateways. And then after we hit the next button, it's going to automatically deploy.36:26Play the gateways into our public clouds.36:46So if we go to the AWS environment, we can see here, these are the two gateways that we just deployed with the previous setup widget. And the last step in the MCD for this section is.36:52Is we need to tell the MCD what application vpcs that we want to protect. So this will connect the application VPC, the traffic to the service VPC to the MCD gateways for centralized inspection.37:12Okay, so for better understand about this deployment process, so here let's take a look at the 3rd demo. So we log into the MCD dashboard.37:32And this time we will click on secure your account, and we can choose the deployment method. So e.g., as you can see here, there's two steps that we need to.37:49Complete for the gateway deployment. So 1st is we need to configure the service VPC.38:09So we need to give it a name and choose the specific public accounts that and the ranges that we want to provision this service VPC. And then we need to give it an IP block for VP service VPC and the gateways.38:17And then choose the availability zones for the deployment.38:37So here is about the transit gateway deployment. So it provides us two methods, so we can choose to create a new transit gateway or whether use the existing transit gateway that's deployed in current deployment. So in this case.38:42We are, use, we are creating a new transit gateway.39:02In the public cloud. And after we click on the next, we can see we have successfully provisioned the service VPC and the transit gateways. So 2nd step is we deploy the gateways.39:07So we choose the account, and the service VPC that we just provisioned and we will deploy these gateways within this service VPC. So we may wait a few moments for the service VPC to complete the provisioning.39:23And then we can choose the instance type. So, this is based on our requirements, we can choose which performance type that we want. And we also need to specify the types of the gateways, whether to deploy both ingress and the egress gateway.39:41And then define the name for the gateway, the ingress gateway, the egress gateway, as well as associate the initial access control policies for these gateways.40:01Okay, then we click on the next step. This will complete the deployment of the gateways to the AWS environment. Okay, so if we take a look at the MCD dashboard, if we go to.40:17The service VPC dashboard, we will see this is the VP service VPC that we just provisioned as well as the gateways that's deployed within this service VPC.40:37And we can also take a look at the status of the gateways. So we just provision and deploy these two gateways into the AWS environment and then we can see the current status is due activation.40:51And after a few moments, the status will change to become active. Okay, so now we can see the MCD gateways has become active.41:10Okay, and here we can also check more details about this gateway as well, ok? And the last step is we need to tell the MCD which application vpcs that we want to protect.41:24So here we can filter the application vpcs. E.g., the, the application one VPC. We need to connect it to the service VPC, we need to specify and route the traffic from this application VPC to the.41:41Service VPC. So this traffic will be going through the transit gateways and through the transit gateway to and send to the MCD gateway for centrally processing.42:00And furthermore, we can also choose other application VPC that we want to protect. E.g., the app to VPC and then specify and route the traffic from this application VPC to the service VPC to the.42:17MCD gateway.42:37Okay, so now we have complete this setting of the application VPC connect application VPC to the service VPC. And then if we go to the AWS dashboard, so firstly we can see these are the two gateways.42:39That's we just deployed through the setup widget. So this is automatically deployed in the AWS environment.42:58And if we go to the vpcs, we can also see the settings for the service VPC that we just created. As we can see, this is the service VPC that, that we just created and provision provisioned.43:08And if we take a look at the road tables for our application vpcs, we will see now the application, the traffic from from this app to applications, the traffic will be route to the transit gateways as we.43:27Can see here.43:46So through the transit gateways, the traffic will route to the MCD gateways for central inspection before it's going into the destination. And this is for the application one vpcs. So as we can see also.43:49The route tables has also changed to the our transit gateway for routing as well.44:07Okay, so here if we go to the transit gateways, we can also see this is the transit gateways that we just provisioned through the setup widget. Okay, so finally let's have some test for the traffic. So this is.44:16Is the testing PC within our application VPC, and we are trying to visit the Google.com so we can immediately see this event showing up in the MCD dashboard. And we also try to visit some destination IPs.44:34And we can also immediately see this event logs for this access. And then we try to make some, make some attack. E.g., we try to create some data execution behaviors.44:54And this will trigger the DLP preventions deployed in the gateways.45:15So if we take a look at, this traffic event, we will see this traffic has triggered the DLP event because it is, it has been detected. Some data is exportution behaviors. And then we can see this action is.45:23Denied because we have configured the deployed the gateways and we also configured the policy to prevent this DLP pro the attacks.45:42Okay? So you can immediately see how this, how gateways protecting our traffics. Okay, so this is about the step two. I hope you have a clear better understanding about the gateways, how we deploy the gateway.45:53Is to protect our traffic. And finally, the steps three is we can define and customize our access control policies based on our use case and requirement. So this is the centralized dashboard for the policies.46:13So we can define different role policy rule set for different gateways that's deployed across different public clouds and then we can use this place to centrally manage all the policy set.46:34And this is an example of how a rule looks like. So when we define the rules, we need to specify the type of this rule or whether it's used to inspect the ingress traffic, egress traffic or it's used for the segmentation, the.46:51Who was the inspection.47:10So this diagram shows all the components when we define the rules. E.g., we need to specify the, what traffic that we want to inspect. E.g., whether the HTTP, HTTPS, the SSH, and et cetera.47:13And we need to define the type, whether for the ingress, egress or east to western traffic. And then we need to specify the source, destinations, and also the action for this matched traffic, whether to allow or deny this specific traffic.47:31And finally, we can also apply the advanced security inspection features such as the WAF, the dlps, antivirus, IDS, IPS, and also combining with Cisco's threat intelligence to better detect and prevent those.47:49Non bad traffics.48:09And after we create the policies, we need to save the configuration and apply to the MCD gateways. So MCD provider feature for the rule comparison, it shows the rules that we are going to delete and it also shows what's rules that we.48:13We are going to create and deploy.48:33So this screenshot shows us the comparison be before and after the changes. Okay, and finally we need to apply these rules, policy rules to our MCD gateways. So we go to the gateway and we need to also.48:36Straight the rules specifically for these gateways.48:56Okay, so from here I will jump into a live demo to show you how the, how to configure the MCD policies. So here I'm going to share my whole screen.49:02Okay, so firstly I need to log into the, to the security cloud console. So let me log into this dashboard again. So now we use, as I mentioned, we use a security.49:19The cloud control to manage.49:39The MCD. Okay so we are still accessing to this dashboard ok so now it's logging to this dashboard.49:43Okay, so now we are logging to the security cloud control dashboard. So in the right side, we can see the products that we are managing in the security cloud control. E.g., the firewalls, the multi.50:07Cloud defense. So we go to the multi cloud defense. So as we can see, I have integrated my testing MCD with the AWS environment.50:27If we go to the infrastructure, you can see these are the two gateways that I deployed in my environment. And I also have provisioned the service vpc's configurations and the connect my, the application vpcs to the service.50:41This VPC as well. So now let's go to the policies. So the policy tab panel, this is the place that we configure all the related components for the access control policies. So we go to the policy rule set.51:01So here we can see there will be default MCD policy set that we can just utilize or or take as a reference. And we can then define our customized MCD policies specifically for the egress gateway.51:19And also for the ingress gateways. E.g., for the ingress gateway, so this is how my testing policy looks like. So by default, there will be a rule used to detect the health between the gateways and the MCD controller.51:38And then we can define the rules within this policy. E.g., here I have created a rule that is allowing my remote desktop application. So if we take a look at this rule configuration, we can see, so firstly this is.51:57Ingress, ingress traffic rule.52:17And then we can specify the RDP the service service and the port, and we can specify the source and the destinations, where is our the RDP, the RDP host that we want to visit. And then we can specify.52:22By the actions whether to allow or deny, and then for this incoming RDP traffic, I also want to apply my security inspections for further inspection.52:41E.g., we can apply the IPS, the anti malwares, WAF, the URL filterings, and also the malicious IP inspections for this incoming traffic. And we can also take a look at the egress policy. So this is my testing egress policy.52:56See, so I have created a rule for the outgoing HTTP traffic. So for those traffic, I'm going to inspect whether it is connecting to any better servers, domains, IPs, and I will also apply the.53:16Advancing inspections as well, ok? So this is how the policy looks like. So here, let me go to my testing PC. So here when my testing PC, he's trying to connect some of the malicious websites.53:37I am launching the traffics here and immediately if we go to the investigate, we go to all the events and we will see the event logs here, ok, events logs here.53:57Okay, I think this is this one. So as you can see, this is the, this is the traffic that I am going to visit, and now this has been blocked. This has been blocked because this this has been detected as a malicious accessing.54:15Traffic, ok? So immediately we can analysis this this traffics and the events with our MCD events dashboard. Okay, so these are the policy.54:35Demo that I want to show you. Okay, and here, ok, so I hope you are able still able to see my screen. And finally let's take a look at some.54:52Some key points. Hello Lisa, I think we're not able to see your screen now. Yeah, let me share my slide again. Thank you, Jenny. Thank you. Yeah, yeah. We can see it.55:10Yeah, thank you. So finally, let's take a look at the key points for today's webinar. So today I have introduced a lot for the MCD. So I hope you can have a better understanding about this MCD.55:27Our solution. So basically this is a unified multi cloud network security, platform that we can use to provide the protection for the public clouds such as the AWS, Azure, Google Cloud, and Oracle Cloud.55:47So we can see these are the three key use cases for the, that MCD provide, either the ingress protection, the egress protection as well as the east to west segmentation use case. And I also showed you the entire.56:05Deployment process, how we can utilize the automation feature provided by MCD to quickly complete the MCD deployment within few hours.56:24Okay, and MCD also provide the flexible policies and the architecture deployments mode, which is based on our specific requirements. Okay, and these are some of the references resources for you.56:37Two which includes the introductions for the MCD, also the detail user guide, the ordering guide, the white papers for the MCD introduction.56:56Okay, so from here I will stop sharing and over to our host Jenny over to you Jenny. Thank you very much, Lisa. Let me share my screen now. Thank you very much very much Lisa, just very informative and I think that's a very good.57:08Great presentation. Now it is our Q and A time. If you have any questions, please just type your questions in our Q and A panel. Let me check if we have any.57:28I'm happy to say that currently we do not have any remaining questions, so let me go to our next slide. Okay. So we will have another EIS session on August the 10th, August the 10th, it will introduce the emerging concept of a.57:41Intake identity and how Cisco dual is leading its implementation to enhance security for autonomous AI agents. Let me send the registration URL to you so you can register for our next ERS session using this URL.58:00Oh, I'd like to send this URL to you.58:20Sorry, let me just stop this sharing and send this URL to everyone. Okay, I hope you can see the registration URL for our next ES session.58:47Okay, so, this is the end of today's session. We appreciate your time and attendance. Thank you very much for joining us today. Hope to see you again in our next session. Have a good day. Bye bye.59:04