For the complete documentation index, see llms.txt. This page is also available as Markdown.

Bot Protection

Reduce unwanted automated traffic by blocking known malicious bots and content scraping tools at the CDN edge.

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.

Bot Protection is managed at the CDN level and does not require changes to your origin infrastructure.

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, select the CDN Resource and navigate to the Security tab.

1

Enable Bot Protection

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

2

Save the Configuration

Click Submit to deploy the updated configuration.

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.

Last updated

Was this helpful?