FortiWeb Lesson 12: Tune False Positives with Scoped Exceptions
FORTIWEB CLASSROOM • LESSON 12
Level: Intermediate · Study and lab: 75 minutes
Instructor: Harpreet Singh Virdi, CISSP, CCSP
FortiWeb course guide · FortiWeb training block
Restore legitimate behavior without losing the requirement
A book title containing punctuation triggers a security check. The correct response is to investigate the exact detection and valid application behavior. Do not start by disabling a category or trusting a whole network.
A five-step method
Reproduce the smallest synthetic case. Locate the actual rule or signature. Validate the intended input with the application owner. Scope the change to the necessary location. Retest valid and invalid requests.
An access violation, protocol constraint, signature match, and ML anomaly may require different remedies. An exception for one engine does not necessarily change another engine's decision.
Worked example
The search endpoint legitimately accepts apostrophes, but an inventory identifier does not need the same broad text behavior. If the event identifies a signature match, inspect that signature and the supported exception fields. If it identifies a type or size rule, tune that rule instead. Keep host, URL, parameter, and method scope as narrow as the supported feature and requirement allow.
Guided lab
- Back up the working lab configuration and record the signature database/model state.
- Prepare normal text, legitimate punctuation, boundary-length input, invalid type/length, and an approved security test.
- Run all cases and preserve sanitized before-results.
- Confirm the exact valid input requirement and matching event.
- If a signature exception is justified, clone a predefined policy as needed and use its supported exception controls.
- Inspect every condition. Confirm whether the change skips scanning, changes an action, or changes a rule match.
- Save the scoped change and rerun every case, including unrelated endpoints.
- Document owner, purpose, review date, dependencies, and rollback.
Expected result: valid input succeeds, intended negative controls still work, and the exception has a clear explanation. Fewer alerts alone are not the success criterion.
Review shared objects and upgrades
Check all references before modifying a shared policy. Revisit exceptions after application or signature changes. Release-specific migration behavior can affect protection; compare the effective configuration after upgrades rather than assuming every exception was preserved.
Knowledge check
A user says the WAF is wrong. Should you immediately create an exception?
Instructor answer
No. The client could be malformed, buggy, or malicious. Confirm the legitimate requirement and exact detection first, then use the smallest justified change with regression evidence.
Official reading
- Fortinet: configuring action overrides or exceptions to data leak attack detection signatures
- Fortinet: faq
- Fortinet: 81434
Independent training, not affiliated with Fortinet. Examples use an authorized isolated lab with synthetic data. The lab steps and expected outcomes have not been executed on a FortiWeb appliance for this publication. Firmware, platform, operating mode, licensing, and subscriptions affect behavior; follow the documentation for your exact build. References use 8.0.x examples and do not constitute an upgrade recommendation.
← Previous FortiWeb lesson · FortiWeb course guide · Next FortiWeb lesson →
Comments
Post a Comment