Install Guide
The Web Security app extracts API parameters from web server access logs, monitors bots, errors and object ID crawling, and detects broken object level authorization (BOLA). The app does not collect logs itself. It reads the web logs you already collect with the web log schema.
- Web logs must be collected with the web log schema. Monitoring and detection read only the logs that
log schema=webreturns. - Adding and editing URL templates requires an administrator. Other users can view them.
- The AI panel and agent templates need the AI Assistant or Agentic SOC app and the matching license feature. Everything else works without them.
Follow the steps in order.
1. Check web log collection
Check with a query that a logger stores web logs with the web log schema.
sonar-loggers | explode log_schemas | search log_schemas == "web" | stats values(name) as loggers by table_name
Each table_name in the result is a table the Web Security app works on. If there is none, create a web server logger first and set its log schema to web. The web log schema has these fields.
| Field | Description |
|---|---|
_time | Request time |
src_ip | Source IP |
method | HTTP method |
path | Request path |
query | Query string |
status | Response status code |
user_agent | User-Agent |
referer | Referer |
The web log schema has no host field, so the Web Security app uses the table name as the host. Collecting each site into its own table lets you manage URL templates per site.
2. Install the app
Install Web Security from the App Store.
When installation finishes, Web Monitoring and URL Normalization appear in the left menu. On first start the app prepares the following.
- Creates the table that stores URL templates.
- Creates the behavior profile
websec-path-templates, which distributes URL templates to every node. - Registers two baseline behavior profiles and two batch rules for BOLA detection. The batch rules are installed disabled.
The app is ready when URL Normalization → Sync Status shows a status.
3. Register URL templates
BOLA detection and crawling monitoring look only at parameters set to Object ID on a URL template. Without templates, only the Bots and Errors tabs of Web Monitoring work. You register templates in one of two ways.
- By hand: In URL Normalization → URL Templates → Add template, enter the host (table name), method, path template and parameter types. See URL Normalization in the user guide.
- With an AI agent: With the AI Assistant or Agentic SOC app, the Web Path Profiler agent investigates the web logs and registers templates and parameter types. Do step 4 first.
4. Install the AI agent template (optional)
- Open the AI Agents menu of the AI Assistant (or Agentic SOC) app.
- Click Templates on the agent list and install Web Security Lead Analyst. Only administrators can install templates.
- Its sub-agent, Web Path Profiler, is installed with it.
After that, you can open the AI Assistant panel on the right of the Web Security screens. Ask something like "Register the URL templates of the web_access table and set the parameter types", and the lead analyst hands the work to the Web Path Profiler.
5. Turn on BOLA detection
Baselines are built from the last 30 days of web logs normalized with URL templates. After you register templates, do the following.
- In Policies → Behavior Profiles, click Build Now for
websec-bola-baseline-5mandwebsec-bola-baseline-1h. After this they are rebuilt every day at 04:00. - When the builds finish, enable these two rules in Policies → Batch Rules.
| Rule | Schedule | Detects |
|---|---|---|
| BOLA 객체 열거 의심 (5분) | Every 5 minutes | Fast object enumeration in the last 5 minutes |
| BOLA 객체 열거 의심 (1시간) | Every hour | Slow enumeration that stays under the 5-minute baseline |
A baseline build reads 30 days of web logs and can take a while on a large volume. Rebuild the baselines after you change the templates substantially.
6. Verify the installation
- Open Web Monitoring and pick a table and a range (for example, the last hour). Charts on the Bots and Errors tabs show that the app reads the web logs.
- 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.
- Object ID requests on the Web Monitoring → Crawling tab show that object ID parameters are set correctly.
Troubleshooting
| Symptom | Cause | Action |
|---|---|---|
| The table list of Web Monitoring is empty | No logger uses the web log schema | Set the logger's log schema to web |
| The Crawling tab is empty | No parameter has the Object ID type | Set the parameter type to Object ID on the URL templates |
| A saved template does not show in the test | It has not reached the nodes yet | Check URL Normalization → Sync Status and click Rebuild if needed |
| Add template is disabled | Not an administrator | Sign in as an administrator |
| No BOLA events at all | The batch rules are disabled or the baselines were not built | Check step 5 |
| The AI Assistant panel does not show | The AI Assistant or Agentic SOC app, or its license feature, is missing | Check the app and the license |