# Filebeat to support TLS1.3

**URL:** https://discuss.elastic.co/t/filebeat-to-support-tls1-3/299045
**Category:** Beats
**Tags:** filebeat
**Created:** [March 8, 2022, 6:57am UTC](https://discuss.elastic.co/t/filebeat-to-support-tls1-3/299045 "2022-03-08T06:57:44Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Nikhitha](https://avatars.discourse-cdn.com/v4/letter/n/ba9def/32.png) [@Nikhitha](https://discuss.elastic.co/u/Nikhitha)
#### Post date: [March 8, 2022, 6:57am UTC](https://discuss.elastic.co/t/filebeat-to-support-tls1-3/299045/1 "2022-03-08T06:57:44Z")

</div>

Does filebeat 7.16.0 suport TLS 1.3?

---

<div class="post-metadata">

### Author: ![Edoardo\_Tenani](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/edoardo_tenani/32/94302_2.png) [@Edoardo\_Tenani](https://discuss.elastic.co/u/Edoardo_Tenani)
#### Post date: [March 8, 2022, 2:57pm UTC](https://discuss.elastic.co/t/filebeat-to-support-tls1-3/299045/2 "2022-03-08T14:57:53Z")

</div>

Hi @Nikhitha.

Filebeat 7.16 has been built with [Golang 1.17.2](https://github.com/elastic/beats/blob/v7.16.0/.go-version). Golang supports TLS 1.3 since [Golang 1.13](https://go.dev/doc/go1.13#tls_1_3).

Is there a specific use case you have in mind?

---

<div class="post-metadata">

### Author: ![Nikhitha](https://avatars.discourse-cdn.com/v4/letter/n/ba9def/32.png) [@Nikhitha](https://discuss.elastic.co/u/Nikhitha)
#### Post date: [March 9, 2022, 10:32am UTC](https://discuss.elastic.co/t/filebeat-to-support-tls1-3/299045/3 "2022-03-09T10:32:27Z")

</div>

Hello @Edoardo_Tenani ,  
Trying to test if Filebeat supports TLS 1.3, So to do this we need a connection with Logstash. Logstash has input beats plugin which is currently not supporting TLS 1.3 [Beats input plugin | Logstash Reference [8.1] | Elastic](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-beats.html#plugins-inputs-beats-tls_max_version), so is there any way I can achieve this.

---

<div class="post-metadata">

### Author: ![Edoardo\_Tenani](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/edoardo_tenani/32/94302_2.png) [@Edoardo\_Tenani](https://discuss.elastic.co/u/Edoardo_Tenani)
#### Post date: [March 9, 2022, 11:56am UTC](https://discuss.elastic.co/t/filebeat-to-support-tls1-3/299045/4 "2022-03-09T11:56:42Z")

</div>

Have you tried configuring TLS 1.3 even if the documentation says max is 1.2? It may be the documentation is outdated.

I found an [in progress issue](https://github.com/elastic/logstash/issues/10494) for TLS 1.3 support in Logstash and asked clarification there.

---

<div class="post-metadata">

### Author: ![Edoardo\_Tenani](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/edoardo_tenani/32/94302_2.png) [@Edoardo\_Tenani](https://discuss.elastic.co/u/Edoardo_Tenani)
#### Post date: [March 22, 2022, 4:22pm UTC](https://discuss.elastic.co/t/filebeat-to-support-tls1-3/299045/6 "2022-03-22T16:22:19Z")

</div>

This [comment](https://github.com/elastic/logstash/issues/10494#issuecomment-1066621216) confirms that support for TLS 1.3 for beats is not yet available, but expected to land soon:

> for Beats, unfortunately, the [`tls_max_version`](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-beats.html#plugins-inputs-beats-tls_max_version) parameter is hard-coded to 1.2 thus it does not adapt to enabling 1.3 despite the underlying Java SSL engine having the support (likely relates to the `cipher_suites` parameter which also needs revisiting). part of this meta issue we plan to look into getting Beats ready for TLS 1.3 - work is done plugin by plugin, hopefully Beats will be completed within the next few weeks.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 19, 2022, 6:22pm UTC](https://discuss.elastic.co/t/filebeat-to-support-tls1-3/299045/7 "2022-04-19T18:22:22Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
