Skip to main content

Overview

The Vulnerabilities page provides an organization-wide view of open security findings. Use it to review findings across projects, investigate details, export results, and apply triage decisions without opening each scan separately.
The Vulnerabilities Workbench is available to organizations where it has been enabled by Corgea. Contact your Corgea representative to request access. Users also need Can view vulnerabilities workbench, granted through their role, and permission to view at least one finding type. Existing users and roles with finding-view permissions retain access after the upgrade.
Vulnerabilities Workbench with finding-type tabs, status controls, search, a filter icon, and grouped findings
Findings are separated into these tabs:
  • Secrets
  • SAST
  • Logic & Auth
  • SCA Packages
  • Containers
  • IaC
Each tab is available only when you have permission to view that finding type. The badge on a tab shows its unfiltered open-finding count. Counts of 1,000 or more are shortened (for example, 1.8K). If the Workbench shows Almost ready, Corgea is preparing it for your organization. Finding counts, lists, exports, and bulk selection are unavailable until preparation finishes.
Vulnerabilities Workbench showing the Almost ready state

Find and review findings

Select a tab, then expand its groups and projects to reach individual findings. Grouping is tailored to each finding type—for example, SCA findings begin with packages, container findings with images, and IaC findings with rules. Counts of 1,000 or more are shortened (for example, 24.6K). Point at a shortened count to see the exact number. Project rows include an icon that opens the project page in a new tab. Use Previous, Next, and page numbers, when they appear, to move through grouped results. Each list shows the current row range and a total when Corgea has one. Use the status controls to switch between Open, Fixed, False Positive, and the other statuses available for that finding type. Click the filter icon to show severity, project, team, and tag filters. A count on the icon shows how many of those filters are set while the row is hidden. Hiding the row leaves them active. Selecting multiple tags shows findings from projects that have any selected tag. Tag matching is case-sensitive and must match the stored project tag exactly. SCA Packages adds a reachability filter on the main toolbar.
SAST tab with the filter row open and the Tags menu showing a tag search
On Secrets, SAST, Logic & Auth, and IaC, searching by file path requires an explicit Project filter. Expanding a project group alone does not enable file-path search. Without that filter, search matches secret subtypes, CWEs, or IaC rules, depending on the tab. The same search scope applies to group counts, exports, and bulk selections.
SCA Packages tab with package groups, severity, and the Reachable toggle
Use the Team filter on any tab to show findings from projects owned by the selected team that you have permission to view. Combined with a project filter, it shows only projects that match both filters. The team filter also applies when expanding groups, exporting filtered results, and selecting all findings matching the current filters.
Vulnerabilities Workbench with the filter row open and the Team menu showing a team search
Select a finding to open the same details panel used on scan pages. When auto-triage reasoning is available, the panel shows it on the Auto-Triage tab, selected by default, next to a Files Read tab that lists the files read during scanning. From the panel, you can review evidence, assign the finding, and change its status with Current Status. Use Open Full View when it is shown to open the full finding page. The address bar keeps the selected finding, so opening that link again restores the panel when the finding is still in the current results. A comment is required when changing a disposition, and it has to explain the decision rather than repeat it—see Triage Justifications. When you mark a supported finding as accepted risk, you can also choose when that expires. Scan revalidation is disabled by default; contact Corgea support about enabling it. When it is enabled, incremental, full, and pull request scans recheck earlier SAST findings that the new scan did not report again. Corgea carries a finding into the new results when it confirms the finding is still present. During full scans, findings in files that have not changed since the earlier scan are also carried forward. If a recheck cannot be completed, Corgea carries the finding forward unverified, with its triage unchanged. If a recheck completes but is inconclusive, the finding remains on the earlier scan; its absence from the new results does not by itself mean it was fixed. On the main branch, findings that the recheck confirms are gone can be marked fixed. On later pushes to the same pull request, Corgea also marks findings fixed when the code changes confirm their removal, unless the same finding is still open outside the pull request. When recheck reasoning is available, the Auto-Triage tab in the finding details shows it under Re-checked against the current version of this file, above the original reasoning under From the scan that found it.
The Auto-Triage tab showing the recheck reasoning under Re-checked against the current version of this file, above the original reasoning under From the scan that found it
SAST findings carried forward from a previous scan, including unverified ones, retain their triage status, justification, assignee, due date, and accepted-risk expiry date. Carrying a finding forward does not reset or remove its due date or expiry date. When Corgea recognizes a finding at a corrected location, it can carry over an existing triage decision without replacing a decision already made on the new finding. In incremental branch scans, a matching finding in an unchanged file can also inherit the earlier decision; findings in files changed by that scan remain open for review. The finding history records Decision carried over from the finding’s previous location, with the previous location and original decision date when available. SCA and container findings show package details and history in that panel, plus reachability when it is available. If your company requires triage approval for False positive or Accepted risk, changing a Secrets, SAST, Logic & Auth, or SCA Packages finding to that disposition creates a request and leaves the finding unchanged. Containers and IaC change immediately. A different authorized reviewer can approve or reject a request from the approvals queue or the finding details. Requesters can withdraw their own pending requests. Findings awaiting review show a Pending approval badge beside their current status in the workbench and in expanded finding groups on scan pages.
Expanded finding group on a scan page with a Pending approval badge next to the Open status

Export findings

Click Export to open the CSV export dialog. Choose findings matching the active tab and filters, or use Export selection for selected findings. Filtered exports start with the current status, search, and filters; edit them in the dialog before confirming. Selection exports use the selected findings (up to 1,000) instead of those filters. Each finding is exported at its latest occurrence. When findings are selected, the toolbar Export button also defaults to the selection; with no selection, it defaults to the filtered view. For a filtered export, first choose one or more finding types and click Next. All selected types go into one CSV with a Finding Type column. Review the filters copied from the active tab; the dialog warns before dropping filters that the selected types cannot share. The CSV uses Finding Type as its second column, labels dependency findings SCA, and includes First Detection Date and Last Detection Date (blank when unavailable). Fix Status and Scan Metadata are no longer included.
Step 1 of the Vulnerabilities Workbench export dialog with Secrets, SAST, and Logic & Auth selected
Workbench exports are CSV only. The final button reads Download, or Start export for exports that build in the background, and is enabled only after you acknowledge the sensitive-data notice. CSV exports support up to 150,000 rows by default; your deployment may set a different limit. Exports of up to 30,000 rows download as a CSV. Larger exports arrive as a ZIP containing the CSV and export-criteria.txt, which records the scope, filters, row count, requester, request time, and acknowledgement. You can close the dialog while an export builds: Corgea notifies you in the app when the file is ready. If processing takes longer, the dialog shows progress and confirms that a download link will be emailed; when ready, use Download CSV or Download ZIP. Use View progress in Recent exports to return to a running export. Files stay in Recent exports for 12 hours. When an export has expired or failed, its page offers Build it again, which uses the same types and filters with current findings and emails you a link when the file is ready. Exports exceeding the limit are refused; narrow the filters and try again. If the export dialog says the export builds now, keep it open until the download completes. On deployments without background export processing, the dialog shows how long a larger export may take.
Step 2 of the Vulnerabilities Workbench export dialog with three finding types, the Status: Open filter, CSV, and the sensitive-data acknowledgement

Triage findings in bulk

Select individual findings or an expanded group. You can also choose Select all findings matching the current filters after making an initial selection. The bulk action bar lets you:
  • Assign findings to a team member
  • Change the selection to another status the active tab supports, including reopening a finding or accepting risk
  • Export the selection
Bulk action bar with the selected finding, project, and team counts, and Assign, Change status, Export selection, and Clear
Click Change status, choose a Decision, and add a comment that explains the change. The menu lists that tab’s statuses except the one you are already viewing. For Accepted Risk, set Expiry Date (Optional) to a future time, or leave it empty so the acceptance does not expire. After that time, the finding returns to Open and Corgea sends a notification. IaC findings have no expiry date. When your company requires approval, a bulk change to False positive or Accepted Risk on Secrets, SAST, Logic & Auth, or SCA Packages is submitted for approval, and those findings keep their current status until it is approved. Containers and IaC change immediately. Someone who can approve triage requests applies the change immediately on every tab.
Change Status dialog with a Decision menu and a required comment. Expiry Date appears after Accepted Risk is selected.
Bulk status changes require a comment, and the same justification requirement applies: a comment that only repeats the decision is rejected and no status is changed. The action bar summarizes the number of selected findings, projects, and teams, and reports any findings that were skipped. A bulk selection can contain up to 1,000 findings.
Assignment and disposition controls appear only when you have permission to change that finding type. Export remains available with view permission.