This feature is included with Titan Secure.
The Supply Chain Risk dashboard gives you a consolidated view of high-priority vendor risk and remediation activity across your supply chain. It draws entirely on findings data and brings together signals such as actively exploited vulnerabilities, high-criticality open findings, and closure outcomes, so you can see both where risk exists and how effectively your team is addressing it.
Instead of reviewing individual vendor records to assess exposure, you can use the dashboard to surface the most critical patterns across your vendors and portfolios at a glance.
The dashboard helps you answer three questions:
- How urgent is the situation? Which vendors carry actively exploited vulnerabilities, and how much high-priority risk is open right now.
- Are we making progress? Whether your team resolves findings faster than new ones appear.
- How responsive are vendors? How findings move through the workflow and how they are ultimately closed.
How the time period works
The dashboard covers a fixed 30-day window, based on when each finding is first detected. Findings first detected 31 or more days ago do not appear in the dashboard.
Within this window, each widget plots a daily trend: for any given day, it shows the number of findings first detected on that day. For example, looking at 20 days ago, you can see how many findings were first detected then.
Widgets that compare two periods use a preceding 30-day comparison period.
Widgets in this report
The dashboard includes the following widgets. Each widget supports drill-down to the underlying findings and CSV export.
| Widget name | What it shows | How to read it |
| Active Security Events | A metric with a 30-day trend showing the count of security events currently in "Active" status across the vendor portfolio, based on when each event was first detected. | Use this as a live pulse check. A rising trend means new active security events are accumulating faster than they're being resolved or downgraded. |
| Security Events Snapshot | A table of the top 5 security events (status Active or Investigating) with the most vendors impacted, sorted by vendor-impact count, showing event name, type, status, and number of vendors affected. | Use this to spot the events with the widest blast radius across your portfolio. The ones affecting the most vendors are usually the ones to prioritize for coordinated outreach. |
| Vendors with KEVs | The number of vendors with known exploited vulnerabilities (KEVs) detected in the last 30 days, and how that volume changes over the period. | Use this as your urgent escalation list. A rising trend means more vendors carry actively exploited vulnerabilities and need attention before an exploit becomes a breach. |
| Priority Open Findings | The total volume of high-criticality findings that remain open across vendors over the last 30 days, shown as a trend. | Use this to gauge your overall unresolved high-priority risk. An upward trend means a new risk is outpacing remediation, and the team is falling behind. |
| Findings Status Distribution | A current snapshot of open high-criticality findings, broken down by workflow status (Open, In progress, and Pending SSC review). | Use this to see where work sits today. A large "Pending SSC review" segment points to an approval bottleneck; a large "Open" segment means findings have not been picked up yet. |
| Open vs Resolved Findings by Type | The number of new and resolved high-criticality findings during the period, grouped by finding type (for example, Vulnerability or Misconfiguration). | Use this to compare incoming risk with outgoing risk by category. If one type keeps growing while another is being resolved, it signals a gap in how you handle that risk. |
| Portfolio Risk | A snapshot of open high-criticality risk distributed across your portfolios. Resolved findings are excluded, so the widget reflects only current open exposure. | Use this as an executive rollup to compare active risk across business areas and prioritize where to focus. |
| Flagged Open vs Resolved Findings | A week-over-week comparison of flagged high-criticality findings that remain open against those resolved during the period. "Flagged" findings are the items your team actively works on. | Use this to track remediation flow. When the resolved line converges toward the open line, the team is gaining ground; when the lines diverge, new work is arriving faster than it is closed. |
| Resolved Findings: Flagged vs Not Flagged | A stacked bar chart with two bars, "Flagged" and "Not Flagged", each stacked by resolution status (for example, Resolved vs. Decayed) for high-criticality findings. | Use this to compare how much of your resolved-findings volume came from proactively flagged work vs. items closed without ever being flagged, and to see the resolution-status mix within each. |