> 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-6-installation-guides/6.15/cortex-xsoar-installation-guide/single-server-installation/install-cortex-xsoar-with-elasticsearch/elasticsearch-general-security-guidelines.md).

# Elasticsearch General Security Guidelines

Elasticsearch security guidance for Cortex XSOAR 6.15 single-server deployments.

Elasticsearch implements its own security features, most of which are free, using the X-Pack. Cortex XSOAR recommends you use these [security features](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-settings.html#security-settings) to protect your data.

{% hint style="info" %}
As Elasticsearch is an external service, the default behavior is no longer secured. It is highly recommended to enable secure connections to and from Elasticsearch including secure connections between nodes; otherwise, your data can be exposed from outside Cortex XSOAR.
{% endhint %}

The following provides some guidelines for implementing security in a single instance deployment using an Elasticsearch database.

**Authentication**

To connect from Cortex XSOAR to Elasticsearch, you should use Elasticsearch authentication with either a username and password, or an API key to ensure that communication between Elasticsearch and Cortex XSOAR is secure.

You can provide the credentials either in the **`demisto.conf`** configuration file under the Elasticsearch branch, or as flags in the Cortex XSOAR installer. The XSOAR configuration file for Elasticsearch password and API key may accept a plain text or encrypted using the server encryption key. After you start the Cortex XSOAR server, the Elasticsearch credentials are automatically encrypted.

**Communication**

Cortex XSOAR recommends that you implement an https connection using TLS for [secure communication](https://www.elastic.co/blog/elasticsearch-security-configure-tls-ssl-pki-authentication).

Use the Elasticsearch certificate verification method to establish a secure connection between your Elasticsearch nodes to avoid man in the middle attacks.

**User Permissions**

The following lists the user permissions required for the Elasticsearch user in single-instance and multi-tenant deployments.

* create (indices)
* delete (indices)
* index (indices)
* monitor (indices)
* create\_index (or at least auto\_configure to dynamically create partitions) (indices)

In addition, multi-tenant deployments require the following user permission:

* manage (or view\_index\_metadata, manage\_index\_templates) (cluster)


---

# 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-6-installation-guides/6.15/cortex-xsoar-installation-guide/single-server-installation/install-cortex-xsoar-with-elasticsearch/elasticsearch-general-security-guidelines.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.