Loading

BeyondInsight and Password Safe Integration

Version 0.3.0 beta:[] (View all)
Compatible Kibana version(s) 8.15.3 or higher
9.0.0 or higher
Supported Serverless project types
What's this?
Security
Observability
Subscription level
What's this?
Basic
Level of support
What's this?
Elastic

BeyondInsight and Password Safe enable real-time monitoring of privileged account access, session recordings, and password checkout patterns to help security teams maintain compliance and quickly identify potential privilege abuse.

  • useraudit Provides audit data for users that includes user actions like login, logout, password change, etc., on a machine. This data stream utilizes the BeyondInsight and Password Safe API's /v3/UserAudits endpoint.

  • session Provides details on active sessions and their status with duration for an asset. This data stream utilizes the BeyondInsight and Password Safe API's /v3/Sessions endpoint.

  • managedsystem Provides a list of managed systems. This data stream utilizes the BeyondInsight and Password Safe API's /v3/ManagedSystems endpoint.

  • managedaccount Provides a list of managed accounts. This data stream utilizes the BeyondInsight and Password Safe API's /v3/ManagedAccounts endpoint.

  • asset Provides a list of assets. This data stream utilizes the BeyondInsight and Password Safe API's /v3/assets endpoint.

Administrators can configure API key-based API registration in BeyondInsight and Password Safe. To configure the BeyondInsight and Password Safe integration, a BeyondInsight administrator needs to create an API registration and provide an API key, a username and (depending on configuration) the user's password. In order to create the registration, the administrator may need to know the IP address of the Elastic Agent that will run the integration.

Having an admin account with beyondtrust, create an API registration as mentioned below

Login in to application and go to Configuration > General > API Registrations. Click Create API Registration. Add Authentication Options and Rules on the API Registration Details page. Select API Key Policy from the dropdown list. The Details screen is displayed. Fill out the new API registration details, as detailed below:

If checked User Password Required option - an additional Authorization header value containing the RunAs user password is required with the web request. If not enabled, this header value does not need to be present and is ignored if provided.

Use API key with usernanme and password (if password option is opted while registration) to access the APIs. We donot use oAuth method in this integration.

UserAudit documents can be found by setting the filter event.dataset :"beyondinsight_password_safe.useraudit".

ECS Field Reference

Please refer to the following document for detailed information on ECS fields.

The following non-ECS fields are used in useraudit documents:

Session documents can be found by setting the filter event.dataset :"beyondinsight_password_safe.session".

ECS Field Reference

Please refer to the following document for detailed information on ECS fields.

The following non-ECS fields are used in session documents:

ManagedSystem documents can be found by setting the filter event.dataset :"beyondinsight_password_safe.managedsystem".

ECS Field Reference

Please refer to the following document for detailed information on ECS fields.

The following non-ECS fields are used in managedsystem documents:

ManagedAccount documents can be found by setting the filter event.dataset :"beyondinsight_password_safe.managedaccount".

ECS Field Reference

Please refer to the following document for detailed information on ECS fields.

The following non-ECS fields are used in managedaccount documents:

Asset documents can be found by setting the filter event.dataset :"beyondinsight_password_safe.asset".

ECS Field Reference

Please refer to the following document for detailed information on ECS fields.

The following non-ECS fields are used in asset documents: