> 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/system/security.md).

# Security

The eAuditor system uses data protection, access control, and communication security mechanisms between components. The infrastructure maintenance approach and the configuration of certain security controls vary depending on the deployment model.

This page describes the security of **eAuditor Cloud**  (SaaS service) and **eAuditor On-Premise**  (installation in the organization's infrastructure). Select the appropriate tab in each section to view information about the version you use.

{% hint style="info" %}
**How to Read This Page** Information above the tabs applies to both models. Information in the **eAuditor Cloud** or **eAuditor On-Premise** tab applies only to the specified model. The detailed description of historical V9 AI tests does not confirm that the latest release or eAuditor Cloud has undergone an identical scope of testing.
{% endhint %}

## Infrastructure, Data Protection, and Storage

Data security depends both on the technical controls in place and on who maintains the system environment.

{% tabs %}
{% tab title="eAuditor Cloud" %}

### Cloud Infrastructure and Data Separation

* All **eAuditor Cloud** servers are located in **Poland**, in data centers that meet the requirements of **the GDPR** and national personal data protection regulations.
* Infrastructure location:
  * **OVHcloud data center in Ożarów Mazowiecki (Kazimierza Kamińskiego 6, 05-850 Ożarów Mazowiecki, Poland) —** a facility managed by [**OVHcloud sp. z o.o.**](https://www.ovhcloud.com/pl/), which holds, among others, the **ISO 27001, ISO 27017, ISO 27018, ISO 27701**certifications, as well as **SOC 1/2/3** standards (as of November 13, 2025). \
    More information: [OVHcloud Compliance and Certifications](https://www.ovhcloud.com/pl/compliance/)
* Each customer has **their own dedicated database**, which is not shared with other services or customers.
* Data is not transferred outside the **European Economic Area (EEA)**.
* To ensure the highest level of security, the service regularly undergoes **penetration tests** and **security audits** conducted by independent, specialized organizations. More information is available at this [link](https://www.eauditor.eu/cloud-trust).

### Data Location and Flow

Data is not transferred outside the European Economic Area (EEA). **The only exception is data related to payment processing**, which is processed by the Stripe operator on servers also located outside the EEA (including in the United States). This includes only information required to process payments, such as purchaser details, billing information, subscription information, and transaction details.

**This does not apply to any data collected by the eAuditor cloud system**, such as inventory, activity monitoring, security policies, disk encryption, DLP data, or any technical information from the customer's computers—this data remains exclusively on servers in Poland.

More information about the security of payment processing is available in the section [**Payment and Payment Processor Security**](#bezpieczenstwo-platnosci-i-operatora-rozliczen).

### Data Storage and Deletion

Data sent to **eAuditor cloud Services** is stored in the **Customer Account** and can be deleted by the Customer at any time.

After the Service ends, the Customer Account is blocked for 14 days, after which the data is **permanently deleted (on the 15th day after the Account is closed)**, subject to obligations under applicable law.

After data is permanently deleted, it is **technically impossible to recover it**.

After the Account is closed, the Administrator processes Customer data **only to the extent and for the period necessary to fulfill legal obligations**, in particular those arising from accounting and tax regulations.
{% endtab %}

{% tab title="eAuditor On-Premise" %}

### Organization Infrastructure

eAuditor On-Premise is installed in infrastructure designated by the organization. The data storage location, network configuration, application server, database, and administrative access depend on the selected deployment architecture.

The entity maintaining the deployment—the organization or its IT service provider—is responsible for the physical and network security of the environment, updating server systems, data storage, and access management.

Data residency rules, data center certifications, or account retention policies for eAuditor Cloud should not be assumed to apply to an On-Premise installation. In this model, these depend on the specific environment and procedures in place.

<figure><img src="https://3262380731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdzip3GyvGq5q5J3qckWN%2Fuploads%2F3sLlqoN1xdSzVHfIdhZG%2Fimage.png?alt=media&amp;token=fdf10cd7-bceb-4b73-b175-37d5d529a419" alt="Schemat lokalnego wdrożenia eAuditor On-Premise pokazujący serwer aplikacyjny, bazę danych, konsolę administratora i komputery z agentami."><figcaption><p><em>Diagram of a local eAuditor On-Premise deployment showing the application server, database, administrator console, and computers with agents.</em></p></figcaption></figure>
{% endtab %}
{% endtabs %}

## Transmission Encryption and Component Communication

Communication **eAgent - eServer** is secured using **TLS 1.3**. In both models, this refers to an SSL certificate with a key length of **4096 bits** for the eAgent and eServer components. Encryption mechanisms protect the confidentiality and integrity of transmitted information.

{% tabs %}
{% tab title="eAuditor Cloud" %}
Access to the eAuditor Cloud console is provided over a secure **HTTPS**connection. Transmission encryption covers user-to-service communication, data exchange between components, and authentication operations.

Data transmission is secured using **SSL/TLS**, ensuring the confidentiality and integrity of communication between the user and the service.

Communication between system components (**eAgent** and **eServer** ) uses the **TLS 1.3**.

Both **eAgent**and **eServer** have their own certificates **with 4096-bit SSL keys**, providing a very high level of data transmission security.

Encryption covers real-time data transmission as well as communication during authentication processes and the exchange of system information.

{% hint style="info" %}
Cloud infrastructure security configuration is the service provider’s responsibility. The customer does not need to configure the application server or console certificates themselves.
{% endhint %}
{% endtab %}

{% tab title="eAuditor On-Premise" %}
Agent-to-server communication uses TLS 1.3. In addition, the organization should ensure that access to the web console is properly secured, particularly by configuring **HTTPS** and managing certificates properly.

Configuring certificates and HTTPS connections in **Apache Tomcat**is recommended. The specific settings depend on the application server version and the architecture in use.&#x20;

{% hint style="warning" %}
Do not copy historical configurations from Tomcat 8.5 or earlier Java environments into a modern deployment without verification.
{% endhint %}
{% endtab %}
{% endtabs %}

## Authentication and Access Control

Console access is tied to user authentication. Additional identity verification reduces the risk of unauthorized access if a password is exposed. Administrator permissions should be assigned according to job responsibilities.

{% tabs %}
{% tab title="eAuditor Cloud" %}

### Multifactor Authentication (MFA)

eAuditor Cloud supports **MFA** through applications such as **Google Authenticator** and **Microsoft Authenticator**. An organization administrator can require account users to use MFA.

Access to features and data can be organized based on **roles and assigned permissions (RBAC)**.

**One-Time Code Sent by Email**. When a user covered by additional verification signs in, the system sends a code to the user's email address.

{% hint style="info" %}
Identity integrations, including **Microsoft Entra ID**, may depend on the current version and feature rollout stage.&#x20;
{% endhint %}
{% endtab %}

{% tab title="eAuditor On-Premise" %}

#### Sign-In with Additional Security

The eAuditor On-Premise system supports additional authentication mechanisms that enhance the security of access to the administration console. Depending on the configuration, an administrator can require additional user identity verification during sign-in.

Available mechanisms include:

* **Multifactor Authentication (MFA)** — additional identity verification using the Google Authenticator or Microsoft Authenticator app.
* **One-Time Code Sent by Email (2FA)** — during sign-in, the system generates a unique verification code and sends it to the user's email address.

**Sign-In with a One-Time Code (2FA)**

The 2FA mechanism secures access to the administration console by requiring an additional verification code.

Two-factor sign-in can be enabled for all administrators or selected user accounts.

The system allows you to specify mechanism parameters, such as:

* **Code validity** — the period during which the generated code remains active.
* **Interval between messages** — the minimum time between consecutive code deliveries.
* **Message subject and body** — the ability to customize the email containing the verification code.

For email-based authentication to work, the SMTP server must be configured correctly.

**Communication Security**

Communication with the administration console can be secured using HTTPS, which encrypts transmitted data.

When authentication uses certificates and hardware keys, properly configuring encrypted communication is an important part of protecting the sign-in process.

The system supports the use of certificates and security configuration at the Apache Tomcat application server level.

For detailed instructions on configuring each authentication method, see the eAuditor On-Premise system administration documentation.
{% endtab %}
{% endtabs %}

## Backups, Availability, and Updates

Backups are used to restore data after a failure. Backups performed by the Cloud service provider should be distinguished from those organized and maintained in an On-Premise environment.

{% tabs %}
{% tab title="eAuditor Cloud" %}
The scope and availability of backups depend on the selected subscription plan:

* **FREE plan** – backups are not available.
* **INV100** and **ACT200** plans – the system creates **1 backup**, stored in the same location as the eAuditor cloud infrastructure, namely at the **OVHcloud data center in Ożarów Mazowiecki**.
* **DLP300 plan** – **2 backups**:
  * are available, one stored in **Ożarów Mazowiecki**,
  * and the other in a **separate location within the European Union**, meeting the described security and compliance standards.

Backups are used to restore data in the event of a failure or loss of service availability. The documentation does not specify how frequently they are created or a guaranteed recovery time, so these parameters should not be assumed without confirmation from the provider.

### Service Availability

The provider states that **eAuditor Cloud has an annual availability of 99.90%**. Detailed service terms are governed by the applicable contractual documents and the [terms and conditions](https://www.eauditor.eu/regulamin-cloud).

### Updates

New versions of eAuditor Cloud and patches are made available automatically. Updates include security patches, functional changes, and service improvements.
{% endtab %}

{% tab title="eAuditor On-Premise" %}

### Backups and Recovery

Backup creation and retention policies depend on the organization's environment configuration. As part of deployment maintenance, the backup schedule, target locations, retention period, and recovery testing procedure should be defined.

### Availability and Updates

The availability of an On-Premise deployment depends on the organization's infrastructure, administration practices, and recovery procedures. Application, operating system, database, and application server updates should be planned as part of environment maintenance.

{% hint style="info" %}
The availability statement **99,90%** provided for eAuditor Cloud does not automatically guarantee the availability of an On-Premise installation.
{% endhint %}
{% endtab %}
{% endtabs %}

## Security Testing and Audits

Security testing helps identify potential weaknesses in applications, interfaces, and components installed on computers. The scope of published information about testing performed differs between Cloud and On-Premise.

{% tabs %}
{% tab title="eAuditor Cloud" %}
The service is subject to **regular penetration testing and security audits** conducted by independent specialized organizations.

Information about the current scope of Cloud testing and the availability of audit documents should be obtained directly from the provider.
{% endtab %}

{% tab title="eAuditor On-Premise" %}

### Documented Scope of eAuditor V9 AI Testing

The **eAuditor V9 AI** system underwent **126 vulnerability tests**. According to the description of the work performed, the identified vulnerabilities were analyzed and remediated. Testing included:

* **threat modeling** - identifying, classifying, and prioritizing threats;
* **web application and REST API penetration testing** - assessing security controls and communications;
* **agent security testing (Thick Client application)** - assessing the component installed on the computer.

The components tested included the eAuditor web application, the agent, and the REST API used by agents.

### Testing methodology

The following was used to test the web application: **OWASP ASVS**, and the following recommendations were used when analyzing the API: [OWASP REST Security Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/REST_Security_Cheat_Sheet.html).

The scope of the assessment included, among other things:

* injection vulnerabilities (SQL, XML, code, and command injection), XSS, and CSRF;
* authentication, authorization, and the possibility of bypassing access controls;
* insecure object references, data exposure, and configuration errors;
* SSL/TLS security, vulnerable components, redirects, and Local/Remote File Inclusion;
* security of data and credentials stored by the agent;
* integrity and confidentiality of client-server communications;
* process memory and resource management, including overflow, format string, type confusion, and DLL hijacking vulnerabilities;
* service permissions and correct use of cryptographic mechanisms.

The analysis used, among other tools: **IDA Professional, Hex-Rays Decompiler, Burp Suite Professional, Wireshark, WinDbg, GDB, and Process Monitor**. **No source code audit was performed**.

Vulnerabilities were assessed using **CVSS (Common Vulnerability Scoring System)**, taking into account, among other factors, the attack vector and complexity, required privileges, user interaction, and impact on confidentiality, integrity, and availability.

{% hint style="info" %}
The description applies to the tested release **eAuditor V9 AI**. It does not indicate that the same audit was performed for every subsequent version of the system.
{% endhint %}
{% endtab %}
{% endtabs %}

## Secure configuration and administrator responsibilities

Protecting the system requires not only the mechanisms implemented by the vendor, but also proper management of access, configuration, and the operating environment.

{% tabs %}
{% tab title="eAuditor Cloud" %}

### Payment security

As part of our billing model, we use **Stripe**, which also contributes to the security of the eAuditor cloud system.

Stripe is certified as a [**PCI DSS 4.0-compliant Service Provider Level 1**](https://docs.stripe.com/security), representing the highest level of security for processing payment card data.

Stripe has **SOC 1 and SOC 2 Type II**compliance reports, and all API connections and the dashboard operate exclusively over a secure HTTPS/TLS channel. [More.](https://docs.stripe.com/security/guide)

As a result, your payment data and subscription information are processed by a provider that meets rigorous industry standards.

### User responsibilities

To ensure secure use of the Service, the following rules apply to everyone with access to the Customer's account, both **Users**and **Account Administrators** (as defined in the Service Terms):

* Use the current version of a recommended web browser: **Chrome, Edge, Firefox** or **Safari**.
* Regularly update your browser to the latest release.
* Note that using browsers other than those recommended may cause the Service to malfunction.
* Protect credentials and do not share them with unauthorized individuals.
* Use the Service in accordance with applicable laws and the rules set out in the Service Terms.

**Additional responsibilities of the Account Administrator:**

* Manage User access and control the permissions granted.
* Oversee the configuration of the Customer Account.
* Respond to suspected unauthorized access or security breaches.

For more information, see the [**eAuditor Cloud Service Terms**](https://app.eauditor.eu/register).
{% endtab %}

{% tab title="eAuditor On-Premise" %}

### Restricting access in the application configuration

eAuditor allows you to restrict the servers and paths permitted for use by the application through the **`config.properties`**. This solution allows you to restrict, among other things:

* servers **AD DS** used for imports;
* locations of **database backups**;
* paths and servers used during **data imports**;
* locations for saving **reports**;
* permitted values for the **Host** and **Origin**;
* headers **SMTP** servers used to send messages.

Example parameter names from historical documentation:

```properties
props.activedirectory.allowedservers = ["172.16.115.17"]
props.dbbackup.allowedpaths = ["c:/btc/backup-db/ehelpdesk*"]
props.imports.allowedpaths = ["c:/btc/import/*"]
props.reportssend.allowedpaths = ["c:/btc/reports/*"]
props.imports.allowedservers = ["127.0.0.1","172.16.115.251"]
props.headerhost.allowedservers = ["172.16.115.251:8543","dbr-hvdlpdev:8543"]
props.headeroriginhost.allowedservers = ["172.16.115.251:8543","dbr-hvdlpdev:8543"]
props.smtp.allowedservers = ["127.0.0.1"]
```

These are **syntax examples**, not a ready-to-use set of settings to paste directly. Replace the addresses and paths with values for your own environment, and verify the availability and meaning of the parameters for your installed version. An empty list `[]` for selected settings disabled the corresponding function (e.g., import or backup).

### Secure HTTPS communication

The eAuditor On-Premise system allows you to secure communication between the user's browser and the administrative console using HTTPS.

Using an encrypted connection protects transmitted data, including authentication information, from unauthorized access during transmission.

Secure connections are handled by the application server **Apache Tomcat**, which allows you to configure SSL/TLS certificates and encryption parameters.

Security configuration may include:

* **SSL/TLS certificates** — used to secure communication and verify the server's identity.
* **Java Key Store (JKS)** - used to store certificates and cryptographic keys.
* **Encryption protocols and algorithms** - selected according to the organization's security requirements and the capabilities of the environment in use.

Security parameters should be adjusted to the current version of the application server and applicable cryptographic standards.

Detailed instructions for configuring HTTPS and managing certificates will be provided in a separate eAuditor On-Premise administration guide.

### Administrator Responsibilities

The organization should apply updates to the server, database, and middleware components; control access to the console; secure data backups; restrict service permissions; and verify the configuration after changes to the environment.
{% endtab %}
{% endtabs %}

***

## Frequently Asked Questions

<details>

<summary><strong>Do eAuditor Cloud and On-Premise have identical security measures?</strong></summary>

No. Both models use mechanisms to secure communications and access, but they differ in architecture, scope of administration, configuration, and responsibility for maintaining the infrastructure.

</details>

<details>

<summary><strong>Does eAuditor Cloud store customer data outside Poland?</strong></summary>

According to the environment provider's statement, technical data collected by the system is stored in Poland. Payment-related data is processed separately by Stripe and may be transferred outside the EEA.

</details>

<details>

<summary><strong>Does eAuditor Cloud perform backups?</strong></summary>

Yes, but this depends on the plan. FREE does not include backups, INV100 and ACT200 include one backup, and DLP300 includes two backups in separate locations.

</details>

<details>

<summary><strong>Does eAuditor support MFA?</strong></summary>

Yes. eAuditor Cloud and eAuditor On-Premise support authenticator apps and email codes, while On-Premise additionally supports the ePass hardware token. The availability of a particular method depends on the system model and version.

</details>

<details>

<summary><strong>Has the system undergone penetration testing?</strong></summary>

A description has been published for eAuditor V9 AI of **126 vulnerability tests**, covering the web application, REST API, and agent.

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

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

```
GET https://eaclouddoc.eauditor.eu/eacloud-docs-en/system/security.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.
