Compliance management in HexnodeSolved

@timo-liam ,there’s a section specifically reserved for creating compliance policies through Hexnode UEM. There are pre-defined polices that contain a set of rules and regulations that determine the state of compliance of the devices. For instance, using these policies you can mark devices as non-compliant if they satisfy/violate conditions such as the by the removal of MDM app/profile, device inactivity, jailbreaking etc.  

That really clears things up, @skylar-a . I do have one more question though about creating compliance policies. While configuring them, I noticed there are two different settings: Basic and Advanced.

What is the exact difference between these two? 

@timo-liam , that’s a great question! When you create custom compliance policies in Hexnode (instead of relying on the default ones), you’ll find two settings: Basic and Advanced. Basic settings are a set of predefined compliance checks that are quite straightforward to configure. These include conditions such as the MDM app or profile being removed from the device, the device becoming inactive, or the device not being encrypted. If any of these settings are enabled and a device fails to meet them, the device will automatically be marked as non-compliant. 

Advanced settings, on the other hand, give you much more flexibility and granular control. You can create your own rules by selecting specific attributes and combining multiple conditions with logical operators like AND/OR. This allows you to build more complex compliance rules like for example, verifying whether the Hexnode agent app on a device is the required version, checking if the device is connected to a trusted Wi-Fi network, and ensuring it’s running the latest OS version, all at the same time. The available attributes and conditions will vary depending on the device platform, so there’s plenty of room for customization. 

In short, Basic settings are quick, predefined checks, while Advanced settings let you tailor compliance rules to fit more detailed requirements.  

 For the full list of available configurations while define compliance policies, I’d recommend checking our help docs. 

@kylian_parker , so basically: Basic = simple checks, Advanced = custom rules with more control.

 You’re spot on there, @timo-liam .