Skip to main content

​
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.
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.
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.
For these integrations, simply configure the required credentials and complete the setup as described in the respective integration guide.
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.

​
Integrations Without Remote Agent Support

The following integrations currently do not support Remote Agent.
IntegrationRemote Agent SupportAuthentication MethodNotes
(To be updated by the documentation team)❌ Not Supported——
(To be updated by the documentation team)❌ Not Supported——
(To be updated by the documentation team)❌ Not Supported——
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.
  • 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.

​
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.

​
Support

If you need help selecting the right deployment model or validating connectivity, contact AirMDR Support through your designated support channel.