LeanIX EAM

LeanIX EAM (Enterprise Architecture Management) is a system management tool that manages and optimizes your IT landscape and architecture. You can bring application, project, user, and other data from LeanIX into Brinqa to enhance visibility into your organization's IT architecture, thus strengthening your cybersecurity posture.

This document details the information you must provide for the connector to authenticate with LeanIX EAM and how to obtain that information from LeanIX. See create a data integration for step-by-step instructions on setting up the integration.

Required connection settings

When setting up a data integration, select LeanIX EAM from the Connector drop-down. If you cannot find the connector in the drop-down, make sure that you have installed it first. You must provide the following information to authenticate LeanIX with Brinqa:

• API URL: The LeanIX API URL. The default format is https://<your-instance>.leanix.net/, where <your-instance> is the instance name of your organization's LeanIX deployment.

• API Token: The API token associated with the LeanIX account, which must have permissions to log in to the API server and return data.

Generate a LeanIX API token

For the LeanIX EAM connector to access the LeanIX Pathfinder API, you must provide an API token. According to LeanIX, personal tokens are being deprecated, although there's no official timeline for this change. LeanIX recommends using the Technical User functionality to generate an API token. To create a technical user, follow these steps:

1. Log in to your organization's LeanIX account as an administrator.

2. Click the account icon and select Administration from the drop-down.

3. Click Technical Users.

4. Click New Technical User and fill in the following fields:

   • Username: The username for the Technical user.

   • Permission Role: Click the drop-down and select VIEWER. The VIEWER role has read-only access.

   • Expiry Date: Set the expiry date for the token of the Technical user.

5. Click Save.

   Your new API token for the Technical user displays. You cannot view the token after this, so copy the token and save it to a secure location.

note

If you do not have permissions to create a technical user, contact your LeanIX administrator. For additional information, see LeanIX documentation.

Additional settings

The LeanIX EAM connector contains additional options for specific configuration:

• Workspace ID: A comma-separated list of LeanIX workspace identifiers.

• Custom fact sheet types: A comma-separated list of LeanIX EAM custom fact sheet types.

• Page size: The maximum number of records to get per API request. The default setting is 1000. It is not recommended to go over 1000.

Types of data to retrieve

The LeanIX EAM connector can retrieve the following types of data from the LeanIX EAM Pathfinder API:

Table 1: Data retrieved from LeanIX

Connector Object	Required	Maps to Data Model
Application	Yes	Application
Business Capability	No	Not mapped
Data Object	No	Not mapped
Interface	No	Not mapped
IT Component	No	Not mapped
Process	No	Not mapped
Project	No	Not mapped
Provider	No	Not mapped
Subscription	No	Not mapped
Technical Stack	No	Not mapped
User	No	Not mapped
User Group	No	Not mapped

info

For the connector objects that are not mapped, you must define the mappings yourself. See Data Consolidation for additional information.

The LeanIX EAM connector does not currently support operation options for the types of data it retrieves.

For detailed steps on how to view the data retrieved from LeanIX EAM in the Brinqa Platform, see How to view your data.

Attribute mappings

The table below details the mappings between the source and the Brinqa data model attributes.

Table 2: Application attribute mappings

Source Field Name	Maps to Attribute
APPROVED_AT	Local variable
CREATED_AT	sourceCreatedDate
DESCRIPTION	description
DISPLAY_NAME	name
DOCUMENTS	Local variable
EXCLUDE_FROM_QUOTA	Local variable
FULL_NAME	name
LEVEL	Local variable
NAME	name
QUALITY _SEAL_STATUS	Local variable
REV	Local variable
SCORE	Local variable
STATE	Local variable
STATUS	status
SUBSCRIPTIONS	Local variable
SYS_ID	uid
TAGS	tags
TYPE	categories, Local variable
UPDATED_AT	sourceLastModified

info

Local variable indicates that the field is processed within a specific context, such as a particular workflow or calculation. Unlike other attributes, local variables aren't mapped to the unified data models. They only exist on the source data model.

APIs

The LeanIX EAM connector uses the Pathfinder API. Specifically, it uses the following endpoints:

Table 3: LeanIX EAM Pathfinder API Endpoints

Connector Object	API Endpoint
Application	GET https://app.leanix.net/services/pathfinder/v1/factSheets?type=Application
Business Capability	GET https://app.leanix.net/services/pathfinder/v1/factSheets?type=BusinessCapability
Data Object	GET https://app.leanix.net/services/pathfinder/v1/factSheets?type=DataObject
Interface	GET https://app.leanix.net/services/pathfinder/v1/factSheets?type=Interface
IT Component	GET https://app.leanix.net/services/pathfinder/v1/factSheets?type=ITComponent
Process	GET https://app.leanix.net/services/pathfinder/v1/factSheets?type=Process
Project	GET https://app.leanix.net/services/pathfinder/v1/factSheets?type=Project
Provider	GET https://app.leanix.net/services/pathfinder/v1/factSheets?type=Provider
Subscription	GET https://app.leanix.net/services/pathfinder/v1/factSheets
Technical Stack	GET https://app.leanix.net/services/pathfinder/v1/factSheets?type=TechnicalStack
User	GET https://app.leanix.net/services/pathfinder/v1/factSheets?type=permissions
User Group	GET https://app.leanix.net/services/pathfinder/v1/factSheets?type=UserGroup

Changelog

The LeanIX EAM connector has undergone the following changes:

3.0.2

• Added a new connection setting: Custom fact sheet types.

3.0.1

• Fixed a pagination issue in the User object.

3.0.0

• Initial Integration+ release.