Dashboard and Metrics

Overview

The Fencer dashboard on Main > Home is your security posture at a glance. It aggregates vulnerability data across all of your assets and scan types — code, cloud, network, application, containers — into a sidebar that shows where you stand today and whether things are improving over time.

The dashboard is the starting point for daily security reviews, sprint planning discussions, and stakeholder reporting. The burndown chart and daily metrics snapshots give you the data to demonstrate remediation progress over weeks and months. See Dashboard for the full Home layout.

Dashboard sections

Vulnerability breakdown

The Where you stand card shows how many critical and high vulnerability groups are open, then a Severity breakdown of open vulnerability groups:

Critical — Vulnerabilities requiring immediate attention
High — Significant risk that should be addressed in the near term
Medium — Moderate risk with a longer remediation window
Low — Minor issues to address when capacity allows
Info — Informational findings
Ignored — Findings you have explicitly dismissed from your active backlog

Vulnerability groups collect related findings — for example, all instances of the same CVE across your container images — so you can prioritize systemic issues rather than individual findings. Each count links to the grouped vulnerability list, filtered to match. These counts reflect the live state of your vulnerabilities at the time you load the page.

The same card shows SLA compliance — how many open vulnerabilities have Breached their SLA and how many are Approaching it — once an SLA policy is configured.

Burndown chart

The Progress card plots the total count of open critical and high severity vulnerabilities over the last 90 days. This gives you a trend line showing whether your vulnerability backlog is growing or shrinking.

Key features of the burndown chart:

90-day window — Shows the full rolling quarter of vulnerability data
Per-asset breakdown — Hover over any data point to see which assets (up to ten) are contributing to the total at that point in time
Daily granularity — Each data point represents the snapshot recorded for that day

A declining trendline indicates active remediation. A flat or rising trendline may indicate that new findings are being introduced faster than existing ones are being resolved.

Below the chart, the card shows critical and high remediation figures: Fixed (30 days) (with the number found in the same period), Median days to fix (with the mean), New this week, and Resolved this week. Each figure links to the matching vulnerability list.

Agent tasks and recommended actions

Home’s task board is the working list of agent tasks for the organization. The sidebar’s Recommended actions card surfaces in-progress reviews and pentests to resume, then recurring activities to start (a vulnerability review, pentest, access review, or architecture review) when none has been done in the last 30 days.

Each item links directly to the relevant page so you can act on it without navigating manually. See Dashboard for the full Home layout.

Identity summary

If identity management is enabled for your organization, the Where you stand card includes identity counts:

Total identities discovered
Identities needing review — those flagged for follow-up based on access patterns, stale status, or policy violations

Daily vulnerability metric snapshots

Fencer keeps one vulnerability metric snapshot per asset per day, and updates the current day’s snapshot each time a scan finishes. These snapshots are the data source for the burndown chart and trend analysis features. Ignored vulnerabilities are counted separately and left out of the severity and category counts.

Each snapshot captures:

By count:

Total open vulnerability count
Total ignored vulnerability count

By severity:

Critical, High, Medium, Low, Info counts

By category:

Code (source code vulnerabilities)
Secret (exposed credentials and secrets)
Logs (sensitive data in logs)
Infrastructure (cloud misconfigurations)
Dependency (vulnerable dependencies)
Artifact (container image vulnerabilities)
Config (configuration issues)
License (license compliance findings)
Application (DAST findings)

Snapshots are recorded per asset, which is what lets the burndown chart break each day’s total down by repository, cloud account, or container image.

Burndown chart mechanics

The burndown chart computes each data point by summing the critical and high severity vulnerability counts from the daily snapshots across all assets for that day.

Hover interaction: Hovering over a data point on the chart reveals a breakdown by asset, showing the ten assets with the highest critical + high counts on that day. This helps you identify which assets are driving the overall trend.

Per-asset breakdown: If a single asset accounts for a large portion of the total, it appears prominently in the hover details. This is useful for targeting remediation efforts on the assets with the most impact.

Trend analysis

The 90-day window provides enough history to:

Identify whether recent remediation sprints are producing measurable results
Spot assets that are persistently contributing to the total despite remediation efforts
Correlate vulnerability count spikes with specific scan runs or infrastructure changes
Demonstrate security posture improvement to stakeholders over time

Identifying problematic assets: If the burndown chart shows a persistent baseline that is not declining, use the hover breakdown to identify which assets are holding the count up. Navigate to those assets’ vulnerability views to understand what is outstanding.

Using the dashboard for security posture reporting

The dashboard provides a shareable view of your organization’s security posture. For stakeholder reporting:

Open Main > Home and review the vulnerability breakdown and burndown chart.
Note the current critical and high counts alongside the 90-day trend.
Use the per-asset breakdown to highlight which areas have improved and which need attention.
For formal reports, use the penetration test PDF reports or the SBOM and identity exports described in Reports.

Examples

Reading the burndown chart

After 30 days of active remediation, you expect to see a declining trend in the burndown chart. If the chart shows a flat line despite closing tickets, hover over recent data points — you may find that a new cloud account added 3 weeks ago is introducing new findings at the same rate that existing ones are being resolved.

Identifying problematic assets

Hover over the highest point on the burndown chart. The per-asset breakdown shows that one repository accounts for 60% of the critical + high count on that day. Navigate to that repository in the vulnerability view to review what is outstanding and assign findings to the responsible team.

Tracking remediation progress

Compare the current critical and high count to the count from 30 days ago using the burndown chart. A 20% reduction in critical and high vulnerabilities over a month is a meaningful data point to share with leadership and demonstrates that the security program is producing results.

Troubleshooting

Burndown chart shows no data — The chart needs snapshots from at least two days. New organizations or those that just connected their first integration will see it once scans have run on a second day.
Counts differ from the vulnerability list — The severity breakdown counts vulnerability groups, not individual vulnerabilities, and reflects live data, while the burndown chart counts vulnerabilities as of the last scan that finished on each day. There may be a small discrepancy if vulnerabilities were opened or closed since the last scan.
Identities to review not visible on Home — Identity counts appear on the posture card when identity management is enabled for your organization. Contact your administrator if you expect this feature to be available.
Posture severity breakdown is empty — This means there are no open vulnerabilities to count. If you expect findings, confirm that a scanning integration has completed at least one run.