PH_Rule_TH_Linux_14
Enabled
Detects attempts to modify file time attributes. Timestomping is an anti-forensics technique to modify the timestamps of a file, often to mimic files that are in the same folder, so that they do not appear conspicuous to forensic investigators or file analysis tools. This requires process monitoring via FortiSIEM Linux agent.
5
Security
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/TA0005T1070.006
Indicator Removal on Host: Timestomp
Adversaries may modify file time attributes to hide new or changes to existing files. Timestomping is a technique that modifies the timestamps of a file (the modify, access, create, and change times), often to mimic files that are in the same folder.
https://attack.mitre.org/techniques/T1070/006Server
Linux Process Monitoring via FortiSIEM Agent
Correlation
No remediation guidance specified
If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.
300 seconds
If the following defined pattern/s occur within a 300 second time window.
Filter
This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.
This is the query logic that matches incoming events
eventType = "LINUX_PROCESS_EXEC" AND procName = "touch" AND swParam REGEXP ("-[amrt]+.*")
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
hostName, user, procName, swParam
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT(*) >= 1
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.hostName,
user = Filter.user,
procName = Filter.procName,
swParam = Filter.swParam