Web Security

Download 0
Last updated Nov 23, 2026

Getting Started

This page walks through the whole procedure, from looking at the web logs to turning on BOLA detection. For installation and prerequisites, see the install guide.

1. Look around the web logs

Open Web Monitoring and pick tables and a range at the top right.

  • Without a table, every table collected with the web log schema is read.
  • The range is the last 1 minute, 5 minutes, 10 minutes or 1 hour.

Check non-browser clients on the Bots tab and responses of 400 and above on the Errors tab. These two tabs work without URL templates.

2. Register URL templates

Templates are how request paths are grouped and parameters extracted. With few or no templates, the Crawling tab and BOLA detection do not work.

With an AI agent (recommended)

  1. Install the Web Security Lead Analyst template in the AI Assistant or Agentic SOC app.
  2. Open the AI Assistant panel on the right of the Web Security screens.
  3. Ask something like "Register the URL templates of the web_access table and set the parameter types".

The agent investigates recent web logs and registers templates until 98% of the requests are normalized. Then it sets a type on each parameter. See AI Agents.

By hand In URL Normalization → URL Templates → Add template, enter the following.

  • Host: the table name. Leave empty to apply to every table.
  • Method
  • Path template: for example /api/orders/:order_id

See URL Normalization for the syntax.

3. Check parameter types

BOLA detection looks only at parameters of the Object ID type. Open the registered templates and check the following.

  • Set parameters that point to an object someone owns, such as an order number or account ID, to Object ID.
  • Set names of public pages anyone may read, such as blog post slugs, to Public name. As Object ID, they would bring legitimate crawlers up as BOLA candidates.
  • Leave a parameter Not set when the evidence is thin.

4. Check normalization

In URL Normalization → Test, enter a real request path and click Test. The matched template and parameter values show that the templates reached the nodes. Also check that object ID requests show on the Web Monitoring → Crawling tab.

5. Turn on BOLA detection

  1. In Policies → Behavior Profiles, click Build Now for websec-bola-baseline-5m and websec-bola-baseline-1h.
  2. In Policies → Batch Rules, enable the rules BOLA 객체 열거 의심 (5분) and BOLA 객체 열거 의심 (1시간).

See BOLA Detection for how it judges and how to tune it.

6. Operation

  • When a BOLA event comes in, drill down the Web Monitoring → Crawling tab to the event's subject (IP), and see which objects it touched and how fast.
  • New APIs bring paths without templates. Rerun the Web Path Profiler from time to time, or check unknown paths with URL Normalization → Test and add templates.
  • Rebuild the baselines after you change the templates substantially.