Skip to main content

MDM-09: Mobile Device Geofencing

MDM 7 — High Protect

Mechanisms exist to restrict the functionality of mobile devices based on geographic location.

Control Question: Does the organization restrict the functionality of mobile devices based on geographic location?

General (4)
Framework Mapping Values
CSA CCM 4 UEM-12
CSA IoT SCF 2 IAM-05
NIST 800-207 NIST Tenet 4
Shared Assessments SIG 2025 M.1.2

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to restrict the functionality of mobile devices based on geographic location.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to restrict the functionality of mobile devices based on geographic location.

Level 2 — Planned & Tracked

C|P-CMM2 is N/A, since a well-defined process is required to restrict the functionality of mobile devices based on geographic location.

Level 3 — Well Defined

Mobile Device Management (MDM) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • An Identity & Access Management (IAM) function, or similar function, performs the implementation of access controls for mobile devices that restricts the connectivity of mobile devices from communicating with systems, applications and services.
  • Organization-owned mobile devices are configured to protect data with the strength and integrity commensurate with the classification or sensitivity of the information stored on the device, and conform to industry-recognized standards for hardening (e.g., DISA STIGs, CIS Benchmarks or OEM security guides), including cryptographic protections for sensitive/regulated data.
  • MDM software is used to restrict the data that is stored/processed/transmitted on organization-owned and/ or applicable Bring Your Own Device (BYOD) (e.g., personal devices) across the entire organization.
  • MDM enforces a separate device workspace on applicable mobile devices to separate work-related and personal-related applications and data.
  • Technologies are configured to use cryptographic mechanisms to protect the confidentiality and integrity of information on mobile devices through full-device or container encryption.
  • Mobile devices are configured to restrict the functionality based on geographic location.
Level 4 — Quantitatively Controlled

See C|P-CMM3. There are no defined C|P-CMM4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to restrict the functionality of mobile devices based on geographic location.

Level 5 — Continuously Improving

See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to restrict the functionality of mobile devices based on geographic location.

Assessment Objectives

  1. MDM-09_A01 the functionality of mobile devices is restricted based on geographic location.

Technology Recommendations

Micro/Small

  • ManageEngine Endpoint Central (https://manageengine.com)
  • Microsoft Entra (https://microsoft.com)
  • AWS IAM (https://aws.amazon.com)

Small

  • ManageEngine Endpoint Central (https://manageengine.com)
  • Microsoft Entra (https://microsoft.com)
  • AWS IAM (https://aws.amazon.com)

Medium

  • ManageEngine Endpoint Central (https://manageengine.com)
  • Microsoft Entra (https://microsoft.com)
  • AWS IAM (https://aws.amazon.com)

Large

  • Microsoft Entra (https://microsoft.com)
  • AWS IAM (https://aws.amazon.com)

Enterprise

  • Microsoft Entra (https://microsoft.com)
  • AWS IAM (https://aws.amazon.com)

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.