Zero Trust Architecture 101 - A 5 Minute Explanation

have you seen the endless announcements about organizations being breached and you find yourself trying to figure out what you should do to not end up on the news like these organizations hi I'm William today we're going to talk about a relatively new security architecture that a lot of people are really excited about zero trust before we get into today's topic be sure to subscribe and hit the bell notification so that you're notified when we release future videos ok let's put 5 minutes up on the clock and let's get started talking about zero trust and the zero trust architecture so there's a real problem with how organizations have traditionally designed security systems sometimes we refer to it as the candy bar effect the security has a hard shell and a soft inside once an attacker breaks through the perimeter or the shell they can pivot pretty effortlessly part of the problem is that cloud solutions and SAS or software as a service has completely changed the way our IT infrastructure is built you can't just automatically trust the devices that are inside of your network anymore so zero trust is a new model for designing and thinking about security architecture simply put nothing is trusted until it can prove its trustworthiness and at the same time we bring the security perimeter as close to the individual devices and the services as possible treating every device like it's facing the Internet this is done with micro segmentation gateways so here are a few of the broader your trust principles that you should understand so that you can follow along with the finer details number one there is no longer any such thing as inside the network here's a simple way to think about it act like every device is that a coffee-shop number two trust nothing and verify everything you have to assume that your network has been breached and you want to contain the attackers everything must prove its trustworthiness number three security will need to adapt in real time security policies must be dynamic so that they can change based on insight from data sources for an example should a device to come compromise the policies that allow it to communicate with other devices they should dynamically change and isolate that device now let's talk about some of the finer 0 trust principles first this sort of what we mentioned about trusting nothing and verifying everything to do this we have to do a few things we need to always identify by using a single authentication source something like single sign-on then we want to have the object prove its authorization with multi-factor authentication a second step in next we want to control access using least privilege principles only give access to the minimum needed for an individual to do their job and nothing more we also want to record and log all activities so that we can catch malicious activity early the next big concept in Xero Trust is micro segmentation or micro perimeters IT infrastructure must be segmented and isolated as much as possible and as much as makes sense so for example the marketing team do they need to access the HR department files on the file share most likely not so set rules access control rules different servers etc that enforce this on a similar note if you have an HR teams in different countries they most likely don't need to access each other files micro segmentation can come in many ways be it access control lists share permissions VLANs network segments application proxies etc so that's a 30,000 foot view of Xero trust now let's talk briefly about the process that organizations should take when they decide to move towards a zero trust architecture the first thing that you have to do when you begin implementing zero trust is to define your resources and the surface that you want to secure you need to know exactly what apps software file shares services etc are deployed in your environment this will tell you what you have and what needs to be secured within your environment the next phase is you need to begin mapping the pathways of the process flows and the behaviors that are permissible like the computer and HR department that will access a certain file share for example or the software development team who will maybe possibly use PowerShell commands against certain servers or against other computers and be sure not to forget about the administrative pathways things like admins who need to RDP to certain servers or RDP to certain desktops then once you know what's on your network and who or what accesses or uses what within your in mind then you can begin designing and creating the policies and the rules to enforce them so you may add a policy to one of your micro segmentation gateways to block secretaries from running PowerShell commands against other devices as it's just an example and then the final phase is continuous monitoring of the perimeter or your micro poonam perimeters now because you want to watch for indicators and misuse a compromise or four attackers attempting to do something remember earlier we said that one of the big changes with zero trust is that we assume the attacker is inside the network so recap zero Trust is an architecture as much as it is a philosophy it's really a new way of looking at our networks we never trust we always verify and we assume that the attacker is within our environment this means that we bring the perimeter or the edge as close to the device as possible with micro segmentation gateways and security policies if you need help with the cyber security at your small or medium business feel free to contact us at the link in the description we'll see you next Friday

Channel: SMBSECURE

Views: 2,703

Rating: 4.9230771 out of 5

Keywords:

Id: 5IcZdeNITYk

Length: 5min 26sec (326 seconds)

Published: Fri Jan 31 2020