> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/ox-code/ox-code-inventory/applications/application-details/application-details-more-info-tab.md).

# Application Details: More Info tab

The More Info tab provides additional insights into the application's security posture and findings. Use this tab to review findings by attack technique, monitor issue trends, and analyze issue statistics.

### OSC\&R

The OSC\&R section organizes application findings according to the Open Source Cybersecurity Reference (OSC\&R) framework.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-327b676837d493cbda49ce9c7885ddf066fb0d46%2FApplications_details_more_info1.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

Findings are grouped by attack tactic, making it easier to understand how vulnerabilities relate to different stages of the software supply chain attack lifecycle.

Each tactic displays:

* The number of techniques for which findings were identified.
* The OSC\&R techniques associated with the application.
* The number of findings for each severity level within each technique.

Select a technique to view the related findings.

### Issue Trends

The Issue Trends chart shows how the number of issues has changed over time.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-b9cc32c97505e0e06c8d2341a0b46dab0f2d492d%2FApplications_details_more_info2.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

The chart displays issues by severity, allowing you to identify trends such as:

* Increasing or decreasing numbers of findings.
* Changes in the application's overall security posture.
* The impact of remediation efforts over time.

Use this chart to monitor the application's security progress across successive scans.

### Issue Statistics

The Issue Statistics section summarizes the application's findings from multiple perspectives.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-354ae05b46df833b4bc1c17a5a5adb61dd491227%2FApplications_details_more_info3.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

Each widget groups findings by a different attribute.

The available widgets include:

| Widget          | Description                                                                                                        |
| --------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Category**    | Distribution of findings by security category, such as Code Security, Open Source Security, or Container Security. |
| **Severity**    | Distribution of findings by severity level.                                                                        |
| **Issue Owner** | Distribution of findings by the assigned issue owner.                                                              |
| **Source Tool** | Distribution of findings by the OX scanning capability or integrated source that identified them.                  |

Select a value within a widget to further analyze the corresponding findings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ox.security/ox-code/ox-code-inventory/applications/application-details/application-details-more-info-tab.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.