Imperva

Imperva

Imperva WAF gateway (formerly SecureSphere)

web application security

Imperva WAF gateway boasts an overwhelming track record and reliability in the WAF market, and has been introduced by a wide range of companies, including financial institutions and government agencies. In addition, due to the recent rise in cloud computing, Imperva has also released appliances that can be deployed in AWS and Azure environments and can guarantee the same security as on-premises.

Installation form without making changes to the existing network

  • Transparent bridge (inline)
    • Fail open/close support
  • Sniffing (non-inline) installation
    • Packet copy from switch mirror port
  • Installation form without making changes to the existing network

Various attack defense methods

  • Blacklist by signature
    • Provided by ADC on a regular basis (on average twice a month)
    • Block Recommended Signatures, Detect Recommended Signatures
  • Whitelist (dynamic profiling feature)
    • Automatically generate web communication whitelist (profile) from communication content
  • Correlation attack verification
    • Detect complex attacks by judging from multiple anomalies
  • Reputation defense (THREAT INTELLIGENCE feature)
    • Detect malicious source IP, anonymous proxy, phishing site URL

WAF Operation Example: Strengthening Security

  • Operational issues
    • Created a threshold-based custom policy for list-type attack countermeasures, but there are many false positives/false blockings
  • Countermeasure option
    • Adjustment of the threshold according to the actual situation (high load)
    • Policy & Alert Weighting with Threat Intelligence Bot Detection (low load)
  • Examples of threat intelligence countermeasures:
    Create custom policies based on Threat Intelligence information
    • Limits the scope of blocking to only highly malicious accesses, but also raises alerts and records other accesses that show malicious behavior
      1. "Access the login page from the same source IP address 5 times per minute" → Not blocked, but logging with LowAlert
      2. "Access the login page from the same source IP address 5 times per minute" "Access by malicious bot" → Logging & log inspection with Block + High Alert
  • WAF Operation Example: Strengthening Security

Frequently Asked Questions

  • Please tell me the schedule until the introduction.
  • It takes about 1 to 2 months from setting to service launch. If you wish to support implementation including tuning, we will provide it.
  • Is it possible to use it in AWS or Azure environment?
  • Yes.

Inquiry/Document request

In charge of Macnica Imperva Co., Ltd.

Mon-Fri 8:45-17:30