FSecure WithSecure Elements Integration via API

Step 1: Create API Credentials in Elements Security Center

  1. Log in to Elements Security Center using an EPP administrator account.

  2. Navigate to Management > Organization Settings.

  3. In the Organization Settings view, open the API Clients tab from the top menu.

  4. From the Scope Selector, ensure the scope is set to the organization for which you intend to create the credentials.

    Note: If you are a partner managing multiple organizations, you must switch the scope to the relevant organization before proceeding.
  5. While still in Organization Settings, note the Organization UUID shown on the settings overview (or in the organization's URL in the address bar). Logsign needs this value separately from the API credentials below.

  6. Click on Add new to initiate the API client creation process.

  7. In the Add new API client window:

    • Provide a description for the new client credentials.

    • Choose the Read-only option if you only require read access.

      To enable the client to send requests that modify data (e.g., remote actions), uncheck the "Read-only" box. This allows the client to request authentication tokens with the connect.api.write scope.
  8. Click Add to finalize the creation.

  9. Follow the on-screen instructions to obtain your Client ID and Client Secret.

    ⚠️ Important: Make sure to securely save the Client Secret. It will not be displayed again.
  10. Select "I have copied and stored the secret" and click Done to complete the process.

The newly created API client will now appear in the list.

Step 2: Add Elements API Key to Logsign Unified SecOps Platform

  1. Log in to the Logsign Unified SecOps Platform.

  2. From the top navigation bar, select Settings.

  3. In the settings window, navigate to Data Collection from the left menu.

  4. Click on the + Device button on the top-right corner.

  5. In the Devices section:

    • Select API as the device type.

    • Choose FSecure WithSecure Elements from the Provider dropdown.

  6. In the configuration window, fill in all three required fields:

    • Client ID: the Client ID obtained from the API client in Step 1.

    • Client Secret: the Client Secret obtained from the same API client. This is the credential's secret value, separate from the Client ID.

    • Organization UUID: the Organization UUID noted in Step 1.5 above. Without this field the integration cannot scope its requests to your organization.

  7. Click Save to complete the integration.

Was this article helpful?
0 out of 0 found this helpful

Articles in this section

See more
Become a Certified Logsign User/Administrator
Sign-up for Logsign Academy and take the courses to learn about Logsign USO Platform in detail. Enjoy the courses, and get your badges and certificates. In these courses, you'll learn how to use Logsign in your work and add value to your career.
Visit Our Blog
Our Logsign USO Platform illustrate our expertise. So do the blog. Through our blog posts, deepen your knowledge on various SecOps topics or get updated about important news & modern approaches for cybersecurity. Get into the habit of reading valuable information provided by Logsign. Be a step ahead.