Cross-source coverage

T1553.004 / ATT&CK

Subvert Trust Controls: Install Root Certificate

19 rules across 4 sources.

From MITRE ATT&CK 19.2

Adversaries may install a root certificate on a compromised system to avoid warnings when connecting to adversary controlled web servers. Root certificates are used in public key cryptography to identify a root certificate authority (CA). When a root certificate is installed, the system or application will trust certificates in the root's chain of trust that have been signed by the root certificate. Certificates are commonly used for establishing secure TLS/SSL communications within a web browser. When a user attempts to browse a website that presents a certificate that is not trusted an error message will be displayed to warn the user of the security risk. Depending on the security settings, the browser may not allow the user to establish a connection to the website.

Installation of a root certificate on a compromised system would give an adversary a way to degrade the security of that system. Adversaries have used this technique to avoid security warnings prompting users when compromised systems connect over HTTPS to adversary controlled web servers that spoof legitimate websites in order to collect login credentials.

Atypical root certificates have also been pre-installed on systems by the manufacturer or in the software supply chain and were used in conjunction with malware/adware to provide Adversary-in-the-Middle capability for intercepting information transmitted over secure TLS/SSL communications.

Root certificates (and their associated chains) can also be cloned and reinstalled. Cloned certificate chains will carry many of the same metadata characteristics of the source and can be used to sign malicious code that may then bypass signature validation tools (ex: Sysinternals, antivirus, etc.) used to block execution and/or uncover artifacts of Persistence.

In macOS, the Ay MaMi malware uses /usr/bin/security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain /path/to/malicious/cert to install a malicious certificate as a trusted root certificate into the system keychain.

Platforms
Linux · macOS · Windows
Telemetry
WinEventLog:SecurityWinEventLog:Sysmonauditd:SYSCALLauditd:EXECVEmacos:unifiedlogmacos:osquery

How MITRE says to detect it DET0056

Detection Strategy for Subvert Trust Controls via Install Root Certificate.

Windows Analytic 0153

Detection of unauthorized modifications to Windows root certificate stores by monitoring registry keys, certificate installation processes, and creation of new certificate entries not in baseline trusted lists.

  • WinEventLog:Security EventCode=4657
  • WinEventLog:Sysmon EventCode=12
  • WinEventLog:Sysmon EventCode=1

Linux Analytic 0154

Detection of unexpected additions or modifications to system-wide certificate stores or execution of commands adding certificates to trusted stores.

  • auditd:SYSCALL open, write: File modifications under /etc/ssl/certs, /usr/local/share/ca-certificates, or /etc/pki/ca-trust/source/anchors
  • auditd:EXECVE execve: Execution of update-ca-certificates or trust anchor modification commands

macOS Analytic 0155

Detection of malicious certificate installation via monitoring execution of the `security add-trusted-cert` command and modifications to system keychains.

  • macos:unifiedlog Execution of /usr/bin/security add-trusted-cert or keychain modifications to System.keychain
  • macos:osquery query: Enumeration of root certificates showing unexpected additions

SigmaHQ/sigma

10 rules
Detection Severity Format
Cisco Crypto Commands High Sigma
Root Certificate Installed From Susp Locations High Sigma
New Root Certificate Installed Via CertMgr.EXE Medium Sigma
New Root Certificate Installed Via Certutil.EXE Medium Sigma
Root Certificate Installed - PowerShell Medium Sigma
Suspicious Package Installed - Linux Medium Sigma
Suspicious X509Enrollment - Process Creation Medium Sigma
Suspicious X509Enrollment - Ps Script Medium Sigma
Active Directory Certificate Services Denied Certificate Enrollment Request Low Sigma
Install Root Certificate Low Sigma

socfortress/Wazuh-Rules

5 rules
Detection Severity Format
CA trust database updated (T1553.004) High Wazuh XML
Certificate copied to /etc/pki/ca-trust/source/anchors/ (T1553.004) High Wazuh XML
Certificate copied to /usr/local/share/certs (T1553.004) High Wazuh XML
Certificate moved to /usr/local/share/ca-certificates/ (T1553.004) High Wazuh XML
OpenSSL used to generate root certificate and key (T1553.004) Medium Wazuh XML

elastic/detection-rules

3 rules
Detection Severity Format
Attempt to Install Root Certificate Medium Elastic TOML
Root Certificate Installation Medium Elastic TOML
Creation or Modification of Root Certificate Low Elastic TOML

splunk/security_content

1 rule
Detection Severity Format
Windows Registry Certificate Added Undefined SPL

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.