Technical Tip: Verify whether the signature package version is up to date

[opetr_FTNT]

Description	This article describes how to display current signature package on FortiWeb and how to verify if it is the latest version available.
Scope	FortiWeb.
Solution	View information about the current signature package version in the GUI by navigating to System -> Config -> FortiGuard.   View the same information in the CLI by running 'diag sys waf-signature status': FWB_Lab # diag sys waf-signature status Signature Build Number: 0.00397                        <----- Verify if the signature package version is up to date. Signature Engine Version: 5.5.0 Total number of signatures: 3073 Total number of loaded signatures: 3023 Total number of obsolete signatures(Bad Robot) and unused signatures(SBD): 50 Total number of unsupported signatures: 0 Hyperscan Version: 4.7.0 Hyperscan valid platform: Yes PII by Hyperscan: All signatures Compilation of PII by Hyperscan: Success Total number of unsupported Hyperscan PII signatures: 0 In the example above, the version on FortiWeb is 0.00397. See Web Application Security - FortiGuard Labs for information regarding the latest signature package version.  From the above the latest version is 0.00398, so this means the FortiWeb does have the latest version. This may happen, for example, when FortiWeb is configured to update on a weekly basis. The current configuration can be also viewed in the GUI, low on the page under System -> Config -> FortiGuard. To manually trigger the database update, select the 'Update Now' button on the same page. Alternatively, run 'exec update-now' in the CLI: FWB_Lab # exec update-now FWB_Lab # There is no visible output from running the command, but the signature update will complete in 2-3 minutes. FWB_Lab # diag sys waf-signature status Signature Build Number: 0.00398 Signature Engine Version: 5.5.0 Total number of signatures: 3074 Total number of loaded signatures: 3024 Total number of obsolete signatures(Bad Robot) and unused signatures(SBD): 50 Total number of unsupported signatures: 0 Hyperscan Version: 4.7.0 Hyperscan valid platform: Yes PII by Hyperscan: All signatures Compilation of PII by Hyperscan: Success Total number of unsupported Hyperscan PII signatures: 0 If the signature database does not update, follow the troubleshooting steps described in Troubleshooting Tip: Unable to connect to FDS servers.