Only reason I ask is that this would be a reason to fail the "SafetyNet Compliance" check...

This feature was added in v 14.3 so its still new to us as well.  I would begin with checking on why the device failed...I have listed our Release Highlights for v 14.3 and a link to the Android SafetyNet guide that may shed some light on the potential reasons for failing the requirements..."Caveat emptor"

SOTI delivers new capabilities as part of the Android Enterprise Recommended (AER) program, including hardened authentication and security checks via SafetyNet, Enterprise Factory Reset Protection to prevent unauthorized setup of company owned devices, and the ability to disable all system UI on kiosk devices.

SOTI MobiControl 14.3 goes beyond AER requirements to deliver additional management capabilities that give organizations more control over their Android devices. A new Agent Delivery Service simplifies how administrators obtain and upgrade OEM-specific Android agents, package installation is now supported on Android Enterprise work profiles, a new profile configuration has been added to schedule the execution of device-side scripts, and the installation of packages can now be restricted to specific time windows."

https://developer.android.com/training/safetynet

Good thing we added a check box to bypass this in the "advance section" when creating an enrollment rule as you have already noticed.

BTW you can also submit a case by e-mailing Support@soti.net.  

Hope this helps,