PH_Rule_Change_18
Enabled
FortiSIEM agentless file monitoring detected that a file content is different than its target file
8
Change
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.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/004T1565.001
Data Manipulation: Stored Data Manipulation
Adversaries may insert, delete, or manipulate data at rest in order to manipulate external outcomes or hide activity. Stored data could include a variety of file formats, such as Office files, databases, stored emails, and custom file formats. By manipulating stored data, adversaries may attempt to affect a business process, organizational understanding, and decision making.
https://attack.mitre.org/techniques/T1565/001Server
Any Device Agentless FIM via SSH
Correlation
Make sure it is an authorized change
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.
FileModify
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 = "PH_DEV_MON_TARGET_FILE_CONTENT_CHANGE"
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
hostName, fileName, addedItem, deletedItem, hashCode
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 = FileModify.hostName,
fileName = FileModify.fileName,
addedItem = FileModify.addedItem,
deletedItem = FileModify.deletedItem,
hashCode = FileModify.hashCode