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

# Mandiant ASM source plugin

export const entity_0 = "Mandiant ASM source plugin"

export const plugin_0 = "Mandiant ASM source plugin"

The Mandiant ASM [source plugin](/ingest/pipeline/plugins/source-plugins)
(name: `http_loader`, alias: `mandiant_asm`) lets you query Mandiant ASM to
ingest data into a telemetry pipeline.

This is a [pull-based](/ingest/pipeline/plugins/source-plugins#push-based-and-pull-based-source-plugins) source plugin.

<Note>
  This plugin doesn't support the use of a
  [descriptive metadata name](/ingest/pipeline/plugins#descriptive-names) in the
  Pipeline Builder interface.
</Note>

<Note>
  This plugin doesn't support duplicates of itself within the same pipeline.
  Additionally, this plugin can't be used in combination with these source plugins
  within the same telemetry pipeline:

  * [Absolute](/ingest/pipeline/plugins/source-plugins/absolute)
  * [HTTP API collector](/ingest/pipeline/plugins/source-plugins/http-api-collector)
  * [Okta](/ingest/pipeline/plugins/source-plugins/okta)
  * [Signal Sciences](/ingest/pipeline/plugins/source-plugins/signal-sciences)
  * [Slack](/ingest/pipeline/plugins/source-plugins/slack)
  * [Vectra M365](/ingest/pipeline/plugins/source-plugins/vectram365)
</Note>

## Supported telemetry types

The {plugin_0} for Chronosphere Telemetry Pipeline supports these telemetry types:

|                    Logs                    |             Metrics             |              Traces             |
| :----------------------------------------: | :-----------------------------: | :-----------------------------: |
| <Icon icon="circle-check" color="green" /> | <Icon icon="ban" color="red" /> | <Icon icon="ban" color="red" /> |

## Configuration parameters

Use the parameters in this section to configure the {entity_0}. The
Telemetry Pipeline web interface uses the items in the **Name** column to
describe these parameters. [Pipeline configuration files](/ingest/pipeline/v2/configure/config-files)
use the items in the **Key** column as YAML keys.

### General

The configured fields replace sections of the `url` field in the YAML file in the
following way:

```text theme={null}
url: https://asm-api.advantage.mandiant.com/api/v1/search/SEARCH_ELEMENT/SEARCH_QUERY
```

| Name               | Key                   | Description                                                                           | Default    |
| ------------------ | --------------------- | ------------------------------------------------------------------------------------- | ---------- |
| **Project ID**     | `PROJECT_ID`          | Required.                                                                             | *none*     |
| **Search element** | *none*                | Required. Used in `url` field. Accepted values: `entities`, `issues`, `technologies`. | `entities` |
| **Search Query**   | *none*                | Required. Used in `url` field.                                                        | *none*     |
| **Access Key**     | `INTRIGUE_ACCESS_KEY` | Required.                                                                             | *none*     |
| **Secret Key**     | `INTRIGUE_SECRET_KEY` | Required.                                                                             | *none*     |

### Advanced

| Name                    | Key             | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Default |
| ----------------------- | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
| **Memory Buffer Limit** | `mem_buf_limit` | For pipelines with the Deployment or DaemonSet [workload](/ingest/pipeline/v2/configure/kubernetes/workloads) type only. Sets a limit for how much buffered data the plugin can write to memory, which affects [backpressure](/ingest/pipeline/v2/configure/backpressure). This value must follow Fluent Bit's rules for [unit sizes](https://docs.fluentbit.io/manual/administration/configuring-fluent-bit#unit-sizes). If unspecified, no limit is enforced. | *none*  |