BYOD must operate under a Mobile Device Management (MDM) solution with at least these capabilities enabled: the MDM can wipe agency data from a lost or stolen device; if the MDM cannot tell agency data apart from personal data, all data on a lost or stolen device, personal data included, is deleted; the MDM can apply agency security configurations to BYOD devices remotely; the MDM validates device security configurations through a health check before the device may connect to agency systems; devices that are jail-broken, rooted or in violation of settings must be detected and isolated; a jail-broken device is not allowed to access agency resources; access to agency resources stays limited until both the device and the user fully comply with policy and SOPs; auditing and logging are turned on; and SIM card changes are monitored so the device can be remotely blocked and wiped after theft or compromise.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.