Genian EDR

Download 176
Last updated Nov 17, 2026

Getting Started

This page walks through every step from registering a connect profile to handling a threat. See the page of each screen for details.

1. Create a dedicated integration account

Create an administrator account for the app in the Genian Insights E console.

The app signs in to the console with a forced login. If the app and a person share an account, each sign-in ends the other side's session. Create a dedicated integration account to avoid the conflict.

If the console uses two-factor authentication, sign in to the console once with the integration account and register Google OTP. Write down the secret key shown in step 3 of the registration wizard. The key cannot be viewed again after registration, and you enter it in the connect profile in step 2.

Note
Google OTP is the only second factor the app can answer. Accounts that use RSA or email authentication
cannot be used for the integration. If the console restricts access by IP, add the Logpresso server IP
to the allow list.

2. Register a connect profile

In Logpresso, add a connect profile of type Genian EDR.

  • Endpoint URL - Console address. e.g. https://hostname:8443
  • User ID / Password - The account created in step 1
  • OTP secret key - Only when two-factor authentication is used. The base32 secret key written down in step 1

With an OTP secret key, the app generates an authentication code each time it signs in. The code is generated against the console server clock, not the Logpresso server clock, so it works regardless of any time difference between the two servers.

The app screens use the first Genian EDR connect profile. There is no profile selector on screen, so register one profile per console.

When you change the password, the app signs in again with the new value on the next request. When sign-in fails, the app does not retry for 30 seconds. Threat Monitoring queries several widgets at once and the auto refresh of Threat Management queries every minute, so retrying a wrong password on every request would get the account locked by the console.

3. Check the threat overview

Open Threat → Threat Monitoring.

Choose an OS and a period at the top and every widget refreshes for that range. Threat status, malware distributed across multiple endpoints and endpoints with multiple threats are all on one screen.

Click an item name in a TOP 10 list to open Threat Management filtered by that threat. The selected period is carried over.

4. Pick the threats to handle

In Threat → Threat Management, pick the threats to handle.

  • Choose a state with the cards on the left: New, In Progress, Resolved, All
  • Choose detection engines with the Malware and XBA check boxes at the top
  • Add conditions as field:value in the search box

Click a row to see the threat summary in the bottom panel. For threats that need a closer look, click the Details button.

5. Analyze the threat

The threat details screen has four tabs.

TabContent
GeneralIndicators, threat detect description, file information, external links
DevicesEndpoints where the same threat was detected
IndicatorsAssociated threat indicators and associated behavior tags
Attack Story LineProcess relationships drawn as a graph to trace how the attack progressed

Click a node in the attack story line to see the execution information and events of that process in the panel on the right.

6. Verify with events

When the detection evidence needs more checking, query the events of the endpoint in Investigation → Event Investigation.

For example, the network events of a suspicious endpoint are queried as follows.

HostName:DESKTOP-01 AND EventType:network

7. Handle the threat

Handle the threat in the threat management panel on the right of the threat details screen.

  • State - New, In Progress, Resolved
  • Decision - Malicious, Safe, Pending
  • Response - The response applied to all matching threats in the future
  • Auto-Response - Whether all matching threats in the future are set to Resolved automatically
  • Memo - The reason for the decision

Click Save to apply it to the console; it is recorded in the History at the bottom. The app works on the same threat records as the console, so a change made on either side shows on both.

8. Request a response

Request actions on the endpoint with the buttons at the top of the threat details screen.

ButtonFunction
Collect sampleCollects the threat file from the endpoint
Request Threat AnalysisSends the collected file to the analyzer
Collect artifactCollects artifacts from the endpoint
Restore fileRestores a quarantined file to its original location

Only the buttons that apply to the threat type and its progress are shown. A malicious IP detection, for example, has no file to collect, so the Collect sample and Collect artifact buttons do not appear.

Collected files are listed in Investigation → Collected Files.

The next page is Threat Monitoring.