G DATA 365 | MXDR
Glossary G DATA 365 | MXDR
Terms you might encounter in connection with G DATA 365 | MXDR and their meaning.
Agent |
G DATA Software that runs on an endpoint. The agent contains the sensors and communicates with a backend. |
||
Agent ID |
A value that uniquely identifies each agent installation regardless of the device name. This enables devices with the same name to be managed in an organisation unit. |
||
html5 |
Any type of machine on which the services required for the provision of G DATA product services are executed. These can provide various services such as incident detection, configuration, telemetry, or web interface. |
||
Endpoint |
A device with an operating system such as Windows, Linux, Mac, iOS or Android on which a G DATA Agent is installed. This can be a laptop, desktop PC, server or virtual machine, etc. At this time Microsoft Windows is supported. Other operating systems will follow. |
||
Endpoint Sensor |
A component (within the agent) that runs on endpoints and can collect events of a certain type. For example, the creation or deletion of processes/files, access to the Windows registry, entries in the event display of the operating system or software uninstallations/installations. |
||
Endpoint Actor |
A component (within the agent) that can perform operations on endpoints. Among other things, for example deleting files, terminating processes or preventing their execution and blocking certain networks. |
||
Endpoint Status |
The currently measured status of the endpoint reported by the agent’s communication channels, e.g. installed. |
||
Deployment consulting |
Technical consultation on migrating your existing solutions to G DATA 365 | MXDR (Depending on service level). |
||
Frontend |
Any type of user interface that is visible to authorized users. |
||
The kick-off is the first meeting of our {secoperation team} with the responsible project participants in your company.
|
|||
NIS-2 Directive |
|||
Onboarding |
This refers to the practical implementation of the agreements made during the kick-off or review. |
||
Response Module |
This module is included in the G DATA Agents. It provides our G DATA Security Analysts access to the endpoints to analyze and, if possible, resolve the security incident (with the exception of the systems blocked as discussed during onboarding). |
||
Review |
In the review, the target profile of your personal G DATA 365 | MXDR product is defined on the basis of the findings and agreements from the kick-off, which is then implemented during onboarding. |
||
SetupID |
An ID that can be used to assign the G DATA Agents to their organisation unit during installation. |
||
Security Incident |
Every alert that occurs on an endpoint is initially an incident and is assigned a unique ID. In some cases, different alerts from different sensors of the agent can be identified as belonging together. In this case, the various alerts are combined into a single incident with one ID. |
||
Threat Intelligence |
This refers to everything G DATA knows about, or can associate with a file, a process, a URL or anything similar. |