Phishing attack found but not remediated

Rule ID

PH_Rule_Vuln_18

Default Status

Enabled

Description

Detects that host anti-virus or content inspection devices found phishing attacks that it failed to remediate

Severity

MITRE ATT&CK® Tactics

Reconnaissance

Reconnaissance consists of techniques that involve adversaries actively or passively gathering information that can be used to support targeting. Such information may include details of the victim organization, infrastructure, or staff/personnel. This information can be leveraged by the adversary to aid in other phases of the adversary lifecycle, such as using gathered information to plan and execute Initial Access, to scope and prioritize post-compromise objectives, or to drive and lead further Reconnaissance efforts.

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

MITRE ATT&CK® Techniques

T1598.002

Phishing for Information: Spearphishing Attachment

Before compromising a victim, adversaries may send spearphishing messages with a malicious attachment to elicit sensitive information that can be used during targeting. Spearphishing for information is an attempt to trick targets into divulging information, frequently credentials or other actionable information. Spearphishing for information frequently involves social engineering techniques, such as posing as a source with a reason to collect information (ex: Establish Accounts or Compromise Accounts and/or sending multiple, seemingly urgent messages.

https://attack.mitre.org/techniques/T1598/002

T1598.003

Phishing for Information: Spearphishing Link

Before compromising a victim, adversaries may send spearphishing messages with a malicious link to elicit sensitive information that can be used during targeting. Spearphishing for information is an attempt to trick targets into divulging information, frequently credentials or other actionable information. Spearphishing for information frequently involves social engineering techniques, such as posing as a source with a reason to collect information (ex: Establish Accounts or Compromise Accounts and/or sending multiple, seemingly urgent messages.

https://attack.mitre.org/techniques/T1598/003

Impacts

Server

Data Source

FortiGate via Syslog, FortiProxy via Syslog, Checkpoint IPS-1 via LEA/Syslog, PaloAlto PAN-OS via Syslog etc

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.

MalwareFound

SubPattern Definitions

SubPattern Name: MalwareFound

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 IN (Group@PH_SYS_EVENT_Phish_Found) AND eventType NOT IN (Group@PH_SYS_EVENT_Phish_Remedy_Success)

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

srcName,srcIpAddr

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

 srcName = MalwareFound.srcName,
 srcIpAddr = MalwareFound.srcIpAddr

FortiSIEM Rules