FortiWeb

Detection rules for FortiWeb 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-fortiweb, which the Fortinet FortiWeb integration sends.

This category contains 10 detection rules.

RuleCategoryTechniqueImpact (C/I/A)
FortiWeb Authentication Bypass Attempt DetectedInitial AccessT1190 - Exploit Public-Facing ApplicationC:3 / I:3 / A:1
FortiWeb Cross Site Scripting Attack DetectionWeb Application AttackT1190 - Exploit Public-Facing ApplicationC:3 / I:3 / A:2
FortiWeb File Upload Security Violation DetectedResource DevelopmentT1608 - Stage Capabilities: Upload MalwareC:3 / I:3 / A:2
FortiWeb Known Exploit Attempt DetectionWeb Application AttackT1190 - Exploit Public-Facing ApplicationC:3 / I:3 / A:2
FortiWeb Malware DetectionMalwareT1190 - Exploit Public-Facing ApplicationC:3 / I:3 / A:2
FortiWeb OWASP Top 10 Violation AttemptsInitial AccessT1190 - Exploit Public-Facing ApplicationC:3 / I:3 / A:2
FortiWeb SQL Injection Attack DetectionWeb Application AttackT1190 - Exploit Public-Facing ApplicationC:3 / I:3 / A:2
FortiWeb SSRF Attack DetectionWeb Application AttackT1190 - Exploit Public-Facing ApplicationC:3 / I:2 / A:1
FortiWeb Web Application Attack DetectionInitial AccessT1190 - Exploit Public-Facing ApplicationC:3 / I:3 / A:2
FortiWeb Web Shell Upload DetectionPersistenceT1505.003 - Server Software Component: Web ShellC:3 / I:3 / A:3

Rule Example

Below is an example of a rule definition for FortiWeb Authentication Bypass Attempt Detected (view in repository):

# Rule version v1.1.0

dataTypes:
- firewall-fortiweb
name: FortiWeb Authentication Bypass Attempt Detected
impact:
  confidentiality: 3
  integrity: 3
  availability: 1
category: Initial Access
technique: T1190 - Exploit Public-Facing Application
adversary: origin
references:
- https://docs.fortinet.com/document/fortiweb/7.2.2/log-message-reference/252057/event
- https://attack.mitre.org/techniques/T1078/
- https://attack.mitre.org/techniques/T1190/
description: |
  Detects explicit authentication or authorization bypass classifications/messages. A notification policy name, login failure or account lockout alone is insufficient.

  Both Alert (log-only) and explicit blocking decisions are covered. Check log.action and actionResult to distinguish detection from prevention; neither establishes successful exploitation. Review log.subtype, log.attacktype, log.signatureid and log.msg, then validate the request and outcome in application logs before escalating.
where: |
  exists("origin.ip") && exists("target.ip") && equalsIgnoreCase("log.type", "attack") &&
  regexMatch("log.action", "(?i)^(alert|alert_deny|deny|denied|block|blocked|period_block)$") &&
  ((regexMatch("log.subtype", "(?i)^(Authentication Bypass|Authorization Bypass|auth_bypass)$") || regexMatch("log.attacktype", "(?i)^(Authentication Bypass|Authorization Bypass|auth_bypass)$") || regexMatch("log.signaturesubclass", "(?i)^(Authentication Bypass|Authorization Bypass|auth_bypass)$")) || ((equalsIgnoreCase("log.maintype", "Signature Detection") || (!exists("log.subtype") && !exists("log.attacktype"))) && regexMatch("log.msg", "(?i)\\b(auth(?:entication|orization)?[ _-]*bypass)\\b")))
groupBy:
- adversary.ip
- target.ip

Rule Details

FortiWeb Authentication Bypass Attempt Detected

Detects explicit authentication or authorization bypass classifications/messages. A notification policy name, login failure or account lockout alone is insufficient.

Both Alert (log-only) and explicit blocking decisions are covered. Check log.action and actionResult to distinguish detection from prevention; neither establishes successful exploitation. Review log.subtype, log.attacktype, log.signatureid and log.msg, then validate the request and outcome in application logs before escalating.

FortiWeb Cross Site Scripting Attack Detection

Detects cross-site scripting classified by FortiWeb, including extended signatures.

Both Alert (log-only) and explicit blocking decisions are covered. Check log.action and actionResult to distinguish detection from prevention; neither establishes successful exploitation. Review log.subtype, log.attacktype, log.signatureid and log.msg, then validate the request and outcome in application logs before escalating.

FortiWeb File Upload Security Violation Detected

Detects repeated file-upload or antivirus policy violations against the same application and attack subtype. A policy violation is not proof of a web shell or successful malware upload.

Both Alert (log-only) and explicit blocking decisions are covered. Check log.action and actionResult to distinguish detection from prevention; neither establishes successful exploitation. Review log.subtype, log.attacktype, log.signatureid and log.msg, then validate the request and outcome in application logs before escalating.

FortiWeb Known Exploit Attempt Detection

Detects the Known Exploits signature category reported by FortiWeb. This records an exploit attempt and does not establish that the application was compromised.

Both Alert (log-only) and explicit blocking decisions are covered. Check log.action and actionResult to distinguish detection from prevention; neither establishes successful exploitation. Review log.subtype, log.attacktype, log.signatureid and log.msg, then validate the request and outcome in application logs before escalating.

FortiWeb Malware Detection

Detects the Trojans signature category reported by FortiWeb. A single malware detection is sufficient; prevention status is carried separately.

Both Alert (log-only) and explicit blocking decisions are covered. Check log.action and actionResult to distinguish detection from prevention; neither establishes successful exploitation. Review log.subtype, log.attacktype, log.signatureid and log.msg, then validate the request and outcome in application logs before escalating.

FortiWeb OWASP Top 10 Violation Attempts

Detects repeated medium-or-higher HTTP protocol violations that FortiWeb assigns to an OWASP category. Low-severity missing Content-Type, duplicate parameters and information disclosures are excluded from this rule.

Both Alert (log-only) and explicit blocking decisions are covered. Check log.action and actionResult to distinguish detection from prevention; neither establishes successful exploitation. Review log.subtype, log.attacktype, log.signatureid and log.msg, then validate the request and outcome in application logs before escalating.

FortiWeb SQL Injection Attack Detection

Detects SQL injection classified by FortiWeb, including extended signatures. A single classified attack is sufficient; unrelated requests must not be required to satisfy a history threshold.

Both Alert (log-only) and explicit blocking decisions are covered. Check log.action and actionResult to distinguish detection from prevention; neither establishes successful exploitation. Review log.subtype, log.attacktype, log.signatureid and log.msg, then validate the request and outcome in application logs before escalating.

FortiWeb SSRF Attack Detection

Detects an explicit SSRF classification or a vendor message identifying server-side request forgery. A localhost URL or internal address alone is insufficient.

Both Alert (log-only) and explicit blocking decisions are covered. Check log.action and actionResult to distinguish detection from prevention; neither establishes successful exploitation. Review log.subtype, log.attacktype, log.signatureid and log.msg, then validate the request and outcome in application logs before escalating.

FortiWeb Web Application Attack Detection

Detects repeated Generic Attacks (including Extended) classifications from FortiWeb against the same application. Dedicated SQLi, XSS Known Exploits and malware rules handle those classes. Routine geographic/IP-reputation blocks are excluded.

Both Alert (log-only) and explicit blocking decisions are covered. Check log.action and actionResult to distinguish detection from prevention; neither establishes successful exploitation. Review log.subtype, log.attacktype, log.signatureid and log.msg, then validate the request and outcome in application logs before escalating.

FortiWeb Web Shell Upload Detection

Detects an explicit web-shell classification or named web-shell evidence in a FortiWeb attack message. Generic upload restrictions and script file extensions alone are insufficient.

Both Alert (log-only) and explicit blocking decisions are covered. Check log.action and actionResult to distinguish detection from prevention; neither establishes successful exploitation. Review log.subtype, log.attacktype, log.signatureid and log.msg, then validate the request and outcome in application logs before escalating.