User Guide
The Web Security app analyzes web server access logs collected with the web log schema. It normalizes request paths to URL templates to extract API parameters, monitors bots, errors and object ID crawling with them, and detects broken object level authorization (BOLA).
Concepts
- URL template: A pattern that groups request paths such as
/api/orders/1024into/api/orders/:order_id. Values inside a path can be extracted as parameters only through a template. - Parameter type: What each parameter of a template carries. Object ID points to an object someone owns (an order, an account, a document), and BOLA detection and crawling monitoring look only at this type.
- Host: The web log schema has no host field, so the table name that stores the logs serves as the host.
Basic workflow
Use the app in this order: register URL templates → set parameter types → web monitoring → run BOLA detection.
You can register templates and parameter types by hand, or leave it to an AI agent (the Web Path Profiler). Once templates are in place, the Crawling tab and the BOLA batch rules work per object.
Menus
| Menu | Description | Guide |
|---|---|---|
| Web Monitoring | Recent web requests as charts and lists on the Bots, Errors and Crawling tabs | Web Monitoring |
| URL Normalization | Manage URL templates and parameter types, check node distribution and normalization results | URL Normalization |
Guide pages
| Page | Contents |
|---|---|
| Getting Started | The whole procedure from registering templates to BOLA detection |
| Web Monitoring | Common conditions, drill-down, the Bots, Errors and Crawling tabs |
| URL Normalization | Template syntax, parameter types, sync status, test |
| BOLA Detection | How it judges, baselines, batch rules, tuning |
| AI Agents | The AI Assistant panel, the Web Security Lead Analyst and the Web Path Profiler |
If you are new to the app, start with Getting Started.