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

# AirMDR Remote Agent Integration Compatibility

> The AirMDR Remote Agent enables secure, controlled connectivity between AirMDR and customer-managed environments.

## Overview

The **AirMDR Remote Agent** enables secure communication between the AirMDR platform and supported third-party integrations by acting as a trusted intermediary within your environment. While many integrations can leverage this capability, **certain integrations do not support Remote Agent functionality** due to their authentication model, architecture, or native cloud connectivity requirements.

This page serves as the authoritative reference for integrations that **cannot be configured with a Remote Agent**.

<Note>
  The absence of Remote Agent support does **not** affect the integration's functionality. These integrations can still be configured and used with AirMDR through their supported authentication mechanisms, such as API keys, OAuth 2.0, access tokens, or service-specific credentials.
</Note>

<AccordionGroup>
  <Accordion title="🧐 When Is a Remote Agent Not Required?">
    A Remote Agent is typically **not required** in the following scenarios:

    * The integration communicates directly with a cloud-hosted service over secure APIs.
    * Authentication is performed using OAuth 2.0, API keys, bearer tokens, or service principals.
    * The provider does not support agent-based connectivity.
    * AirMDR can securely establish communication without requiring an intermediary component.
    * The integration documentation does not expose a **Remote Agent** selection option during connection creation.

    <Tip>
      For these integrations, simply configure the required credentials and complete the setup as described in the respective integration guide.
    </Tip>
  </Accordion>

  <Accordion title="🤔 How to Determine Whether an Integration Supports a Remote Agent?">
    Before configuring an integration:

    1. Navigate to **Integrations** in the AirMDR portal.
    2. Select the desired integration.
    3. Click **+ New Connection**.
    4. Review the available configuration fields.
    5. If a **Remote Agent** field is displayed, the integration supports Remote Agent functionality.
    6. If no such field is available, configure the integration using its native authentication method.
  </Accordion>
</AccordionGroup>

## Integrations Without Remote Agent Support

The following integrations currently **do not support Remote Agent**.

<Info>
  The integrations listed below continue to function normally using their supported authentication mechanisms. \
  Their exclusion from Remote Agent support is based on their current implementation architecture and communication model, not on any limitation in AirMDR functionality.
</Info>

<Note>
  This list may change as integrations are enhanced to support Remote Agent capabilities in future releases.
</Note>

| **Integration**    | **Remote Agent Support** | **Reason for Not Supporting Remote Agent**                                             |
| :----------------- | :----------------------- | :------------------------------------------------------------------------------------- |
| Hybrid Analysis    | ❌ Not Supported          | Uses raw HTTP requests that do not pass through the Remote Agent framework.            |
| LogicHub           | ❌ Not Supported          | Implements direct API communication and does not support Remote Agent routing.         |
| McAfee             | ❌ Not Supported          | Uses direct HTTP communication and does not integrate with the Remote Agent framework. |
| Palo Alto Panorama | ❌ Not Supported          | Uses raw HTTP requests instead of the shared Remote Agent communication layer.         |
| SonicWall          | ❌ Not Supported          | Connects directly to the appliance APIs without Remote Agent support.                  |
| Symmetry Systems   | ❌ Not Supported          | Makes direct API requests that bypass the Remote Agent execution path.                 |

<Note>
  **This table is maintained based on the latest engineering validation and product capabilities. It may be updated as additional integrations gain Remote Agent support in future releases.**
</Note>

<AccordionGroup>
  <Accordion title="✅ Best Practices">
    * Always refer to the individual integration documentation before creating a connection.
    * Do not attempt to assign a Remote Agent to integrations that do not support it.
    * Use the authentication method recommended for each integration.
    * Periodically review this page for compatibility updates as new features and integrations are released.
    * If you are unsure whether an integration supports a Remote Agent, consult the latest AirMDR documentation or contact your administrator.
  </Accordion>

  <Accordion title="🙋 Frequently Asked Questions">
    ### Does the lack of Remote Agent support prevent me from using an integration?

    No. Integrations listed on this page remain fully supported by AirMDR and can be configured using their respective authentication methods.

    ### Why do some integrations not support Remote Agent?

    Some third-party services are designed to communicate directly with cloud applications and do not require an intermediary agent. Others rely on authentication mechanisms or provider-specific architectures that are incompatible with Remote Agent connectivity.

    ### Will more integrations support Remote Agent in the future?

    Yes. AirMDR continuously enhances its integration capabilities. As Remote Agent support is introduced for additional integrations, this page will be updated accordingly.

    ### Where can I learn more about the AirMDR Remote Agent?

    Refer to the **Remote Agent Overview** and **Create Remote Agent** documentation pages for detailed information about its purpose, architecture, deployment, and configuration.
  </Accordion>
</AccordionGroup>

### Support

If you need help selecting the right deployment model or validating connectivity, contact [**AirMDR Support**](mailto:support@airmdr.com) through your designated support channel.