Insider Threat Matrix™Insider Threat Matrix™
  • ID: AF035
  • Created: 08th July 2026
  • Updated: 23rd July 2026
  • MITRE ATT&CK®: T1218T1218.001T1218.002T1218.003T1218.004T1218.005T1218.007T1218.008T1218.009T1218.010T1218.011T1218.012T1218.013T1218.014T1218.015T1059T1059.001T1059.003T1059.004T1059.008T1059.009T1059.013
  • Contributor: The ITM Team

Trusted Tool Misuse

The subject uses applications, binaries, scripts, services, or administrative utilities already trusted or commonly present within the organizational environment to support or conceal an infringement without introducing new software.

 

Trusted tool misuse may involve operating system utilities, command and scripting environments, archive tools, managed browsers, synchronization clients, productivity applications, remote management components, or administrative consoles. Because these capabilities are routinely used for legitimate purposes, the subject’s activity may avoid software installation alerts, application control restrictions, and indicators associated with unfamiliar executables.

 

The anti-forensic significance arises where the subject deliberately selects a trusted capability to reduce detection, obscure intent, or make unauthorized activity appear consistent with normal operational use. Investigators should assess the subject’s role, command-line activity, file access, timing, tool combinations, and surrounding investigative indicators. The execution of a trusted tool should not be treated as inherently suspicious.

 

Example Behaviors

  • Using a signed operating-system binary to execute unauthorized code while avoiding controls focused on unknown executables.
  • Using PowerShell, Windows Command Shell, Terminal, or a Unix shell to collect, copy, encode, alter, or remove information.
  • Using a built-in archive utility to stage sensitive files without installing external compression software.
  • Using an approved browser, synchronization client, collaboration platform, or cloud service to transfer information through activity that resembles routine business use.
  • Using native screenshot, clipboard, print, preview, export, or file-management functions to collect or alter information without specialist tooling.
  • Using a trusted administrative utility or indirect execution pathway to perform unauthorized activity while reducing distinct control violations.
  • Using scheduled tasks, launch agents, login items, shortcuts, or existing automation features to repeat activity without introducing new software.