> For the complete documentation index, see [llms.txt](https://docs.fusion.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fusion.vectra.ai/automate-responses/configuring-response-integrations/rtbh.md).

# RTBH

Block Type Response Integration

{% hint style="warning" %}
**Prior to creating a RTBH plugin, you will need to configure at least 1 device with a unicast BGP neighbor.**
{% endhint %}

## Usage <a href="#usage" id="usage"></a>

The Remotely Triggered Black Hole (RTBH) block type response integration enables the quick isolation and nullification of malicious traffic. It operates by directing unwanted traffic into a "black hole," effectively protecting the network from potential threats such as denial-of-service (DoS) attacks.

Integrated with Netography's analytics, monitoring, compliance, and reporting tools, RTBH serves as a scalable, cost-effective, and robust solution for maintaining network integrity and security.

## Netography Portal Steps <a href="#netography-portal-steps" id="netography-portal-steps"></a>

In **Settings > Response Integrations**, click **Add Integration**. Select **RTBH**\`

![](https://1075194167-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7upncbzIm3grJePXaOO9%2Fuploads%2Fgit-blob-75dcf602933c90eb8d0332244f0d1b9a395102eb%2F15a18051a012c8e325bebdbc1557b133e0d111726d9ff2f13c91a73e5894d682.png?alt=media)

## Configuration <a href="#configuration" id="configuration"></a>

The following fields are specific to the RTBH integration.

| Field              | Required | Description                                                                                       | Examples    |
| ------------------ | -------- | ------------------------------------------------------------------------------------------------- | ----------- |
| `Next Hop`         | yes      |                                                                                                   | 12.12.12.12 |
| `Neighbors`        | yes      | IPv4/v6 unicast BGP neighbors configured in the Netography Portal.                                |             |
| `Communities`      | yes      | One or many BGP communities.                                                                      | 3232:32     |
| `Local Preference` | yes      | Used to choose the exit path for an autonomous system. Default 100                                | 100         |
| `Factors`          | yes      |                                                                                                   | srcip       |
| `Expiration`       |          | Number of seconds the blocklist will remain active                                                | 3600        |
| `Max`              |          | Limit on number of blocks                                                                         | 1000        |
| `Allow List`       |          | One or many Allow Lists configured in the Netography Portal, or a List of IP or IP/CIDR addresses |             |
| `Aggregate`        |          | Aggregate IP addresses by mask length                                                             |             |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fusion.vectra.ai/automate-responses/configuring-response-integrations/rtbh.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
