Description
Setting up Imperva WAF configuration when an application is migrated on the WAF to enable the following services
o Protocol conformance
o Tool-based browsing detection
o Account take-over protection
o Method enforcement
o SIEM integration
o Error handling blinding (500, 400, 403, 404, …)
o Learning + signaling mode
o URL, method, parameter ..; learning & whitelisting
o Forced browsing protection
o Cookie protection
o Blacklist stop-gap
o Header restrictions (in & out) and anonymizing (out)
o Monitoring integration with QRADAR
o Critical URL: parameter & type checking
o Blocking + signaling mode
o Blocking sources with known bad reputation
• Cleaning the URL Whitelists for applications already exist in preparation for parameter whitelisting
• Finetune the set detection rules as time is passing and locking down the whitelists (turning off automatic mode)
For immediate consideration please get in touch directly on :