T1137.002 Office Test

sub-techniqueEnterprise

Adversaries may abuse the Microsoft Office "Office Test" Registry key to obtain persistence on a compromised system. An Office Test Registry location exists that allows a user to specify an arbitrary DLL that will be executed every time an Office application is started. This Registry key is thought to be used by Microsoft to load DLLs for testing and debugging purposes while developing Office applications. This Registry key is not created by default during an Office installation. There exist user and global Registry keys for the Office Test feature, such as: * <code>HKEY_CURRENT_USER\Software\Microsoft\Office test\Special\Perf</code> * <code>HKEY_LOCAL_MACHINE\Software\Microsoft\Office test\Special\Perf</code> Adversaries may add this Registry key and specify a malicious DLL that will be executed whenever an Office application, such as Word or Excel, is started.

01

platforms

Platforms this applies to.

WindowsOffice Suite
02

tactics

ATT&CK tactics this technique serves.

03

sub-technique of

The broader entity this sits under.

04

mitigations

ATT&CK mitigations that reduce this.

06

countered by (D3FEND)

D3FEND countermeasures that counter this.

07

NIST CSF 2.0 — areas of relevance (Protect / Detect)

NIST CSF 2.0 areas this most relates to (evidence-ranked).

Derived from MITRE CTID (Apache-2.0) and the NIST 800-53 ↔ CSF crosswalk (public domain). Indicative relevance along the Protect/Detect axis — not a compliance assessment or coverage claim.

08

mitigating controls (10)

Security controls that mitigate this.

09

groups (1)

Threat groups associated with this.

11

source

Where this definition is published.