I was wondering as for SQL or XSS attacks fortiweb has 3 options for detections what is the order of operations ?
Is it first signatures then Syntax Detection and then attack ML models that are build on the appliance itself after time from the passed traffic?
Also what happens it an attack matches all 3 options?
My final question is for SQL injection and XSS attacks shouldn't signatures be stopped and just Syntax Detection and attack ML models to be used as I have read that they have less false positives ?
Solved! Go to Solution.
I think I got it with the feature false positive detection False Positive Mitigation for SQL Injection signatures | FortiWeb 7.6.2 | Fortinet Document Library that it will then try to use the Syntax Detection. So all features work together. Maybe for XSS there are not so many false positives and this is why it is not available.
For XSS the parser seems to help wilth encodings or obfuscations so it is more to detect false negatives than to help with false positive.
If there is anything else please share but I think this is the case.
I think I got it with the feature false positive detection False Positive Mitigation for SQL Injection signatures | FortiWeb 7.6.2 | Fortinet Document Library that it will then try to use the Syntax Detection. So all features work together. Maybe for XSS there are not so many false positives and this is why it is not available.
For XSS the parser seems to help wilth encodings or obfuscations so it is more to detect false negatives than to help with false positive.
If there is anything else please share but I think this is the case.
User | Count |
---|---|
2587 | |
1380 | |
796 | |
658 | |
455 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.