# Proxy Property Configuration

Prerequisites

To successfully implement the Proxy Property, please ensure you have:

1. A **CNAME record**, which can be registered by your DNS management platform, such as Akamai Edge DNS.
2. A valid **Certificate** for the CNAME.
3. Completed the [Monitoring Configuration](https://docs.netacea.com/netacea-plugin-information/akamai/monitoring-configuration).

## CNAME and Certificate

The CNAME record must be pointing to the edgekey.net domain of the [proxy property](#proxy-property-configuration) that is described below. For example, for the proxy property hostname "mitigations.examplehost.com", the CNAME record value should be "mitigations.examplehost.com.edgekey.net". The CNAME DNS record can be created from within Akamai Edge DNS or from any other DNS management platform.

For the CNAME to be valid, a certificate must be assigned to it. This can be a new or a re-used certificate from your existing DNS records.

## Proxy Property Configuration

To avoid any conflict with any existing standard rules within your Akamai property, a new proxy property must be created. The sole purpose of this property is to act as a proxy between the Akamai EdgeWorker and the Netacea Protector API.

{% hint style="info" %}
The hostname of the property can be anything, but to increase security measures, it should not relate to Netacea. For example, "mitigations.examplehost.com".
{% endhint %}

To create such property, click on **Properties**, under the **CDN** section of the menu. Then click on **+New Property**

<figure><img src="https://3359534748-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8KQH1bDl0sVMvZgHUjkC%2Fuploads%2Fgit-blob-69c71f88ea3c5b8142a9482a61c94f838879eb4e%2Fimage%20(10).png?alt=media" alt=""><figcaption></figcaption></figure>

While editing the property version, add the domain created earlier as the Property Hostname.

<figure><img src="https://3359534748-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8KQH1bDl0sVMvZgHUjkC%2Fuploads%2Fgit-blob-e372c82bd334bfa09daeb730b2566b3bea74cf9d%2Fimage%20(17).png?alt=media" alt=""><figcaption></figcaption></figure>

Under the **Property Configuration Settings**, add/edit the **Default Rule** with the following:

### **Default Rule**

{% hint style="info" %}
Default behaviors are applied to all requests for the property hostname(s).
{% endhint %}

The Default Rule template contains all the necessary and recommended behaviors. Rules are evaluated from top to bottom and the last matching rule wins.<br>

<table data-full-width="false"><thead><tr><th>Behaviors</th></tr></thead><tbody><tr><td><p><strong>Origin SSL Certificate Verification</strong></p><p><strong>Ports</strong></p></td></tr><tr><td>3d2d365e9533444f96c27058ee7849e1-1b922c6863224f2e9565a9a2a5a7d997</td></tr><tr><td>9a0fff7e8d404e05bb905cb3b7b116a3-1b922c6863224f2e9565a9a2a5a7d997</td></tr><tr><td></td></tr></tbody></table>

Within the default rule add a new Behavior of type **Content Provider Code**.\
\
The Content Provider Code hostname selected from the drop down should be the proxy property hostname. If that is not available, you can create a new CP code for that hostname.

<table><thead><tr><th width="244">Content Provider Code</th><th></th></tr></thead><tbody><tr><td>Content Provider Code</td><td><strong>000000 - ExampleCPCode1</strong></td></tr></tbody></table>

### CAPTCHA Assets Rule

Under the **Property Configuration Settings**, add a new blank rule against the proxy property called "CAPTCHA Assets Rule". Include the following criteria and behaviors within the rule:

| Criteria         |
| ---------------- |
| Match All        |
| **If**           |
| Path             |
| matches one of   |
| `/Mitigations/*` |

<table data-full-width="false"><thead><tr><th>Behaviors</th></tr></thead><tbody><tr><td><p><strong>Origin SSL Certificate Verification</strong></p><p><strong>Ports</strong></p></td></tr></tbody></table>

{% hint style="danger" %}
Ensure that the proxy property only contains the **Default** and the **CAPTCHA Assets** Rules. Any other Rules (including automatically created ones) must be deleted before saving the proxy property configuration.
{% endhint %}

<figure><img src="https://3359534748-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8KQH1bDl0sVMvZgHUjkC%2Fuploads%2Fgit-blob-e7f70ec69ae4316c1c3a07280817b3d3f099af8f%2Fimage%20(4)%20(5).png?alt=media" alt=""><figcaption><p>Proxy Property Rules</p></figcaption></figure>

### Activate the Property

Once all the Rules described above have been created, click **Save** and use the **Activate** tab to activate (deploy) your changes to the property's configuration.

{% hint style="info" %}
A single Proxy Property can be used by multiple Properties. For example it can be used by a Staging and multiple Production Properties.
{% endhint %}

### Finishing Up

{% hint style="success" %}
You have now completed the configuration for the proxy property of the Proxy Property.
{% endhint %}