<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ELK Stack on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/elk-stack/</link>
    <description>Recent content in ELK Stack on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 13 Jan 2021 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/elk-stack/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pentesting the ELK Stack</title>
      <link>https://insinuator.net/2021/01/pentesting-the-elk-stack/</link>
      <pubDate>Wed, 13 Jan 2021 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2021/01/pentesting-the-elk-stack/</guid>
      <description>&lt;p&gt;With this blog post, I will provide information on how to proceed when testing&#xA;ELK Stack landscapes. Information regarding the exploitation of the ELK Stack is&#xA;very rare on the internet. Therefore, following article aims to provide you with&#xA;some approaches that can be useful during a penetration test.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Disclaimer:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;All information below were collected during a research project and there is no&#xA;claim for completeness. The guide focuses on ELK Stack deployments for Linux&#xA;machines. Further, this article does not include information for identifying&#xA;misconfigurations in a white-box configuration audit.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
