> 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/security-token.md).

# Security Token

Control access to your CDN resources by requiring a valid security token in every request URL.

Restrict access to CDN-delivered content by requiring a valid security token in the request URL.

**Security Token** validates a token included in each protected request before serving content. Requests that do not contain a valid token are denied.

The Control Panel provides the token key used by the feature. Request tokens must be generated by your origin server or application.

Security Token is configured per CDN Resource in the [Medianova Control Panel](https://cloud.medianova.com).

## Common Use Cases

Security Token can be used to restrict access to:

* Time-limited content
* Private downloads
* Resources that should not be publicly accessible without authorization

## Configure Security Token

{% stepper %}
{% step %}

### Open Security

Open your CDN Resource and select **Security**.
{% endstep %}

{% step %}

### Enable Security Token

Turn on **Security Token**.

<figure><img src="https://542970813-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtK7oIwmhUHdEJcaH4Hx8%2Fuploads%2FKK97RHxkr14Cy49b3Hoo%2Fimage.png?alt=media&amp;token=eb6cd75e-7b79-4aba-abcc-9611aba77001" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Configure Token Parameters

Configure the parameters included in token validation as required:

* **URI** — Select **Include the URI in the token** to include the request URI in the token.
* **Rate limit** — Select **Include network rate limit parameters** to include network rate limit parameters.
  {% endstep %}

{% step %}

### Generate the Token Key

Under **Token key**, select **Generate** to generate the key used for Security Token.

Use this key when implementing token generation in your origin server or application.

{% hint style="warning" %}
Treat the token key as sensitive information. Do not expose it in client-side code or publicly accessible content.
{% endhint %}
{% endstep %}

{% step %}

### Save the Configuration

Select **Save** in the pending changes bar.

Review the pending changes and confirm the configuration.
{% endstep %}
{% endstepper %}

## How Security Token Works

When Security Token is enabled, Medianova CDN validates the security token included in the request URL before serving protected content.

* Requests containing a valid token are processed normally.
* Requests without a valid token or with an invalid token are denied.
* The CDN validates request tokens but does not generate them for individual requests.
* Token generation must be implemented by your origin server or application using the configured token key.

The parameters included in token validation depend on the **URI** and **Rate limit** options configured for the CDN Resource.

## Important Notes

* Security Token is configured independently for each CDN Resource.
* Generate and store the token key securely.
* Request token generation must be implemented on your origin or application side.
* Enable **URI** or **Rate limit** only when those parameters are required by your token implementation.


---

# 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://clients.medianova.com/products/security/security-token.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.