84 lines
4.3 KiB
JSON
84 lines
4.3 KiB
JSON
{
|
|
"type": "bundle",
|
|
"id": "bundle--65cb5e5e-7ffd-45e7-baa7-c47dd86c9ddb",
|
|
"spec_version": "2.0",
|
|
"objects": [
|
|
{
|
|
"type": "x-mitre-analytic",
|
|
"id": "x-mitre-analytic--83b759ca-097c-4d9f-926b-fb41e0740644",
|
|
"created": "2025-10-21T15:10:28.402Z",
|
|
"created_by_ref": "identity--c78cb6e5-0c4b-4611-8297-d1b8b55e40b5",
|
|
"revoked": false,
|
|
"external_references": [
|
|
{
|
|
"source_name": "mitre-attack",
|
|
"url": "https://attack.mitre.org/detectionstrategies/DET0675#AN1776",
|
|
"external_id": "AN1776"
|
|
}
|
|
],
|
|
"object_marking_refs": [
|
|
"marking-definition--fa42a846-8d90-4e51-bc29-71d5b4802168"
|
|
],
|
|
"modified": "2026-03-04T23:46:03.218Z",
|
|
"name": "Analytic 1776",
|
|
"description": "Defender correlates an application gaining/retaining fine or background location capability with subsequent location sensor sessions that occur while the app is backgrounded or the device is locked, followed by repeated location reads at a periodic cadence and near-term outbound connections to domains not typical for fleet navigation/MDM services, indicating covert location tracking.",
|
|
"x_mitre_modified_by_ref": "identity--c78cb6e5-0c4b-4611-8297-d1b8b55e40b5",
|
|
"x_mitre_deprecated": false,
|
|
"x_mitre_version": "1.1",
|
|
"x_mitre_attack_spec_version": "3.3.0",
|
|
"x_mitre_domains": [
|
|
"mobile-attack"
|
|
],
|
|
"x_mitre_platforms": [
|
|
"Android"
|
|
],
|
|
"x_mitre_log_source_references": [
|
|
{
|
|
"x_mitre_data_component_ref": "x-mitre-data-component--9bde2f9d-a695-4344-bfac-f2dce13d121e",
|
|
"name": "android:logcat",
|
|
"channel": "Application invokes LocationManager, FusedLocationProviderClient, or GPS/location sensor APIs"
|
|
},
|
|
{
|
|
"x_mitre_data_component_ref": "x-mitre-data-component--1887a270-576a-4049-84de-ef746b2572d6",
|
|
"name": "EDR:telemetry",
|
|
"channel": "Sustained or high-frequency location sensor access, including background location usage"
|
|
},
|
|
{
|
|
"x_mitre_data_component_ref": "x-mitre-data-component--b1e0bb80-23d4-44f2-b919-7e9c54898f43",
|
|
"name": "android:MDMLog",
|
|
"channel": "Application granted/retaining ACCESS_FINE_LOCATION and/or ACCESS_COARSE_LOCATION; background location capability present (ACCESS_BACKGROUND_LOCATION on Android 10+)"
|
|
}
|
|
],
|
|
"x_mitre_mutable_elements": [
|
|
{
|
|
"field": "LocationSamplingFrequencyThreshold",
|
|
"description": "Defines acceptable rate of location queries before triggering anomaly conditions"
|
|
},
|
|
{
|
|
"field": "BackgroundLocationPolicy",
|
|
"description": "Baseline of legitimate background location usage across applications"
|
|
},
|
|
{
|
|
"field": "LocationToNetworkTimeWindow",
|
|
"description": "Temporal linkage between location access and outbound traffic"
|
|
},
|
|
{
|
|
"field": "UserInteractionWindow",
|
|
"description": "Maximum time since last user interaction before location access becomes suspicious."
|
|
},
|
|
{
|
|
"field": "AllowedLocationApps",
|
|
"description": "Allow-list of expected location-heavy apps (maps, rideshare, fleet apps) for the enterprise device population"
|
|
},
|
|
{
|
|
"field": "DevicePolicySensitivity",
|
|
"description": "Tuning for how aggressively to treat background location permission as risky depending on org policy."
|
|
},
|
|
{
|
|
"field": "AllowedDestinationsBaseline",
|
|
"description": "Baseline of expected domains/IPs for legitimate location services (OEM, mapping SDKs, MDM endpoints) to reduce false positives."
|
|
}
|
|
]
|
|
}
|
|
]
|
|
} |