Organization Dashboard
The Organization Dashboard gives you a single view of your security across all projects. Instead of checking each project separately, you can quickly understand risks, track progress, and prioritize actions in one place.
Accessing the Dashboard
- Go to: Dashboard → Organization Dashboard
- By default, the dashboard shows data for all projects you have access to.
- You can:
- Select specific projects using the project picker
- Search by project name or ID
- Select multiple projects
Your project selection is saved, so next time you open the dashboard, it will load the same view.

Permissions and Access
- All users with project access can view their project in the dashboard.
- To view the Dashbaord you need the following scope:
project:Read
Data Refresh and Update Behavior
Dashboard data updates automatically following every completed scan. If no new scan data is available, widgets will display the latest available snapshot.
Notes
- Data is based on the latest available scans
- Different projects may have different scan times
- Always check the Last Scan Date for accuracy
Dashboard Widgets
1. Projects Overview
This section shows 3 key metrics:
Projects - total selected projects, including how many are vulnerable or critical
Users - total users and active users in the last 48 hours
Scans- number of scans in the past 30 days and the last completed scan time
Use this section to quickly understand activity and coverage.
2. Security Grade (A-E)
This shows your overall security posture across several projects
It is automatically calculated based on the number and severity of unresolved Issues (CVSS) detected across the projects.
The grade reflects the worst (highest risk) project in the selected scope. Click the info icon in the widget to view the highest-risk projects.
- A - Excellent Indicates minimal security risk. The projects contains very few or no open Issues. Any issues that were detected are low-severity and were remediated quickly. Reflects a strong, proactive security posture.
- B - Good Represents a generally healthy security status. Some medium-severity issues may still be open, but the overall risk exposure remains controlled.
- C - Moderate Shows the presence of noticeable Issues across multiple components. Typically includes a mix of medium and high severity issues. Requires focused remediation to prevent escalation.
- D - Poor Indicates outstanding high-severity issues and delayed or limited remediation activities. The projects' security posture is weakened and needs immediate attention.
- E - Critical Reflects severe, widespread Issues and significant security debt. Exposure is high and requires urgent remediation to restore acceptable security levels.

3. Unresolved Issues
This widget shows all open issues across your selected projects.
It includes:
- Total number of unresolved issues
- Breakdown by severity (Critical, High, Medium, Low)
- Visual donut chart with percentage breakdown
This helps you understand where your biggest risks are.
You can click on a severity or the chart to open a detailed list of issues.
Inside the table, you can search or filter by:
- Project name or ID
- Issue name of ID
- URL
- Issue type
- Severity level
Clicking on an issue will lead to the issue details page
5. Scheduled & Completed Scans
This section shows scan activity across projects. Use this to track execution and coverage of your scans.
Completed tasks:
Shows which tasks were already completed for the selected projects.
The table includes the following details:
- Project name
- task type (Discovery/Scan)
- Number of Issues or entrypoints found
- Severity breakdown
Clicking on the project name will lead you to the project details page.
Scheduled Tasks:
Shows which tasks are scheduled for the selected projects.
The table includes the following details:
- Project name
- Task name
- Type (Discovery/Scan))
- Countdown
Clicking on the project name will lead you to the project details page
6. Entrypoints Overview
This widget shows the health of your scanned entrypoints.
It includes:
- New, changed, tested, and vulnerable entrypoints
- Connectivity status (OK, problems, unreachable, etc.)
This helps you understand what is being tested and where there are gaps or issues
7. Top 10 Aging Issues
These issues represent security debt and should be prioritized across all selected projects.
These are Issues that have been open for a long time and may require attention.
Use this to identify security debt and prioritize fixes.
8.Repeater Insights
The widget shows:
- Connected, active, and idle repeaters
- Disconnected and disabled repeaters
- Running, queued, and scheduled Scan and Discovery tasks
When multiple projects are selected, the information is combined across those projects.
This gives you an immediate view of your repeater infrastructure, helping you identify availability or capacity issues before they affect your security testing. You can select More Info to open the Repeaters page and investigate the relevant repeaters.
9.Top 5 Issue Types
The widget displays the number and percentage of issues for each issue type. Select an issue type to see the affected projects. Then, select a project to open its Issues page, filtered by that issue type.
This helps you quickly understand your main security risks and decide where to focus.

10.OWASP Top 10 Risk Overview
The OWASP Top 10 Risk Overview provides a clear view of how your open security issues are distributed across the OWASP Top 10:2025 categories.
Available on both Organization and Project dashboards, the widget automatically maps open issues to the relevant OWASP categories. At the organization level, results are aggregated across selected projects, helping security teams identify broader risk patterns across their application portfolio.
Current coverage limitation: Bright does not currently provide security tests mapped to Security Logging and Alerting Failures or Mishandling of Exceptional Conditions. These categories will therefore display 0 open issues. This reflects current test coverage and should not be interpreted as confirmation that the application is not exposed to these risks. Support for additional relevant test types is planned for a future release.
Note: This widget is an informational view based on detected open issues and is not a compliance assessment or certification.
11.Task Results
The widget displays how Scans and Discoveries across the organization ended, with a breakdown of completed, failed, paused, and stopped tasks. Use the project, task type, and date filters to focus on the relevant activity.
This helps you monitor task outcomes across projects and quickly identify projects with execution problems.
12.Task Triggers
The widget displays how Scans and Discoveries across the organization were started, with a breakdown of scheduled and ad-hoc tasks. Use the project, task type, and date filters to compare activity across the organization.
This helps you understand automation adoption across projects and identify teams that still rely heavily on manual execution.
13.Task Actors
The widget displays where Scans and Discoveries across the organization were started from, such as the Web UI or API. Use the project, task type, and date filters to analyze execution sources across projects.
This helps you understand how teams and integrations use Bright and identify the main sources of task activity across the organization.
14.Task Durations
The widget displays how long completed, paused, and stopped Scans and Discoveries across the organization took, grouped into duration ranges. Use the project, task type, and date filters to focus on the relevant activity.
This helps you identify unusual execution patterns across projects and determine where performance or configuration problems may require attention.
Viewing the hosts
To see the hosts that are associated with the selected projects, click on the “hosts” button.

Security Performance & ROI
Use Security Performance & ROI on the Organization Dashboard to see how your team uses Bright, how quickly it resolves issues, and how much time and money it may save. The savings figures are estimates based on the assumptions in your organization’s ROI settings.
Risk Reduction
The Risk Reduction chart shows how many issues opened and how many were fixed over time, broken down by severity. Find it under Risk Management on both the Organization Dashboard and the Project Dashboard.
New and Reappeared issues count as Open, and Resolved issues count as Fixed. The chart excludes issues whose latest status is Ignored.
The totals above the chart reflect the bars currently displayed. To see which issues are included, open the issue list from the widget. To download the chart data, select Export.
Security Practices
The Security Practices score shows which Bright capabilities your organization uses and where you can improve. Bright divides the points earned by 9 to calculate the percentage. Each row shows how many points you earned for that criterion.
| Criterion | Max Points | How to Earn Points |
|---|---|---|
| Scheduled Scans | 1 | Run at least one scan on a schedule during the selected period. Scans started by scheduled workflows also count. |
| Workflow-Triggered Scans | 1 | Run at least one scan started by a workflow during the selected period. |
| Project Coverage | 2 | Complete at least one successful scan or discovery per project. Coverage of 20%, 40%, 60%, or 80% of the selected projects earns 0.5, 1, 1.5, or 2 points, respectively. Each threshold includes the stated percentage. |
| Auto-Resolve Enabled | 1 | Enable Auto-Resolve for the organization or for more than half of its projects. Bright checks the current settings when you view the widget. |
| SLA Compliance | 4 | Resolve findings within their service-level agreement (SLA). Compliance above 20%, 40%, 60%, or 80% earns 1, 2, 3, or 4 points, respectively. |
Mean Time to Remediate (MTTR)
MTTR shows how many days it takes, on average, to resolve an issue after Bright first finds it. Use it to see whether remediation is getting faster and how long issues remain open before resolution.
Each bar shows the average for issues resolved in that interval. The headline shows the most recent interval’s average. An interval with no resolved issues has no average.
Estimated Savings
These widgets estimate the value of time saved on DAST findings. Analyst Hours Saved and Dev Hours Saved use resolved DAST findings in the selected date range and exclude ignored findings.
| Widget | What It Shows | How Bright Calculates It |
|---|---|---|
| Analyst Hours Saved | Estimated time security analysts save when triaging findings with Bright. | For each eligible finding, Bright counts 75% of your configured Manual Triage Time per Finding as time saved. With the default of 1 hour, that’s 45 minutes saved per finding. |
| Dev Hours Saved | Estimated developer time saved by fixing a vulnerability during development. | Bright estimates production fix time at 2.5 times your configured Development Fix Time per Finding. The difference is the estimated time saved per eligible finding. With the default development fix time of 4 hours, that’s 6 hours saved per finding. |
| Estimated Savings | The estimated financial value of the analyst and developer hours saved. | Bright multiplies analyst and developer hours saved by their respective hourly rates in your ROI settings, then adds the two amounts. |
Bright uses a calculation model to estimate time and cost savings. Actual savings vary by team and workflow.
Savings with STAR
Savings with STAR estimates the developer time and cost your team could save with STAR-assisted remediation. Bright applies 80% of your configured development fix time per eligible finding, leaving 20% for review and follow-up. It multiplies the estimated hours by your developer hourly rate.
Organization Settings
Go to Organization Settings → ROI to set the assumptions Bright uses for your organization.
| Setting | Default | What It Changes |
|---|---|---|
| Manual Triage Time per Finding | 1 hour | The time an analyst would spend triaging one finding manually. Used for Analyst Hours Saved. |
| Development Fix Time per Finding | 4 hours | The time a developer would spend fixing one finding during development. Used for Dev Hours Saved and Savings with STAR. |
| Security Analyst Hourly Rate | 75 per hour | The cost of an analyst hour in your selected currency. Used for Estimated Savings. |
| Developer Hourly Rate | 75 per hour | The cost of a developer hour in your selected currency. Used for Estimated Savings and Savings with STAR. |
| Currency | USD | The currency used to display monetary estimates. Enter both hourly rates in the currency you select. Changing the currency keeps the numeric amounts you entered. |
Exporting Data
- The entire dashboard view can be exported as a PDF snapshot for reporting and sharing
- Exports reflect current filters and date ranges.
- Some widgets can be exported as CSV.
- Unresolved Issues
- Risk Reduction
- Exporting data (CSV/PDF) requires
project.reports:read.
Filters
Project selection controls which projects are included
- Severity filter updates all widgets
- All data on the dashboard is affected by these filters

Updated 5 days ago