<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Arslan Khawaja on Medium]]></title>
        <description><![CDATA[Stories by Arslan Khawaja on Medium]]></description>
        <link>https://medium.com/@khawaja.m.arslan?source=rss-f5677dda31fd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*8I2w1ShTSvjoFPcf</url>
            <title>Stories by Arslan Khawaja on Medium</title>
            <link>https://medium.com/@khawaja.m.arslan?source=rss-f5677dda31fd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:47:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@khawaja.m.arslan/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building a Real World SOC Architecture with Wazuh at the Core]]></title>
            <link>https://medium.com/@khawaja.m.arslan/building-a-real-world-soc-architecture-with-wazuh-at-the-core-694b0aa208f4?source=rss-f5677dda31fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/694b0aa208f4</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[wazuh]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[incident-response]]></category>
            <dc:creator><![CDATA[Arslan Khawaja]]></dc:creator>
            <pubDate>Wed, 29 Apr 2026 09:35:37 GMT</pubDate>
            <atom:updated>2026-04-30T09:24:19.185Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A practical look at how a fully integrated, production running Security Operations Center can be built around open source tooling</em></p><h4>Why I Built This</h4><p>After working with Wazuh for over two and a half years, I stopped treating it as just a SIEM. It became the backbone of an entire SOC architecture one that’s currently live, fully operational, and actually useful. This article walks through that architecture. Not theory nor a lab setup. Something that runs in production and gives real visibility into an organization’s security posture : endpoints, servers, cloud, the whole picture. I’ll explain each component, what it does, and where it connects to Wazuh. In the future, I will be creating and uploading individual integration guides so that you can build your own SOC architecture from scratch, following the same approach demonstrated here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JMsDCrr8F-1CFg3PmJMDPw.png" /><figcaption>Complete SOC Architecture Diagram using Wazuh, Dify, and IRIS</figcaption></figure><h4>The Big Picture</h4><p>Here’s how to think about this architecture before diving into the parts:<br><strong>Left side</strong> : log and alert sources. Everything that generates security relevant data feeds into <strong>Wazuh</strong>.<br><strong>Center</strong> : <strong>Wazuh</strong>. Every log, every event, every alert flows through here first.<br>There’s also an intelligent layer in the middle a pipeline that takes critical events and runs them through an <strong>LLM</strong> for analysis before they ever land on an analyst’s desk.<br><strong>Right side: </strong>response and case management. <strong>DFIR-IRIS</strong> takes over for investigation and case tracking, backed by automation modules that make analyst life easier.</p><blockquote>Simple idea. Powerful in practice.</blockquote><h3>The Log Sources</h3><h4>Direct to Wazuh:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DIqKmo-qm5-X8m5ot74b1A.png" /><figcaption>Syslogs being captured in Wazuh</figcaption></figure><p>Two primary log ingestion methods feed into Wazuh. <br>The first is <strong>syslog</strong>, which is the most widely supported protocol for network security appliances. Any device capable of forwarding syslog whether it is a firewall, router, switch, or network monitoring tool can send its alert and critical events directly to the Wazuh server. Custom rules and decoders can then be applied to normalize the log formats and improve detection accuracy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tUibFWUgtws5_SZkxXA_4A.png" /><figcaption>Alerts being captured in Wazuh</figcaption></figure><p>The second method is <strong>API based log ingestion</strong>. Cloud platforms and endpoint security solutions expose APIs that Wazuh can pull from natively. No middleware or third party forwarder is needed. This covers cloud audit trails, API activity logs, and endpoint telemetry all landing in one place for correlation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NozbH_rBXNd0RPn9YPOciA.png" /><figcaption>Cloud based Alerts being captured in Wazuh</figcaption></figure><h4>Direct to IRIS:</h4><h4>Email Based Alerts</h4><p>Not everything needs to go through a SIEM. Some alert sources are better handled as direct, high priority notifications. <br>In this architecture, three sources operate on an email based pipeline that bypasses Wazuh entirely and creates alerts/cases directly in DFIR-IRIS.</p><p><strong>Endpoint alerts</strong> trigger when a managed device reports a critical event such as a malware detection, encryption failure, or compliance violation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yB2YIYrq9Pg8E0AApH-C_A.png" /><figcaption>Incoming Email (Malware) Alerts being Captured in IRIS</figcaption></figure><p><strong>Leaked credential alerts</strong> fire when a monitored email domain has a compromised account detected externally.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GCI1D9Ou5aNzncYhMNkJAA.png" /><figcaption>Leaked Password Email Alerts being Captured in IRIS</figcaption></figure><p><strong>Report and query forms</strong> allow employees to submit security incidents or questions through an existing internal platform, which automatically generates a structured case in IRIS without any manual intervention from the SOC team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VWmLi4rnr5SnJWsXPVr5UA.png" /><figcaption>Query from employee (case) created in IRIS</figcaption></figure><h3>Wazuh: The Core</h3><p>Logs that needs to be proccess, get feeds into Wazuh. <br>Here’s what it does with all of it.<br>Wazuh correlates events across all those sources, applies its detection rules, and assigns a <strong>severity level</strong> to every alert. That level determines where the alert goes next.</p><ul><li><strong>Level 10 and above</strong> → forwarded to DFIR-IRIS for case management and analyst review</li><li><strong>Level 13 and above</strong> → sent to Dify for LLM assisted analysis before hitting IRIS</li></ul><p>The rule-based engine is what makes this work. Wazuh’s out-of-the-box rules cover a huge amount of ground, and custom rules on top of that handle organization specific logic.</p><h3>The Intelligence Layer: Dify + LibreChat</h3><p>This is where things get interesting.<br>For <strong>Level 13 and above</strong> (critical events) the alert doesn’t go straight to a <strong>human</strong>. It goes to <strong>Dify</strong> first.<br><strong>Dify</strong> acts as an <strong>orchestration layer</strong>. It takes the raw alert data, extracts the relevant fields, structures it, and passes it to <strong>LibreChat</strong> running LLM.<br>The LLM does the first pass analysis:</p><ul><li>What kind of event is this?</li><li>What’s the likely context?</li><li>Is this worth escalating or does it look like a false positive?</li><li>What are the next recommended steps?</li></ul><p>That analysis then gets packaged and sent into DFIR-IRIS as part of the case. So when an analyst opens the case, the initial triage is already done. They’re not starting from a raw log, they’re starting from a structured, <br>AI-assisted summary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t2K0i9XjUWapNB-T14MY3g.png" /><figcaption>Wazuh’s Alert analyzed by Libra’s LLM with the help of Dify Automation</figcaption></figure><p><strong>This is the part that saves the most analyst time in practice.</strong></p><h3>DFIR-IRIS: Case Management</h3><p>DFIR-IRIS is the incident response platform that sits on the right side of this architecture. Every Level 10+ alert that comes out of Wazuh lands here as a case or alert.<br>IRIS gives the SOC team a structured place to:</p><ul><li>Track investigations</li><li>Document findings</li><li>Assign cases to analysts</li><li>Manage the full incident lifecycle</li></ul><p>It’s open source, API-driven, and critically extensible. Which brings us to the automation modules.</p><h4><strong>IRIS Automation Modules:</strong></h4><p>This is the part, built specifically for this architecture. Four modules that plug directly into IRIS and automate enrichment tasks that would otherwise require manual analyst effort.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/745/1*kiCLpOhP_SCQXRSXT2IEPg.png" /><figcaption>List of Processor Modules enabled in DFIR-IRIS</figcaption></figure><h4>VirusTotal Module</h4><p>DFIR-IRIS ships with a native VirusTotal module out of the box. When a case comes in with a file hash, IP address, or domain, queries VirusTotal and pulls the reputation data directly back into the case no copy-pasting hashes into a browser.</p><h4>Gemini Module</h4><p>Google’s Gemini models is integrated here for additional AI-assisted analysis particularly useful for cases where a second opinion or different reasoning model adds value alongside the LibreChat analysis earlier in the pipeline.</p><h4>History Module</h4><p>Pulls historical context for indicators and entities appearing in a case. Has this IP been seen before? Has this endpoint had previous incidents? Context matters in triage, and this module surfaces it automatically.</p><h4>Jira Module</h4><p>When an incident needs to be tracked as a formal ticket escalated to a any other team, this module creates the Jira ticket directly from IRIS. The case and the ticket stay linked.</p><h3>Infrastructure Monitoring : Uptime Kuma</h3><p>Running in parallel to the main pipeline is <strong>Uptime Kuma</strong>, monitoring the availability of the SOC infrastructure itself. If any component Wazuh, IRIS, or the integrations goes down, an <strong>Up/Down alert fires immediately to Slack</strong>.<br>This matters more than people think. A SOC that doesn’t know its own tooling is offline isn’t really operating. Uptime Kuma closes that gap with minimal setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7c1lwL_EolGKPNu_QAuc_w.png" /><figcaption>Active Server Monitoring by Uptime Kuma</figcaption></figure><h3>The Notification Layer : Slack</h3><p>Two types of alerts hit Slack:</p><ol><li><strong>Uptime Kuma up/down alerts</strong> — infrastructure health</li><li><strong>IRIS case update alerts</strong> — when a case status changes, gets assigned, or gets escalated</li></ol><p>Slack isn’t where investigation happens. It’s where awareness happens. Analysts get notified without having to constantly poll dashboards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tQdSQcHCkLIpt9S6Qbwydw.png" /><figcaption>IRIS case updates in Slack</figcaption></figure><h3>What’s Coming Next</h3><p>This article is the overview. Each integration listed here : <br>Wazuh with AWS, Wazuh with the endpoint security platform, the Dify pipeline, the IRIS modules has its own setup complexity. <br>I’ll be publishing individual integration guides for each one so you can actually build this yourself.</p><blockquote><em>By the end of this series, you’ll have everything needed to build this architecture from scratch. It’s fully open source (or offers a free tier), production tested, and proven to work reliably in real-world environments.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=694b0aa208f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting Up ML Based Anomaly Detection in Wazuh]]></title>
            <link>https://medium.com/@khawaja.m.arslan/setting-up-ml-based-anomaly-detection-in-wazuh-badd567fe9da?source=rss-f5677dda31fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/badd567fe9da</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[siem]]></category>
            <category><![CDATA[wazuh]]></category>
            <category><![CDATA[anomaly-detection]]></category>
            <dc:creator><![CDATA[Arslan Khawaja]]></dc:creator>
            <pubDate>Wed, 18 Mar 2026 06:58:15 GMT</pubDate>
            <atom:updated>2026-03-18T06:58:15.202Z</atom:updated>
            <content:encoded><![CDATA[<p>If you work in a SOC, you know the feeling. You open your Wazuh dashboard in the morning and there are hundreds of the same alert staring back at you. Some Static Rules fired again. And again. And again.</p><p>After dealing with this for way too long, I decided to actually fix it using the Anomaly Detection feature that has been sitting in the Wazuh dashboard the whole time. Most people don’t even know it exists.</p><p>This article walks you through exactly how I set it up, what it does, and how it can help your team stop drowning in noise and start catching real threats.</p><h3>The Problem: Static Rules Are Too Dumb</h3><p>Wazuh’s built-in rules work like this: if X happens Y times in Z seconds, fire an alert. Simple. Fast. And incredibly annoying.</p><p>The rule that was killing my dashboard was <strong>Rule 31533</strong> <strong>“High amount of POST requests in a small period of time (likely bot).”</strong> It fires if any IP sends 8 POST requests in a short window.</p><p>The problem? Modern web apps make dozens of background POST requests every minute just to work. Internal chat tools, course platforms, webmail, they all do this constantly. None of it is a threat, but Wazuh doesn’t know that.</p><p>So instead of my dashboard showing me real attacks, it was buried in noise from my own internal applications.</p><h3>The Solution: Machine Learning That Learns Your Environment</h3><p>The Wazuh dashboard (which runs on OpenSearch) has an <strong>Anomaly Detection plugin</strong> built in. As of Wazuh 4.8 and above, it comes out of the box you don’t need to install anything extra.</p><p>Instead of checking “did X happen more than Y times,” it asks a smarter question: <strong>“Is this behaviour unusual for this specific IP, based on everything I’ve seen before?”</strong></p><p>The algorithm powering this is called <strong>Random Cut Forest (RCF)</strong>. It’s an open-source ML algorithm originally built by AWS, designed specifically for real-time streaming data which is exactly what your Wazuh logs are.</p><p>Here’s the simple version of how it works:</p><p>Imagine plotting every IP address and its behaviour on a graph. Normal users cluster together in the middle because they all behave roughly the same. An attacker doing a vulnerability scan sits way out at the edge of the graph because they’re doing something wildly different.</p><p>The RCF algorithm keeps making “cuts” across this graph to separate data points. Normal IPs are hard to separate because they’re all bunched together. Attackers are easy to isolate because they’re already alone at the edge.</p><p><strong>The fewer cuts it takes to isolate an IP, the higher the anomaly score.</strong> A score of 1.0 means critical. A score of 0.0 means completely normal.</p><p>The best part: it’s <strong>unsupervised</strong>. You don’t train it with labelled data. You just turn it on and it figures out your environment by itself.</p><h3>What Was Actually Happening in My Logs</h3><p>Before building the detector, I looked at what was actually firing all these alerts. I had two very different things mixed together:</p><p><strong>Thing 1 (Harmless):</strong> An internal IP making hundreds of POST requests to internal tools. It was just background polling from chat and course platform apps doing their normal thing. Completely safe, but Rule 31533 was screaming about it every few seconds.</p><p><strong>Thing 2 (Actual Attack):</strong> An external IP from Singapore systematically requesting hundreds of file paths like /.env, /.env.local, /.stripe.bak, /config.env and similar variations all returning 404s. This is a classic automated vulnerability scanner trying to find accidentally exposed credentials and API keys. This one genuinely deserved an alert.</p><p>The static rules couldn’t tell the difference. The ML model can.</p><h3>Building the Detector Step by Step</h3><p>Go to your Wazuh Dashboard and look in the left sidebar for <strong>Anomaly Detection</strong>. Click <strong>Create detector</strong>.</p><h4>Step 1: Click on <strong>Create detector</strong></h4><figure><img alt="Wazuh Anomaly Detetector page" src="https://cdn-images-1.medium.com/max/1024/1*6fYI8c24S-ARYd3KKjxdFA.png" /><figcaption>The “Anomaly Detector” page is shown above</figcaption></figure><h4>Step 2: Add the Following Information</h4><p>Detector name: nginx-recon-and-spam<br>Description:Detects vulnurability scanning and abnormal POST traffic on Nginx<br>Index:wazuh-alerts-4.x-2026*<br>Data filter:agent.name is nginx-proxy<br>Timestamp field:timestamp<br>Detector interval:1 minute <br>Window delay:1 minute <br>Custom result index Leave disabled</p><figure><img alt="The “Define Detector” page with the fields filled in as shown" src="https://cdn-images-1.medium.com/max/1024/1*LuxziKmcdffI0NQjVV_c-Q.png" /><figcaption>The “Define Detector” page with the fields filled in as shown above</figcaption></figure><p><strong>Why 1 minute for the interval?</strong> The attack I was seeing fired hundreds of requests in under 40 seconds. A 1-minute window catches that almost in real time.</p><p><strong>Why 1 minute for window delay?</strong> There’s a small gap between when Nginx logs something, Wazuh processes it, and OpenSearch indexes it. This 1 minute buffer makes sure all the logs have arrived before the model does its math.</p><p><strong>Click Next.</strong></p><h4>Step 3: Configure the Model Features</h4><p>This is the most important step. You’re telling the ML model what to measure.</p><p><strong>Feature 1: Count the alerts<br></strong>Feature name:alert_count<br>Aggregation method:count()<br>Field:data.id<br>Anomaly criteria:Deviation in any direction<br>This simply counts how many Wazuh alerts any given IP generates per minute. A normal user might generate 2 or 3. An attacker running a scanner might generate 80.</p><p><strong>Feature 2: Track the maximum severity<br></strong>Feature name:max_severity<br>Aggregation method:max()<br>Field:rule.level<br>Anomaly criteria:Deviation in any direction<br>This watches the severity level of the alerts. A normal IP might occasionally hit a level 5. An active scanner will keep hitting level 8, 9, and 10 alerts. When both features spike at the same time, the model knows something serious is happening.</p><p>Scroll down to <strong>Categorical fields</strong> and enable it. Set the field to data.srcip.</p><p>This one setting changes everything.</p><p>Without it, the model looks at your entire server’s traffic as one big number. With it, the model creates a <strong>separate mathematical profile for every single IP address</strong> that connects to you.</p><p>That’s how it knows your internal app making 300 POST requests is normal (it does this every day), but a brand new IP from Singapore making 300 requests is not (it has never done this before).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mb8Gt0RhNQ8OfqTU8--6ng.png" /><figcaption>The configuring the model and categorical fields section selected</figcaption></figure><h4>Step 4: Check the Preview</h4><p>The preview will show you a heatmap. Each row is an IP address. The colours show anomaly grades from the past few weeks.<br>What you want to see:</p><p><strong>Light yellow or no colour</strong> for your known internal IPs — this means the model recognised their traffic as normal background noise.</p><p><strong>Dark orange or red blocks</strong> for external IPs that did something suspicious — these are the actual threats you care about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yg6JSWLYy73BkaCGe7hxTQ.png" /></figure><p>If you click on one of the red blocks, you’ll see two graphs below it showing exactly when the alert_count and max_severityspiked for that IP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tlXv3mWmE7doV0kA25olxQ.png" /><figcaption>The drill-down view of a suspicious IP showing the feature graphs with spikes</figcaption></figure><p>If the preview looks right, click <strong>Next</strong></p><h4>Step 5: Check the Detector Jobs</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wuFIfTTE9S5YtuOtNAMEvw.png" /></figure><p>click <strong>Next again</strong></p><h4>Step 5: Review and Create Detector</h4><p>You might see a yellow warning banner that says <strong>“Data is too sparse after data filter is applied.”</strong></p><p>Ignore it. This is completely normal.</p><p>ML algorithms prefer continuous streams of data every second. Our detector is watching for attacks that only happen sometimes. An empty gap in the data means your server wasn’t being attacked during that window which is a good thing. When an attack does happen, the spike is so dramatic compared to the baseline that the model catches it immediately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZnT6DOQt-bvPCS5cn1THxw.png" /></figure><p>Review the Page and then click <strong>Next</strong></p><h4>Step 6: Live Dashboard Looks Like</h4><p>Once the detector is running, go to the <strong>Real-time results</strong> tab.<br>When you first start it, the graph will be empty. This does not mean it’s broken. It means no anomalies have occurred since you turned it on. The model is running in the background watching everything.</p><p>Switch to the <strong>Historical analysis</strong> tab and run it on the last 7 days to see past attack patterns. This is what you’d show to management or in a team meeting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eXIzazOn4U-Pr7-LaMT8zw.png" /><figcaption>The Real-time results tab showing “Running since [date/time]” with a blank graph</figcaption></figure><h4>Where Is This Model Actually Running?</h4><p>The RCF model runs on the <strong>Wazuh Indexer</strong> (the OpenSearch component), not the Wazuh Manager. This means it has zero impact on your log ingestion pipeline. Your Wazuh Manager keeps processing rules and forwarding alerts completely unaffected.</p><p>It also comes built into Wazuh 4.8 and above, so there’s nothing extra to install or pay for. You already have it.</p><h4>What This Doesn’t Do (Important)</h4><p>The anomaly detector runs <strong>alongside</strong> your regular Wazuh rules, not instead of them.</p><p>If you build this detector but don’t touch your rules, you’ll still get flooded by Rule 31533 and Rule 31101 on your main dashboard. The anomaly detector lives in its own section.</p><p>To fully solve alert fatigue, you’d also want to tune or suppress the noisy static rules for known internal IPs but that’s a separate step. The anomaly detector gives you the intelligent layer on top that catches what the static rules miss.</p><h4>The Next Step: Automated Alerts</h4><p>On the anomaly detector results page, there’s a <strong>“Set up alerts”</strong> button. This connects the ML model to the OpenSearch Alerting plugin.</p><p>You can configure it so that when the model detects a Grade 1.0 anomaly with high confidence, it automatically sends a message to a Slack channel, Teams, or email. Instead of someone having to watch the dashboard, the dashboard messages you.</p><p>That’s the full pipeline: raw logs go in, ML filters the noise, and a single high-confidence alert comes out to your team.</p><h3>Summary</h3><p>The whole point of this setup is to compress hundreds of low-quality alerts into a handful of high-confidence ones.</p><p>Before: 6000+ alerts from Rule 31533 and Rule 31101, mostly from internal apps doing normal things, mixed in with one actual attacker that you’d easily miss.</p><p>After: One Critical anomaly for the actual attacker. Silence for everything else.</p><p>The model is unsupervised so it adapts over time. If something genuinely changes in your environment a new internal service that starts making more requests the model will learn the new normal within a few days and stop alerting on it.</p><p>It’s already in your Wazuh installation. It just needs to be turned on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=badd567fe9da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Upgrade Wazuh v4.7 to v4.10]]></title>
            <link>https://medium.com/@khawaja.m.arslan/upgrade-wazuh-v4-7-to-v4-10-75212a01aec3?source=rss-f5677dda31fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/75212a01aec3</guid>
            <category><![CDATA[upgrade]]></category>
            <category><![CDATA[wazuh-agent]]></category>
            <category><![CDATA[troubleshooting]]></category>
            <category><![CDATA[wazuh]]></category>
            <category><![CDATA[wazuh-manager]]></category>
            <dc:creator><![CDATA[Arslan Khawaja]]></dc:creator>
            <pubDate>Mon, 03 Feb 2025 12:18:13 GMT</pubDate>
            <atom:updated>2025-02-03T12:18:13.270Z</atom:updated>
            <content:encoded><![CDATA[<p>Step by Step instruction to Upgrade wazuh</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/1*Q9WufM05PryZpNWooCHfSg.jpeg" /></figure><p>The current deployment of Wazuh involves a distributed architecture with three separate machines dedicated to running the Indexer, Server, and Dashboard. The upgrade process for this architecture will be carried out incrementally, starting with the Indexer, followed by the Server, and finally the Dashboard</p><p><strong><em>Root user</em></strong><em> privileges are required to run all the commands described below</em></p><h3>Wazuh-Indexer</h3><p>For deployments utilizing multiple Wazuh indexer nodes, begin the installation process from step 1. For single-node indexer deployments, proceed directly to step 2.</p><p><strong>Note:</strong> In a Wazuh indexer cluster with multiple nodes, the cluster remains available throughout the upgrade process. This rolling upgrade allows for the shutdown of one Wazuh indexer node at a time, ensuring minimal disruption of service</p><blockquote><strong>Step-1:(only for Multi-nodes Indexer)<br></strong>Repeat the following steps for every Wazuh indexer node, replacing <strong>“indexer-ip”, “user”, and “pass”<br></strong> →Disable shard allocation</blockquote><pre>curl -X PUT &quot;https://indexer-ip:9200/_cluster/settings&quot; -u user:pass -k -H &#39;Content-Type: application/json&#39; -d&#39;{&quot;persistent&quot;:{&quot;cluster.routing.allocation.enable&quot;:&quot;primaries&quot;}}&#39;</pre><blockquote><strong>Step-2:<br></strong>→Stop non-essential indexing and perform a synced flush</blockquote><pre>curl -X POST &quot;https://indexer-ip:9200/_flush/synced&quot; -u user:pass -k</pre><figure><img alt="result of step2" src="https://cdn-images-1.medium.com/max/1024/0*yU2SlSZoAAcEd_ZS" /><figcaption>Result of step#2</figcaption></figure><blockquote><strong>Step-3:<br></strong>→Stop wazuh-indexer</blockquote><pre>systemctl stop wazuh-indexer</pre><blockquote><strong>Step-4:<br></strong>→Start the wazuh-indexer upgrade</blockquote><pre>apt-get install wazuh-indexer</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dY9Kxo1rZpFSCR8ED8vttw.png" /><figcaption>Result of step#4</figcaption></figure><p><strong>Note:</strong> During the upgrade process, if the following instructions appear, it means that the upgrade is prompting to either retain the current configuration or overwrite it with the default configuration included in the package update</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CL0LTPIRr1rTDHA5yD6XUA.png" /><figcaption>Result of step#4</figcaption></figure><blockquote><strong>Step-5:<br></strong>→Reload, Enable , Restart</blockquote><pre>systemctl daemon-reload<br>systemctl enable wazuh-indexer<br>systemctl start wazuh-indexer</pre><blockquote><strong>Step-6:<br></strong>→Re-enable shard allocation</blockquote><pre>curl -X PUT &quot;https://indexer-ip:9200/_cluster/settings&quot; -u user:pass -k -H &#39;Content-Type: application/json&#39; -d&#39;{&quot;persistent&quot;:{&quot;cluster.routing.allocation.enable&quot;:&quot;all&quot;}}&#39;</pre><blockquote><strong>Step-7:<br></strong>→Check the status of the Wazuh indexer cluster to see if the shard allocation has finished</blockquote><pre>curl -k -u user:pass https://indexer-ip:9200/_cat/nodes?v</pre><h3>Wazuh-Server</h3><p>When upgrading a multi-node Wazuh manager cluster, execute the upgrade on each node to ensure all Wazuh manager nodes join the cluster.</p><p><strong>Note:</strong>Begin with the master node to minimize server downtime.</p><blockquote><strong>Step-1:<br></strong>→Start the wazuh-server upgrade</blockquote><pre>apt-get install wazuh-manager</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IqsCZsg6gRL9mtoPX9mTVQ.png" /><figcaption>Result of step#1</figcaption></figure><p>The configuration file <strong><em>/var/ossec/etc/ossec.conf</em></strong><em> , </em>it will not be automatically update during the upgrade. This means that the settings for new vulnerability capability introduced in the upgrade must be manually added.</p><blockquote><strong>Step-2:<br></strong>Edit <strong>/var/ossec/etc/ossec.conf</strong> to configure the new vulnerability detection module<em><br></em>Remove the existing <strong>&lt;vulnerability-detector&gt;</strong> if it is present.<br>Add the new <strong>&lt;vulnerability-detection&gt;</strong> block</blockquote><pre>&lt;vulnerability-detection&gt;<br>  &lt;enabled&gt;yes&lt;/enabled&gt;<br>  &lt;index-status&gt;yes&lt;/index-status&gt;<br>  &lt;feed-update-interval&gt;60m&lt;/feed-update-interval&gt;<br>&lt;/vulnerability-detection&gt;</pre><p><strong>Note:</strong> This configuration activates the vulnerability detection module, allowing it to index vulnerabilities and generate alerts. The vulnerability feed is updated every 60 minutes.</p><blockquote><strong>Step-3:<br></strong>A default Indexer configuration in the last of <strong>ossec.conf</strong> file is automatically appended to <strong>/var/ossec/etc/ossec.conf</strong> as part of a new<strong> &lt;ossec_conf&gt;</strong> block.<br>Replace <strong>0.0.0.0</strong> with your <strong>Wazuh indexer</strong> node IP address or hostname<br>If you have a Wazuh indexer cluster, add a <strong>&lt;host&gt;&lt;/host&gt;</strong> entry for each one of your nodes.</blockquote><pre>&lt;indexer&gt;<br>  &lt;enabled&gt;yes&lt;/enabled&gt;<br>  &lt;hosts&gt;<br>    &lt;host&gt;https://0.0.0.0:9200&lt;/host&gt;<br>  &lt;/hosts&gt;<br>  &lt;ssl&gt;<br>    &lt;certificate_authorities&gt;<br>      &lt;ca&gt;/etc/filebeat/certs/root-ca.pem&lt;/ca&gt;<br>    &lt;/certificate_authorities&gt;<br>    &lt;certificate&gt;/etc/filebeat/certs/filebeat.pem&lt;/certificate&gt;<br>    &lt;key&gt;/etc/filebeat/certs/filebeat-key.pem&lt;/key&gt;<br>  &lt;/ssl&gt;<br>&lt;/indexer&gt;</pre><p><strong>Note: </strong>Vulnerability detection prioritizes reporting to the first node in the list. It switches to the next node in case it’s not available.</p><blockquote><strong>Step-4:<br></strong>Save the <strong>Wazuh indexer username </strong>and <strong>password</strong> into the <strong>Wazuh manager</strong> keystore using the <strong>Wazuh-keystore tool.</strong></blockquote><pre>echo &#39;&lt;USERNAME&gt;&#39; | /var/ossec/bin/wazuh-keystore -f indexer -k username<br>echo &#39;&lt;PASSWORD&gt;&#39; | /var/ossec/bin/wazuh-keystore -f indexer -k password</pre><p><strong>Note:</strong> In case you’ve forgotten your Wazuh indexer password, Reset the password by following Password Management through Official Documentation.</p><blockquote><strong>Step-5:<br></strong>Download the latest alerts template.</blockquote><pre>curl -so /etc/filebeat/wazuh-template.json https://raw.githubusercontent.com/wazuh/wazuh/v4.10.1/extensions/elasticsearch/7.x/wazuh-template.json<br>chmod go+r /etc/filebeat/wazuh-template.json</pre><blockquote><strong>Step-6:<br></strong>Reload, Enable , Restart</blockquote><pre>systemctl daemon-reload<br>systemctl enable filebeat<br>systemctl start filebeat</pre><blockquote><strong>Step-7:<br></strong>Upload the new Wazuh template and pipelines for Filebeat</blockquote><pre>filebeat setup --pipelines<br>filebeat setup --index-management -E output.logstash.enabled=false</pre><h3>Wazuh-Dashboard</h3><p><strong>Note:</strong> That this upgrade process doesn’t update plugins installed manually. Outdated plugins might cause the upgrade to fail.</p><blockquote><strong>Step-1:<br></strong>Save the <strong>/etc/wazuh-dashboard/opensearch_dashboards.yml</strong> file to some place<br>Upgrade the <strong>Wazuh dashboard</strong>.</blockquote><p>Note: When prompted, Replace the <strong>/etc/wazuh-dashboard/opensearch_dashboards.yml</strong> file with the updated version.</p><pre>apt-get install wazuh-dashboard</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6HWbP7WAm_rAwyBWjSlXSw.png" /><figcaption>Result of step#1</figcaption></figure><p>Manually reapply any settings changes to the <strong>/etc/wazuh-dashboard/opensearch_dashboards.yml</strong> file</p><blockquote><strong>Step-2:<br></strong>Reload, Enable , Restart</blockquote><pre>systemctl daemon-reload<br>systemctl enable wazuh-dashboard<br>systemctl start wazuh-dashboard</pre><h3>Troubleshoot</h3><p>If any issue arises after the upgrade, please refer to the official documentation for known issues via the following link.<br><a href="https://documentation.wazuh.com/current/upgrade-guide/troubleshooting.html">Troubleshooting</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75212a01aec3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wazuh All in One Installation]]></title>
            <link>https://medium.com/@khawaja.m.arslan/wazuh-all-in-one-installation-ded09910c7aa?source=rss-f5677dda31fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/ded09910c7aa</guid>
            <category><![CDATA[wazuh-agent]]></category>
            <category><![CDATA[wazuh]]></category>
            <category><![CDATA[wazuh-active-response]]></category>
            <category><![CDATA[wazuh-manager]]></category>
            <category><![CDATA[siem]]></category>
            <dc:creator><![CDATA[Arslan Khawaja]]></dc:creator>
            <pubDate>Wed, 04 Sep 2024 11:54:10 GMT</pubDate>
            <atom:updated>2024-11-09T08:58:59.425Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is Wazuh?</h3><p>Wazuh is a free and open-source security platform that provides unified XDR and SIEM protection for endpoints and cloud workloads. It is a comprehensive security solution that can be used to detect, prevent, and respond to security threats.</p><h3>Deployment Types of Wazuh:</h3><p>The installation guide is divided into two independent sections: <strong>all-in-one deployment </strong>and <strong>distributed deployment</strong>. The installation requirements for the Wazuh server and Elastic Stack are similar to those described in the requirements section.</p><h3>All-in-one deployment:</h3><p>Wazuh server and Elastic Stack are installed on the same host. This type of deployment is appropriate for testing and small working environments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/858/0*KCU3kicNfyBkP9lO" /></figure><h3>The following components will be installed:</h3><ul><li>The <strong>Wazuh server</strong>, including the <strong>Wazuh manager</strong> as a <strong>single-node cluster,</strong> and <strong>Filebeat.</strong></li><li><strong>Elastic Stack</strong>, including <strong>Elasticsearch</strong> as a <strong>single-node cluster</strong>, and <strong>Kibana</strong>, including the<strong> Wazuh Kibana plugin</strong>.</li></ul><p>The communication is encrypted using certificates. Follow the installation guide to install and configure all the required components.</p><h3>Starting Installation:</h3><p>You need root user privileges to run all the commands described below.</p><h3>Install prerequisites:</h3><p>Install all the necessary packages:</p><p>apt-get install apt-transport-https zip unzip lsb-release curl gnupg</p><h3>Installing Elasticsearch:</h3><h4>Add the Elastic Stack repository:</h4><p>Install the GPG key:</p><p><em>curl -s </em><a href="https://artifacts.elastic.co/GPG-KEY-elasticsearch"><em>https://artifacts.elastic.co/GPG-KEY-elasticsearch</em></a><em> | gpg — no-default-keyring — keyring gnupg-ring:/usr/share/keyrings/elasticsearch.gpg — import &amp;&amp; chmod 644 /usr/share/keyrings/elasticsearch.gpg</em></p><p>Add the repository:</p><p><em>echo “deb [signed-by=/usr/share/keyrings/elasticsearch.gpg] </em><a href="https://artifacts.elastic.co/packages/7.x/apt"><em>https://artifacts.elastic.co/packages/7.x/apt</em></a><em> stable main” | tee /etc/apt/sources.list.d/elastic-7.x.list</em></p><p>Update the package information:</p><p><em>apt-get update</em></p><h4>Elasticsearch installation and configuration:</h4><p>Install the Elasticsearch package:</p><p><em>apt-get install elasticsearch=7.17.13</em></p><p>Download the configuration file as follows:</p><p><em>curl -so /etc/elasticsearch/elasticsearch.yml </em><a href="https://packages.wazuh.com/4.5/tpl/elastic-basic/elasticsearch_all_in_one.yml"><em>https://packages.wazuh.com/4.5/tpl/elastic-basic/elasticsearch_all_in_one.yml</em></a></p><p>If want to do configuration to elastic search file, it can be viewed and edited with <strong>sudo:</strong></p><p><em>sudo nano /etc/elasticsearch/elasticsearch.yml</em></p><p>(only configure if wanted to deploy elastic search on different ip)</p><h3>Certificates creation and deployment:</h3><p>Download the configuration file for creating the certificates:</p><p><em>curl -so /usr/share/elasticsearch/instances.yml </em><a href="https://packages.wazuh.com/4.5/tpl/elastic-basic/instances_aio.yml"><em>https://packages.wazuh.com/4.5/tpl/elastic-basic/instances_aio.yml</em></a></p><p>In the following steps, a file that contains a folder named after the instance defined here will be created. This folder will contain the certificates and the keys necessary to <strong>communicate with the Elasticsearch node using SSL.</strong></p><p>Certificates can be created using the elasticsearch-certutil tool:</p><p><em>/usr/share/elasticsearch/bin/elasticsearch-certutil cert ca — pem — in instances.yml — keep-ca-key — out ~/certs.zip</em></p><p>Extract the generated zip file from the previous step:</p><p><em>unzip ~/certs.zip -d ~/certs</em></p><p>This zip file located at <strong>/usr/share/elasticsearch/certs.zip</strong></p><p>The next step is to create the directory <strong>/etc/elasticsearch/certs</strong>, and then copy the <strong>CA file</strong>, the certificate and the key there:</p><p><em>mkdir /etc/elasticsearch/certs/ca -p</em></p><p><em>cp -R ~/certs/ca/ ~/certs/elasticsearch/* /etc/elasticsearch/certs/</em></p><p><em>chown -R elasticsearch: /etc/elasticsearch/certs</em></p><p><em>chmod -R 500 /etc/elasticsearch/certs</em></p><p><em>chmod 400 /etc/elasticsearch/certs/ca/ca.* /etc/elasticsearch/certs/elasticsearch.*</em></p><p><em>rm -rf ~/certs/ ~/certs.zip</em></p><h4>Enable and start the Elasticsearch service:</h4><p><em>systemctl daemon-reload</em></p><p><em>systemctl enable elasticsearch</em></p><p><em>systemctl start elasticsearch</em></p><p>Generate credentials for all the Elastic Stack pre-built roles and users:</p><p><em>/usr/share/elasticsearch/bin/elasticsearch-setup-passwords auto</em></p><p>The command above will prompt an output of username &amp; password of the elastic user.</p><p>&lt;&lt;SAVE ALL THE USERNAMES AND PASSWORDS&gt;&gt;</p><p>To check that the installation was made successfully, run the following command replacing &lt;elastic_password&gt; with the password generated in the previous step for elastic user:</p><p><em>curl -XGET </em><a href="https://localhost:9200/"><em>https://localhost:9200</em></a><em> -u elastic:&lt;elastic_password&gt; -k</em></p><p>This command will prompt package name, cluster name with uuid and version details.</p><p>At the end Tagline will be <strong>“You Know, for Search”</strong></p><h3>Installing Wazuh server:</h3><p>The Wazuh server collects and analyzes data from deployed agents. It runs the Wazuh manager, the Wazuh API and Filebeat.</p><h4>Adding the Wazuh repository:</h4><p>Install the GPG key:</p><p><em>curl -s </em><a href="https://packages.wazuh.com/key/GPG-KEY-WAZUH"><em>https://packages.wazuh.com/key/GPG-KEY-WAZUH</em></a><em> | gpg — no-default-keyring — keyring gnupg-ring:/usr/share/keyrings/wazuh.gpg — import &amp;&amp; chmod 644 /usr/share/keyrings/wazuh.gpg</em></p><p>Add the repository:</p><p><em>echo “deb [signed-by=/usr/share/keyrings/wazuh.gpg] </em><a href="https://packages.wazuh.com/4.x/apt/"><em>https://packages.wazuh.com/4.x/apt/</em></a><em> stable main” | tee -a /etc/apt/sources.list.d/wazuh.list</em></p><p>Update the package information:</p><p><em>apt-get update</em></p><h4>Installing the Wazuh manager</h4><p>Install the Wazuh manager package:</p><p><em>apt-get install wazuh-manager</em></p><h4>Enable and start the Wazuh manager service:</h4><p><em>systemctl daemon-reload</em></p><p><em>systemctl enable wazuh-manager</em></p><p><em>systemctl start wazuh-manager</em></p><p>Check if the Wazuh manager is active</p><p>systemctl status wazuh-manager</p><h3>Installing Filebeat:</h3><p>Filebeat is the tool on the Wazuh server that securely forwards alerts and archived events to Elasticsearch.</p><h4>Filebeat installation and configuration:</h4><p>Install the Filebeat package:</p><p><em>apt-get install filebeat=7.17.13</em></p><p>Download the pre-configured Filebeat config file</p><p><em>curl -so /etc/filebeat/filebeat.yml </em><a href="https://packages.wazuh.com/4.5/tpl/elastic-basic/filebeat_all_in_one.yml"><em>https://packages.wazuh.com/4.5/tpl/elastic-basic/filebeat_all_in_one.ym</em></a><em>l</em></p><p>Download the alerts template for Elasticsearch</p><p><em>curl -so /etc/filebeat/wazuh-template.json </em><a href="https://raw.githubusercontent.com/wazuh/wazuh/v4.5.4/extensions/elasticsearch/7.x/wazuh-template.json"><em>https://raw.githubusercontent.com/wazuh/wazuh/v4.5.4/extensions/elasticsearch/7.x/wazuh-template.json</em></a></p><p><em>chmod go+r /etc/filebeat/wazuh-template.json</em></p><p>Download the Wazuh module for Filebeat:</p><p><em>curl -s </em><a href="https://packages.wazuh.com/4.x/filebeat/wazuh-filebeat-0.2.tar.gz"><em>https://packages.wazuh.com/4.x/filebeat/wazuh-filebeat-0.2.tar.gz</em></a><em> | tar -xvz -C /usr/share/filebeat/module</em></p><p>Edit the file <strong>/etc/filebeat/filebeat.yml </strong>and add the following line</p><p>output.elasticsearch.password: &lt;elasticsearch_password&gt;</p><p>Copy the certificates into<strong> /etc/filebeat/certs/</strong></p><p><em>cp -r /etc/elasticsearch/certs/ca/ /etc/filebeat/certs/</em></p><p><em>cp /etc/elasticsearch/certs/elasticsearch.crt /etc/filebeat/certs/filebeat.crt</em></p><p><em>cp /etc/elasticsearch/certs/elasticsearch.key /etc/filebeat/certs/filebeat.key</em></p><h4>Enable and start the Filebeat service:</h4><p><em>systemctl daemon-reload</em></p><p><em>systemctl enable filebeat</em></p><p><em>systemctl start filebeat</em></p><p>To ensure that Filebeat has been successfully installed, run the following command:</p><p><em>filebeat test output</em></p><h3>Kibana installation and configuration:</h3><p>Kibana is a flexible and intuitive web interface for mining and visualizing the events and archives stored in Elasticsearch.</p><p>Install the Kibana package:apt-get install kibana=7.17.13 Copy the Elasticsearch certificates into the Kibana configuration folder:</p><p><em>mkdir /etc/kibana/certs/ca -p</em></p><p><em>cp -R /etc/elasticsearch/certs/ca/ /etc/kibana/certs/</em></p><p><em>cp /etc/elasticsearch/certs/elasticsearch.key /etc/kibana/certs/kibana.key</em></p><p><em>cp /etc/elasticsearch/certs/elasticsearch.crt /etc/kibana/certs/kibana.crt</em></p><p><em>chown -R kibana:kibana /etc/kibana/</em></p><p><em>chmod -R 500 /etc/kibana/certs</em></p><p><em>chmod 440 /etc/kibana/certs/ca/ca.* /etc/kibana/certs/kibana.*</em></p><p>Download the Kibana configuration file:</p><p><em>curl -so /etc/kibana/kibana.yml </em><a href="https://packages.wazuh.com/4.5/tpl/elastic-basic/kibana_all_in_one.yml"><em>https://packages.wazuh.com/4.5/tpl/elastic-basic/kibana_all_in_one.yml</em></a></p><p>Edit the <strong>/etc/kibana/kibana.yml</strong> file:</p><p>Values to be replaced:</p><p>&lt;elasticsearch_password&gt;: the password generated during the Elasticsearch installation and configuration for the elastic user.</p><p>elasticsearch.password: &lt;elasticsearch_password&gt;</p><p>Create the /usr/share/kibana/data directory:</p><p><em>mkdir /usr/share/kibana/data</em></p><p><em>chown -R kibana:kibana /usr/share/kibana</em></p><p><em>Install the Wazuh Kibana plugin.</em></p><p><em>cd /usr/share/kibana</em></p><p><em>sudo -u kibana /usr/share/kibana/bin/kibana-plugin install </em><a href="https://packages.wazuh.com/4.x/ui/kibana/wazuh_kibana-4.5.4_7.17.13-1.zip"><em>https://packages.wazuh.com/4.x/ui/kibana/wazuh_kibana-4.5.4_7.17.13-1.zip</em></a></p><p>Link Kibana’s socket to privileged port 443:</p><p><em>setcap ‘cap_net_bind_service=+ep’ /usr/share/kibana/node/bin/node</em></p><h4>Enable and start the Kibana service:</h4><p>Now before enabling the Kibana, stop Elasticsearch and filebeat</p><p><em>systemctl stop elasticsearch</em></p><p><em>systemctl stop filebeat</em></p><p><em>systemctl daemon-reload</em></p><p><em>systemctl enable kibana</em></p><p><em>systemctl start kibana</em></p><p>Now after starting the Kibana, start Elasticsearch and filebeat</p><p><em>systemctl start elasticsearch</em></p><p><em>systemctl start filebeat</em></p><h3>Deployment of Agents:</h3><p>Go to the home page of Wazuh Manager, Click on the Modules Dropdown Menu, Click on the Agents Button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*i5Zx--4cKEgic_iE" /></figure><p>Click on the Deploy new agent button</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tUmDp6rwIz8_hVM-" /></figure><p>Here enter all the relevant details</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2e1Ne6MdVAEwRHwc" /></figure><p>In step 6 of Install and enroll the agent, copy the command and if installing on</p><p><strong>Linux/MacOS : paste the command in terminal and let it install</strong></p><p><strong>Windows: paste in power shell and let it install</strong></p><p>In step 7 start the agent from terminal/powershell</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jURkUXaMiDZNhl82" /></figure><h3>Notes of agent deployment:</h3><p>Wazuh agents needs 2 ports to work from wazuh server side</p><p>Port 1515 for enrollment</p><p>Port 1514 for connection establishment</p><p>If the agent is installed on the system but does not show on the wazuh manger, it means the wazuh server side ports are not open, make sure they are open and restart the agent</p><p>Sudo systemctl restart wazuh-agent</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9yNraRPru0loRsen" /></figure><p>In case using AWS(wazuh server), open 1515 and 1514 ports and also whitelist the IPs of the machines where agents are installed and then restart the agent.</p><p><em>Sudo systemctl restart wazuh-agent</em></p><p><strong>/var/ossec/logs/ossec.log</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ded09910c7aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>