> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.14/install-cortex-xsoar/post-installation/use-a-signed-certificate-instead-of-ssl-verification.md).

# Use a signed certificate instead of SSL verification

Use a signed HTTPS certificate instead of SSL verification in Cortex XSOAR 8.14 On-prem MSSP deployments.

Self-signed certificates are customizable and cost-effective for internal systems or development environments where external trust is not required, offering independence from third-party certificate authorities. For more information about creating a signed certificate, see [HTTPS with a signed certificate](/cortex-xsoar-8-on-prem/8.14/install-cortex-xsoar/post-installation/https-with-a-signed-certificate.md).

### **Disable SSL verification for multi-tenant**

In a multi-tenant setup, if a child tenant has a self-signed certificate, you can disable SSL verification for requests between the parent and child tenant.

1. From the textual UI menu in your VM, select **Application Settings**.
2. Select **Skip SSL Verification for MSSP**.
3. Click **Apply**.

### **Disable SSL verification for content management**

If you use a remote repository to manage content, you can use a self-signed certificate instead of SSL verification for requests between the development tenant, the remote repository, and the production tenant. Using a self-signed certificate provides encryption and secure communication without the cost and complexity of obtaining a trusted SSL certificate from a certificate authority.

1. From the Textual UI menu in your VM, select **Application Settings**.
2. Select **Skip SSL Verification for Content**.
3. Click **Apply**.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.14/install-cortex-xsoar/post-installation/use-a-signed-certificate-instead-of-ssl-verification.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.