ナビ付きでトピックを開く

 

Web Application Firewall (Legacy)

Applies To:
HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.
HTTP SmallLegacy. If you are currently serving traffic over this platform, then you may continue to do so. However, we recommend that you serve your traffic over our more robust HTTP Large platform.
ADNThe Application Delivery Network platform has been optimized to deliver dynamic content (e.g., login credentials, account information, etc.) over HTTP or HTTPS. Typically, user-specific and database-driven content are served over this platform.
Rules EngineAllows the customization of how requests are handled by our CDN service. It may be used to override the default response provided by an origin server, CDN settings, and the default edge server behavior.
WAFWeb Application Firewall (Legacy) is designed to secure site traffic against DDoS and application layer attacks. It also filters unwanted traffic by enforcing a custom delivery profile and whitelists/blacklists.

This article explains the legacy version of WAF that will undergo end-of-life on June 30, 2021. Our new version of WAF expands upon all of the capabilities offered by WAF and Rate Limiting with a simplified and centralized setup. Please upgrade to the latest version of WAF at your earliest convenience.

This feature requires the Web Application Firewall platform which must be purchased separately. Contact your CDN account manager to activate it.

Category: WAF

Purpose: Allows Web Application Firewall to screen requests.

A Web Application Firewall instance must be defined for this feature. The selected instance determines how traffic will be screened and whether unwanted traffic will be blocked or simply generate alerts.

Default Behavior: Disabled

Best Practices

It is strongly discouraged to perform either of the following actions:

The proper way to apply a new WAF instance or profile is described below.

To apply a new WAF instance

  1. Create the desired WAF instance.
  2. Create a draft from the policy deployed to the Production environment.
  3. Assign the new WAF instance to this feature.
  4. Lock the draft and deploy it to the Production environment.
  5. Optional. Delete the old version of the WAF instance.

To apply a new WAF profile

  1. Create the desired WAF profile.
  2. Update the WAF instance associated with this feature to use the new WAF profile.
  3. Optional. Delete the old version of the WAF profile.