> ## Documentation Index
> Fetch the complete documentation index at: https://docs.backline.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Applications
> Get an application-level view of your security posture across repositories, runtime assets, vulnerabilities, and remediations
The Applications page gives you an application-level view of your security posture across repositories, runtime assets, vulnerabilities, and remediations.
Use Applications to understand which applications are affected by security issues, how severe the exposure is, and what remediation work is currently open.
You can find this page under: **Applications**
## Overview
Backline automatically discovers applications from connected code, runtime, and security data.
The Applications page helps security and engineering teams:
* Review all discovered applications in one place
* Understand the current risk level of each application
* See related vulnerabilities and open remediations
* Review runtime assets connected to an application
* Add business context such as criticality, business unit, description, notes, and tags
* Navigate from an application to the relevant Vulnerabilities and Remediations views
## Applications Inventory
The Applications page shows all discovered applications in a table.
Each row represents one application and includes key information such as:
* **Application Name** — The application display name.
* **Risk Score** — The current application-level risk score.
* **Business Criticality** — The business importance assigned to the application.
* **Environment** — The environment or environments associated with the application.
* **Deploy Status** — Whether the application is deployable or not.
* **Vulnerabilities** — The number of vulnerabilities associated with the application.
* **Open Remediations** — The number of active remediations associated with the application.
* **Scan State** — The current scan state of the application.
* **Tags** — Custom tags assigned to the application.
* **Last Scanned** — The most recent scan date.
Click an application row to open the application details panel.
## Searching and Filtering Applications
Use search and filters to focus the application list.
Search supports application names and works together with all active filters.
Available filters include:
* **Scan State** — Active, Stale
* **Risk Score** — Critical, High, Medium, or Low
* **Business Criticality** — Critical, Standard, Not critical
* **Environment**
* **Tags**
* **Last Scanned** — Less than a week, less than a month, more than a month
Environment values are shown as detected by Backline unless they were manually renamed.
## Application Risk Score
The Application Risk Score helps you understand which applications need attention first.
The score reflects the risk created by active vulnerabilities associated with the application. Resolved and dismissed vulnerabilities do not affect the score.
The score is based on the highest-risk active vulnerability in the application, with additional weight when the application has multiple high-risk active vulnerabilities. This means that an application with one severe vulnerability may already have a high score, and an application with several high-risk vulnerabilities may receive an even higher score.
Score ranges:
| Score | Range |
| -------- | ------ |
| Critical | 90–100 |
| High | 70–89 |
| Medium | 40–69 |
| Low | 0–39 |
If Backline does not have enough information to calculate the score, the value is shown as N/A.
## Application Details Panel
Click an application to open its details panel.
The panel includes the application name, business criticality, scan state, and last scanned date. It also includes four tabs:
Main application summary and discovery context.
Runtime or deployment assets associated with the application.
All active vulnerabilities associated with the application.
All active remediations associated with the application.
### Overview Tab
The Overview tab shows the main application summary and discovery context.
**Identity**
This section shows technical information about how the application was discovered. It may include:
* Repository
* Path
* Dockerfile
* Languages
* Last Scanned
* Scan Status
**Risk and Security Context**
This section shows the application's current security context. It includes:
* Risk Score
* Vulnerability count
* Environments
**Tags**
This section shows the tags assigned to the application. Tags can be used to group, search, and filter applications.
**Business Context**
This section shows business metadata that helps your team understand the application. It may include:
* Business Unit
* Description
* Notes
Use this section to explain what the application does, who owns it, or any additional context that can help security and engineering teams prioritize work.
### Runtime Assets Tab
The Runtime Assets tab shows runtime or deployment assets associated with the application.
Runtime asset details may include:
* Environment
* Service
* Registry
* Image
If no runtime assets are associated with the application, Backline shows an empty state.
### Vulnerabilities Tab
The Vulnerabilities tab shows all active vulnerabilities associated with the selected application.
Use this tab to understand which security issues currently affect the application. Clicking a vulnerability opens the vulnerability details view.
### Remediations Tab
The Remediations tab shows all active remediations associated with the selected application.
Use this tab to track active remediation work for the application. Clicking a remediation opens the remediation details view when supported.
## Editing Application Metadata
You can edit supported application metadata from the application details panel or from the row actions menu in the Applications table.
Click **Edit** to open the Edit Application modal.
Editable fields may include:
* **Name** — The application display name.
* **Business Criticality** — The business importance of the application.
* **Environments** — Environment display names associated with the application.
* **Business Unit** — The organizational or business group related to the application.
* **Description** — A short explanation of what the application does.
* **Notes** — Internal notes for your team.
* **Tags** — Custom tags used for grouping and filtering.
Changes are not saved automatically. Click **Save Changes** to apply updates, or **Cancel** to discard them.
Environment names are shared across applications. If the same environment is used by multiple applications, renaming it updates the display name everywhere it is used.
## Applications in Vulnerabilities
Applications are also shown in the Vulnerabilities area.
The Vulnerabilities table includes an **Application** column and an **Application** filter. Use the filter to view vulnerabilities for one or more applications.
The vulnerability details panel also shows the associated application in the Details section.
If no application is associated with a vulnerability, Backline shows N/A.
## Applications in Remediations
Applications are also shown in the Remediations area.
The Remediations table includes an **Application** column and an **Application** filter. Use the filter to view remediations for one or more applications.
A remediation can be associated with one or more applications. When multiple applications are associated, Backline shows the first application and a **+N** indicator for the remaining applications.
The remediation details panel also shows the associated application or applications in the Details section.
If no application is associated with a remediation, Backline shows N/A.
## Best Practices
Use Applications to review security risk by business context, not only by technical asset.
Recommended workflows:
Begin with applications that have a **Critical** or **High** Risk Score.
Use Business Criticality to understand which important applications need faster attention.
Add descriptions, business units, notes, and tags so security and engineering teams share the same context.
Use the Vulnerabilities tab to review the issues affecting an application.
Use the Remediations tab to track the work already opened for that application.
Review stale applications to make sure application data is still accurate.