FortiAppSec Cloud
FortiAppSec Cloud delivers unified application security and performance with WAF, bot protection, GSLB, DDoS mitigation, threat analytics, and CDN.
kmak
Staff
Staff
Article Id 409932
Description This article describes how to enable the security module in FortiAppSecCloud-WAF to erase the HTTP Server header and X-Powered-By header.
Scope FortiAppSec Cloud WAF.
Solution

FortiAppSecCloud-WAF has the Information Leakage security module whose purpose is to erase sensitive information from the server HTTP response header or body data.

There are signatures in the category 'Server Information Disclosure' which detect and erase the common sensitive headers, such as the 'Server' header or 'X-Powered-By'.

 

  1. Example of a website application that is showing the 'Server' header and 'X-Powered-By' header.

 

kmak_0-1757230381450.jpeg

 

  1. Before checking on the Information Leakage security module, make sure that the WAF Application’s Block Mode is enabled.

 

kmak_1-1757230381454.jpeg

 

  1. Navigate to the Information Leakage module page. Add the module from the module page if it is not available. The security module should be in 'Erase & Alert' action, and toggle to enable the Security Information Disclosure option.

 

kmak_2-1757230381459.jpeg

 

  1. The signature ID checks and erases the HTTP 'Server' header and 'X-Power-By' header. Both signature IDs have the sensitivity level of '4'.
  • Signature ID 080200001 - Server Header:

 

kmak_3-1757230381465.jpeg

 

  • Signature ID 080200004 – X-Powered-By Header:

 

kmak_4-1757230381470.jpeg

 

  1. Navigate to the Known Attacks module page and check the Sensitivity Level. Make sure to change the Sensitivity Level to '4' and save.

 

kmak_5-1757230381476.jpeg

 

  1. Try to browse the testing page that is proxied through the FortiAppSecCloud-WAF endpoint. The 'Server' Header and 'X-Powered-By' Header should be erased now.

 

kmak_6-1757230381481.jpeg

 

  1. If the level 4 Sensitivity Level is causing a large number of false positive blocking or content erasing, revert the Sensitivity Level to 1 and use the Erase HTTP Headers module to erase the header content information. Navigate to the Information Leakage page, toggle to enable the option Erase HTTP Headers. Add the specific header name to the list.

 

kmak_7-1757230381485.jpeg

 

Related documents:

Information Leakage Security Module

Known Attacks Signature Security Module

Contributors