Hi, folks. Ed Amoroso here, and I want to give you part three now of our Advanced Cloud Security Architecture, Hybrid Cloud. What we want to do is kind of put the pieces together into what I think should be your enterprise security architecture of the future. Now, let's start with kind of where we left off. We've got five dots here on the screen, a red dot showing C&C, four dots showing our nodes. It's kind of where we left off, and we investigated the hyper resilience property in the last video, and you saw each of these nodes really emerged from workloads that sat in our perimeter to micro segments that we popped out into cloud. And we're just simplifying things. I'm not showing the cloud infrastructure. We don't need to. You understand that that's there. So what we're going to do now is I'm going to just assume that there's a geography behind all of this. Let's put a geographic map right over where our dots are. Doesn't make a lot of sense where I put the dots now, right? The PowerPoint chart just drop some dots in the middle of the ocean, and one in Africa, somewhere, and it's sort of kind of all over. The goal here would be for us to make sure that we've created workloads that can be hosted in places that make sense. So let's now put them in places that make sense. We had a chart here. There's a lot of red dots and blue dots. The red dots are seen in seas. The blue dots here are workloads. They're all individual, micro-segmented components in containers in their own cloud infrastructure possibly with CASB sitting between the user and that workload. That whole concept I'm going to tie together, link it all up into a bunch of different components, where they logically interact, where they've got network connections, and again, they're all isolated segments. And guess what, my friends? This is the enterprise architecture of the future. This is the way it should be set up. Remember the first couple of videos back? In part one, we started by saying we had a big oval, and we put our workloads in it. We had a big round sort of protection around that, but we had to cut a bunch of holes in it because we said the perimeter requires access. So it's not really a perimeter protection. It's just something else with all these holes. And then we move them all out the cloud. We micro-segmented. We put CASBs in. We made it hyper resilient. Now, we've hosted them in logical places around the world and maybe just in one country, maybe it's global. Connect them all up. This is awesome. This is really tracking the way a botnetwork. This is an architecture that has all the resilience characteristics of a botnet. This is not a botnet, clearly. Not like we're stealing compute resources from people's PCs. That's not what this is. But each of the dots here exhibits some of the characteristics, the autonomous behavior, the distribution, the virtualization, hyper resilient, secure communication, honing back and control from a C&C, intermediary from a CASB. These are all the characteristics that we'll be working from over the next few years in building security architectures. I think this gives you a glimpse into where this is all headed. And the answer is B, both are sort of managed by control nodes. I think that gives you an understanding of how there are some differences here between botnets and the architecture. But the same framework exists, distributed, hyper resilient, and I think this is a glimpse into the way things will be in the future. I hope this been helpful. I'll see you in the next video.
