Fortinet 144 FortiWeb 5.0 Patch 6 Administration Guide
5. Click Apply.
The FortiWeb appliance next requests an update according to the schedule. Results appear
in FortiWeb Security Service in the FortiGuard Information widget. If you have enabled
logging in:
•Log & Report > Log Config > Other Log Settings
•Log & Report > Log Config > Global Log Settings
when the FortiWeb appliance requests an update, the event is recorded in Log & Report >
Log Access > Event, such as these log message:
FortiWeb virus signature is already up-to-date
FortiWeb IP reputation signature update succeeded
If the FortiWeb appliance cannot successfully connect, it will record a log with a message
that varies by the cause of the error, such as:
FortiWeb is unauthorized.
Once the attack signature update is complete, FortiWeb will immediately begin to use them.
No reboot is required.
See also
•How often does Fortinet provide FortiGuard updates for FortiWeb?
•Blocking known attacks & data leaks
•Validating parameters (“input rules”)
•Preventing tampering with hidden inputs
•Limiting file uploads
•Predefined data types
•Predefined suspicious request URLs
•Blacklisting source IPs with poor reputation
•Blacklisting countries & regions
Manually initiating update requests
If an important update has been released but there is too much time remaining until your
appliance’s next scheduled update poll, you can manually trigger the FortiWeb appliance to
connect to the FDN or FDS server override to request available updates for its FortiGuard
service packages.
To manually request updates
1. Before manually initiating an update, first verify that the FortiWeb appliance has a valid
license and can connect to the FDN or override server. For details, see “To determine your
FortiGuard license status” on page 134 and “To verify FortiGuard update connectivity” on
page 136.
You can manually initiate updates as an alternative or in addition to other update methods. For
details, see “Scheduling automatic signature updates” on page 141 and “Uploading signature &
geography-to-IP updates” on page 146.