T1553.004

Install Root Certificate

Adversaries may install a root certificate on a compromised system to undermine TLS/SSL trust validation, enabling Adversary-in-the-Middle (AiTM) attacks against encrypted communications. By adding a malicious CA certificate to the system or user trust store, the adversary can intercept HTTPS traffic, sign malicious executables to bypass code signing checks, or spoof legitimate websites to harvest credentials without triggering browser security warnings. This technique has been observed in banking trojans (RTM, Hikit), macOS malware (Dok, Ay MaMi), and supply chain attacks (Superfish). On Windows, certutil.exe is the primary living-off-the-land tool for adding certificates to named stores (ROOT, CA, TrustedPublisher). On macOS, the security binary can add trusted root certificates to the System or login keychain. On Linux, certificates can be dropped into /usr/local/share/ca-certificates/ followed by update-ca-certificates.

Microsoft Sentinel / Defender
kusto
// T1553.004 — Install Root Certificate
// Detects certutil adding certificates to trust stores, suspicious registry writes to certificate stores,
// and process-based certificate installation on Windows endpoints.
let CertUtilAddStore = DeviceProcessEvents
| where Timestamp > ago(24h)
| where FileName =~ "certutil.exe"
| where ProcessCommandLine has_any ("-addstore", "/addstore", "-AddStore", "/AddStore")
| extend TargetStore = extract(@"(?i)(?:-|/)addstore\s+(\S+)", 1, ProcessCommandLine)
| extend CertFile = extract(@"(?i)(?:-|/)addstore\s+\S+\s+(\S+\.(?:cer|crt|p7b|pfx|pem|der))", 1, ProcessCommandLine)
| extend IsRootStore = TargetStore has_any ("ROOT", "TrustedRoot", "AuthRoot")
| extend IsTrustedPublisher = TargetStore has_any ("TrustedPublisher", "Trusted")
| extend SuspiciousPath = CertFile has_any ("\\Temp\\", "\\AppData\\", "\\Downloads\\", "\\ProgramData\\", "\\Users\\Public\\", "C:\\Windows\\Temp")
| extend Severity = case(
    IsRootStore and SuspiciousPath, "High",
    IsRootStore, "Medium",
    IsTrustedPublisher and SuspiciousPath, "High",
    "Low")
| project Timestamp, DeviceName, AccountName, AccountDomain, FileName, ProcessCommandLine,
         InitiatingProcessFileName, InitiatingProcessCommandLine, InitiatingProcessParentFileName,
         TargetStore, CertFile, IsRootStore, IsTrustedPublisher, SuspiciousPath, Severity;
let RegistryCertStore = DeviceRegistryEvents
| where Timestamp > ago(24h)
| where ActionType in ("RegistryKeyCreated", "RegistryValueSet")
| where RegistryKey has_any (
    "\\SOFTWARE\\Microsoft\\SystemCertificates\\ROOT\\Certificates",
    "\\SOFTWARE\\Microsoft\\SystemCertificates\\AuthRoot\\Certificates",
    "\\SOFTWARE\\Microsoft\\SystemCertificates\\TrustedPublisher\\Certificates",
    "\\SOFTWARE\\Policies\\Microsoft\\SystemCertificates\\ROOT\\Certificates",
    "\\SOFTWARE\\Policies\\Microsoft\\SystemCertificates\\AuthRoot\\Certificates"
  )
| where InitiatingProcessFileName !in~ ("svchost.exe", "WmiPrvSE.exe", "TrustedInstaller.exe", "MicrosoftEdgeUpdate.exe", "chrome.exe", "msedge.exe", "firefox.exe")
| project Timestamp, DeviceName, AccountName, ActionType, RegistryKey, RegistryValueName, RegistryValueData,
         InitiatingProcessFileName, InitiatingProcessCommandLine, InitiatingProcessAccountName;
CertUtilAddStore
| union RegistryCertStore
high severity high confidence

Data Sources

Process: Process Creation Command: Command Execution Windows Registry: Windows Registry Key Creation Windows Registry: Windows Registry Key Modification Microsoft Defender for Endpoint

Required Tables

DeviceProcessEvents DeviceRegistryEvents

False Positives

  • Enterprise software deployment (SCCM, Intune, Group Policy) pushing internal CA certificates to trusted stores — typically initiated by svchost.exe or a management agent with a known certificate path under Program Files
  • Developers installing self-signed certificates for local HTTPS development environments (certutil -addstore ROOT localhost.cer from a known dev machine)
  • SSL inspection proxies (Zscaler, Netskope, Blue Coat) requiring client-side root certificate installation as part of authorized security tooling rollout
  • Software installers (antivirus, VPN clients, enterprise applications) that embed certificate installation steps during setup — initiating process will be a signed installer from a known vendor path
  • Browser certificate management (Chrome, Edge, Firefox enterprise policies) making registry-level cert store changes as part of normal operation

Unlock Pro Content

Get the full detection package for T1553.004 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections