Detection of One-Way Communication

ID: DET0610
Domains: Mobile
Analytics: AN1663, AN1664
Version: 1.0
Created: 21 October 2025
Last Modified: 12 May 2026

Analytics

AN1663

For Android, detect One-Way Communication by correlating analyst-visible device/network evidence and management state; use streaming or batched telemetry only where the documented collector is deployed. Correlate Application Permission via Android Enterprise DPC / Application Vetting [DevicePolicyManager.getPermissionGrantState(); PackageManager manifest/requested-permission review]; Application State via Android Enterprise / EMM [Managed package inventory/status and package metadata]; Network Traffic Content via Enterprise Secure Web Gateway / Proxy [DNS/HTTP(S) inspection or proxy transaction metadata where enterprise decryption/inspection is deployed]. 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
Application State (DC0123) android:EMM Managed package inventory/status and package metadata
Network Traffic Content (DC0085) webproxy:applog DNS/HTTP(S) inspection or proxy transaction metadata where enterprise decryption/inspection is deployed
Mutable Elements
Field Description
ApprovedPlatformApps Apps approved for periodic read access to each platform. News readers (RSS/social), weather apps — legitimate pollers. Unknown apps periodically polling paste/code platforms are anomalous.
PollingIntervalThreshold Default 900s (15 min) maximum interval between fetches to same platform from background. More frequent background polling without user activity = C2 check-in.
CommandProcessWindow Default 30s between platform content retrieval and behavioral change (new connection, file write). Command processing is near-synchronous.

AN1664

For iOS, detect One-Way Communication by correlating analyst-visible device/network evidence and management state; use streaming or batched telemetry only where the documented collector is deployed. Correlate Application Permission via Application Vetting [Code-signing entitlements and Info.plist privacy usage-description keys]; Application State via Apple MDM [InstalledApplicationList / ManagedApplicationList]; Network Traffic Content via Enterprise Secure Web Gateway / Proxy [DNS/HTTP(S) inspection or proxy transaction metadata where enterprise decryption/inspection is deployed]. 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) mobile:ApplicationVetting Code-signing entitlements and Info.plist privacy usage-description keys
Application State (DC0123) iOS:MDM InstalledApplicationList / ManagedApplicationList
Network Traffic Content (DC0085) webproxy:applog DNS/HTTP(S) inspection or proxy transaction metadata where enterprise decryption/inspection is deployed
Mutable Elements
Field Description
ApprovedPlatformApps Apps approved for periodic read access to each platform. News readers (RSS/social), weather apps — legitimate pollers. Unknown apps periodically polling paste/code platforms are anomalous.
PollingIntervalThreshold Default 900s (15 min) maximum interval between fetches to same platform from background. More frequent background polling without user activity = C2 check-in.
CommandProcessWindow Default 30s between platform content retrieval and behavioral change (new connection, file write). Command processing is near-synchronous.