The compliance engine is an automated tool by Workspace ONE UEM that ensures all devices abide by your policies. These policies can include basic security settings such as requiring a passcode and having a minimum device lock period.
For certain platforms, you can also decide to set and enforce certain precautions. These precautions include setting password strength, denylisting certain apps, and requiring device check-in intervals to ensure that devices are safe and in-contact with Workspace ONE UEM. Once devices are determined to be out of compliance, the compliance engine warns users to address compliance errors to prevent disciplinary action on the device. For example, the compliance engine can trigger a message to notify the user that their device is out of compliance.
In addition, devices not in compliance cannot have device profiles assigned to it and cannot have apps installed on the device. If corrections are not made in the amount of time specified, the device loses access to certain content and functions that you define. The available compliance policies and actions vary by platform.
Compliance Rules can be used to target specific OS versions. This includes major, minor, Rapid Security Response, and patch versions.
For example:
-
Major = iOS 17
-
Minor = iOS 17.1
-
Rapid Security Response = iOS 17.1 (a)
-
Patch = iOS 17.1.1
When using logical operators to evaluate OS version, note that Rapid Security Responses are treated as less than (<) patch versions and greater than (>) minor versions. In the above example, iOS 17.1 (a) is less than iOS 17.1.1 and iOS 17.1 (a) is greater than iOS 17.1.
For more information about compliance policies, including which policies and actions are supported for a particular platform, see the Managing Devices documentation on docs.omnissa.com.
Was this page helpful?