---
title: "BeyondTrust Remote Support"
slug: "beyondtrust-remote-support"
updated: 2025-12-03T14:11:43Z
published: 2025-12-03T14:11:43Z
canonical: "docs.hunters.ai/beyondtrust-remote-support"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hunters.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# BeyondTrust Remote Support

****TL;DR****

| Supported data types | 3rd party detection | Hunters detection | IOC search | Search | Table name | Log format | Collection method |
| --- | --- | --- | --- | --- | --- | --- | --- |
| BeyondTrust Remote Support |  | ✅ | ✅ | ✅ | beyondtrust_remote_support_support_session | NDJSON | API |

---

## Overview

![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/beyond.png)Front-end integration of the BeyondTrust API enables customers to integrate Remote Support support sessions with third-party or in-house developed applications to pull report data, issue commands, or automatically save backups of the B Series Appliance's software configuration.

## Supported data types

### Beyondtrust Remote Support Support Session

**Table name:** beyondtrust-remote-support-support-session

provides detailed logs for BeyondTrust Remote Support sessions. It includes session metadata (start/end time, duration, participants), endpoint information (OS, IP, hostname), and a full list of session actions such as file transfers, command-shell activity, and permission changes. The API also exposes summary reports and optional links to session recordings, enabling auditing, compliance, and analytics use cases.

Learn more [here](https://docs.beyondtrust.com/rs/reference/reporting-api#supportsession).

## Send data to Hunters

Hunters supports the ingestion of beyondtrust logs via API.

**To connect BeyondTrust logs:**

1. Generate client id, and client secret by following [this guide](https://docs.beyondtrust.com/rs/reference/api-guide)[.](https://docs.beyondtrust.com/rs/reference/api-guide)
2. Once created, go to Hunters portal and onboard the integration by specifying the **client id**, **client secret** and the **domain**.

## Expected format

Logs are expected in JSON format.

```json
{ "timestamp": "1764218854", "event_type": "Session Start", "eventName": "Session Start", "deviceHost": "example.org", "sessionId": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" }
```