Agentless FIM: Audited file or directory created

Rule ID

PH_Rule_Change_14

Default Status

Enabled

Description

FortiSIEM agentless file monitoring detected that a file or a directory was created

Severity

MITRE ATT&CK® Tactics

Collection

Collection consists of techniques adversaries may use to gather information and the sources information is collected from that are relevant to following through on the adversary's objectives. Frequently, the next goal after collecting data is to steal (exfiltrate) the data. Common target sources include various drive types, browsers, audio, video, and email. Common collection methods include capturing screenshots and keyboard input.

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

MITRE ATT&CK® Techniques

T1074.001

Data Staged: Local Data Staging

Adversaries may stage collected data in a central location or directory on the local system prior to Exfiltration. Data may be kept in separate files or combined into one file. Interactive command shells may be used, and common functionality within cmd and bash may be used to copy data into a staging location.

https://attack.mitre.org/techniques/T1074/001

T1565.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/001

Impacts

Server

Data Source

Any Device Agentless FIM via SSH

Detection

Correlation

Remediation Guidance

Make sure it is an authorized change

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.

FileCreate

SubPattern Definitions

SubPattern Name: FileCreate

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_DEV_MON_CUST_FILE_CREATE"

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

hostName, fileName, user, fileAccess, hashCode

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 = FileCreate.hostName,
 fileName = FileCreate.fileName,
 user = FileCreate.user,
 fileAccess = FileCreate.fileAccess,
 hashCode = FileCreate.hashCode

FortiSIEM Rules