Windows Process with deleted binaries

Rule ID

PH_Rule_OSQ_WIN_2

Default Status

Enabled

Description

Detects a running Windows processes whose binaries have been deleted from disk. This is related to MITRE Technique Indicator Removal (T1070) and Tactic File Deletion (004)

Severity

MITRE ATT&CK® Tactics

Defense Evasion

Defense Evasion consists of techniques that adversaries use to avoid detection throughout their compromise. Techniques used for defense evasion include uninstalling/disabling security software or obfuscating/encrypting data and scripts. Adversaries also leverage and abuse trusted processes to hide and masquerade their malware. Other tactics’ techniques are cross-listed here when those techniques include the added benefit of subverting defenses.

https://attack.mitre.org/tactics/TA0005

MITRE ATT&CK® Techniques

T1070.004

Indicator Removal on Host: File Deletion

Adversaries may delete files left behind by the actions of their intrusion activity to minimize the adversary's footprint. Tools such as cmd functions such as DEL, secure deletion tools such as Windows Sysinternals SDelete, or other third-party file deletion tools can be used.

https://attack.mitre.org/techniques/T1070/004

Impacts

Server

Data Source

Windows osquery windows_processes_with_deleted_binaries via FortiSIEM Agent

Detection

Correlation

Remediation Guidance

No remediation guidance specified

Time Window

If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.

300 seconds

Trigger Conditions

If the following defined pattern/s occur within a 300 second time window.

Filter

SubPattern Definitions

SubPattern Name: Filter

This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.

SubPattern Query

This is the query logic that matches incoming events

eventType = "PH_OSQUERY_WIN_RUNNING_PROC_DELETED" AND totalNum >= 1

Group by Attributes

This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID

reptDevName,procName,procId

Aggregate Constraint

This is most typically a numerical constraint that defines when the rule should trigger an incident

COUNT(*) >= 1

Incident Attribute Mapping

This section defines which fields in matching raw events should be mapped to the incident attributes in the resulting incident.

The available raw event attributes to map are limited to the group by attributes and the aggregate event constraint fields for each subpattern

 hostName = Filter.reptDevName,
 procName = Filter.procName

FortiSIEM Rules