Active Issues new

The Active Issues page is your central workspace for monitoring and managing security, compliance, and configuration risks detected across your connected applications and infrastructure.

Use this page to understand what issues are currently open, where they originate, who owns them, and how they align with your remediation targets. From here, you can prioritize critical findings, assign ownership, and track progress over time.

Issues Table

The Issues table is the main working area of the Active Issues page. It presents all detected security, compliance, and configuration issues across your connected applications and infrastructure, and allows you to review ownership, severity, age, and remediation status in a single, sortable view.

Use this table to identify high-risk issues, understand where they originate, track how long they have been open, and take action to resolve them.

Column reference

The following table explains the purpose and behavior of each column in the Issues table.

Column	Description
Selection	Use the checkbox at the beginning of each row to select one or more issues. Selection enables bulk actions from the page toolbar, such as assigning owners or applying workflow actions.
#	Displays the row number in the current table view. The numbering reflects the current sort and filter state rather than a permanent issue identifier.
Severity	Indicates the risk level assigned to the issue, such as Critical. Severity helps you prioritize remediation based on potential impact and exposure.
Category	Shows the security domain or scan type that detected the issue, such as Open Source Security, Container Security, SBOM, or Infrastructure as Code Scan. This column helps you quickly understand the technical context of the finding.
Name	Provides a short, descriptive title for the issue. The name usually includes the affected component and a brief explanation of the risk, such as a vulnerable dependency, an exposed resource, or a misconfiguration. Select the issue name to open the issue details page, where you can review technical evidence, remediation guidance, and activity history.
SLA	Displays the service level agreement status for the issue. This value shows how much time has passed relative to the defined remediation target. Positive values, such as +8mo or +2y, indicate how long the issue has exceeded its SLA.
Application	Identifies the application, repository, or environment where the issue was detected. This value reflects the connection source, such as a GitHub repository, container image, or cloud resource. Select the application name to navigate to the related asset or integration context.
Issue Owner	Shows the user currently assigned to the issue. Ownership indicates who is responsible for reviewing and coordinating remediation. If no owner is assigned, this column may be empty or display a placeholder, depending on your organization settings.
First Seen	Indicates when OX first detected this issue. This value helps you understand how long the risk has existed in your environment.
Count	Displays how many times this issue appears across assets or scans. A higher count can indicate a systemic problem, such as a vulnerable dependency used in multiple projects.
Actions	Provides a menu for issue-level actions. Use this column to perform tasks such as assigning an owner, updating status, or triggering workflow steps, depending on your organization configuration.

Sorting and scanning

Most column headers support sorting. Select a column header, such as Severity, SLA, or First Seen, to reorder the table and surface the most critical or oldest issues at the top of the list.

Sorting works together with any active filters applied to the page, allowing you to narrow the table to a specific category, application, or risk level and then order the results for review.

Typical workflow

1. Sort by Severity or SLA to identify the most urgent issues.

2. Select an issue name to review technical details and remediation guidance.

3. Assign an Issue Owner if one is not already set.

4. Track progress over time using the First Seen and SLA columns to verify that issues are being addressed within your organization’s targets.