AN1790: Analytic 1790
Applications could be vetted for their use of the clipboard manager APIs with extra scrutiny given to application that make use of them.
Analyst context for executives and security teams
This analytic is about reducing mobile data-exposure risk by scrutinizing Android applications that use clipboard manager APIs. For executives and security leaders, the practical issue is that clipboard access can intersect with sensitive business data, credentials, tokens, or copied customer information, so mobile app vetting and policy enforcement need to account for this behavior before apps are approved for enterprise use.
Executive priority
Prioritize this as a mobile application governance and compliance-readiness concern rather than a standalone alerting rule. Leaders should ask whether Android app approval processes, mobile security reviews, and acceptable-use controls identify apps that access clipboard functionality, especially where employees handle regulated data or business-critical credentials on mobile devices.
Technical view
For SOC, mobile security, and IR teams, the validation point is whether Android application inventories and app-vetting workflows expose use of clipboard manager APIs. Because the official object provides no detection logic, teams should treat this as a review requirement: identify applications declaring or using clipboard-related functionality, apply extra scrutiny during approval, and correlate findings with local mobile policy, data-handling requirements, and incident context.
Likely telemetry
- Android application inventory and package metadata
- Mobile application vetting or static analysis results showing clipboard manager API usage
- Enterprise mobility management or mobile device management application approval records
- Mobile security policy exceptions and app allow/block decisions
- Incident response evidence from affected Android devices when clipboard access is relevant
Detection direction
- Validate that mobile app review tooling can identify Android applications that use clipboard manager APIs.
- Tune review workflows so clipboard API usage triggers additional scrutiny rather than automatic blocking, since legitimate applications may use clipboard features.
- Check for blind spots where personally installed, unmanaged, or unsanctioned Android applications bypass enterprise app-vetting processes.
- Use local business context to decide severity, especially for users or workflows involving sensitive data, credentials, or regulated information.
- Do not treat this object as a complete detection rule; the official detection field is not provided.
Mitigation priorities
- Establish or update Android application approval criteria to include clipboard manager API usage review.
- Require extra scrutiny for applications requesting or using clipboard-related functionality before enterprise approval.
- Use mobile device or application management processes to enforce approved-app lists where appropriate.
- Document review outcomes and exceptions to support audit and compliance evidence.
- During incidents, include clipboard-capable applications in the mobile application triage scope when relevant to the case.
Analyst notes and limits
This is a MITRE ATT&CK mobile detection analytic for Android focused on vetting applications that use clipboard manager APIs. There are no supplied tactics, relationships, aliases, or detection implementation details, so the value is primarily in governance, app review, and mobile telemetry validation.
The supplied ATT&CK fields do not provide detection logic, related techniques, adversary use, impact claims, or relationship context. Local mobile inventory, app-vetting capability, and data-handling requirements are required to determine practical risk and control coverage.
Analytic 1790
Applications could be vetted for their use of the clipboard manager APIs with extra scrutiny given to application that make use of them.
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 | e79f48302e67… |
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 AN1790Open 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.