> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/security/bot-protection.md).

# Bot Protection

Bot Protection helps reduce unwanted automated traffic by identifying and blocking known malicious bots before requests reach your content.

The feature operates at the CDN edge and can help protect websites, APIs, and media assets from automated attacks, scraping activity, and other non-human traffic patterns.

{% hint style="info" %}
Bot Protection is enabled at the CDN edge and does not require changes to your origin infrastructure.
{% endhint %}

## How Bot Protection Works

When Bot Protection is enabled, the CDN evaluates incoming requests and applies bot detection mechanisms to identify known malicious automated traffic.

Requests identified as malicious bots may be blocked before they reach your origin.

Bot Protection is designed to reduce:

* Content scraping
* Automated scanning activity
* Unwanted crawler traffic
* Malicious bot requests

### Configure Bot Protection

In the [Medianova Control Panel](https://cloud.medianova.com), select the CDN Resource and navigate to the **Security** tab.

{% stepper %}
{% step %}

### Enable Bot Protection

Enable the **Status** toggle to activate Bot Protection for the selected CDN Resource.

<figure><img src="/files/Rj5vD9WzpyPR1RxaUXN5" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Save the Configuration

Click **Submit** to deploy the updated configuration.
{% endstep %}
{% endstepper %}

## Common Use Cases

#### Protect Public Websites

Reduce automated requests that attempt to scrape content or consume bandwidth.

#### Protect Media Assets

Limit access from known scraping tools targeting downloadable content, images, or video assets.

#### Reduce Unwanted Traffic

Block known malicious bots before requests reach your infrastructure.

## Important Notes

* Bot Protection operates at the CDN edge.
* No origin-side configuration is required.
* Automated services, integrations, or monitoring tools should be validated after enabling the feature.
* Detection methods and bot classifications may change as the protection system evolves.
* Bot Protection should be considered one layer of a broader security strategy and can be combined with IP Restriction, Geo Blocking, Rate Limiting, and other CDN security features.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://clients.medianova.com/products/security/bot-protection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.