Send Assets Data - TRIMEDX Device Vulnerabilities

Send Assets Data - TRIMEDX Device Vulnerabilities sends device vulnerability data from Axonius to the TRIMEDX Medical Device Security Platform (MDSP) for:

• Assets returned by the selected query or assets selected on the relevant asset page.

Required Fields

These fields must be configured to run the Enforcement Action.

• Use stored credentials from the TRIMEDX adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.

  • When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.

    📘

    Note

    To use this option, you must successfully configure a TRIMEDX adapter connection.

• Customer ID - Customer ID provided by TRIMEDX.

• Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.

Additional Fields

These fields are optional.

• Map Axonius fields to adapter fields - Use the Field Mapping Wizard to map Axonius fields to fields in external systems. In this way, you can transfer data found in Axonius into the external system as part of the configuration of relevant enforcement actions. The wizard shows you which fields exist on the Axonius system, allowing you to map them easily.

  📘

  Note:

  For details, see Axonius to External Field Mapping.

⚠️

Connection and Credentials

When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

• Host Name or IP Address - Base domain for the API. Should contain a prefix of http:// or https://. Do not add any specific endpoints after the domain. Example: https://api.trimedx.com/
• User Name - User Name for OAuth2 authentication.
• Password - Password for OAuth2 authentication.
• Client ID - OAuth2 Client ID provided by TRIMEDX.
• Subscription Key - Ocp-Apim-Subscription-Key provided by TRIMEDX.

• Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

• HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

• HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.

• HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.

• Gateway Name - Select the Gateway through which to connect to perform the action.

APIs

Axonius uses the TRIMEDX Cyber API - POST /mdsp-alertdevice/alertdevice

Required Ports

Axonius must be able to communicate via the following ports:

• TCP port 80/443

Required Permissions

The following permissions and requirements are needed:

• OAuth2 authentication with the following scopes:
  • openid
  • mdsp.alertdevice.write
• A valid TRIMEDX Customer ID
• A valid Ocp-Apim-Subscription-Key provided by TRIMEDX
• Access to the TRIMEDX Medical Device Security Platform (MDSP) API

Version Matrix

This Enforcement Action was tested only with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.