Detection of Account Access Removal

Technique Detected:  Account Access Removal | T1640

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

Analytics

AN1655

For Android, detect Account Access Removal by correlating analyst-visible device/network evidence and management state; use streaming or batched telemetry only where the documented collector is deployed. Correlate API Calls via Application Vetting / Instrumented Dynamic Analysis [Dynamic API/runtime trace: DevicePolicyManager.resetPassword() or lockNow() or wipeData() called by caller NOT IN $MDMAgentPackageList$]; Application Permission via Android Enterprise DPC / Application Vetting [DevicePolicyManager.getPermissionGrantState(); PackageManager manifest/requested-permission review]; Host Status via Android Enterprise DPC [DevicePolicyManager policy/compliance/security-state queries and SecurityLog events where supported]. 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
API Calls (DC0112) mobile:DynamicAnalysis Dynamic API/runtime trace: DevicePolicyManager.resetPassword() or lockNow() or wipeData() called by caller NOT IN $MDMAgentPackageList$
Application Permission (DC0114) android:DevicePolicyManager DevicePolicyManager.getPermissionGrantState(); PackageManager manifest/requested-permission review
Host Status (DC0018) android:DevicePolicyManager DevicePolicyManager policy/compliance/security-state queries and SecurityLog events where supported
Mutable Elements
Field Description
MDMAgentPackageList MDM agent and approved Device Admin packages. Derive from MDM platform.
LockoutWindow Default 300s between Device Admin API call and device check-in failure.