Detection of Device Lockout

Technique Detected:  Device Lockout | T1629.002

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

Analytics

AN1652

For Android, detect Device Lockout 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.lockNow(), creates persistent fullscreen overlay (TYPE_APPLICATION_OVERLAY covering full screen), or uses accessibility to block UI interaction — lock or UI-denial API invocation]. 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.lockNow(), creates persistent fullscreen overlay (TYPE_APPLICATION_OVERLAY covering full screen), or uses accessibility to block UI interaction — lock or UI-denial API invocation
Mutable Elements
Field Description
MDMAdminAllowList MDM agent packages only. Any other app with Device Admin or accessibility-based lock capability is anomalous.
LockDurationThreshold Default 60s. Legitimate app-initiated locks (screen timeout) are brief; sustained programmatic lock without user interaction = lockout evasion.