Analytics Overview - Executive Bird's-Eye View of Security Posture
Release Date: December 19, 2025
We're launching a streamlined Overview Analytics page that gives executives an instant pulse on security posture. At the top, unified KPIs for Protect, Detect, Remediate, and Govern surface repository coverage, incident volume, remediation speed, and identity safeguards—all at a glance.
What does this mean for you?
- Unified KPI Strip: Quick status check across all security dimensions—repository coverage, critical incidents, remediation time, and governance metrics.
- Monitored Perimeter Trends: Visualize how your monitored repository count evolves week over week.
- Top Risky Data Sources: Identify which repositories generate the most critical and high-severity incidents.
- Critical Incident Trajectories: Track how incident volume changes over time to spot emerging risks.
- Most Common Secret Types: Understand which secret categories appear most frequently in your perimeter.
- Closure Progress: Monitor remediation performance including auto-closures and manual resolutions.
- Governance Signals: View vaulted secrets and breached policies for NHI governance insights.
Why is this important?
This view is purpose-built for leadership reviews and status reporting. Use it to:
- Identify where risk concentrates: Quickly pinpoint which data sources need immediate attention.
- Measure response speed: Track how fast teams respond to security incidents.
- Plan coverage expansion: Understand where monitoring should grow next.
- Demonstrate progress: Show month-over-month / quarter-over-quarter improvements in security posture.
Get started
Navigate to Analytics > Overview to access the new dashboard. Use the KPI strip for a quick status check, then drill into each section to pinpoint hotspots and validate remediation performance.
Learn more about Analytics overview
Fixes
- Risk Score: Removed an empty bullet point that appeared in the risk score explanation when no specific factors were highlighted.
- GitHub Check runs: Fixed an issue where check runs continued to run and block pull requests despite being disabled by property.
