# I encountered three security-related issues when using elasticserrch version 7.6.1. Thank you for your help

**URL:** <https://discuss.elastic.co/t/i-encountered-three-security-related-issues-when-using-elasticserrch-version-7-6-1-thank-you-for-your-help/278838>\
**Category:** Elastic Security\
**Tags:** elastic-stack-security\
**Created:** [July 16, 2021, 1:15am UTC](https://discuss.elastic.co/t/i-encountered-three-security-related-issues-when-using-elasticserrch-version-7-6-1-thank-you-for-your-help/278838 "2021-07-16T01:15:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![yupengj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yupengj/32/91709_2.png) [@yupengj](https://discuss.elastic.co/u/yupengj)\
**Post date:** [July 16, 2021, 1:15am UTC](https://discuss.elastic.co/t/i-encountered-three-security-related-issues-when-using-elasticserrch-version-7-6-1-thank-you-for-your-help/278838/1 "2021-07-16T01:15:12Z")

</div>

_I encountered three security-related issues when using elasticserrch version 7.6.1. Thank you for your help._

1. How does elasticserrch configure http response headers, such as X-Content-Type-Options, X-XSS-Protection, Content-Security-Policy, Strict-Transport-Security, etc.
2. How does elasticserrch solve this security scanning problem "The target host may have a slow HTTP denial of service attack detected"
3. Are elasticserrch and http OPTIONS methods necessary? Where is he used? Can it be closed?

thank!

---

<div class="post-metadata">

**Author:** ![Frank\_Hassanabad](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frank_hassanabad/32/49255_2.png) [@Frank\_Hassanabad](https://discuss.elastic.co/u/Frank_Hassanabad)\
**Post date:** [July 16, 2021, 4:52pm UTC](https://discuss.elastic.co/t/i-encountered-three-security-related-issues-when-using-elasticserrch-version-7-6-1-thank-you-for-your-help/278838/2 "2021-07-16T16:52:39Z")

</div>

This part of the forums is primarily for security related things such as endpoints, SIEM, etc...

You would probably be better off posting to:

> **[Elastic Stack](https://discuss.elastic.co/c/elastic-stack/81)**
>
> \<a href="https://www.elastic.co/elasticsearch"\>Elasticsearch\</a\>, \<a href="https://www.elastic.co/kibana"\>Kibana\</a\>, \<a href="https://www.elastic.co/beats"\>Beats\</a\>, and \<a href="http://www.elastic.co/logstash"\>Logstash\</a\> - also known as the \<a href="https://www.elastic.co/elk-stack"\>ELK Stack\</a\>. Reliably and securely take data from any source, in any format, then search, analyze, and visualize it in real time.\<br\>
> Please post your your topic under the relevant product category: \<a class="hashtag-cooked" href="/c/elastic-stack/elasticsearch/6" data-type="category" data-slug="elasticsearch" data-id="6" data-ref="elastic-stack:elasticsearch"\>\<span class="hashtag-icon-placeholder"\>\<svg class="fa d-icon d-icon-square-full svg-icon svg-node"\>\<use href="#square-full"\>\</use\>\</svg\>\</span\>\<span\>Elasticsearch\</span\>\</a\>, \<a class="hashtag-cooked" href="/c/elastic-stack/kibana/7" data-type="category" data-slug="kibana" data-id="7" data-ref="elastic-stack:kibana"\>\<span class="hashtag-icon-placeholder"\>\<svg class="fa d-icon d-icon-square-full svg-icon svg-node"\>\<use href="#square-full"\>\</use\>\</svg\>\</span\>\<span\>Kibana\</span\>\</a\>, \<a class="hashtag-cooked" href="/c/elastic-stack/beats/28" data-type="category" data-slug="beats" data-id="28" data-ref="elastic-stack:beats"\>\<span class="hashtag-icon-placeholder"\>\<svg class="fa d-icon d-icon-square-full svg-icon svg-node"\>\<use href="#square-full"\>\</use\>\</svg\>\</span\>\<span\>Beats\</span\>\</a\>, \<a class="hashtag-cooked" href="/c/elastic-stack/logstash/14" data-type="category" data-slug="logstash" data-id="14" data-ref="elastic-stack:logstash"\>\<span class="hashtag-icon-placeholder"\>\<svg class="fa d-icon d-icon-square-full svg-icon svg-node"\>\<use href="#square-full"\>\</use\>\</svg\>\</span\>\<span\>Logstash\</span\>\</a\>, \<a class="hashtag-cooked" href="/c/elastic-stack/elastic-agent/91" data-type="category" data-slug="elastic-agent" data-id="91" data-ref="elastic-stack:elastic-agent"\>\<span class="hashtag-icon-placeholder"\>\<svg class="fa d-icon d-icon-square-full svg-icon svg-node"\>\<use href="#square-full"\>\</use\>\</svg\>\</span\>\<span\>Elastic Agent\</span\>\</a\> .

And using the tags of `elastic-stack-security`

You can also search around here or on google for some some of those keywords and there's a lot of forum posts explaining the content security policies and how you can change them to suit your needs such as this one:

> [@Is unsafe-eval required for script-src in the content-security-policy for Kibana 6.7.1?](https://discuss.elastic.co/t/is-unsafe-eval-required-for-script-src-in-the-content-security-policy-for-kibana-6-7-1/226298/3):
>
> Hi @LizaD - Thank you for the quick reply. I already reviewed that post before I raised my question - it unfortunately does not address my question. What I'd like to do is to set the csp.rules parameter in the kibana.yml file to no longer have unsafe-eval for script-src - to make it more secure: [https://www.elastic.co/guide/en/kibana/6.7/settings.html](https://www.elastic.co/guide/en/kibana/6.7/settings.html) However, I do not know whether removing unsafe-eval from script-src will cause any issues with the list of Kibana functions below: Discover …

Either way, welcome, and good luck on your journeys and when it comes to security, I would always recommend using our latest versions of the stack as well 😉

---

<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:** [August 13, 2021, 4:53pm UTC](https://discuss.elastic.co/t/i-encountered-three-security-related-issues-when-using-elasticserrch-version-7-6-1-thank-you-for-your-help/278838/3 "2021-08-13T16:53:23Z")

</div>

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