Detection of Microsoft Office Protected View Disablement
Adversaries modify registry keys to disable Microsoft Office Protected View security controls, facilitating the execution of malicious documents.
Attackers frequently modify Windows Registry keys related to Microsoft Office security configurations to impair defensive controls. Specifically, by disabling 'Protected View', threat actors ensure that malicious documents, once downloaded or opened, bypass the sandbox environment designed to restrict code execution from untrusted sources. This technique, observed in campaigns by actors such as Gorgon Group, enables the successful execution of macro-based malware or exploits contained within document files. This behavior is a form of defense impairment that allows an attacker to proceed with malicious activity after initial access, effectively neutralizing a critical layer of defense provided by Microsoft Office security policies.
Attack Chain
- Attacker sends a malicious Office document via spearphishing or direct download.
- Victim receives the document or saves it to a local drive.
- Attacker executes a secondary dropper or script on the host machine.
- Script modifies HKEY_CURRENT_USER registry keys associated with Office Protected View (e.g., DisableInternetFilesInPV).
- The integrity of the sandbox environment is removed by setting the specific registry values to disable safety checks.
- Victim opens the malicious document, which executes macros or embedded code without being restricted by Protected View.
- Final payload (malware) achieves execution and initiates command and control (C2).
Impact
Disabling Protected View significantly lowers the barrier for malware execution on Windows endpoints. Successful exploitation allows for the full compromise of the user session, credential theft, and potential lateral movement within the network. This technique is commonly leveraged as a precursor to ransomware deployment or long-term persistent espionage activities.
Recommendation
Deploy the provided Sigma rule to monitor for registry modifications related to Office security features. Block administrative scripts that attempt to modify these specific keys under HKCU/Software/Microsoft/Office. Monitor for anomalous execution of office-related processes immediately following registry changes to these specific paths.
Immediate actions
Deploy the registry monitoring rule and monitor for the specific keys identified.
Threat Hunt
Search for historical registry set events (Event ID 13) matching Office ProtectedView paths.
Data: Registry modification logs
Mitigations
Use Group Policy Objects (GPO) to enforce Protected View settings and prevent user/script-based modifications.
Defense Impairment
Detection coverage 1
Detect Microsoft Office Protected View Disablement
highDetects changes to Microsoft Office protected view registry keys indicating that the security feature is being disabled.
Detection queries are available on the platform. Get full rules →