> For the complete documentation index, see [llms.txt](https://eaclouddoc.eauditor.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/it-infrastructure/software.md).

# Software

Section **Software** enables viewing and analyzing applications detected on computers monitored by eAuditor Cloud. It allows you to check which programs are used in the organization, where they were installed, and whether known security vulnerabilities exist for the detected versions.

In this section, you can:

* check which applications were detected in the organization,
* see the number of installations of individual programs,
* determine which computers have a given application installed,
* check the vendor, version, and installation date,
* monitor recently installed programs,
* identify known vulnerabilities assigned to the detected versions,
* remotely initiate uninstallation of selected applications,
* filter, sort, and export data.

<figure><img src="/files/1b836c14d1a3c4723585da7eaf6717f9be02b57e" alt="główny widok sekcji Oprogramowanie" width="375"><figcaption></figcaption></figure>

{% hint style="info" %}
Software information is collected by the eAgent service. Data freshness depends on the last computer scan and on establishing communication with eAuditor Cloud.
{% endhint %}

### How do you use this section?

Select the subpage appropriate for the task you want to perform:

* [**Software inventory**](/eacloud-docs-en/features/it-infrastructure/software/software-inventory.md) - viewing programs, versions, vendors, computers, and installation dates.
* [**Application uninstallation**](/eacloud-docs-en/features/it-infrastructure/software/uninstalling-applications.md) - initiating and monitoring remote program removal.
* [**Software vulnerabilities**](/eacloud-docs-en/features/it-infrastructure/software/software-vulnerabilities.md) - identifying known vulnerabilities assigned to detected products and versions.
* [**Troubleshooting**](/eacloud-docs-en/features/it-infrastructure/software/troubleshooting.md) - assistance with incomplete data, uninstallation errors, or vulnerability identification issues.

### Filtering and sorting

Available views allow you to narrow the results to the information needed at a given time. Depending on the view, you can filter the data, among other criteria, by:

* program name,
* vendor,
* version,
* computer,
* organizational structure,
* operating system,
* installation date,
* detected vulnerabilities.

Column headers allow you to sort the data. Active filters also affect the scope of the data displayed and exported. [More about filtering](/eacloud-docs-en/features/it-infrastructure/computers/filtering-and-search.md).

{% hint style="warning" %}
Before exporting, check the active filters. The export may include only the data visible in the currently selected view.
{% endhint %}

### Data export

Data can be exported to a supported format, for example:

* CSV,
* ODS,
* XLSX,
* XML.

Export is useful when:

* preparing reports,
* performing license control,
* verifying disallowed applications,
* analyzing changes in the environment,
* planning updates,
* analyzing vulnerabilities.

### How to interpret the data?

A single program may appear on multiple computers and in several versions. Therefore, during analysis, it is worth distinguishing between:

* **program** - a consolidated entry representing an application,
* **installation** - an instance of a program on specific computers,
* **version** - an application variant detected on the device,
* **installation date** - information provided by the operating system or installer,
* **detected vulnerability** - a known vulnerability matched to the product and its version.

{% hint style="info" %}
The data is based on information collected from computers. The application vendor may record the name, version, or installation date in an incomplete or nonstandard way. This may affect how the program is displayed in the table.
{% endhint %}

### Frequently Asked Questions

<details>

<summary><strong>Why does the same program appear in several rows?</strong></summary>

A program may be installed in different versions or recorded under different names. Separate entries may also refer to different architectures, components, or editions of the same product.

</details>

<details>

<summary><strong>Does the absence of a program from the list mean it is not installed?</strong></summary>

Not always. The program may not have been detected yet, the computer may not have sent current data, or the application may not record the installation in a standard way. This also applies to some portable applications.

</details>

<details>

<summary><strong>How quickly will a newly installed program appear?</strong></summary>

The program will appear after a software scan is performed and the results are sent by eAgent. The update time depends on the scan schedule, the state of the computer, and its connection to eAuditor Cloud.

</details>

<details>

<summary><strong>Can all detected applications be uninstalled remotely?</strong></summary>

No. The ability to uninstall depends, among other things, on the information recorded by the program installer and support for silent installation. Some applications require user interaction or the use of a dedicated vendor tool.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/it-infrastructure/software.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
