﻿---
title: Secure Heartbeat
description: The following topics provide information about securing the Heartbeat process and connecting to a cluster that has security features enabled. You can...
url: https://docs-v3-preview.elastic.dev/elastic/beats/pull/48485/reference/heartbeat/securing-heartbeat
applies_to:
  - Elastic Stack: Generally available in 9.0+
---

# Secure Heartbeat
The following topics provide information about securing the Heartbeat process and connecting to a cluster that has security features enabled.
You can use role-based access control and optionally, API keys to grant Heartbeat users access to secured resources.
- [*Grant users access to secured resources*](https://docs-v3-preview.elastic.dev/elastic/beats/pull/48485/reference/heartbeat/feature-roles)
- [*Grant access using API keys*](https://docs-v3-preview.elastic.dev/elastic/beats/pull/48485/reference/heartbeat/beats-api-keys).

After privileged users have been created, use authentication to connect to a secured Elastic cluster.
- [*Secure communication with Elasticsearch*](https://docs-v3-preview.elastic.dev/elastic/beats/pull/48485/reference/heartbeat/securing-communication-elasticsearch)
- [*Secure communication with Logstash*](https://docs-v3-preview.elastic.dev/elastic/beats/pull/48485/reference/heartbeat/configuring-ssl-logstash)

On Linux, Heartbeat can take advantage of secure computing mode to restrict the system calls that a process can issue.
- [*Use Linux Secure Computing Mode (seccomp)*](https://docs-v3-preview.elastic.dev/elastic/beats/pull/48485/reference/heartbeat/linux-seccomp)