Read risk posture as an action list, not just a dashboard.
Risk posture is where operators translate deny events and control drift into concrete remediation work. It should help you see whether the system is safe to promote, not just whether it is noisy.
Who this is for
Operations leads, security reviewers, and admins responsible for promotion readiness and policy hygiene.
When to use it
Use this before release, after repeated denies, during post-incident review, or whenever a tenant shows worsening violation trends.
Required setup
Required setup: tenant-scoped admin session. The risk surface is an admin route, so the tenant must be present in the URL and the session must already be active.
How to use
1. Open tenant risk posture
Enter via /admin/risk?tenant_id=<tenant> after logging into the tenant admin session.
2. Review trend direction
Look for rising deny counts, repeated policy conflicts, or concentrated violation types instead of isolated one-off events.
3. Group by category
Separate configuration problems, approval gaps, and payload quality issues so the right team can act on the right failure mode.
4. Decide release readiness
Use the trend view to determine whether releases should pause, continue in dry-run, or move ahead with explicit approval.
5. Link remediation back to evidence
Carry audit IDs and evidence references into tickets, exports, or release bundles so remediation stays traceable.
What success looks like
Related console surfaces
/admin/risk?tenant_id=<tenant> - risk posture surface/console/agents/risk-baselines/ - related agent risk view