MITRE ATT&CK T1562.001: Detecting Attempts to Disable Security Tools

· Original article ↗

Summary

A practitioner walkthrough of MITRE ATT&CK T1562.001 explains how to distinguish legitimate security-tool changes from tampering, investigate alerts and process chains, and account for gaps involving kernel drivers and third-party tools.

Key points

  • Attackers may kill endpoint security processes, alter registry settings, or disable logging early in an intrusion to reduce visibility.
  • The article cites RansomHub’s EDRKillShifter using a known vulnerable driver in 2024 to terminate EDR and antivirus processes before a ransomware payload ran.
  • Legitimate security-tool changes are typically tied to documented maintenance or management activity and return to service on an expected timeline; abrupt changes without that context warrant investigation.
  • Direct process or registry tampering and kernel-driver attacks require different detection paths; the article cautions that agent tamper resistance does not necessarily cover driver attacks or third-party tools.
  • The vendor says Symantec CBX Tamper Protection covers its own agent processes, registry settings, and files, and that an attempted tamper triggers a high-severity alert linked to an investigation.
  • Practitioners are advised to inspect the initiating process and its chain, check whether the relevant driver-detection layer is enabled and current, and review agent uninstall controls and exclusions.

Article Details

Defense Focus
Detect and prevent attempts to disable or tamper with security tools, while distinguishing protection of the CBX agent from detection of tampering against third-party tools or kernel-driver attacks.
Detection Methods
  • Review high-severity tamper alerts, including attempts that were blocked.
  • Trace the process chain around the attempt and assess the initiating process and its deployment context.
  • Look for abrupt process termination, registry changes, or file modification attempts against security tools.
  • For kernel-driver attacks, verify that the separate driver-detection layer is enabled and current.
Data Sources
  • Tamper Protection alerts and linked investigations
  • Process-chain and process-initiator telemetry
  • Registry changes, including Sysmon Start and Enable values
  • Security-tool process and file modification activity
  • Kernel-driver detection telemetry
  • Change tickets, maintenance windows, and deployment context
Rule Types
  • Tamper-protection alerting
  • Behavioral detection policies for third-party tool tampering
Platforms
  • CBX
  • Sysmon
Defensive Actions
  • Treat a tamper alert as a significant signal even when the attempt was blocked.
  • Determine whether the action came from an expected management console or patch tool, or from an unfamiliar process without deployment context.
  • Confirm that local administrators cannot stop or uninstall the agent without the configured client password, and that this requirement is enforced fleetwide.
  • Review third-party-tool exclusions and verify exactly what they permit to access or modify on the agent.
  • Ensure another control can detect registry tampering that disables logging in third-party tools.
  • Verify that the separate detection layer for kernel-driver attacks is enabled and current.

MITRE ATT&CK

Threat Actors

Vendors

Products

Tools

Related Articles