Policy analytics

Policy, action and rule hit analysis.

Policy, action and rule hit analysis.

This screen belongs to the Secure deployment operator, not an ordinary hosted customer. Hosted customers have a separate account page with their own keys and limits; policy and service settings are not exposed there. Contact the operator to change protection. In the operator console, open the route listed above; a report tenant filter does not automatically scope a global setting.

Examples use educational data. Use your own authorized tenant in real integrations. Each screenshot shows the actual frontend, with the source and educational/demo mode stated below it.

Step-by-step actions

  1. Policy analytics → 7d → Refresh.
  2. Locate policy ID and compare hits/blocked/block rate.
  3. Click its row to open audit and review sample requests.
  4. Edit under Policies after reviewing false positives.

Every control and its meaning

Control / parameterValues, units and effect
Период / Period7d / 30d / 90d for policy hits. Does not change status or rule order.
Hits / Block rate / Top ruleHits, blocks and block share; top rule/tenant identify records to investigate.
Строка политики / Policy rowClick opens Audit filtered by policy_id. Edit the policy under Policies.

Verify the result

Find the matching rule in audit after a synthetic request; reread the report using the same window.

Errors, disabling and reverting changes

Zero hits does not prove a disabled policy: it may be draft/paused, use another scope or have no matches. Check status and conditions.

Policy analytics · actual staging
Policy analytics · actual staging
2026-10-15 · Actual staging application. Non-personal settings or aggregate test-stand metrics, not real customer statistics or a benchmark. Operator profile and other tenant lists excluded. Protection settings were not changed.
  1. Period
  2. Open policy audit

Detailed security settings · Traffic analysis · FAQ · All application sections