Potential File Transfer via Certreq

Identifies Certreq making an HTTP Post request. Adversaries could abuse Certreq to download files or upload data to a remote URL.

Elastic rule (View on GitHub)

  1[metadata]
  2creation_date = "2023/01/13"
  3integration = ["endpoint", "windows", "system", "m365_defender", "sentinel_one_cloud_funnel"]
  4maturity = "production"
  5updated_date = "2024/10/15"
  6min_stack_version = "8.14.0"
  7min_stack_comments = "Breaking change at 8.14.0 for the Windows Integration."
  8
  9[transform]
 10[[transform.osquery]]
 11label = "Osquery - Retrieve DNS Cache"
 12query = "SELECT * FROM dns_cache"
 13
 14[[transform.osquery]]
 15label = "Osquery - Retrieve All Services"
 16query = "SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"
 17
 18[[transform.osquery]]
 19label = "Osquery - Retrieve Services Running on User Accounts"
 20query = """
 21SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE
 22NOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR
 23user_account == null)
 24"""
 25
 26[[transform.osquery]]
 27label = "Osquery - Retrieve Service Unsigned Executables with Virustotal Link"
 28query = """
 29SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,
 30services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =
 31authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'
 32"""
 33
 34
 35[rule]
 36author = ["Elastic"]
 37description = """
 38Identifies Certreq making an HTTP Post request. Adversaries could abuse Certreq to download files or upload data to a
 39remote URL.
 40"""
 41from = "now-9m"
 42index = [
 43    "winlogbeat-*",
 44    "logs-endpoint.events.process-*",
 45    "logs-windows.forwarded*",
 46    "logs-windows.sysmon_operational-*",
 47    "endgame-*",
 48    "logs-system.security*",
 49    "logs-m365_defender.event-*",
 50    "logs-sentinel_one_cloud_funnel.*",
 51]
 52language = "eql"
 53license = "Elastic License v2"
 54name = "Potential File Transfer via Certreq"
 55note = """## Triage and analysis
 56
 57### Investigating Potential File Transfer via Certreq
 58
 59Certreq is a command-line utility in Windows operating systems that allows users to request and manage certificates from certificate authorities. It is primarily used for generating certificate signing requests (CSRs) and installing certificates. However, adversaries may abuse Certreq's functionality to download files or upload data to a remote URL by making an HTTP POST request.
 60
 61This rule identifies the potential abuse of Certreq to download files or upload data to a remote URL.
 62
 63> **Note**:
 64> This investigation guide uses the [Osquery Markdown Plugin](https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html) introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 65
 66#### Possible investigation steps
 67
 68- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 69- Identify the user account that performed the action and whether it should perform this kind of action.
 70- Contact the account owner and confirm whether they are aware of this activity.
 71- Investigate other alerts associated with the user/host during the past 48 hours.
 72- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
 73- Examine the details of the dropped file, and whether it was executed.
 74- Check the reputation of the domain or IP address used to host the downloaded file or if the user downloaded the file from an internal system.
 75- Examine the host for derived artifacts that indicate suspicious activities:
 76  - Analyze the file using a private sandboxed analysis system.
 77  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
 78    - Attempts to contact external domains and addresses.
 79      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process's `process.entity_id`.
 80      - Examine the DNS cache for suspicious or anomalous entries.
 81        - $osquery_0
 82    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
 83    - Examine the host services for suspicious or anomalous entries.
 84      - $osquery_1
 85      - $osquery_2
 86      - $osquery_3
 87  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 88
 89### False positive analysis
 90
 91- This activity is unusual but can be done by administrators. Benign true positives (B-TPs) can be added as exceptions if necessary.
 92
 93### Response and remediation
 94
 95- Initiate the incident response process based on the outcome of the triage.
 96- Isolate the involved host to prevent further post-compromise behavior.
 97- If the triage identified malware, search the environment for additional compromised hosts.
 98  - Implement temporary network rules, procedures, and segmentation to contain the malware.
 99  - Stop suspicious processes.
100  - Immediately block the identified indicators of compromise (IoCs).
101  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
102- Remove and block malicious artifacts identified during triage.
103- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
104- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
105- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
106- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
107"""
108references = ["https://lolbas-project.github.io/lolbas/Binaries/Certreq/"]
109risk_score = 47
110rule_id = "79f0a1f7-ed6b-471c-8eb1-23abd6470b1c"
111severity = "medium"
112tags = [
113    "Domain: Endpoint",
114    "OS: Windows",
115    "Use Case: Threat Detection",
116    "Tactic: Defense Evasion",
117    "Tactic: Command and Control",
118    "Tactic: Exfiltration",
119    "Data Source: Elastic Endgame",
120    "Data Source: Elastic Defend",
121    "Data Source: System",
122    "Data Source: Microsoft Defender for Endpoint",
123    "Data Source: Sysmon",
124    "Data Source: SentinelOne",
125]
126timestamp_override = "event.ingested"
127type = "eql"
128
129query = '''
130process where host.os.type == "windows" and event.type == "start" and
131 (process.name : "CertReq.exe" or ?process.pe.original_file_name == "CertReq.exe") and process.args : "-Post"
132'''
133
134
135[[rule.threat]]
136framework = "MITRE ATT&CK"
137[[rule.threat.technique]]
138id = "T1105"
139name = "Ingress Tool Transfer"
140reference = "https://attack.mitre.org/techniques/T1105/"
141
142
143[rule.threat.tactic]
144id = "TA0011"
145name = "Command and Control"
146reference = "https://attack.mitre.org/tactics/TA0011/"
147[[rule.threat]]
148framework = "MITRE ATT&CK"
149[[rule.threat.technique]]
150id = "T1218"
151name = "System Binary Proxy Execution"
152reference = "https://attack.mitre.org/techniques/T1218/"
153
154
155[rule.threat.tactic]
156id = "TA0005"
157name = "Defense Evasion"
158reference = "https://attack.mitre.org/tactics/TA0005/"
159[[rule.threat]]
160framework = "MITRE ATT&CK"
161[[rule.threat.technique]]
162id = "T1567"
163name = "Exfiltration Over Web Service"
164reference = "https://attack.mitre.org/techniques/T1567/"
165
166
167[rule.threat.tactic]
168id = "TA0010"
169name = "Exfiltration"
170reference = "https://attack.mitre.org/tactics/TA0010/"

Triage and analysis

Investigating Potential File Transfer via Certreq

Certreq is a command-line utility in Windows operating systems that allows users to request and manage certificates from certificate authorities. It is primarily used for generating certificate signing requests (CSRs) and installing certificates. However, adversaries may abuse Certreq's functionality to download files or upload data to a remote URL by making an HTTP POST request.

This rule identifies the potential abuse of Certreq to download files or upload data to a remote URL.

Note: This investigation guide uses the Osquery Markdown Plugin introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.

Possible investigation steps

  • Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
  • Identify the user account that performed the action and whether it should perform this kind of action.
  • Contact the account owner and confirm whether they are aware of this activity.
  • Investigate other alerts associated with the user/host during the past 48 hours.
  • Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
  • Examine the details of the dropped file, and whether it was executed.
  • Check the reputation of the domain or IP address used to host the downloaded file or if the user downloaded the file from an internal system.
  • Examine the host for derived artifacts that indicate suspicious activities:
    • Analyze the file using a private sandboxed analysis system.
    • Observe and collect information about the following activities in both the sandbox and the alert subject host:
      • Attempts to contact external domains and addresses.
        • Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process's process.entity_id.
        • Examine the DNS cache for suspicious or anomalous entries.
          • $osquery_0
      • Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
      • Examine the host services for suspicious or anomalous entries.
        • $osquery_1
        • $osquery_2
        • $osquery_3
    • Retrieve the files' SHA-256 hash values using the PowerShell Get-FileHash cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.

False positive analysis

  • This activity is unusual but can be done by administrators. Benign true positives (B-TPs) can be added as exceptions if necessary.

Response and remediation

  • Initiate the incident response process based on the outcome of the triage.
  • Isolate the involved host to prevent further post-compromise behavior.
  • If the triage identified malware, search the environment for additional compromised hosts.
    • Implement temporary network rules, procedures, and segmentation to contain the malware.
    • Stop suspicious processes.
    • Immediately block the identified indicators of compromise (IoCs).
    • Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
  • Remove and block malicious artifacts identified during triage.
  • Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
  • Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
  • Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
  • Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).

References

Related rules

to-top