When defining security policies, it is critical to know who the user is and what their privileges should be based on their role, and whether the device itself or the state of the device at the time of connection is in a known good state. Providing controls around what the user can perform once they are sending traffic to the internet is critical, but it’s easier said than done with traditional security solutions, as it is difficult to implement contextual controls with the desired granularity without introducing massive complexity.
In a previous blog, I wrote about an “out-of-the-box” experience for users, using the Netskope integration with Chrome, that was minimally invasive, yet provided deep contextual control to the administrator. The latest Netskope integration with Google Chrome Enterprise and Verified Access helps take this a step further.
To start, let’s examine what the “out-of-the-box” experience looks like here. First, the security administrator would set up an API connection between the Netskope Security Clou