Skip to main content
T1112Defense Evasionmedium difficulty

Modify Registry

Modify Registry (T1112) is a MITRE ATT&CK technique in the Defense Evasion tactic. SOC analysts detect it by monitoring for XDR, SIEM events, behavioral anomalies, and the specific indicators described in this detection guide. Practice detection in SOCSimulator Operations.

XDRSIEM

What is Modify Registry?

Adversaries may interact with the Windows Registry to hide configuration information within Registry keys, remove information as part of cleaning up, or as part of other techniques to aid in persistence and execution. Access to specific areas of the Registry depends on account permissions, some requiring administrator-level access. The entire Registry is not susceptible to manipulation; however, adversaries may use Registry modifications for hiding malicious content, disabling security features, and establishing persistence through run keys and service configurations. Registry keys can store malicious payloads, configuration data for malware, and encoded scripts that are decoded and executed at runtime. Modifying registry settings for security tools, network configurations, and system policies allows attackers to weaken defenses, disable monitoring, and create conditions favorable for their operation. The Windows Registry is a critical target for forensic analysis during incident response, making its manipulation a priority for sophisticated attackers seeking to remove evidence of compromise.

Modify Registry is documented as technique T1112 in the MITRE ATT&CK knowledge base under the Defense Evasion tactic. Detection requires visibility into XDR, SIEM telemetry.

Detection Strategies

The following detection strategies help SOC analysts identify Modify Registry activity. These methods apply across XDR, SIEM environments and can be implemented as detection rules, correlation queries, or behavioral analytics in your security platform.

  1. 1

    Monitor high-value registry key modifications including security policy settings, Windows Defender configuration, audit policy keys, and network configuration settings that attackers commonly modify to weaken defenses.

  2. 2

    Alert on processes writing binary data or encoded content to registry values in unusual locations, as malware frequently stores encrypted payloads in registry keys to avoid writing files to disk where they could be scanned.

  3. 3

    Detect modifications to registry keys that control security-relevant OS behaviors including LSA protection settings, credential guard configuration, and Protected Users security settings that limit attack surface.

  4. 4

    Monitor for registry key deletions in locations commonly used for forensic evidence including ShellBags, MUICache, UserAssist, and other activity tracking registry keys that attackers delete to remove evidence of their presence.

  5. 5

    Track registry modifications through Sysmon Event ID 13 and Windows audit subcategory "Registry" events, correlating changes with the making process and user context to identify unauthorized modifications from unexpected sources.

Example Alerts

These realistic alert examples show what Modify Registry looks like in your security tools. Use them to tune detection rules and train analysts to recognize true positives versus false positives in live environments.

CriticalXDR

LSA Protection Disabled via Registry Modification

Registry modification detected: HKLM\SYSTEM\CurrentControlSet\Control\Lsa\RunAsPPL changed from 1 to 0, disabling LSASS protected process mode. This protection prevents credential dumping tools from reading LSASS memory. The modification was made by a process running with kernel privileges immediately after a suspicious driver was loaded, indicating the attacker disabled this protection specifically to enable subsequent credential dumping with Mimikatz or similar tools.

HighXDR

Malware Payload Stored in Registry for Fileless Persistence

Suspicious registry write detected: HKCU\Software\Microsoft\Windows\CurrentVersion\Notes value set to a 48KB binary blob. Analysis of the blob reveals it is an XOR-encoded PowerShell script that decodes to a post-exploitation framework stager. A companion scheduled task reads this registry value, decodes it, and executes it in memory. This fileless technique stores the payload in the registry rather than on disk to evade file-based detection.

HighSIEM

Security Audit Policy Disabled via Registry

Registry audit detected changes to HKLM\SYSTEM\CurrentControlSet\Services\EventLog disabling multiple Windows Event Log channels including Security, System, and Application logs. These modifications were made at 02:17 AM by the SYSTEM account following a suspicious privilege escalation event. Disabling event logs removes the primary evidence source for reconstructing attacker activity and is a common defensive evasion step before deploying destructive payloads.

Practice Detecting Modify Registry

SOCSimulator provides hands-on training rooms where you investigate real-world attack scenarios including Modify Registry. Build detection skills with zero consequences — free forever.

12,000+ analysts trained
No credit card required

Frequently Asked Questions

How do SOC analysts detect Modify Registry?
SOC analysts detect Modify Registry (T1112) by monitoring XDR, SIEM telemetry for behavioral anomalies and specific indicators. Key detection methods include monitor high-value registry key modifications including security policy settings, windows defender configuration, audit policy keys, and network confi. SOCSimulator provides hands-on practice detecting this technique with realistic alerts.
What security tools are used to detect Modify Registry?
Modify Registry can be detected using XDR, SIEM platforms. XDR tools are particularly effective for this technique because they provide visibility into the defense evasion phase of the attack chain. SOCSimulator simulates all three tool types for hands-on training.
How common is Modify Registry in real-world attacks?
Modify Registry is a well-documented MITRE ATT&CK technique in the Defense Evasion tactic. It appears in threat intelligence reports from multiple security vendors and has been observed in campaigns by various threat actor groups. SOCSimulator includes realistic Modify Registry scenarios based on documented attack patterns, helping analysts build detection intuition.
Can I practice detecting Modify Registry for free?
Yes. SOCSimulator offers free forever access to training scenarios, including Defense Evasion techniques like Modify Registry. You can investigate realistic alerts in guided Operations rooms, build detection skills with SIEM, XDR, and Firewall interfaces, and test yourself under pressure in Shift Mode. No credit card required.
Glossary

What is False Positive? — SOC Glossary

A false positive is a security alert that fires on legitimate, benign activity, incorrectly classifying safe behavior as…

Read more
Glossary

What is EDR? — SOC Glossary

Endpoint Detection and Response (EDR) is a security technology that continuously monitors endpoint activity, recording p…

Read more
Glossary

What is Threat Hunting? — SOC Glossary

Threat hunting is the proactive, human-led process of searching through security telemetry to find hidden threats that e…

Read more
Glossary

What is Log Management? — SOC Glossary

Log management is the process of collecting, normalizing, storing, retaining, and analyzing log data from across the IT …

Read more
Career Path

Detection Engineer Career Guide — Salary & Skills

Detection Engineers build the rules, analytics, and automated workflows that determine what the SOC can see. You transla…

Read more
Career Path

Threat Hunter Career Guide — Salary & Skills

Threat Hunters do not wait for alerts. You develop hypotheses based on threat intelligence and adversary behavior models…

Read more
Tool

XDR Training Console — SOCSimulator

The XDR console in SOCSimulator replicates the investigation workflow of platforms like CrowdStrike Falcon, Microsoft De…

Read more
Tool

SIEM Training Console — SOCSimulator

The SIEM console in SOCSimulator replicates the workflow of enterprise platforms like Splunk Enterprise Security, Micros…

Read more
Comparison

SOCSimulator Vs. Letsdefend — Platform Comparison

SOCSimulator wins on operational realism. You get multi-tool shift simulation with SLA pressure, noise injection, and al…

Read more
Comparison

SOCSimulator Vs. Tryhackme — Platform Comparison

SOCSimulator is the better tool for dedicated SOC analyst preparation. TryHackMe is the better tool for broad cybersecur…

Read more
Glossary

SOC Glossary — Security Operations Terminology

Complete glossary of Security Operations Center terminology for aspiring SOC analysts.

Read more
Feature

Shift Mode — Real-Time SOC Simulation

Practice alert triage under realistic time pressure with SLA timers and noise injection.

Read more

We use cookies to improve your experience and measure usage. Learn more