Coro Cybersecurity received an AAA Rating from SE Labs for Enterprise Advanced Security Protection. Read the report
Coro Cybersecurity

How to manage your device security policies with Coro, simply

May 17, 2023

As an IT professional, you know that managing the posture policies of the devices in your organization can be a daunting task. With so many devices and users to account for, it can seem impossible to ensure that everyone is following security protocols. Coro makes it easy for you, thanks to device grouping with labels.

Creating labels (introduced in v1.9.2) is easy and intuitive. On May 14 we launched version 2.0 of the Coro Console. One of the major changes we made impacts how admins can use the device labels feature more effectively to ensure the right policies are applied to the right set of devices. In this post, we will walk you through some of the ways you can use the labels feature.

Custom labels

As before, you can add labels from the Control Panel. Go to the Labels tab from the Devices area.

You can easily add and remove devices from your custom labels directly from the Devices page. Simply select the device from the Devices list, select Actions, and click Add label.

Click the Name field to choose the label to be applied to the device or devices.

You can add multiple labels to each device and you can apply labels to multiple devices at once.

Pre-defined labels

With the v2.0 release, we've now also added pre-defined labels. Pre-defined labels automatically group together devices by Windows PC, Windows Servers, and macOS.

Keep in mind, these default labels cannot be changed. But of course, you can create your own labels, so you can manage devices however suits your processes best.

Apply policies by label

Once you've set the custom labels, you can use the groupings to apply device settings and device posture policies to that specific set of devices. This gives admins greater control over how their defined policies are applied across different devices.

For example, enabling Development mode for a device can expose it to higher risk, but developers might need this capability for their job. Therefore, while an admin might want to enforce device passwords for all devices, Development Mode Enabled may need to be limited to only non-developer devices.

Admins can add labels (both pre-defined and custom) to existing and new policies alike.

For more detailed information about the labels feature and additional updates we've made with this release, check out our release notes for 2.0.

If you have any questions, you can reach out to our support team by emailing [email protected].