<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Wazuh on Keldo.uk</title>
    <link>https://keldo.uk/tags/wazuh/</link>
    <description>Recent content in Wazuh on Keldo.uk</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 29 Jul 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://keldo.uk/tags/wazuh/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Wazuh File Premissions</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/wazuh-file-premissions/</link>
      <pubDate>Mon, 29 Jul 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/wazuh-file-premissions/</guid>
      <description>&lt;p&gt;I noticed today that Wazuh wasn&amp;rsquo;t working after I restarted my server. I saw in the logs it was failing the bootstrap test. I thought the issue was the mass of file permission error that were appearing before this error showed. However after messing around with file permissions I noticed a error about sysctl vm.max_map_count after running &amp;ldquo;sysctl -w vm.max_map_count=262144&amp;rdquo; it started working however I have no idea how this wasn&amp;rsquo;t a issue until now.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Wazuh</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/wazuh/</link>
      <pubDate>Mon, 22 Jul 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/wazuh/</guid>
      <description>&lt;p&gt;I was originaly planing to try security onion but while reasurching it I came across Wazuh which runs on docker which I always prefer. Once I installed it using a edited version of the compose file in the github repository.&lt;/p&gt;
&lt;p&gt;I managed to install the agent on two of my servers however on my main proxmox host I didn&amp;rsquo;t understand that the server I was the ip of the main host not the server I was installing it on. This lead to a botched install I haven&amp;rsquo;t been able to fix yet.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
