Chrome OS Demo: Configuring security settings to manage theft

Chrome OS Demo: Configuring security settings to manage theft


Chrome OS Demo: Configuring security settings to manage theft

In this video, we’ll review some best practices to lock down your fleet. Learn how to ensure your devices remain managed by setting a forced re-enrollment policy, and how to disable a device.


Content

1.24 -> [Music]
4.84 -> in this video we'll review some best
7.88 -> practices to lock down your fleet let's
10.61 -> walk through how to ensure your devices
12.5 -> remain managed by setting a forestry
14.45 -> enrollment policy and how to disable a
16.82 -> device as a chrome administrator you may
19.97 -> be concerned about a bad actor who may
21.89 -> take a corporate device without
23.119 -> permission and tried to factory reset it
25.43 -> and use it for their own purposes
27.17 -> to set a forestry enrollment policy
29.449 -> start by clicking the device's tile on
31.849 -> the home page of the admin console on
33.559 -> the left click on chrome management then
38.69 -> click the device Settings tab like most
41.839 -> chrome policies these settings can be
43.819 -> made at an organizational unit level but
46.309 -> in the interest of making the entire
47.78 -> organization as secure as possible we're
50.389 -> choosing to set the policies at the root
52.309 -> level to be inherited by the child
54.53 -> OU's under enrollment and access changed
57.679 -> the forestry enrollment policy to force
59.749 -> the device to automatically re-enroll
61.609 -> after wiping it's very likely that this
64.189 -> policy is already set this way by
65.96 -> default but it's always a good idea to
68 -> verify it additionally you'll want to
70.579 -> set the verified mode policy to require
73.009 -> verified boot mode for verified access
75.71 -> this will ensure your managed devices
77.99 -> won't be placed in developer mode click
80.929 -> Save next let's reduce risk in case one
86.119 -> of your managed corporate devices
87.469 -> becomes lost or stolen we do this by
90.439 -> disabling a device even though a
92.78 -> username and password is required to
94.82 -> unlock a device and the forestry
96.74 -> enrollment policy prevents its reuse you
99.229 -> have the ability to proactively disable
101.39 -> it altogether use the drop down menu to
104.149 -> navigate to devices to view your manage
106.759 -> devices here you can select the device
109.549 -> in question and choose to disable it
111.35 -> when you do so you'll see a confirmation
113.78 -> dialog box with the option to display
116.03 -> language on the disabled device to help
118.189 -> recover it unlike breaking a device this
121.13 -> option allows you to re-enable it if the
123.109 -> device is recovered now let's take a
125.719 -> look at the user experience upon booting
129.44 -> up the device this is how the
130.819 -> instructions would appear on a disabled
132.739 -> machine
134.59 -> to learn more visit the google chrome
137.269 -> Help Center

Source: https://www.youtube.com/watch?v=Bf8SRkH4tfQ