AN1791: Analytic 1791
Mobile security products may provide URL inspection services that could determine if a domain being visited is malicious. Enterprises may be able to detect anomalous traffic originating from mobile devices, which could indicate compromise.
Analyst context for executives and security teams
This analytic matters because Android mobile devices can become a path for risky or malicious web traffic that may bypass traditional workstation-focused monitoring. The practical value is not the analytic name itself, but whether the organization can see and assess domains visited from managed mobile devices, and whether anomalous mobile-originated traffic can be investigated quickly enough to support incident response decisions.
Executive priority
Security leaders should treat this as a coverage-validation item for mobile security and managed detection programs. Key questions are: do we inspect or log mobile URL/domain activity for Android devices, can we identify traffic that originates from enterprise mobile assets, and can SOC or IR teams use that evidence during a suspected mobile compromise? This is relevant to operational resilience and compliance evidence where mobile access to corporate resources is in scope, but the supplied ATT&CK object does not define a specific tactic, threat actor, or confirmed impact scenario.
Technical view
For SOC, detection engineering, and IR teams, validate whether Android mobile security controls, network monitoring, or mobile device management integrations provide usable URL/domain inspection and anomaly evidence. The official description supports two detection paths: mobile security products may determine whether a visited domain is malicious, and enterprises may detect anomalous traffic originating from mobile devices. Because no official detection logic or relationships are supplied, teams should focus on data availability, device attribution, alert triage workflow, and baselining rather than assuming a ready-made detection.
Likely telemetry
- Mobile security product URL inspection results for Android devices
- Visited domain or URL logs from managed mobile devices, where available
- Network traffic metadata associated with mobile device egress
- Device identity or enrollment context linking traffic to an Android asset
- Security alerts or reputation verdicts for malicious domains
Detection direction
- Confirm that Android mobile traffic is visible and attributable to a device or user; lack of attribution is a major blind spot for investigation.
- Validate whether mobile URL inspection produces searchable logs, alerts, and domain reputation context rather than only blocking locally on the device.
- Tune anomaly detection against expected mobile application and browsing behavior to reduce false positives from normal app background traffic, roaming, or network changes.
- Ensure mobile-originated suspicious domain activity can be correlated with identity, device management, and incident response records.
- Because ATT&CK provides no detection logic for this analytic, avoid treating its presence as proof of coverage; test with approved benign validation methods and local telemetry review.
Mitigation priorities
- Prioritize enrollment and management coverage for Android devices that access enterprise resources.
- Enable or validate mobile security capabilities that inspect or record domain and URL activity when consistent with privacy, legal, and policy requirements.
- Ensure network and mobile telemetry can identify traffic as originating from mobile devices, not just from shared gateways or carrier networks.
- Define SOC triage playbooks for suspicious mobile domain activity, including device owner identification, containment options, and evidence preservation.
- Use findings to inform mobile access policy, incident response readiness, and audit evidence for mobile security monitoring.
Analyst notes and limits
This object is a mobile ATT&CK detection analytic for Android. The official content is high level and describes possible URL inspection by mobile security products and detection of anomalous mobile traffic. No tactics, relationships, aliases, labels, or formal detection logic were supplied, so this take emphasizes program validation and telemetry readiness rather than a specific analytic rule.
The supplied ATT&CK fields do not identify a specific technique, tactic, adversary, campaign, detection query, data source schema, or mitigation. Local architecture, mobile management coverage, privacy constraints, and logging availability are required to determine whether this analytic is actionable in a given environment.
Analytic 1791
Mobile security products may provide URL inspection services that could determine if a domain being visited is malicious. Enterprises may be able to detect anomalous traffic originating from mobile devices, which could indicate compromise.
How security teams should use this page
Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.
All related ATT&CK context
No relationships are available in the current normalized data for this object.
Object version and sync metadata
The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates .
Imported snapshots across ATT&CK releases (1)
| Release | Bundle imported | Object version | Modified | Status | Raw hash |
|---|---|---|---|---|---|
| 19.1 | 1.0 | Current bundle | 00c678a4fa1a… |
Mirrored ATT&CK source object
The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.
External references and citations
MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.
-
[1]
mitre-attack AN1791Open source URL
Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.