# Bring Your Own Certificate (BYOC)

While CloudGuard WAF SaaS offers managed public SSL/TLS certificates signed by Let’s Encrypt, you may choose to use your **own certificate and private key**—ideal for compliance needs or existing certificate infrastructure.

{% hint style="success" %}
Your private key is **end-to-end encrypted** during upload, ensuring complete confidentiality and security.
{% endhint %}

To configure HTTPS traffic with your own certificates, follow the steps below:

#### Step 1: Upload Certificate and Private Key

1. In the Infinity Portal, navigate to **Policy → Profiles**.
2. Select the **CloudGuard WAF SaaS profile** linked to your asset.
3. For each domain listed, click on it and:
   * Upload the **public certificate** (PEM format)
   * Upload the **private key**
   * Ensure the certificate includes the **full chain**

{% hint style="info" %}
This process must be repeated for **each domain**, e.g., `www.myapp.com` and `api.myapp.com`.
{% endhint %}

<figure><img src="https://2760087783-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWA4nfgNrSRL8dA6Kap7%2Fuploads%2FCqsiN0Dnx9pfBx7ViF0M%2Fappsec-as-a-service-profiles-pending-validation.PNG?alt=media&#x26;token=b4e9cc3b-324c-4a36-9afd-ed86b745218b" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2760087783-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWA4nfgNrSRL8dA6Kap7%2Fuploads%2FYLWc1K7YCifExzMFtZTc%2FPicture1.png?alt=media&#x26;token=04b3a011-6fde-497d-a815-f575ab4819a1" alt=""><figcaption></figcaption></figure>

#### Step 2: Connect your domain to WAF SaaS

{% hint style="warning" %}
Before performing this stage, disable any existing AWS CloudFront configuration for your website's address if you have any.
{% endhint %}

Once the environment is ready, a **CNAME value** will be generated for your domain (this may take up to 30 minutes).

1. In your DNS provider’s configuration, **replace the existing CNAME record** with the new value provided by CloudGuard.

Once DNS records have propagated, your domain’s traffic will flow through WAF SaaS and be securely routed to your internal web server.

<figure><img src="https://2760087783-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWA4nfgNrSRL8dA6Kap7%2Fuploads%2F1fqUFXJoTSFSvV2Ognee%2FPicture3.png?alt=media&#x26;token=87306e6a-f9b4-4f89-a744-9d0ce38a82ab" alt=""><figcaption></figcaption></figure>

&#x20;**Step 3:** **Allow WAF SaaS to Access Your Origin Server**

To ensure smooth traffic flow between WAF SaaS and your internal web server:

1. **Allow incoming traffic** from the IP addresses provided in the **WAF SaaS deployment form**.
2. **Do not remove** existing access rules until:
   * 72 hours have passed (to allow full DNS propagation), and
   * You have confirmed successful traffic flow through WAF SaaS.

{% hint style="info" %}
If the origin was previously publicly accessible, restrict access to only WAF SaaS IPs after DNS switchover.\
If you were using another reverse proxy, consider removing its IPs from the access list after confirming the switch.
{% endhint %}

<figure><img src="https://2760087783-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWA4nfgNrSRL8dA6Kap7%2Fuploads%2FDdWkbnTqXs0DtqqdEZEg%2Fappsec-as-a-service-profiles-deployment-instructions.PNG?alt=media&#x26;token=4736c2ed-2ca7-4a7c-9a0b-8dc4669d287e" alt=""><figcaption></figcaption></figure>

#### Step 4: Test access to your site

After completing the above steps:

* Confirm that the website is reachable over HTTPS.
* Verify that traffic is flowing through WAF SaaS (you can check headers or logs in the Infinity Portal).
* Double-check that your origin server is **no longer publicly accessible** (unless intentionally exposed).

{% hint style="danger" %}
Make sure you have not left a publicly exposed domain in your previous environment!
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://waf-doc.inext.checkpoint.com/getting-started/deploy-enforcement-point/waf-as-a-service-waf-saas/bring-your-own-certificate-byoc.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.