G DATA MXDR

Instructions for installing the G DATA Agent on Linux

You can install the G DATA Agent for Linux in a few simple steps.

Important information on using templates.

The G DATA Agent must not be installed on system images/templates that are then used for cloning on other systems. The installation of the G DATA Agent must always be performed after a cloning process to ensure unique identification of Incidents.

If you have installed the G DATA Security Client, uninstall it first and restart the system before installing the G DATA Agent.

1

Download the desired installation file in the "New endpoint installation" view.

2

First, switch to the root user.

su -

3

Depending on whether you have a Debian system or run the installation with RPM, the installation commands differ slightly.

4.a
deb file (Debian-based systems):
SETUPID=<setupid> apt install ./gdata-agent-amd64.deb
You can obtain a setup file as well as the required Setup ID in the G DATA Web-Portal in the "New endpoint installation" view.

In some cases, when installing the G DATA Agent for Linux on Debian-based systems, you will receive the following message:

N: Download is performed unsandboxed as root as file …​ couldn’t be accessed by user '_apt'.

This is only a notice, not an error; "N" stands for Notice. You likely downloaded the file as root and did not grant other users any access permissions to the file.

APT attempts to perform installations in a sandbox, and it does so via the user "_apt". However, if that user does not have access to the file, the message shown above is displayed and the installation is performed by root instead. The Agent is still installed, so this is not an error, but only a notice.

You can easily avoid the message by granting read permissions to the file for others before running it:

sudo chmod 644 ./gdata-agent-amd64.deb

or you can use dpkg instead of apt to install the package:

sudo dpkg -i ./gdata-agent-amd64.deb

4.b
rpm file:
SETUPID=<setupid> rpm -i ./gdata-agent-x86_64.rpm

5

Optionally, if required, you can add the proxy settings PROXYPACURL, PROXYURL, PROXYUSERNAME and PROXYPASSWORD as parameters to the installation command at this point. You can find more details about the parameters here.

Installation example for Debian-based systems:

SETUPID=<setupid> PROXYURL=<myProxyURL> PROXYUSERNAME=<myUsername> PROXYPASSWORD=<myPassword> apt install ./gdata-agent-amd64.deb

Installation example for RPM:

SETUPID=<setupid> PROXYURL=<myProxyURL> PROXYUSERNAME=<myUsername> PROXYPASSWORD=<myPassword> rpm -i ./gdata-agent-x86_64.rpm

6

This completes the installation. You can still configure the G DATA Agent, for example to set proxy settings. How to do this is explained here.

Accessibility of the G DATA cloud

To ensure reliable and timely alerting of events and Incidents, the G DATA Cloud must be reachable and must not be blocked by a firewall. The settings listed below are required for this. It must be ensured that *.gdatasecurity.de and *.gdatasoftware.com can be resolved via DNS and are reachable.

  • Port openings

    • The G DATA agents on the Endpoints must be able to reach the IPs of our backend servers via port TCP/443, IP range 194.156.84.0/22 (194.156.84.0 - 194.156.87.255).

  • Protocols

    • The systems must be able to communicate using the HTTPS:// and WSS:// protocols.

  • TLS

    • Deployed proxy servers must support at least TLS 1.2.

    • SSL Inspection or Deep Packet Inspection must not be enabled.

Troubleshooting

When installing on a Debian-based Linux, the package is installed, but its status is "half configured". You can verify this with the following command.

dpkg --status gdata-agent

This lists some attributes of the Agent installation, similar to what is shown here:

Package: gdata-agent
Status: install ok half-configured
Maintainer: G DATA CyberDefense AG
Architecture: amd64
Version: 2025.0715.1314
Depends: libc6 (>= 2.28)
Description: G DATA Agent for Linux by G DATA CyberDefense AG (365@gdata.de)

If the message "install ok half-configured" is displayed under "Status" (as in the example above), it is best to fully uninstall the package and repeat the installation process.