> 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/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/engines/configure-engines/configure-an-engine-to-use-custom-certificates.md).

# Configure an Engine to Use Custom Certificates

Configure custom certificates for a Cortex XSOAR 6.15 engine.

For communication tasks that go through an engine, you can replace the default self-signed certificate for the engine with your own certificate.

1. Find the two files created by the engine. The default location is **`/usr/local/demisto`**.

   **`d1.key.pem`**

   **`d1.cert.pem`**
2. Replace the contents of these files with your own certificates.
3. Change file owner to demisto:

   **`chown -R demisto:demisto d1.key.pem`**

   **`chown -R demisto:demisto d1.cert.pem`**
4. Set the file permissions:

   **`chmod 600 d1.key.pem`**

   **`chmod 644 d1.cert.pem`**
5. (Optional) If you are using a key passphrase for your custom certificate, add the passphrase to your engine configuration:
   1. Go to Settings → **Engines**.
   2. **Create New Engine** and provide an engine name or select an existing engine and **Edit Configuration**.
   3. Select **Use a passphrase for the engine certificate private key**.
   4. Click **Save**.


---

# 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 dynamically 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/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/engines/configure-engines/configure-an-engine-to-use-custom-certificates.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 `build a script that syncs our docs to a CMS` 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.