heroui logo

Windows Non Browser Process Access Browser Cache Dir

Splunk Security Content

View Source
Summary
This Splunk/analytic detects when non-browser processes access local browser cache directories on Windows by leveraging Windows Security EventCode 4663 (Audit Object Access). The search targets ObjectName paths associated with browser caches (Firefox, Chrome/Chromium-based, Edge, Brave) while excluding common legitimate system or user processes. It derives a cache_family from the path (Firefox, Chrome, Edge, Brave, Chromium) and aggregates results by ObjectName, ObjectType, ProcessName, EventCode, and destination host. The rule records first/last access times and reports the observed cache_family and AccessMask. Annotations highlight that such access could indicate staging or extraction of web-delivered content by a non-browser process, potentially for credential or data theft. The analytic storyline is framed as “Browser Cache Smuggling.” The approach requires enabling Windows Audit Object Access (SACL) on targeted directories, with a policy allowing Success and Failure events. Known false positives include legitimate endpoint security tools, backup/forensic utilities, and browser cleanup utilities that may touch browser cache files; these should be distinguished by inspecting the process path, user, access mask, and surrounding events. The detection maps to MITRE techniques such as T1005, T1105, and T1027.006 and is intended for endpoint monitoring on Windows. Git/References and drilldowns provide ways to review specific destinations and correlate risk events over time.
Categories
  • Endpoint
  • Windows
Data Sources
  • Windows Registry
  • Windows Registry
  • Windows Registry
  • Windows Registry
ATT&CK Techniques
  • T1005
  • T1105
  • T1027
  • T1027.006
Created: 2026-11-16