Link11 WAAP
v5
v5
  • Link11 WAAP Documentation
  • Release Notes
  • Known Issues
  • User Guide
    • Introduction to Link11 WAAP
  • How Link11 WAAP Works
    • Traffic Filtering Process
    • Traffic Reporting and Analytics
    • Policy Mapping and Traffic Routing
    • Tagging
    • UI Overview and Common Elements
  • Console UI Walkthrough
    • Analytics
      • Dashboard
      • Events Log
    • Security
      • Global Filters
      • Flow Control Policies
      • Security Policies
      • Rate Limit Rules
      • ACL Profiles
      • Actions
      • Dynamic Rules
      • Quarantined
      • Content Filter
        • Content Filter Profiles
        • Content Filter Rules
    • Sites
      • Server Groups
      • Proxy Templates
      • Mobile Application Groups
      • Backend Services
      • Edge Functions
      • DNS Records
      • SSL
        • Load Balancers
        • Certificates
    • System
      • Interactive Challenge
      • SSO Configuration
      • Purge CDN Cache
      • Users Management
      • Security Alerts
      • Log Exporters
      • Version Control
      • System DB
      • Publish Changes
    • Account
  • Using the product
    • Best Practices
      • Saving and Publishing Your Changes
      • Enabling Passive Challenges
      • Understanding and Diagnosing Traffic Issues
    • How Do I...
      • Authenticate mobile app users
      • Ban, unban, and allowlist traffic sources
      • Bypass Link11 WAAP for loadtesting or other purposes
      • Configure a new path/section of a site
      • Control caching behavior
      • Enable GraphQL traffic
      • Enable mTLS (mutual TLS)
      • Protect sensitive information in logs and analytics
      • Quickly block an attacker
      • Redirect or block HTTP traffic
      • Run custom code
      • Set rate limits and exemptions
      • Stream event data to a SIEM solution or other destination
    • The Link11 WAAP API
      • Overview
      • Internal data structures
      • Using Swagger UI
      • Using curl
  • Reference Information
    • Acronyms
    • API
      • API access to traffic data
      • Types of namespaces
      • Namespace reference
        • ACL Profiles
        • Actions
        • Backend Services
        • Certificates
        • Configs
        • Content Filter Profiles
        • Content Filter Rules
        • Data queries
        • Dynamic Rules
        • Edge Functions
        • Flow Control Policies
        • Global Filters
        • Load Balancers
        • Log Exporters
        • Mobile Application Groups
        • Planets
        • Proxy Templates
        • Rate Limit Rules
        • Security Alerts
        • Security Policies
        • Server Groups
        • Tags
        • Tools
        • Users
    • Hostile Bot Detection / LWCSI
      • Environmental detection and browser verification
      • Client authentication
      • Biometric behavioral verification
    • HTTP Response Codes
    • Log Exporter Output
    • Pattern Matching Syntax
    • Query Filter Syntax and Best Practices
  • Support
Powered by GitBook
On this page
  • Determining the Security Policy
  • Cloning an existing Path Map
  • Configuring the new Path Map

Was this helpful?

Export as PDF
  1. Using the product
  2. How Do I...

Configure a new path/section of a site

PreviousBypass Link11 WAAP for loadtesting or other purposesNextControl caching behavior

Last updated 1 month ago

Was this helpful?

Scenario: An admin has recently created a new section within an existing domain. (In this context, "section" means a path, or set of paths, that can be described in a single regex.) For example, perhaps a new API version is being exposed at /apiv3, which is a URL that did not previously exist.

How can the admin configure Link11 WAAP's security settings for the new path(s)?

As shown in the diagram below, the association between security settings and paths is done within a .

Specifically, each Security Policy contains a Path Map: a list of paths, and the security settings assigned to each.

Thus, the process for configuring new paths within L11WAAP is as follows:

  1. Determine the Security Policy currently in place for the domain

  2. Within that Security Policy, clone an existing Path Map

  3. Configure the new Path Map as appropriate, to contain the new settings.

These steps are described below.

Determining the Security Policy

  1. Navigate to Sites -> Server Groups.

  2. On the Server Group Editor page, note the current selection in the Security Policy pulldown list.

Cloning an existing Path Map

  1. Navigate to Security -> Security Policies

  2. Select the Security Policy that is (as noted above) currently assigned to the domain's Server Group.

  3. At the bottom of the Security Policies Editor page is the Path Mapping section. Expand one of the entries in this list.

  4. Within the expanded display of the Path Map, at the bottom right, select the Fork Path Mapping button. This will create a clone of the original entry.

Configuring the new Path Map

Ensure that the new Path Map is displayed for editing, and then:

  1. Edit its Name to something appropriate

  2. Define the Match path with an expression that will match all the new path(s) being configured

  3. Verify that the other security settings in this Path Map are appropriate. If not, existing security rulesets (such as Rate Limit Rules, Content Filter Profiles, etc.) are available for selection. If it is necessary to create one or more new rulesets, you will need to leave this page (be sure to select Save first!), create the new settings, and return here to select them.

In the list that appears, select the for the domain in question.

When the new Path Map is correctly defined, select Save. Then the changes.

Server Group
publish
Security Policy