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

When enabled for a CDN Resource, Bot Protection evaluates incoming requests and blocks requests that match configured bot detection rules.

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

## How Bot Protection Works

When Bot Protection is enabled, incoming requests are evaluated against the bot detection rules maintained by Medianova.

Requests identified as blocked bots are rejected, helping reduce unwanted automated traffic before it reaches the protected resource.

Bot Protection can help reduce:

* Automated scanning activity
* Content scraping by known malicious bots
* Unwanted crawler traffic
* Other requests originating from blocked automated clients

### 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/8rkWmHUobbYsrzJ86qyy" 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 requests from known malicious automated clients attempting to access or scrape website content.

### Protect Media Assets

Limit access from known automated tools targeting downloadable content, images, or media assets.

### Reduce Unwanted Automated Traffic

Reduce traffic generated by automated clients classified as unwanted or malicious.

## Important Notes

* No origin-side configuration is required.
* Automated services, integrations, monitoring tools, and other legitimate automated clients should be validated after enabling Bot Protection.
* Bot detection rules may change as the protection system evolves.
* Bot Protection should be used as 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.