FortiSIEM Rules

Windows: Suspicious Rejected SMB Guest Logon From IP

Rule ID

PH_Rule_SIGMA_1103

Default Status

Enabled

Description

Detects PrintNightmare (CVE-2021-1675) Remote Code Execution attempt in Windows Spooler Service. This rule is adapted from https://github.com/SigmaHQ/sigma/blob/master/rules/windows/builtin/smbclient/security/win_smbclient_security_susp_failed_guest_logon.yml

Severity

5

Category

Security

MITRE ATT&CK® Tactics

Credential Access

Credential Access consists of techniques for stealing credentials like account names and passwords. Techniques used to get credentials include keylogging or credential dumping. Using legitimate credentials can give adversaries access to systems, make them harder to detect, and provide the opportunity to create more accounts to help achieve their goals.

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

MITRE ATT&CK® Techniques


T1110.001

Brute Force: Password Guessing

Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.

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

Impacts

Server

Data Source

Windows Security log via OMI or FortiSIEM Agent

Detection

Correlation

Remediation Guidance

Determine if this was an authorized penetration testing activity. Otherwise, there is no reason for this activity to be occurring. The host should be quarantined and investigated immediately. Collect the process hash and check for malware match. Investigate what other incidents are occurring on that host during that time frame. CISA encourages administrators to disable the Windows Print spooler service in Domain Controllers and systems that do not print.

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 REGEXP "Win-.*-31017[^\d]*" AND user IS NULL AND serverName REGEXP "^\\1"

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,serverName,user

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 = Filter.hostName,
serverName = Filter.serverName,
user = Filter.user