PH_Rule_SIGMA_1188
Enabled
Detects the mount of ISO images on an endpoint. This rule is adapted from https://github.com/SigmaHQ/sigma/blob/master/rules/windows/builtin/security/win_security_iso_mount.yml
5
Security
Initial Access
Initial Access consists of techniques that use various entry vectors to gain their initial foothold within a network. Techniques used to gain a foothold include targeted spearphishing and exploiting weaknesses on public-facing web servers. Footholds gained through initial access may allow for continued access, like valid accounts and use of external remote services, or may be limited-use due to changing passwords.
https://attack.mitre.org/tactics/TA0001T1566.001
Phishing: Spearphishing Attachment
Adversaries may send spearphishing emails with a malicious attachment in an attempt to elicit sensitive information and/or gain access to victim systems. Spearphishing attachment is different from other forms of spearphishing in that it employs the use of malware attached to an email. Upon opening the attachment (and potentially clicking past protections), the adversary's payload exploits a vulnerability or directly executes on the user's system. Adversaries frequently manipulate file extensions and icons in order to make attached executables appear to be document files, or files exploiting one application appear to be a file for a different one.
https://attack.mitre.org/techniques/T1566/001Server
Windows Security Log via OMI or FortiSIEM Agent
Correlation
No remediation guidance specified
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.
Filter
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="Win-Security-4663" AND serverName="Security" AND osObjType="File" AND osObjName REGEXP "^\\Device\\CdRom") AND (osObjName!="\\Device\\CdRom0\\setup.exe")
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
hostName,osObjName,osObjType,serverName
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 = Filter.hostName,
osObjName = Filter.osObjName,
osObjType = Filter.osObjType,
serverName = Filter.serverName