FortiWeb Lesson 03: Deployment Modes and an Isolated Reverse-Proxy Lab
FORTIWEB CLASSROOM • LESSON 03
Level: Beginner · Study and lab: 75 minutes
Instructor: Harpreet Singh Virdi, CISSP, CCSP
FortiWeb course guide · FortiWeb training block
Choose a topology deliberately
Operating mode affects how FortiWeb receives, inspects, and forwards traffic, and which protections it supports. Do not confuse a network deployment mode with a rule action such as Alert. A transparent topology is not a synonym for observation-only security.
The modes at a glance
Reverse Proxy: clients connect to a virtual server, and FortiWeb forwards accepted traffic toward a server pool. True Transparent Proxy: an inline bridge/proxy deployment with its own forwarding and feature behavior. Transparent Inspection: an inspection topology with different enforcement characteristics. Offline Protection: an out-of-band approach with significant visibility and prevention limits. WCCP is another supported integration topology in applicable releases.
These modes are not interchangeable. Consult the supported-feature matrix and traffic requirements for your build. Out-of-band reset attempts are not equivalent to deterministic inline request blocking. Changing mode can invalidate or remove incompatible configuration; do not experiment with it on a live system.
Our lab plan
Lab client → FortiWeb virtual address → isolated test server Management workstation → restricted management interface
Use a supported FortiWeb appliance or properly licensed VM, a test client, and a simple bookshop application. Keep credentials and customer data synthetic. Choose sizing, firmware, and VM platform requirements from the deployment documentation. A downloaded image without the needed license and resources is not a completed lab.
Guided lab
- Record the firmware build, platform, license capabilities, and required subscriptions.
- Draw management and application networks separately.
- Place the application server on an isolated network; avoid public exposure.
- Configure the reverse-proxy design using the supported setup procedure.
- Record routing, interface addresses, DNS resolution, and which traffic is permitted.
- Establish time synchronization and basic monitoring for meaningful event correlation.
- Verify management access is limited to the intended lab administration path.
- Record a baseline application request directly within the isolated lab before introducing the proxy path.
Expected result: a topology and prerequisites worksheet. You know the chosen mode and can explain the return path. The next lesson builds the traffic objects and server policy.
Troubleshooting before security rules
A timeout can be a routing, listener, or filtering problem. A TLS failure can be a name, trust, or protocol issue. A healthy management interface proves neither an available origin nor a correctly configured application listener. Work layer by layer.
Knowledge check
Should you select Transparent Inspection simply because you want to observe violations without disrupting users?
Instructor answer
No. Choose topology based on deployment requirements and supported behavior. Then separately configure the intended detection and response actions for that topology.
Official reading
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