SonicWall
Detection rules for SonicWall data sources. Each rule includes its MITRE ATT&CK mapping, impact rating, and a description of what it detects. These rules analyze events with the data type firewall-sonicwall, which the SonicWall integration sends.
This category contains 7 detection rules.
| Rule | Category | Technique | Impact (C/I/A) |
|---|---|---|---|
| SonicWall Anti-Spyware Detection | Discovery | T1082 - System Information Discovery | C:3 / I:2 / A:1 |
| SonicWall Botnet Activity Detected | Command and Control | T1071 - Application Layer Protocol | C:3 / I:3 / A:2 |
| SonicWall Capture ATP Malicious Verdict | Execution | T1204 - User Execution | C:3 / I:3 / A:2 |
| SonicWall Gateway Anti-Virus Detection | Command and Control | T1105 - Ingress Tool Transfer | C:3 / I:3 / A:2 |
| SonicWall Intrusion Prevention System Alert | Initial Access | T1190 - Exploit Public-Facing Application | C:3 / I:3 / A:3 |
| SonicWall Management Interface Authentication Failures | Credential Access | T1110 - Brute Force | C:3 / I:2 / A:1 |
| SonicWall SSL VPN Authentication Failures | Credential Access | T1133 - External Remote Services | C:3 / I:2 / A:1 |
Rule Example
Below is an example of a rule definition for SonicWall Anti-Spyware Detection (view in repository):
# Rule version v2.1.0
dataTypes:
- firewall-sonicwall
name: SonicWall Anti-Spyware Detection
impact:
confidentiality: 3
integrity: 2
availability: 1
category: Discovery
technique: "T1082 - System Information Discovery"
adversary: origin
references:
- https://www.sonicwall.com/techdocs/pdf/sonicos-6-5-4-log-events-reference-guide.pdf
- https://attack.mitre.org/techniques/T1082/
description: |
Detects when SonicWall Anti-Spyware service identifies and blocks spyware,
adware or other potentially unwanted programs (PUPs) that may be attempting
to collect sensitive information or establish persistence on the network.
Next Steps:
- Review the detected spyware category and priority level.
- Investigate the source IP for other malicious activities.
- Check whether the blocked spyware represents a targeted attack or a
widespread infection.
- Verify Anti-Spyware policies are properly configured and signatures
up-to-date.
- Consider quarantining the affected host if multiple detections cluster
on the same source.
where: |
(
oneOf("log.eventCode", ["1157", "1158", "1159"]) ||
exists("log.spywareCategory") ||
contains("log.message", ["spyware", "Anti-Spyware"]) ||
contains("log.contentCategory", "Anti-Spyware")
) && equals("actionResult", "denied")
afterEvents:
- with:
- field: origin.ip
operator: filter_term
value: '{{.origin.ip}}'
within: 1h
count: 3
deduplicateBy:
- adversary.ip
- target.host
Rule Details
SonicWall Anti-Spyware Detection
Detects when SonicWall Anti-Spyware service identifies and blocks spyware,
adware or other potentially unwanted programs (PUPs) that may be attempting
to collect sensitive information or establish persistence on the network.
Category: Discovery
Technique: T1082 - System Information Discovery
Impact: C:3 / I:2 / A:1
Rule file: anti_spyware_detection.yaml
Reference: https://www.sonicwall.com/techdocs/pdf/sonicos-6-5-4-log-events-reference-guide.pdf
Reference: https://attack.mitre.org/techniques/T1082/
SonicWall Botnet Activity Detected
Detects potential botnet command and control (C2) communication identified
by the SonicWall Botnet Filter: an internal host tried to reach an address
that SonicWall's botnet database or dynamic botnet list marks as a botnet
server, and the firewall blocked it (events 1201 and 1519, "Suspected Botnet
responder blocked"). Listed addresses blocked at the perimeter while trying
to connect in ("Suspected Botnet initiator blocked") and addresses on the
firewall's own custom botnet list are not alerted. One alert is raised per
firewall and listed address; repeats are suppressed for seven days.
Category: Command and Control
Technique: T1071 - Application Layer Protocol
Impact: C:3 / I:3 / A:2
Rule file: botnet_detection.yaml
Reference: https://attack.mitre.org/techniques/T1071/
SonicWall Capture ATP Malicious Verdict
Detects when SonicWall Capture ATP (Advanced Threat Protection) sandboxes a
file and returns a malicious verdict. Indicates an attempted malware
delivery. Also covers RTDMI (Real-Time Deep Memory Inspection) verdicts
which share the ATP verdict pipeline on the firewall.
Category: Execution
Technique: T1204 - User Execution
Impact: C:3 / I:3 / A:2
Rule file: capture_atp_verdicts.yaml
Reference: https://www.sonicwall.com/support/knowledge-base/capture-atp-overview/170503785055490
Reference: https://attack.mitre.org/techniques/T1204/
SonicWall Gateway Anti-Virus Detection
Detects when SonicWall Gateway Anti-Virus (GAV) identifies and blocks
malicious content in HTTP/HTTPS/FTP/SMTP traffic. Signals a malware delivery
attempt at the network perimeter.
Category: Command and Control
Technique: T1105 - Ingress Tool Transfer
Impact: C:3 / I:3 / A:2
Rule file: gateway_antivirus_detection.yaml
Reference: https://www.sonicwall.com/techdocs/pdf/sonicos-6-5-4-log-events-reference-guide.pdf
Reference: https://attack.mitre.org/techniques/T1105/
SonicWall Intrusion Prevention System Alert
Detects when SonicWall Intrusion Prevention System (IPS) blocks an attack
matching a known signature — buffer overflow attempts, SQL injection,
cross-site scripting, exploit kits, etc. Reflects the IPS Prevention Alert
message family (event codes 88 / 89 / 100 / 785) as well as the descriptivelog.message, log.contentCategory and log.ipsCategory fields.
Category: Initial Access
Technique: T1190 - Exploit Public-Facing Application
Impact: C:3 / I:3 / A:3
Rule file: intrusion_prevention_alert.yaml
Reference: https://www.sonicwall.com/techdocs/pdf/sonicos-6-5-4-log-events-reference-guide.pdf
Reference: https://attack.mitre.org/techniques/T1190/
SonicWall Management Interface Authentication Failures
Detects failed authentication attempts against the SonicWall management
interface (GUI/CLI/API). Repeated failures from a single source IP suggest
a brute-force or credential-stuffing attack targeting admin credentials.
It counts logins denied due to bad credentials (events 32, 33 and 200),
not SSO probe failures, policy denials or allowed logins, and raises one
alert per source address for seven days.
Category: Credential Access
Technique: T1110 - Brute Force
Impact: C:3 / I:2 / A:1
Rule file: sonicwall_admin_auth_failures.yaml
Reference: https://www.sonicwall.com/techdocs/pdf/sonicos-6-5-4-log-events-reference-guide.pdf
Reference: https://attack.mitre.org/techniques/T1110/
SonicWall SSL VPN Authentication Failures
Detects failed SSL VPN / NetExtender authentication attempts on a SonicWall
firewall. Repeated failures from a single source IP indicate brute-force or
credential-stuffing attacks against the remote access surface.
Category: Credential Access
Technique: T1133 - External Remote Services
Impact: C:3 / I:2 / A:1
Rule file: sonicwall_vpn_failures.yaml
Reference: https://www.sonicwall.com/techdocs/pdf/sonicos-6-5-4-log-events-reference-guide.pdf
Reference: https://attack.mitre.org/techniques/T1133/