FortiWeb - Basic Protect Webpage

Problem

FortiWeb is an excellent solution to protect web applications based on HTTP/HTTPS. 
The big question is how to configure the appliance for basic protection.

Solution

Szenario

An internal web server should be accessible from the Internet. However, this is located in the LAN zone and should therefore be protected by a FortiWeb from the outside.

Configuration Options

You have two different Configuration Options. Decide which one fits better for you:

Single Server/Server Load Balance

Generally, only one server policy can be created per Virtual IP. With this limitation this method is a kind of IP to IP connection.
Here you define a Virtual IP which is matched to a Server Pool. A Server Pool can have one or more Real Servers. 
This means that with the Server Load Balance variant the HTTP header cannot be distinguished and the policy decision is based on IP address.

Content Routing

This method decides which server pool to use based on the HTTP header host field.
This means that, for example, a different server pool can be addressed per URL or sub-URL.

Example:
web.example.com matched on 192.168.10.100
webapp.example.com matched on 192.168.10.101

The first thing to decide is which of the two variants you want to use!

Health Check

The FortiWeb comes with many predefined health checks. Check beforehand if you can use one of them.
Otherwise you have to define your own health check. Please refer to the documentation.

Server Pool

At the beginning the Real Servers have to be defined. These are defined under "Server Objects->Server->Server Pool".
The configuration is self-explanatory:

HTTP Content Routing

If you have decided on the second variant (content routing). Next, the matching between URL and server pool must be established. This is done via the entries in the HTTP content routing table.
If you have chosen the first variant, you can skip this step. 
Consult the documentation from Fortinet for more information: User Guide

Virtual IP

It is recommended to use a virtual IP address for the virtual servers.
This IP address is addressed by the clients.
Define this under "System->Network->Virtual IP".

Virtual Server

The last object needed is a Virtual Server.
This is defined under "Server Objects->Server->Virtual Server" and represents the link to the previously defined Virtual IP.

Server Policy

With all the defined objects, a policy for access can now be created.
A distinction is made whether the Content Routing or Server Balance method was selected.

Content Routing


  • Deployment Mode: Choose between Content Routing or Server Balance (see description above)
  • Virtual Server: Select the defined Virtual Servers and choose which virtual IP this policy should listen to.
  • HTTP Content Routing: Define the matching between Content Routing Policies and Server Pools.
  • Protected Hostnames: See documentation
  • HTTP Service: Select the predefined HTTP Service. Normally that fits. Otherwise read here.
  • HTTPS Service: The same as for the HTTP Service.
That are the important settings. All services are described in the documentation




Comments

  1. Their method makes these virtual video games play like live features. The home edge is with the zero and 00, as these numbers cannot be gained by the participant. The casino has a complicated cell casino which means you can to|you presumably can} sport with 24/7 customer support. The features are properly grouped, 1xbet korea making it easy to maneuver from one segment to a different.

    ReplyDelete

Post a Comment

Popular posts from this blog

FortiGate BGP dual-home with multiple ISP

FortiMail - Server Basic Configuration

FortiGate as DNS Server or DNS Proxy