Organizations have acknowledged Zero Trust to successfully prevent cyberattacks. However, traditional security models and the concept of “all or nothing” has left companies hesitant to begin the Zero Trust journey

Learning Goal: I’m working on a computer science question and need an explanation and answer to help me learn.

Grade (20 points)

A progress report in the form of a PowerPoint. Follow the template I gave you.

Background

Organizations have acknowledged Zero Trust to successfully prevent cyberattacks. However, traditional security models and the concept of “all or nothing” has left companies hesitant to begin the Zero Trust journey. Fortunately, building a Zero Trust architecture is much simpler than it appears. Because Zero Trust is an augmentation of your existing architecture, it does not require a complete technology overhaul. Rather, it can be deployed iteratively while allowing you to take advantage of the tools and technologies you already have.

Zero trust implementation involves a policy of never trusting and always verifying the authenticity and privileges of devices and users, no matter where they are in the network. Implementing zero trust hinges on network access control (NAC) systems and the segmentation of your network according to the areas you most need to protect.

To make Zero Trust a true end-to-end security solution, organizations must design their endpoints to be trusted. However, IT cannot just extremely lock down their endpoints to achieve that level of trust – IT must make sure end-users get a great user experience and can get their jobs done in an efficient, easy, way. Solutions that limit which apps users can use or remove local admin rights will not fly for today’s knowledge workers. Users need a way to use the latest tools and apps, without having IT whitelist every app, website, and service.