This course is powered by Sai Buri for teams. Security leaders encounter new workforce challenges daily cyber for teams helps organizations build a cybersecurity enabled workforce to tackle new challenges, handles security incidents and prevent data breaches. If you'd like to learn more and see how other security leaders like yourself
are utilizing Sai Buri for teams,
you can schedule a free demo at the link below or search teams in the navigation bar.
I wanna welcome everybody e appreciate you all
you know being with us for these sessions. Uh,
this session is kind of by popular demand. A lot of you wrote
saying you wanted to go through in more detail the cloud stuff that we've done in the previous course.
Um, even a number of you asking if we could just reprise that. So we thought, Let's let's do that. Now, If you've sat through kind of my pitch on how the perimeter morphs into a distributed virtualized enterprise,
I sit through it again. It's something that you should absorb, and I'd like you to be able to explain this to your senior leadership team. Remember, this is a course in leadership, so not necessarily here to convey
but to help you see how these opinions air Best explained.
So this has sort of the dual purpose here this next hour or so
of not just showing you, you know, the cloud issue, which of course, is important. It's from my whole life doing this,
to give you a feel for how I think these types of things should be explained and convey. Let's just
you come up with your own style, but you should have a style and it shouldn't be bullet points on view graphs
and it shouldn't be excel spreadsheets. It should be that you develop a way to tell a story.
So so again, sort of.
This is a reprise of some material that we've we've done before, not in this session, but you know, the last course that we thought.
But I'm going to go through something. It's a super set
of what we did before, But I think if you haven't seen, I think you're gonna enjoy it, because this is a very different way of looking
and how the perimeter dissolved and what
you really should be building towards when people say what should the enterprise look like this is my answer. So this is an old A T and T building one of my favorite pictures here. That's right. Right after
the, uh, Pearl Harbor,
you can see they're deciding That's the way they want to protect the bank. All these little sandbags air, like all
individual cybersecurity vendors at RSA, I think.
And this guy is standing here in the That's port 80 just kind of walk right in the building and
see how easy to scare, right?
I think e They're trying to protect the glass here from bombs, but it's a beautiful metaphor for how companies protect themselves. A zillion point solutions piled up in front of the building, and that just doesn't work anymore. So I think this question of what happened to the perimeter,
we all know it went away. But how do you explain it like it's a good way to explain the way I usually do it. Just start by
explaining that we all said there was a perimeter and, you know, little electrons try to bounce off the perimeter.
this would be the cover of most audits
that you turned in over the last 20 years where if it was inside the firewall Oh, thank God. It on it. The report it
if it happens outside Oh, that's bad. That could be reportable. And know your stuff that happens inside the company Looks like this. You trusted access is inside the perimeter. And again the
filled in circle has disallowed. Uh, now we all know the preposterous and and go back and look at some of the things that you share both with your team, with customers with regulators, auditors.
And if you have a chart like this is preposterous, it doesn't make any sense. We all know that the inside has to communicate with the outside. Does utterly,
logically, just just ridiculous here. So let's kind of let let's fix the chart here. Let's let's make it more accurate. So this is what you got inside? The first thing we know is you got email. So this idea that you know, back here on the email, but it doesn't give me the kid outside ridiculous.
Well, that's what it really works, that there are
ways to connect out and whether they're just, you know, naked connections or whether use Demark
to try to be careful about what goes in and goes out, and and the fact that, you know, tryingto make sure nobody spoofing your domain or whether you
have a very special arrange of remain, I don't know.
But I guarantee you're connecting outside, right? Your and even if its office 3 65 which we'll get to in a bit,
you know, there's probably going to be some sort of
so that's the first thing. Second, I bet everybody's outsourced stuff,
and it's always, ah, wonder to May when someone tells me where we outsource. But no, we don't let them in. We authenticate hm
and I say where and they say in our data center,
It's like letting somebody into your kitchen to decide if they should be allowed in your house,
right? I have a desk in my kitchen and I said, All right, I'll term if you should be in my house. Step right in. You come in through the front door, you walk through my living room into my kitchen.
Andi, have a table. Aaron, I said, should be allowed in my house. I authenticate you. I mean, that's essentially what we dio
with internally hosted gateways that authenticate outside entities. It's okay. I mean, you can say, Well, I've got a trusted path there and I monitor all right, But I'm just saying you're open, you let them in. And if you say well, I don't do it in the perimeter. Well, that's exactly the point. That's where we're going. In this presentation,
I mentioned office 3 65. That's outside your perimeter.
If you're doing outsourced gateways outside in the cloud that said, you get the point like either you're in or you're out. Which is it?
If you're in, then the packets come in even if you're authenticating. You know, ditto partners, like, if you've got Tier four support for all your switches and networks or whatever the vendor can get in or you've got third parties that you work with,
they're your law firm. Or maybe I don't know,
partners come into also probably through a gateway did literally. Same thing is the outsourcing. In both cases, you might be doing some weird *** like source I p authentication. You know, it might be shutting based on source. I p. I don't know,
but the point is that
um, you're certainly letting with packets in
remote access, right? Everybody wanted wants toe work from home.
you let him work from home.
What are they doing? They're hitting a gateway. Where is that gateway? If it's inside your perimeter, then accesses starting on the outside and hitting a resource on the inside, period. That's just
we're all at 110% working from home. I say 100 and 10 because nobody knows exactly.
it was coming in and out.
Um, I could remember 20 years ago worrying about having 15% of the company able to
work remotely like for a snowstorm or weekends.
Now, that sounds ridiculous. It's Hateley absurd to say 15% got 100.
So again, you're coming from the outside in
If you're a non trivial company, got a bunch about no gateways and don't think you don't even if you're running scans and building maps
trying to do discovery. Um,
if you do that properly and I'm an example of somebody who does that,
you're always finding stuff that someone set up. It's usually not something blatant and stupid. Once in a while it is.
But see something subtle. Um, that gets set up and you find out about these gateways to the outside from a research lab or
who knows what you find these
I and your web. If your webs Yeah, again, I totally get that. You probably host somewhere else, but I'm making a point here that
you're either inside your perimeter, you're out,
your your resource is or either inside your firewall or they're out, and I get the whole thing around ragged edge perimeters and so on. I'll have some more to say about that
towards the end. I've got a little joke that I'm going to share with you. That I think is quite funny. Particularly nowadays, with all the politics going on.
Um, so this is more along the lines of what you got. And when you have this kind of arrangement,
um, you know, with all these different things. Look, look, look. What can happen, Aiken, tie a path here
from this dot to that dot I can come in through the outsourcing gateway, and we would call that lateral traverse ALS,
like some of you might refer. That is East, west.
If I crossed the boundary. We call that north, south,
on the east, west being the designation.
So you can explain that sort of thing pretty comfortably to finance Team Thio
even to the biggest Luddite on the planet. Concede these little bubbles and get a general sense of what this means.
You know, this is in essence, explains what happened. And you can explain a p t in this context that when these lines happen slowly and when I dwell once I land somewhere maybe for days, months dare I say even years where p the persistent means you dwell.
Then you know I couldn't go through this very slowly and you may not notice I tiptoe in and out
the way of explaining it because when they ask you well, how does it happen? You can show Well, maybe somebody got I don't do DIY, Mark or I don't properly authenticate email and then some jerk clicks on a fish and you know, it's traversed across the records. And maybe I'm not doing the reverse proxy or something where I've got
your elf filtering or
categorizing Internet sites,
you know, for outbound egress type access.
If you're just doing these things wrong, then a PT will absolutely happen to you. It's not even a matter of whether it's just a matter of how intensely. Okay,
so what's the result of this? That's your perimeter. All the little cuts in it.
Okay, so when you're talking to,
And they say, What's all this stuff I hear about the perimeter and firewall and so on? This is how I explain it. I think I just did that in 10 minutes.
It's about 12 minutes after Ah, yeah, you act for two minutes
and 10 minutes. Boom. There is
That's what happened. That's why the perimeter is not really ah, perimeter.
So make sense again. I'm not saying that you have to follow how I do it here,
just saying you should have your own way of doing it, and you should be able to explain a topic like this in 10 minutes
with visuals that would be just a Z interesting to somebody who's got a
background in cybersecurity or networking, as it would be for the chairman of your your corporate board, who
can't even turn a lot uh, iPad on
all the same, should be able to communicate with all of them appropriately.
So let's go on. All right, there's the problem. I get there is a problem. So now there's this thing everybody is running around saying zero trust, right?
Forrester coined the term some number of years ago.
I've been given talks on this
for a long time. If you go back and look on YouTube or something, you can see me up in front of a big
describing something I was calling it. The time rings around things that was You're saying you put things at all of us. So, like workloads, you put rings around. It's like micro segmenting. We didn't have the terminology, but that's what I was describing.
And a lot of people much smarter than me back in the back of 18 t where I was thinking these problems through,
um really zero trust
eso Now the question is Well, how do you explain zero trust? What is that? The first off zero. Trust is a condition.
It is not this thing you choose. It's the result of this thing I showed you like when you have this. What that means is that if there's two entities in here, like if I go back and we just picked two entities marketing and records,
well, should they trust each other? No, they shouldn't
because they're both exposed. I don't mean exposed to the outside. I'm exposed everything. There's insiders in here. It's not just out is bad and is good. We've all learned that's just utterly ridiculous. You know this idea that all the insiders could be trusted. If only it's such a 1975 you
of the way and enterprise would operate
and it was wrong. Then there were insiders that shouldn't be trusted then.
So we shouldn't just inherit trust based on
the fact that we sit on the same local area network, that that's a condition. And when we say zero trust, we mean the condition is when you're communicating, you shouldn't inherit
or based on some sort of common hosting
on ah, on a network or local area network or inside a perimeter. However, um incorrectly that perimeters viewed is providing protection. So zero trust is this condition, and I have to do a Charlie C so cartoon, so I wrote this one, Rich Drew. It is one of my favorites.
It's Charlie. There's a hero talking to his manager,
he says. We've implemented zero trust, the manager says. I don't believe you. And Charlie says exactly So that in essence,
is it in a nutshell. This idea that zero trust is the way that we
you know, the remote work and work from home. And by the way, I my shameless plug here I hope you'll by Rich and I did a cartoon boat that I think is
better than download it to your Kindle for five bucks. But here's the idea.
you must self protect.
And I always think of
you know, talking across some tether here.
The astronaut has to be a self contained, self protected entity. The astronauts, not he or she is not in the space station
and similar this other restaurants, not in the space station. They have to self protect their floating out, like on the Internet or wherever, even if they were inside the space station.
If you believe that the space station is, say,
vulnerable to space dust or junk floating, that might remember that movie gravity where if you were inside the space station boom that blows up, you die.
Well, if you're wearing your spacesuit, in theory, you wouldn't die
because you can exist on the inside or outside.
So I sort of like that image of you wear your spacesuit. You're all jacked up. You've got oxygen, you could exist in or out. If you're inside and something happens to the space station, you don't die. If you take your space suit off and you're wearing the NASA shirt in the
and you're eating an apple or something,
boom, you die immediately.
It's a way of thinking about your trust and kind of a completely non technical
of you. But here's maybe something a little bit more gearhead
that you can use. So entities
inherit or rely on trust when the firewall perimeter really does work.
When you really do believe
that the space station is not going to be leaking and there's not going to be something flying through that will kill you,
then we can take off. Our protective rappers and two entities contrast each other, communicate without having to self protect
so you could see share freely but similarly, in our world malware controversies that well, what is zero trust? Zero. Trust is where I don't trust. I have to. Self protect
makes it more difficult from now. Where to traverse. That's it. In a nutshell, it really is not that much more complicated than that.
Now a million things pop up as consequences of this.
not self protect like this was more convenient. I applications could just
connect to each other. I could have a front end and back end.
I could be dealing with some database. Um,
my users can connect to me the server or the reverse
I don't have to worry about, you know, multi factor authentication or any of that stuff. Maybe a little bit, but probably not.
That's spectacularly convenient. Just like it's convenient to take your space suit off
in the space station. I get that,
but this fourth condition here,
it's just gotten too crazy. So when you're talking to an executive to say, this is the way it used to be, Number four used to not be a big deal, so we put up with it.
But now it's a gigantic problem, and we have ran somewhere and all these things that are just terrible.
it's caused an inflection point to be passed
so that it's just the convenience here no longer
running in that mode.
So we run in this mode and also recognizes that
the perimeter is breaking even mawr. It's not even a little leak. It's just a jailbreak because I showed you
so That's kind of a nice way. And these are all the components in a lot of different pieces. In order to implement that, devices have to traverse networks increasingly five g
to hit some sort of cloud, which might be your legacy enterprise. It's cool to think of Legacy Enterprises, the cloud, What's the difference?
If you're running a legacy enterprise and you've got third parties using things that you provide to them saying a portal,
then don't you just look like a cloud service to them?
What's the difference?
So everything becomes device network cloud nap, and then a cottage industry emerges around protecting these entities like, you know, malware security. Yeah, you still need that.
I wanna make sure I have some anti malware on the end point that's why endpoint security so important? But it also be ableto would like to make sure there's malware avoidance, say, at the workload level or container level. That's why people talk about,
you know, different techniques for protecting individual containers or community clusters. Things like that
on DSO on. You see all the different
functional requirements that emerge
when it behoove is you
to build out a way to do zero trust. For all the reasons that we just said
now, one person's asking here, what's a micro segment?
Here's the idea that this is Elaine. Let me share with you my view of how you describe micro segment.
imagine you're a bank
and you have a big network
and you have firewalls that delimit the inside of the bank network from the outside your traditional perimeter business
and someone comes along and says, You know,
when we have breaches
on this side of the bank, let's say it's a commercial banking
Well, it's possible with this lateral traverse ALS thing that Ed was showing us
that over in our consumer banking area
that the threat could East West itself traversed laterally
a breach and commercial into infrastructure supporting
if we take a piece of duct tape
and just duct tape right down the middle of our network and say we have a left half
and a right half of our network and that duct tape will be like by a bunch of Fortinet firewalls or Palo Alto networks?
Um, firewalls, next generation firewalls, and we mediate. Traffic is if they're different companies
and everybody was Yeah, I think that makes sense.
Figure out what the traffic would be beheaded, um, emailing. But whatever, you you split the place in two.
If we refer to each of those pieces as a segment,
what I've done is I've taken a network and enterprise monolithic enterprise into two segments.
Now, let's say that works out well. And you think, Well, if I did it once
commercial banking I Assad wealth management,
could we break that off? So now you think the duct tape with Palo Alto or Fortinet or somebody and you
segment off wealth management. Now you got three segments
and you're falling in love with this. This is great. You're stopping the a p T lateral traverse ALS
when you can take that to its logical extremes. The segments get smaller
and we refer to them as micro segments. Now, would you do that in a legacy enterprise? Probably not.
You pick these things up and throw them, scatter the men's cloud workloads, and that's micro segmentation. And I'm going to show you how to do that. That's a good segue to exactly where we're going with this presentation. So, Lane, thanks for the
that very nice question. Um,
what do you dio? So this is where I left you. E left you with this. These are the problems. All these
little cuts that were there, and I showed you You got these? Email, Web unknown gateways, outsource partner. Remote access. Right. There's no
mystery here. These air the gateways through which you have to allow traffic and through which,
um, access is granted and through which malware confined its way into your enterprise. So let's put some stuff in there. I'm being generic now, saying for assets,
just sticking them inside. And it's like the astronaut inside the space station
where the space station is leaky and you can't trust that there's oxygen.
So you have to keep your spacesuit on. That's what we're gonna assume in this case. They don't have their space suit on and they die. So something's wrong. I'm just gonna give myself a little scratch space here thio
toe work so that we can explain this
So first thing I'm going to do is let's let's we talked about outsourcing.
Let's say it's a portal
where all of your outsource vendors go to submit
their invoices to collect purchase orders
to ask questions, tohave
procurement. Anybody who does this in support of another business sing portal.
You know, that's set up. Um,
yes, there may be other
and based beer call center work. Say there's some workload
Women in the cloud like Look, I'm be
Find it is Look at this little thing here. So you were the arrows touching.
That is a firewall rule
that has to allow for bidirectional traffic from Yeah,
I want to move it. Watch what happens to this little cut.
See, that closes. You see this line here closes.
That means that the firewall the perimeter for your enterprise
can be simplified because they don't need to allow this traffic.
This thing is a point of vulnerability from which lateral traverse, aeltus A, B or D could occur when I move it.
That goes away to some degree.
I understand that if there is still communication through this cloud of virtual data center back through some opening here,
that, yeah, there's still some risk. But clearly
lateral traverse. ALS risk
the East West Traverse Aly here will be dramatically reduced.
And the only things that you'd allow into and out of this outsourcing workload would be things that air just clearly designed as interactions with your outsourcing vendors. They open the portal, they do something, they go away.
I'm not gonna allow, you know, any type of it's not email or web or what? It's gonna be just a access or very, very specific about what it is that I'm supporting. And yeah, maybe there's a rest a p I and I'm coming through that I don't know what it would be,
but it would be small. And yes, I have
so in the cloud I have to have some sort of utility.
Whether I'm working with VM ware and using their tools or from using open source cloud software or I'm working with Amazon or Microsoft, all of them
of different security solutions that you can use to protect. Ah, workload in cloud. My Gaza is but must be three or 400 companies right now
that sell solutions to protect
So just do it. So I know that this is you. Go gosh is making it so simple.
Andi. This is what you would show an executive. You'd say we went from being inside to being outside on. We're protecting it locally. I'm not relying on this perimeter anymore. And, yes, there is an opening. You can see that,
but it's a small one.
It's a micro segment, has a very well defined
and minimized interaction with the outside. Let's pick another one email.
Pick the thing up and move it to Microsoft. Their use office 3 65.
Guess what? I don't have to worry about
patching exchange servers anymore.
I don't have to worry about scanning of the lands that were supporting my email service.
I still have to do stuff. Maybe you have tow engage with mine. Castor Proofpoint to do.
You know, filtering on the content. Still stuff you dio.
But I don't have the perimeter risk anymore
of dealing with the service hosting the computers, the
infrastructure, the assets that were sitting inside my perimeter before.
I just have to learn to interact with that workload. As all of you have learned, say, with Gmail or office 3 65. Let's pick another one, partner Gateway
Boom, boom! Move it out. Their micro segment. The thing I noticed when I say cloud BDC the word public didn't show up here once, did it?
I'm not saying this has to be a public cloud. If you're Verizon or if you're a Bank of America or you're the U. S. Department of Defense or something, you could afford to do this right.
You can You can build your own private cloud. I don't care. And you can do it in virtual data centers. I'm just saying
you can't rely on the perimeter to do the protection. This whole thing could be wrapped inside your perimeter and you just make believe it doesn't work.
It doesn't matter how you do it. You just can't. You have talked about zero trust here,
having this workload down here no longer trust this workload, they have to communicate through their respective
exported and imported interface services and through the cloud front, front of the front door.
Email one stucked outsourcing. You do it the way everybody else does it. I don't mutually trust you the way
I was mutually trusting this thing. An email. There was mutual trust was inside here,
no more mutual trust. And there did same thing for partner.
Now let's clean this up. I'm going to do just some basic clean up on the diagram. You know, nothing
that z meaningful in terms of the functionality. Let's do this first.
I'm just taking this and redrawing it,
and I'm going to refer to a legacy enterprise. Almost. It's like another cloud, right? It's got It's got all these firewall rules and notice. When I moved this thing when I went partner to cloud, you see, this rule goes away like I cleaned up some of these rules by just going and moving things out to the cloud.
So now I'm going to draw it this way.
I'm going to get rid of like this. Just some space junk around here. I can draw it this way.
you know, we'll we'll get to fix things. What I want to do first is to show you how we manage each of these little cuts. We're gonna take a detour. We're gonna do policy quickly.
If you say, Well, who's managing all this stuff where you're gonna have to have some workload
that can manage the policy, You're gonna have to have some security function
and you're going to sit it in a virtual data center. And again, there's a dozen products that do that.
You know, it could be some sore thing, or it could be a policy manager. Could be an SDP policy controller, like from a VM ware, for example, does things like R V armor does something like that? VM Where does well so So you get this kind of arrangement where a managing the policy
again. Let's clean that up again. I have to show the cloud there.
I could just call them all assets,
clean that up to look like the other stuff and make them look like nodes. Now let's go back. I did a lot of clicks there.
You also where we got to that right? I just moved that over.
I got rid of that picture. I added a policy controller,
got rid of that ugliness and then just kind of cleaned up the dots so that I say command and control and a bunch of nodes. You know what I mean by a node Now, and note is a workload.
Ah, commanding control is something that, in essence, is there too.
to manage policy and to manage what? The security function. So
here we say, node command and control. And now
you would all say, My gosh, if I draw, you know, take a gun and shoot this thing out, I have a mess. Well, I could do something like fast flux. DNS Does,
um, you know, with a baht net
where if the nodes can all become controllers or if I have multiple controllers, I could make this thing more robust. Right? You don't want a single point of failure here, So you're gonna want multiple C and C notes. That's how we'll draw it. But for now I'll just draw it this way. You get the idea.
So now again, let's just clean up the diagram a little bit.
Get rid of those lines. I don't need that.
Put it somewhere, but put it in good. Put them in good places, connect them up. And that's what I think every
enterprise on planet Earth should look like today. This is what your network should look like.
Now Notice the's dots. Here are not servers inside a perimeter.
This is not a perimeter network. These air like I showed you, I got there these air, all assets that are micro segmented workloads and your whole company becomes just a bunch of workloads
with controllers, workloads and controllers. That's
that's the architecture. Ah, blob of work like here in Toronto, a whole bunch of work
and out here in Australia, a whole bunch of work that za workload.
It could be an application. It could be a set of applications. You define it,
but it's self contained, self protected, and it has no mutual trust with anything. And these red dots are the administrators.
That's where we do command and control.
This is what it looked. Whether I'm talking Thio my graduate students or I'm in Washington talking to a bunch of senators.
This this is what I say. They say, Jesus, your I've been doing this so long
we hear that we shouldn't be doing the architecturally we do it now. What should be I do this picture. I still click through all these dots.
I've done this for senators and I've done it for PhD students. And I don't change the words at all. What I've said to you,
I said command and control, but you get what that is. I snuck in fast flux there. Sorry, I probably shouldn't have
because that that is such a logical connection there.
But I'm just saying a letter. I could understand what I just went there. You don't have to be like some
crazy computer scientists. Now there's more to it here.
let's let's have some fun. It's election time. So
why Why couldn't the Russians find the deleted Clinton emails? Look, this is this is probably gonna make fun of the Democrats a little bit here.
Eso Some of you think that I'm doing this toe make fun of you know who I'm not. This is This is more
poking fun at the in a sense, that
Clinton. So here's what I mean by this.
A global perimeter is different,
then that that's a distributed enterprise. That's a global perimeter meaning. If these air just nodes and this thing in Toronto trust the thing down here in Australia,
then that's exactly what that circle was. This is just different shape than a circle. It's a funny blob,
but it's wrapped geographically and you know that's a that's a global perimeter, not secure. There's lateral traverse, a LRIs cure, a p T.
So if somebody hacks Toronto, then Australia is vulnerable. If somebody hacks of Australia, Toronto's vulnerable. So let's say Toronto peoples in my God, I I wanna fix this. I want a micro segment. I just showed you micro segment means moving it away, right?
Isn't that what we just said?
You take that, you move it away, take that and move it away,
That's what it means.
Well, let's look at the US Department of State.
The the US Department of State
has about 350 embassies, consulates all around the world
and I would argue that they're not the best managed
from a security perspective,
their ambassadors, they're wonderful people. They're capable
there for the most part, when it's not too political,
they're assigned because they have some facility in the region, interest in the region and they usually real dedicated. People are smart,
but they don't wanna listen. Toe Washington the foggy bottom, telling them to pick good passwords and
follow good security. Most of the time they don't
I would say respect for the cyber security teams.
So what tends to happen
on networks such as the U. S State Department
each embassy make security decisions
that are often quite somewhat dubious in in their origin. My favorite story, which I think I shared with you guys. Also tell it again, because I love the story so much. Barbara Bush, who was the wife of the first George Bush president, was going to some embassy to dio like a talk or something,
and she died a. She had, like this, uh,
charity or something that she was doing work with. And I think they made a YouTube video
and the embassy was going to show the YouTube video when she came for the visit.
That's how the story was described to may,
and you can imagine the scene flat screen. Everybody comes in Nice party. Everybody step
being wine or whatever. You having a party like that. She comes in. She's nice, Ladies comes in,
explains what she's doing,
and they show the video that shows her work with, You know, this charity and everybody clapping loudly. Everyone who's listening to me has been to 1000 of those s O just before the event.
At this embassy, the Internet goes down,
the team is terrified
that they're not gonna be able to show the video
And just before the event, a new WiFi network becomes visible
inside the enterprise and they realize they can connect to it
and actually get out to the Internet, where their ISP or whatever I had broken,
so they made the decision. Well, let's connect to that. It's fine. We get to the Internet, get to the end. It's connect so low and be able to connect the embassy to that network.
They show the video, everything goes great, she leaves and then magically, that WiFi network disappears and their Internet service is restored. And I think everybody on the call here knows exactly what probably happens, right. They
that that network was put there,
you know, so that they would connect to it.
And that node was then infected with malware,
you know, Might have been Australia. I don't know. That could be whatever. So if it did happen in Australia,
then up here in Toronto or whatever, whatever is up here Calgary, Toronto
Hillary Clinton, back when she was running a mail server,
the argument was that it was less secure for her to move it out into a separate mail server, and I give them zero credit for doing it to be more secure, moving it out.
This is what she did. She isolated it, which makes it where the Russians couldn't find it. But But the point is,
if she had left it there, if she'd been using the State Department's network,
we all know that the nation states have each other's networks.
It's if you go Google
Russian attacks on U. S. State Department,
you'll see that the Russians have owned the U. S. State Department network for years.
It's like Child's play to break into this network. I just gave you an example of how you might do it.
So if she had left everything on the mail server in the official network, those you supposed Thio
she had gotten hacked.
But by moving it like into some basement in New Jersey or whatever the heck that server waas
I have this image of this nation states saying, Darn it, I can't find it. It's It's just often some crazy place.
And the message there for you is not a political one.
I mean that that explains why you know you haven't seen those emails. Not again. I may. I couldn't care less. That's ancient history.
Think Trump has been talking about it again recently? The emails.
But that's why they're not there because they weren't on the official network. What does that mean? For you? Means perimeters air bad, and it's a good way of showing that this idea of the officially sanctioned safe enterprise wide perimeter is a bunch of rubbish sense of a nonsense that's the worst place to bay.
If you want to be insecure
then go inside the perimeter and just rely on the fact that you live in a gated community. You don't have to lock the doors. You can leave the keys in your car.
It's everything's fine because, gosh, that I live in a community that's gated. And you'd say, Well, what about people who live inside? You go. Yeah, I guess that's a problem. What about people know the code? Oh, yeah, that's problem. What about when the gates left open? Oh, yeah, that's problem. How about when there's a party and I let a bunch of people and oh, yeah, it's from suddenly that gated community doesn't seem so good anymore.
And that's the perimeter.
So look, here's what I've done today.
I've used 45 minutes
to show you how I think you explain this stuff
right? There's no equations here doing math. There's no code.
I also don't think I have any bullet lists. Did you see any bullet lists here anywhere?
Bullet lists of the most evil way
to do a presentation. I guess that counts is sort of a bullet list. Uh, not really.
But look, this is Look, I'll flip through the presentation here
I showed this way. The perimeter degrades all these holes in it. A P. T s. There's the real perimeter. Then we had a little side dish on zero Trust. Then I said, Well, now we're gonna move this stuff around. We outsource with workloads out here, workloads out there
connect to command and control the make of nodes stickum on a geography. And there's the architecture er,
like I love that the flip sort of chart nature of that. The flowing nature of showing a visual on a set of visuals. I think that's the way you should be communicating. So this maybe is much about cybersecurity today, as it is about just the topic of communication
now, as we did last year earlier in the year with all of you.
Um, I do want to pause here and just give you a little bit of a pep talk to the end of our six weeks session. I want to take a few minutes. Maybe some of you have some final questions you might wanna ask.
I think the discipline that we are all part off
really will benefit from all of you
learning to be better executives better leaders. This is a leadership course. It's been a leadership course
where we've downplayed the tech part. We've said
there are these soft skills that air perhaps Justus, important as understanding the technology and coming from a computer. Scientists that are not an easy thing for me to admit,
but these executive skills or things that I hope you'll work on hope. Youll get sort of addicted to reading
leadership books find examples that air inspiring. I think during our last session we read Martin Luther King's
amazing speeches and tried to understand why was he such a leader? And it was because he believed in something when he said, I believe I believe said that over and over again. That's why people followed him,
because a lot of his speeches I I've gone through and he's one of my favorite people ever lived. Found some of his speech is a little dry, but when he talks about what he believes they come toe life will remember. We quoted, you know, 60 years later, so do the same thing like believe in something and and I have your communication,
be part of who you are. That's what ah good leader always.
You know it's sincere and believes in something, and people will follow you if you show them the future will follow. And in cybersecurity we've done a very poor job of that. Think about it. There's a jailbreak in terms of the offense beating the defense. All of you are defenders on. We've not done a good job. We've not distinguished ourselves at all.
elections because we think they could get hacked.
An election is X equals X plus one,
right. We talk about
controlling power plants
and we sort of allow that. But then in election, which we sort of understand, we don't understand power plants,
we say, Oh my God, no. Think all these problems on election is X equals X plus one, and we don't think we can keep that secure.
So what are we even doing here? You can't secure that. What can you secure the answers? You probably can't secure anything, Which is the whole point.
This is why we need to become better at what we do. And you become better leaders, feel better teams advance our discipline and hopefully let the defense start to catch up. with the offense. It's just been a terrible embarrassment.
I think for all of us we should be deeply ashamed of what we've allowed toe happen, you know, with all these packs and all these problems
that come through. So that's kind of my closing statement. Is a couple of little questions here that maybe I'll get Thio. Let's see what the State Department was compromised but set up a honey trap
that the Russian government could look. Yeah, I'm all in favor of deception and traps that might help.
That's certainly something that could work.
Um, it would work better in the context of a micro segmented infrastructure,
but I do think I am a very big fan of deception. Kartik. So I I do agree with that.
Um, there's another one thanking for examples. Another session? Yeah, we'll see how the sessions go. I'm glad you
Any additional questions or comments before? Maybe I turn it back to the nice Sai Buri team for any closing comments they might have.
All right. Well, good. Well, listen, I've enjoyed having you guys in class for six weeks and
and I'll turn it back at the library team has any closing remarks or any administrative points you'd like to make. Now would be a wonderful time for you to go ahead and jump in and and share. So again, Thank you all.