Supported platforms and integrations

The eAuditor Cloud system supports a wide range of platforms, providing flexibility and adaptability to diverse IT environments.

Supported platforms

Windows operating systems

• Windows 10 / Windows 11

• Windows Server 2016, 2019, 2022, 2025

• Older versions: Windows 7, Windows 8 (only when installing the agent in specific environments)

Linux operating systems

• Debian

• Ubuntu

• Red Hat Enterprise Linux (RHEL)

• Alma Linux

• Rocky Linux

• Oracle Linux

Agent limitations for Linux systems

The eAuditor agent for Linux-family systems has several limitations resulting, among other things, from differences in architecture and available system libraries. One of them is support for encryption protocols:

• communication with eServer TLS 1.2 or newer,

• older distributions (e.g., Debian 9.x) may not support TLS 1.3, which limits connection capabilities or affects transmission security.

Data transmitted by the agent to eServer

1. Information about the currently logged-in user Sent after establishing a connection with eServer and each time a user logs in or logs out.

2. Static hardware information Sent once after the agent's first connection to eServer. Includes elements that do not change over time (e.g., device model, CPU, RAM, disks).

3. Variable system parameters Sent approximately every 3 minutes and only when the value actually changed. This applies, among others, to:

• free disk space,

• available RAM. Changes are reported with an accuracy of 1 MB.

4. Running services The full list of services is sent after the agent's first connection to eServer. Subsequently the agent reports only changes, for example:

• starting a new service,

• stopping a service,

• changes in its state.

Integrations

Entra ID

The system allows connection to Entra ID directly from the administrative console. After establishing the integration, you can configure automatic data import such as:

• users,

• computers,

• organizational structure.

As a result, the administrator does not need to manually recreate the company's structure in the system; data is retrieved and updated according to the information stored in Entra ID.

The integration also allows logging into the system with an Entra ID account. The user does not need a separate password for eAuditor because authorization is performed on the Entra ID side. This simplifies access management, strengthens security (e.g., through MFA and conditional access policies) and enables single-sign-on to all organization services with one credential.

Note: We are working on this functionality. We will announce its deployment in the changelog as soon as it becomes available.

Google

The system allows logging in using a Google account. In this scenario the user does not provide a password to eAuditor because authorization is performed directly by Google. After successful identity verification, Google returns a confirmation that the user is verified and the system grants access according to their role and permissions.

Note: We are working on this functionality. We will announce its deployment in the changelog as soon as it becomes available.

Microsoft

The system supports logging in with a Microsoft account. The process works analogously to Google: the user is redirected to the Microsoft sign-in page, confirms identity, and the system receives notification of successful authorization. This eliminates the need to remember a separate password, and access is protected by Microsoft mechanisms (e.g., MFA, organizational security policies).

Note: We are working on this functionality. We will announce its deployment in the changelog as soon as it becomes available.

Additional information about integration with Entra ID and Google

Communication between eAuditor Cloud and identity providers occurs over HTTPS, and all traffic is encrypted with TLS. The login mechanism is based on OAuth 2.0 and OpenID Connect standards, so sensitive data such as passwords do not reach the application. User identification is performed using JWT, which conveys basic account information and resulting access. The process uses authorization code and refresh token, which reduces exposure of credential data and increases overall security.

Key technical elements:

• TLS 1.3 is responsible for encrypting data in transit,

• OAuth 2.0 serves as the primary authentication protocol,

• OpenID Connect provides a standard model for conveying user information.

The integration does not require any additional configuration on the eAC side. If a user created an account using Entra ID or Google, login will work immediately after enabling the feature.

Thanks to broad compatibility with operating systems, eAuditor cloud is a flexible and comprehensive solution for IT infrastructure management, resource monitoring, and data security assurance.