> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gcore.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Apply a custom profile to a protected network

> Apply a custom DDoS protection profile to a protected network to activate its rules and policy.

After creating a custom protection profile, apply it to a protected network to activate its rules and policy.

## Step 1. Open protected networks

Protected networks appear in a single list in the Customer Portal, regardless of protection status.

1. In the [Gcore Customer Portal](https://portal.gcore.com), navigate to **DDoS Protection** > **Protected networks**.
2. Locate the protected network to update.

## Step 2. Edit the protected network

Open the edit view for the target network.

1. Next to the target network, click **…**.
2. Select **Edit**.

![Edit the protected network](https://mintcdn.com/gcore/kjCBUlCGkJrvR9v9/images/docs/ddos-protection/onboarding-service/custom-protection-profile-configuration/protected-networks-edit.png?fit=max\&auto=format\&n=kjCBUlCGkJrvR9v9\&q=85\&s=61b24dc3a67c2a34396d8802c9c1b45e)

## Step 3. Assign a protection profile

Select the profile to apply from the network's edit view.

1. In the **Edit protected network** view, open the **Profile** list.
2. Select the required protection profile.

The list includes the default **Basic** profile and any custom profiles created for the account.

## Step 4. Save changes

Click **Save changes** to apply the selected profile to the network. The selected profile becomes active immediately.

![Save the protected network](https://mintcdn.com/gcore/U2swJIsaj88rUw_R/images/docs/ddos-protection/onboarding-service/custom-protection-profile-configuration/protected-network-save.png?fit=max\&auto=format\&n=U2swJIsaj88rUw_R\&q=85\&s=97ddbb7d3ef5ce20da72d065ad646241)

## Verification

After saving, the **Profile** field on the network shows the selected profile name. New attack events in the [events log](/ddos-protection/events-log) reflect the profile's rules and policies: traffic matching a game policy stops appearing under the generic default policy. Adjust the profile settings if the observed behavior does not match expectations.