FortiWeb Lesson 14: Login Security, CSRF, Bot Mitigation and DoS
FORTIWEB CLASSROOM • LESSON 14
Level: Advanced · Study and lab: 90 minutes
Instructor: Harpreet Singh Virdi, CISSP, CCSP
FortiWeb course guide · FortiWeb training block
Different abuse patterns need different controls
A well-formed request can still contribute to abuse. Repeated login guesses, unwanted automation, forged browser actions, and resource exhaustion are separate problems. Start by defining the threat and the legitimate clients before choosing a response.
Login and session context
Document how the application reports successful and unsuccessful authentication. Some applications return the same status code for both. Tracking can help correlate activity, but an IP address or client-supplied field is not automatically a reliable user identity.
CSRF concerns unwanted authenticated browser actions. Coordinate the application's token, cookie, and origin defenses with supported FortiWeb CSRF protection. Browser-oriented features may depend on page processing or cookies and must be tested with cross-domain flows, mobile clients, and APIs.
Bot mitigation
Automation is not inherently malicious. Search indexing, health checks, and approved integrations have business value. Classify client populations and inspect the relevant bot policy. A browser challenge can disrupt an API client that cannot execute JavaScript.
Use narrowly justified exception policies and verify their semantics. A bot exception that skips checks is a security change, not merely a cosmetic classification.
Availability and DoS
Request volume is only one signal. A small number of expensive searches may stress the backend more than many cached images. Observe response time, failures, endpoint cost, and origin health. Avoid universal thresholds copied from another application.
Guided bounded lab
- Inventory a browser, approved API client, monitor, and controlled automation client.
- Record a low-volume baseline and the application's expected login outcomes.
- Configure only the supported observation protections being evaluated.
- Use synthetic accounts and a small agreed set of failed logins; avoid accidental lockout.
- Compare browser and API behavior when testing supported challenges.
- Generate only bounded traffic within your lab capacity ceiling. Do not flood the environment.
- Correlate detections with latency, origin health, and client behavior.
- If testing mitigation, verify recovery and the continued operation of approved clients.
Expected result: you can explain each detection and its scope. A small lab may not activate adaptive protections; state that limitation rather than treating no alert as proof of a defect.
Knowledge check
Why is blocking a shared source address risky?
Instructor answer
Several users may share an address through NAT or a proxy. A source-based response can affect innocent users. Validate trusted client-IP handling and the selected tracking scope.
Official reading
- Fortinet: tracking
- Fortinet: bot mitigation
- Fortinet: exception policy
- Fortinet: defeating cross site request forgery csrf attacks
- Fortinet: dos prevention
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