Arena view
The Arena view provides an interactive, topological representation of your applications and associated components, including source code repositories, images, environments, and access points. Using the toggles, you can overlay various dimensional data — such as prioritized common vulnerabilities and exposures (CVEs), compliance assessments, and certificates — to understand their impact across your application lifecycle.

The ability to view and interact with your application topology this way helps application owners and site reliability engineers (SREs) to understand dependencies across the application lifecycle and assess the impact and priority of identified risks and operational issues.
Populating the Arena view
- Repositories (source code)
- Images
- Applications
- Environments
- Public access points
- Private access points

You can use any of the following methods to populate the Arena view with your application and environment data:
- Use the Concert toolkit to generate, validate, and import data automatically through your CI/CD pipeline. (Recommended)
- Configure data ingestion jobs to import components from your third-party tools and services that you can use to define your applications and environments.
- Upload application, build, and deploy SBOM files in Concert-defined (ConcertDef) format using the Concert UI or API.
| Toggle | Description |
|---|---|
| Priority 1 CVEs | Toggle on to display high priority CVEs impacting your application images and repositories. Concert ingests uploaded vulnerability (CVE) scans of your images, repositories, or runtimes and prioritizes CVEs based on the assessed risk score. |
| Priority 1 exposures | Toggle on to display high priority static or dynamic non-CVE exposures impacting your application and environment components. Concert ingests uploaded vulnerability (DAST or SAST) scans and prioritizes these vulnerabilities based on their scope of impact. |
| Low compliance assessments | Toggle on to display compliance assessments with which the assessed environment received a low compliance score, indicating a higher compliance-related risk. After you create a compliance profile using controls from one or more catalogs, Concert ingests uploaded compliance scans and assesses the compliance level of each environment. |
| Expired certificates | Toggle on to display the access points associated with your expired digital certificates. Concert ingests uploaded certificate data and helps you track and address expiring certificates before they impact the availability of your applications. |
Upload a CVE vulnerability scan in one of the supported formats to assess prioritized CVEs impacting your application components.

Upload a static (SAST) or dynamic (DAST) vulnerability scan to highlight exposures to your source code or environment access points.

Upload a compliance scan to highlight the compliance level of the assessed environments.

Upload your digital certificate data to understand the impact on your environment access points.

Interacting with the Arena view
Each node in the Arena view represents an individual object or component. For example, the following image shows seven node representing the seven applications defined in the Concert instance.

Each node represents the relative number of associated or impacted components. Hovering over a node provides more details about that object and highlights the specific associations across the topology.

- Clicking an image or repository displays additional details, including associated applications, packages, and prioritized CVE findings.
- Clicking an application or environment redirects you to the relevant details page in your Inventory .
- Clicking a CVE or exposure redirects you to the Vulnerability dimension, providing details for the selected CVE, including an Impact view with a more granular view of the components impacted by this CVE.
- Clicking a certificate displays a more granular Impact view for the selected certificate.
- Clicking a compliance assessment displays more detailed scan results, including the assessed environment, relevant compliance profile and controls, and the calculated compliance level and score based on the number of passed versus total controls.