- Hi, and welcome back to the channel.
I'm Marcus Forrester.
And today's video is all going to be
about zero trust architecture.
And what does zero trust security model shift.
Now first off,
if I'm not gonna extremely right,
it's because we're actually having a heat wave in the UK.
For once it's a whole 16 degrees
and I'm absolutely boiling in this office,
but without further ado, let's get on.
So Zero Trust architecture,
if you don't know where this is, this is quickly
becoming the security model of choice for businesses
which are looking to further secure their systems.
Now
secure trust systems
if you haven't already heard of this term
just means that businesses have removed any type
of trust from their system.
As it says,
they have configured the default environment to be treated
as hostile or public.
Now, this can be especially helpful.
If the traditional load
of IOT devices bring your own devices.
You know, BYO databases, anything like that
it just means that whilst you're working,
whether it's in the office or the home,
or even in the coffee shop
or anywhere external, it just means that your system
and resources are designed to be untrusted by default.
Now you might say, why does this make sense?
The simple reason is as more
and more businesses start reaching out to the Cloud.
There's more people going to interested networks.
So I feel I've got a code subscription model.
It's under system
and environment that you don't trust inherently don't trust.
And it's not something that you control
and maintain or anything like that.
So it's now becoming more
and more common for untrusted systems to be done.
So this is where the zero trust model comes into play.
Now, if we take a traditional network
you'll know that there are firewalls, there are switches.
There's the local area network, the land.
And when you plug in your computer, you get an IP address.
You connect in, you get prompted to log
into a network or an industry you're trusted to have access
to that entire network.
Now for a zero trust model, you plug in your computer.
Your computer is not trusted whatsoever.
Everything in that environment
that network will not trust your computer.
So you have to put additional controls
in place to actually do this.
Now, what will happen is you will
have a computer that goes in.
If you understand the connection to something
you have to attend the kid against it,
your machine or your user account
or both after actually identify themselves.
Yes, we are who we say we are.
We're accessing this, the server on the network
or whichever device on the network attended care
to checks that your systems are up to date.
It's whatever controls and policies are in place.
Your rules are in place said, yes, this is right.
Fine. Go ahead.
Connect is social connection.
Now this happens to everything that you do
on a zero trust network.
Now you're not going to be connecting to your computer.
You're not going to get in problems popping up left, right,
and centre and everything like that
because that would just do your head
in what actually happens is a lot
of the time behind the scenes is you've got rules defined
by the ID department or security department
which actually say, if this machine connects
to this device
meets X, Y, and Z.
So for example, it's fully parched.
It's running this version of windows
or Mac iOS or iOS or Android or anything like that.
It's fully up to date. It's got antivirus installed.
It's been updated in the last 30 days.
Well, hopefully more than the last 30 days
and everything else that meets the health and threshold.
So that's a load in there.
Then you might have two factor authentication
multifactor authentication that you need to
access a certain device or service
or anything like that that goes into there.
And it just goes on like that.
So although you will have to authenticate it
across a lot of stuff, majority of is all done automatically
behind the scenes and goes from there.
Now some of the things you can do is use authentication
and trust of the users
which can be managed through using things
like MDM or mobile device management or health services.
So now that we know a little bit more
about what zero trust is, we need to actually
know how would actually remove the inherent trust
from your network or the local area network
and build the confidence from your user base or your, your.
Your staff and your members
of people who actually use that network.
Now, obviously it's easier to do this on new systems
or systems that had just recently been built
because there's no legacy systems
or anything else built in there.
But for systems that are being well-established have
been used for years and years. All I can say is recommend
take your time plan, plan, plan, talk with the members
of the IT department, your security, HR management
all the users within the business.
Talk to them, see what, what they use
see what the happy with, you know
what systems did they use?
What systems don't they use
what versions of the systems are being used.
You might actually have some old legacy applications
that you didn't realise you were using
and running until they actually go and do this.
And then that could open up a massive can of worms.
So have a look, plan out your whole system.
See what you've got,
design it and go from there.
Now,
what you don't want to do is just do a big bang approach
go in to everything out and you've got right there.
We'll go about zero trust network
and everything just breaks.
What you want to do is go in, start small
start turning the little bits away
and go from there and progress until you've done it.
You know, do little bits
test it, plan it, verify and make sure it works.
Once that's done move onto the next bit and an expert
an expert until you've got an entire environment.
Don't aren't, it's the old zero trust security model.
Now, when you're looking at building a legacy
of zero trust security, as I said before
you're going to have rules and policies
in place to actually verify your computers
and devices that are connecting to it.
Now, what you want to do is actually just tell me these
define them, ideally, possibly set them up as rules
and services.
So you have various roles saying any devices or machines
or uses that connect to
HR or payroll.
And it's kind of that got a misrule in this type of service
or anything like that goes into that one.
Therefore, when you're actually troubleshooting or debugging
anything, let it run in life.
You can actually fill it down to group authentications
and roles and permissions and things like that.
And actually just make your life a lot easier.
If all these users and all these rules not getting access
to something, and they're all best in this one group
of users or devices, then you actually know it's just
this area, this set of rules,
this group permissions or anything
like that, that can actually access that.
It just makes life a lot easier moving forward.
So when you are designing a Zero Trust security model
you should be working against
the following their principles,
which are, know your architecture.
This includes your users, your devices, your services
your data, everything, everything
within your infrastructure.
Know it. Detailed that log it,
document it,
do everything.
Next is
know who uses your service
in your device, identities.
So therefore making sure you know, who is logging in
know what user names are your passwords, your credentials.
Is there any legacy there?
Get all that.
So to get all that documented, have all that in place
then know what the healthy users, the devices
and services are.
So, you know, have you got everything supported?
Is everything in place and go from there, then
use all these policies to authorise the request
to your services.
If you're using policies to say, if X, Y, and Zed goes
against this service, or once access to this, then
you've got a policy that says either yes or no
it can do that.
And then obviously it lastly authenticate
and authorise everywhere.
If you are building a zero trust network and system
you want to make sure that everything that you touch
and access, you're getting authenticate against you
getting verified
that you are who you say you want and go from there.
Now, once you put
all these principles in place
and you've designed your network
and you've seen what's what, and you know
what's in place and you're going to go
started re everything else slowly, hopefully
and then go and put it in place.
And you start building that trust.
and that relationship people are logging in.
Things are working
or authenticating.
You know what you are,
you've got your health policies in place.
And then once you've got all that done, you know
you're going to be in peace of mind that no matter
if anyone breaks in, if a malicious actor got in.
If you got exploited somehow,
you know
somehow managed to get into your system.
You know, for a fact
that someone is not gonna be able to move
into your system and then not really move
across all devices and systems like that
because your system is built as a hostile environment.
So if someone gets
in somehow compromises someone's work station,
that's it.
They can't get any further.
In theory, they can't get any further conduct the systems.
They can't do anything else because every time that computer
like device, that user tries to access something
they have to authenticate against it.
Additionally, it could be the case that
you know, if administrators, actors disabled the antivirus
so they'll get a better foothold on it.
That feels a health policy
in the health rules against your environment.
Therefore, that machine can actually connect
to anything else.
Now, this has been a very quick overview
of what is zero trust, security, monitors
or zero trust architecture is I can't expand
on this a lot more cause it's a massive estate
of things like that.
So if you're interested in it, you know, put some comments
in below the video, let me know what your thoughts are.
Are you already using Zero Trust Models?
If you are Lyft and I,
what your experiences of it,
and what you use to think of it?
And feel free to subscribe the channel for more information
and get notified, click the notification bell
as everyone says in YouTube and go from that.
And yeah, I'll see you next time.
(upbeat music)