FortiMail: Malicious Spam File Attachment Found

Rule ID

PH_Rule_FML_Antispam_Malicious_File

Default Status

Enabled

Description

Fortimail Antispam has found a malicious file in the email attachment

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

T1114.001

Email Collection: Local Email Collection

Adversaries may sniff network traffic to capture information about an environment, including authentication material passed over the network. Network sniffing refers to using the network interface on a system to monitor or capture information sent over a wired or wireless connection. An adversary may place a network interface into promiscuous mode to passively access data in transit over the network, or use span ports to capture a larger amount of data.

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

Impacts

Server

Data Source

FortiMail via Syslog

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 = "FortiMail-Antispam-malicious-attachment-file"

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

srcIpAddr,senderMailAddr,receiverMailAddr,fileName,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

 srcIpAddr = filter.srcIpAddr,
 senderMailAddr = filter.senderMailAddr,
 receiverMailAddr = filter.receiverMailAddr,
 fileName = filter.fileName,
 hashCode = filter.hashCode

FortiSIEM Rules