Spyware found but not remediated

Rule ID

PH_Rule_Vuln_4

Default Status

Enabled

Description

Detects that host anti-virus or content inspection devices found a spyware but could not remediate it

Severity

MITRE ATT&CK® Tactics

Execution

Execution consists of techniques that result in adversary-controlled code running on a local or remote system. Techniques that run malicious code are often paired with techniques from all other tactics to achieve broader goals, like exploring a network or stealing data. For example, an adversary might use a remote access tool to run a PowerShell script that does Remote System Discovery.

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

MITRE ATT&CK® Techniques

T1204.001

User Execution: Malicious Link

An adversary may rely upon a user clicking a malicious link in order to gain execution. Users may be subjected to social engineering to get them to click on a link that will lead to code execution. Clicking on a link may also lead to other execution techniques such as exploitation of a browser or application vulnerability via Exploitation for Client Execution. Links may also lead users to download files that require execution via Malicious File.

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

Impacts

Server

Data Source

FortiGate via Syslog, FortiProxy via Syslog, FortiEMS via Syslog, CrowdStrike Falcon via FALCON_STREAMING_API/FALCON_DATA_REPLICATOR, SentinelOne via Syslog, Symantec Endpoint Protection Service via Syslog, Microsoft Defender for Endpoint via HTTPS_ADVANCED, FortiEDR via Syslog, Cisco FireAMP via ESTREAMER_SDK/FIREAMP_CLOUD_API,Palo Alto Traps Endpoint Security Manager via Syslog, Carbon Black Security Platform via Syslog, Cylance Protect 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.

SpywareFound

SubPattern Definitions

SubPattern Name: SpywareFound

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_Spyware_Remedy_Failed) AND reptDevIpAddr IN (Group@PH_SYS_APP_SEC_MGMT,Group@PH_SYS_DEVICE_SEC_GW)

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

hostIpAddr,fileName

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 = SpywareFound.hostIpAddr,
 fileName = SpywareFound.fileName

FortiSIEM Rules