Logpoint

LAST UPDATED: OCTOBER 06, 2025

Overview

Logpoint SIEM serves as a central hub for security event data within an organization. It collects, correlates, analyzes, and visualizes data from various sources, empowering security teams to detect and investigate security incidents quickly. Logpoint SIEM's reporting and historical data analysis capabilities ensure compliance with regulations and facilitate continuous improvement of an organization's security needs.

D3 SOAR is providing REST operations to function with Logpoint.

Logpoint is available for use in:

Connection

To connect to Logpoint from D3 SOAR, follow this part to collect the required information below:

Configuring Logpoint to Work with D3 SOAR

Refer to Finding the Access Key | Logpoint API Reference for instructions on retrieving the Access Key.

Configuring D3 SOAR to Work with Logpoint

1. Log in to D3 SOAR.

2. Find the Logpoint integration.

   

   1. Navigate to Configuration on the top header menu.

   2. Click on the Integration icon on the left sidebar.

   3. Type Logpoint in the search box to find the integration, then click it to select it.

   4. Click on the + Connection button on the right side of the Connections section. A new connection window will appear.

3. Configure the following fields to create a connection to Logpoint.

   

   1. Connection Name: The desired name for the connection.

   2. Site: Specifies the site to use the integration connection. Use the drop-down menu to select the site. The Share to Internal Sites option enables all sites defined as internal sites to use the connection. Selecting a specific site will only enable that site to use the connection.

   3. Recipient site for events from connections Shared to Internal Sites: This field is displayed when Share to Internal Sites is selected for the Site field, allowing selection of the internal site for deploying the integration connection.

   4. Agent Name (Optional): Specifies the proxy agent required to build the connection. Use the dropdown menu to select the proxy agent from a list of previously configured proxy agents.

   5. Description (Optional): Add a description for the connection.

   6. Configure User Permissions: Defines which users have access to the connection.

   7. Active: Check the checkbox to ensure the connection is available for use.

   8. System: This section contains the parameters defined specifically for the integration. These parameters must be configured to create the integration connection.

      

      1. Input the Server URL.
      2. Input the Username.
      3. Copy the Access Key from the Logpoint platform. Refer to Configuring Logpoint to Work with D3 SOAR.

   9. Enable Password Vault: An optional feature that allows users to take the stored credentials from their own password vault. Refer to the password vault connection guide if needed.

   10. Connection Health Check: Periodically checks the connection status by scheduling the Test Connection command at the specified interval (in minutes). Available only for active connections, this feature also allows configuring email notifications for failed attempts.

4. Test the connection.

   1. Click on the Test Connection button to verify credentials and connectivity. A success alert displays Passed with a green checkmark. If the connection fails, review the parameters and retry.

   2. Click OK to close the alert window.

   3. Click + Add to create and add the configured connection.

Commands

Logpoint includes the following executable commands for users to set up schedules or create playbook workflows. With the Test Command function, users can execute these commands independently for playbook troubleshooting.

Integration API Note

For more information about the Logpoint API, refer to the Logpoint API reference.

Note for Time-related parameters

The input format of time-related parameters may vary based on user account settings, which may cause the sample data in commands to differ from what is displayed. To adjust the time format, follow these steps:

1. Navigate to Configuration Application Settings. Select Date/Time Format.

   

2. Choose the desired date and time format, then click on the Save button.

   

   After that, users will be able to view their preferred time format when configuring the DateTime input parameters for commands.

Fetch Event

Returns incidents from the Logpoint SIEM platform based on specified criteria.

Input

[
    "Protocol Impersonation"
]

[
    "Command and Control",
    "Collection"
]

Output

To view the sample output data for all commands, refer to this article.

Fetch Event Field Mapping

Fetch Event commands require event field mapping. Field mapping plays a key role for data normalization within the event pipeline. Field mapping converts the original data fields from the different providers to standardized D3 fields as defined by the D3 Model. Refer to Field Mappings for details.

To add a custom field, click on the + Add Field button. Users can also remove built-in field mappings by clicking x. Note that two underscore characters will automatically prefix the defined Field Name as the System Name for a custom field mapping. Additionally, if an input Field Name contains any spaces, they will automatically be replaced with underscores for the corresponding System Name.

As a system integration, the Logpoint integration has some pre-configured field mappings for default field mapping.

Default Event Source

The Default Event Source is the default set of field mappings that are applied when this fetch event command is executed. For out-of-the-box integrations, users will find a set of field mappings provided by the system. Default event source provides field mappings for common fields from the fetched data. The default event source has a "Main Event JSON Path" (i.e. $.incidents) that is used to extract a batch of events from the response raw data. View the "Main Event JSON Path" by clicking on the Edit Event Source button.

Main Event JSON Path: $.incidents

The Main Event JSON Path determines the root path where the system starts parsing raw response data into D3 event data. The JSON path begins with $, representing the root element. The path is formed by appending a sequence of child elements to $, each separated by a dot (.). Square brackets with nested quotation marks ([‘...’]) should be used to separate child elements in JSON arrays.

For example, the root node of a JSON Path is incidents. The child node denoting the Unique Event Key field would be id. Putting it together, the JSON Path expression to extract the Unique Event Key is $.incidents.id.

The pre-configured field mappings are detailed below:

Error Handling

If the Return Data displays Failed, an Error tab will appear in the Test Result window.

The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.

Generate Search

Generates a search request by sending the required parameters to retrieve a Search ID.

READER NOTE

Query is a required parameter to run this command.

• Run the Fetch Event command to obtain the Query. Queries can be found in the raw data at the path $.incidents[*].query.

Repo Addresses is an optional parameter to run this command.

• Run the Get Repos command to obtain the Repo Addresses. Repo Addresses can be found in the raw data at the path $.allowed_repos[*].address.

• Run the Fetch Event command to obtain the Repo Addresses to search for incident-related logs. Repo Addresses can be found in the raw data at the path $.incidents[*].repos[*].

Input

["***.***.***.***:***/_Logpoint"] 

Output

To view the sample output data for all commands, refer to this article.

Error Handling

If the Return Data displays Failed, an Error tab will appear in the Test Result window.

The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.

Get Repos

Retrieves the names and IP addresses of all repositories configured in Logpoint.

Input

N/A

Output

To view the sample output data for all commands, refer to this article.

Error Handling

If the Return Data displays Failed, an Error tab will appear in the Test Result window.

The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.

Get Search Result

Retrieves search result logs using the Search ID.

READER NOTE

Search ID is a required parameter to run this command.

• Run the Generate Search command to obtain the Search ID. Search IDs can be found in the raw data at the path $.search_id.

Input

Output

To view the sample output data for all commands, refer to this article.

Error Handling

If the Return Data displays Failed, an Error tab will appear in the Test Result window.

The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.

Get User Timezone

Retrieves the timezone and date and time format.

Input

N/A

Output

To view the sample output data for all commands, refer to this article.

Error Handling

If the Return Data displays Failed, an Error tab will appear in the Test Result window.

The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.

Test Connection

Allows users to perform a health check on an integration connection. Users can schedule a periodic health check by selecting Connection Health Check when editing an integration connection.

Input

N/A

Output

Error Handling

If the Return Data displays Failed, an Error tab will appear in the Test Result window.

The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.