Detection of Device Administrator Permissions

ID: DET0630
Domains: Mobile
Analytics: AN1701
Version: 1.0
Created: 21 October 2025
Last Modified: 12 May 2026

Analytics

AN1701

For Android, detect Device Administrator Permissions from documented management, network, or vetting evidence; treat state queries as periodic observations rather than real-time events. Correlate Application Permission via Android Enterprise DPC / Application Vetting [DevicePolicyManager.getPermissionGrantState(); PackageManager manifest/requested-permission review]; OS API Execution via Application Vetting / Instrumented Dynamic Analysis [Dynamic API/runtime trace: App invokes DevicePolicyManager.resetPassword(), lockNow(), wipeData(), or setCameraDisabled() immediately after Device Admin activation without MDM-initiated policy context or user interaction]. Alert on a sequence or state change inconsistent with the device/app baseline, approved management policy, or expected user workflow; do not infer unobserved API calls, file/process activity, or payload content from management state alone.

Log Sources
Data Component Name Channel
Application Permission (DC0114) android:DevicePolicyManager DevicePolicyManager.getPermissionGrantState(); PackageManager manifest/requested-permission review
OS API Execution (DC0021) mobile:DynamicAnalysis Dynamic API/runtime trace: App invokes DevicePolicyManager.resetPassword(), lockNow(), wipeData(), or setCameraDisabled() immediately after Device Admin activation without MDM-initiated policy context or user interaction
Mutable Elements
Field Description
MDMAdminAllowList MDM agent packages authorized for Device Admin. Any other app receiving Device Admin is anomalous. Derive from MDM enrollment documentation.
AdminActivationWindow Default 10s between Device Admin activation and first admin API invocation. Legitimate Device Admin apps wait for user-initiated admin action.