<?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 Aishat Olayinka Yusuf on Medium]]></title>
        <description><![CDATA[Stories by Aishat Olayinka Yusuf on Medium]]></description>
        <link>https://medium.com/@nanaaisha1030?source=rss-234a77c1a817------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vNUtnkucN0HXYuxTsQ1Hkw.png</url>
            <title>Stories by Aishat Olayinka Yusuf on Medium</title>
            <link>https://medium.com/@nanaaisha1030?source=rss-234a77c1a817------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 23:09:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nanaaisha1030/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[Designing and Implementing an Enterprise Security Operations Center Using Microsoft Sentinel]]></title>
            <link>https://medium.com/@nanaaisha1030/designing-and-implementing-an-enterprise-security-operations-center-using-microsoft-sentinel-1d08d6ff04de?source=rss-234a77c1a817------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d08d6ff04de</guid>
            <category><![CDATA[windows]]></category>
            <category><![CDATA[threat-hunting]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Aishat Olayinka Yusuf]]></dc:creator>
            <pubDate>Wed, 15 Jul 2026 23:03:32 GMT</pubDate>
            <atom:updated>2026-07-15T23:04:49.957Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Security Engineering Case Study of Apex Digital Finance Ltd. Kigali, Rwanda.</h4><h3>Executive Summary</h3><p>As cyber threats continue to evolve, organizations require centralized security monitoring to detect, investigate, and respond to threats effectively. This project documents the design and implementation of a cloud-native Security Operations Center (SOC) for Apex Digital Finance Ltd. a financial services organization headquartered in Kigali, Rwanda.</p><p>As the Security Engineer leading this implementation, my objective was to deploy Microsoft Sentinel as the organization’s centralized Security Information and Event Management (SIEM) platform. The solution integrates Microsoft Sentinel, Azure Log Analytics Workspace, Azure Arc, Azure Monitor Agent, Data Collection Rules (DCRs), and Sysmon to provide centralized log collection, enhanced endpoint visibility, and improved security monitoring.</p><p>This guide presents the complete implementation process from provisioning the Azure environment to onboarding endpoints, validating log ingestion, and documenting lessons learned. Although implemented in a controlled lab environment, the deployment methodology reflects enterprise best practices and demonstrates how Microsoft Sentinel can be used to build a scalable and modern Security Operations Center.</p><blockquote>Disclaimer: Apex Digital Finance Ltd. is a fictional organization created solely for this implementation case study. All Azure resources, configurations, deployment procedures, PowerShell commands, KQL queries, troubleshooting activities, and validations documented in this guide were performed by the author in a Microsoft Azure laboratory environment for educational purposes. While the business scenario is fictional, the technical implementation accurately reflects a real Microsoft Sentinel deployment.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z8i8z2OQdI2pRK1PmEcSoA.jpeg" /><figcaption><em>Microsoft Sentinel Overview</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J7f1_WEGcSblIDYXbl1RsQ.png" /><figcaption>High-level architecture of the enterprise Security Operations Center implemented for Apex Digital Finance Ltd.</figcaption></figure><h3>Organization Background</h3><p>Apex Digital Finance Ltd. is a financial service company headquartered in Kigali, Rwanda, providing digital banking and payment solutions to businesses and individual customers across East Africa.</p><p>As the organization expanded its digital services, the volume of transactions, endpoints, and cloud resources increased significantly. However, its cybersecurity capabilities did not evolve at the same pace, resulting in limited visibility into security events and increasing operational risk.</p><p>The organization relied primarily on Microsoft technologies, including Windows endpoints and Microsoft Azure, making Microsoft Sentinel a natural choice for implementing a centralized Security Operations Center (SOC).</p><p>As the newly appointed Security Engineer, I was tasked with designing and deploying the organization’s first enterprise SOC to improve security visibility, strengthen threat detection capabilities, and establish a foundation for effective incident response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NW8u-SiHhXiA-u1ikekmww.jpeg" /><figcaption>Dedicated Azure Resource Group provisioned to host the organization’s Security Operations Center infrastructure.</figcaption></figure><h3>Business Problem</h3><p>As Apex Digital Finance Ltd. expanded its digital services, its cybersecurity capabilities did not grow at the same pace. Security events were generated across multiple Windows endpoints but remained isolated, making monitoring and investigations inefficient.</p><p>Without a centralized Security Operations Center (SOC), the organization lacked real-time visibility into its security environment, increasing the risk of undetected cyber threats.</p><h4>Key Challenges</h4><ol><li>No centralized log collection.</li><li>Limited endpoint visibility.</li><li>Manual incident investigations.</li><li>No centralized alerting or threat detection.</li><li>No proactive threat hunting capability.</li></ol><h4>Business Risks</h4><p>These gaps exposed the organization to several security risks, including:</p><ol><li>Delayed detection of ransomware.</li><li>Credential compromise and unauthorized access.</li><li>Insider threats.</li><li>Prolonged incident response.</li><li>Increased operational and compliance risk.</li></ol><p>To address these challenges, the organization approved the implementation of a centralized Security Operations Center using Microsoft Sentinel to improve visibility, accelerate threat detection, and strengthen its overall security posture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/421/1*vQVsrVpDsrgUHYRnypFskA.jpeg" /><figcaption>Prior to implementation, security events were stored locally on individual endpoints, limiting centralized visibility.</figcaption></figure><h3><strong>Project Objectives</strong></h3><p>The primary objective of this project was to design and implement a centralized Security Operations Center (SOC) that would provide Apex Digital Finance Ltd. with improved visibility into its security environment and establish a foundation for effective threat detection and incident response.</p><p>To achieve this, the project focused on the following objectives:</p><ul><li>Deploy Microsoft Sentinel as the organization’s centralized SIEM platform.</li><li>Centralize Windows and Sysmon event logs using Azure Monitor Agent and Log Analytics Workspace.</li><li>Improve endpoint visibility through enhanced telemetry collection.</li><li>Enable real-time monitoring and security event analysis.</li><li>Establish a scalable architecture that supports future threat hunting, automation, and incident response.</li><li>Build an enterprise-ready SOC capable of supporting the organization’s continued growth.</li></ul><h3><strong>Project Scope</strong></h3><p>This project focused on designing and implementing the foundational components of an enterprise Security Operations Center (SOC) for Apex Digital Finance Ltd. using Microsoft Azure security services.</p><ul><li>Provisioning Microsoft Azure resources.</li><li>Deploying Microsoft Sentinel.</li><li>Creating a Log Analytics Workspace.</li><li>Connecting Windows endpoints using Azure Arc.</li><li>Installing and configuring Sysmon.</li><li>Deploying Azure Monitor Agent (AMA).</li><li>Configuring Data Collection Rules (DCRs).</li><li>Collecting Windows Event Logs and Sysmon telemetry.</li><li>Validating log ingestion into Microsoft Sentinel.</li></ul><h3><strong>Solution Architecture</strong></h3><p>The Security Operations Center (SOC) was designed using Microsoft Azure native security services to provide centralized log collection, security monitoring, and threat visibility across the organization’s Windows environment.</p><p>The architecture follows a layered approach where endpoint telemetry is collected, securely transmitted to Azure, processed within a centralized Log Analytics Workspace, and analyzed by Microsoft Sentinel for security monitoring and future incident response.</p><p>The overall architecture is illustrated below.</p><h4><strong>Architecture Components</strong></h4><p><strong>Windows Endpoint</strong></p><p>The Windows endpoint represents the organization’s workstation where user activities and security events are generated. It serves as the primary source of security telemetry.</p><p><strong>Sysmon</strong></p><p>Sysmon extends the default Windows logging capabilities by generating detailed security events, including process creation, network connections, driver loading, registry modifications, and file creation activities. This enhanced visibility significantly improves threat detection capabilities.</p><p><strong>Azure Arc</strong></p><p>Azure Arc enables non-Azure machines to be managed as Azure resources. By onboarding the Windows endpoint to Azure Arc, the organization can centrally deploy extensions, enforce configurations, and manage security monitoring directly from the Azure Portal.</p><p><strong>Azure Monitor Agent (AMA)</strong></p><p>Azure Monitor Agent is responsible for collecting Windows Event Logs and Sysmon telemetry from the endpoint and securely transmitting them to Azure.</p><p><strong>Data Collection Rules (DCR)</strong></p><p>Data Collection Rules define exactly which logs should be collected and forwarded to Azure. This ensures that only relevant security events are ingested, reducing unnecessary data collection and optimizing storage costs.</p><p><strong>Log Analytics Workspace</strong></p><p>The Log Analytics Workspace acts as the central repository where collected logs are stored, indexed, and made available for querying using Kusto Query Language (KQL).</p><p><strong>Microsoft Sentinel</strong></p><p>Microsoft Sentinel serves as the organization’s cloud-native Security Information and Event Management (SIEM) platform. It provides centralized visibility into security events and forms the foundation for future threat detection, investigations, incident response, and threat hunting.</p><h3>Implementation</h3><h4>Step 1: Provision a Microsoft Azure Environment</h4><p><strong>Objective: </strong>Provision a Microsoft Azure environment to host the Security Operations Center (SOC) infrastructure.</p><p><strong>Procedure</strong></p><ol><li>Navigate to <a href="https://azure.microsoft.com/"><strong>https://azure.microsoft.com</strong></a> and create a Microsoft Azure account (or sign in with an existing Microsoft account).</li><li>Activate the Azure subscription and access the Azure Portal at <a href="https://portal.azure.com/"><strong>https://portal.azure.com</strong></a>.</li><li>Confirm that the subscription is active before proceeding with resource deployment.</li></ol><p>Outcome: Verify that the Azure Portal loads successfully and the active subscription is visible under<strong> </strong>Subscriptions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*brc4hiUgAgEJ80Fn5BBzng.jpeg" /><figcaption><strong><em>Microsoft Azure Portal</em></strong></figcaption></figure><h4>Step 2: Create a Resource Group</h4><p><strong>Objective</strong>: Create a dedicated Resource Group to logically organize and manage all resources required for the Security Operations Center (SOC) deployment.</p><p><strong>Procedure</strong></p><ol><li>Sign in to the Azure Portal by navigating to <a href="https://portal.azure.com/">https://portal.azure.com</a>.</li><li>Search for Resource Groups using the Azure search bar and select Resource Groups.</li><li>Click Create.</li><li>Select the active Azure Subscription.</li><li>Enter RG-EnterpriseSOC-Lab as the Resource Group name.</li><li>Set the region to East US.</li><li>Select Review + Create, then click Create to provision the Resource Group.</li></ol><p><strong>Outcome:</strong> The Resource Group RG-EnterpriseSOC-Lab was successfully created. This Resource Group serves as the centralized container for all Azure resources deployed throughout the implementation, making resource management, access control, and future maintenance significantly easier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/814/1*_IhVO6dluggLDBpbAdz8oA.jpeg" /><figcaption><em>Resource Group Configuration</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NW8u-SiHhXiA-u1ikekmww.jpeg" /><figcaption><em>Resource Group Successfully Deployed</em></figcaption></figure><h4>Step 3: Create a Log Analytics Workspace</h4><p><strong>Objective:</strong> Provision a Log Analytics Workspace to serve as the central repository for collecting, storing, and querying security telemetry generated across the organization’s environment.</p><p>Microsoft Sentinel relies on a Log Analytics Workspace to ingest and analyze security data. Without it, Sentinel cannot collect logs or perform threat detection.</p><p><strong>Procedure</strong></p><ol><li>From the Azure Portal, search for Log Analytics Workspaces and select Log Analytics Workspaces.</li><li>Click Create.</li><li>Select the previously created Resource Group (RG-EnterpriseSOC-Lab).</li><li>Enter LAW-EnterpriseSOC as the workspace name.</li><li>Select East US as the deployment region.</li><li>Leave the remaining settings at their default values.</li><li>Select Review + Create, then click Create.</li></ol><p><strong>Outcome:</strong> The Log Analytics Workspace was successfully deployed. This workspace now serves as the centralized repository for Windows Event Logs, Sysmon telemetry, and all future security data collected throughout the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/729/1*AVmjGgMOELYIIuTjxtPeUg.jpeg" /><figcaption><em>Log Analytics Workspace Configuration</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*83mDwdtKZK2mlWKiuXPOWw.jpeg" /><figcaption><em>Log Analytics Workspace Successfully Deployed</em></figcaption></figure><h4>Step 4: Deploy Microsoft Sentinel</h4><p><strong>Objective:</strong> Deploy Microsoft Sentinel as the organization’s centralized Security Information and Event Management (SIEM) platform.</p><p>Microsoft Sentinel provides the capability to collect, analyze, correlate, and investigate security events from multiple data sources, enabling centralized security monitoring across the enterprise.</p><p><strong>Procedure</strong></p><ol><li>From the Azure Portal, search for Microsoft Sentinel and select Microsoft Sentinel.</li><li>Click Create.</li><li>Select the previously created Log Analytics Workspace (LAW-EnterpriseSOC).</li><li>Click Add to enable Microsoft Sentinel on the workspace.</li><li>Wait for the deployment to complete.</li></ol><p><strong>Outcome:</strong> Microsoft Sentinel was successfully deployed and configured to use the Log Analytics Workspace as its primary data repository. The Security Operations Center was now ready to begin onboarding endpoints and collecting security telemetry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0y5n1YLVCKbMiJYCo2PdWQ.jpeg" /><figcaption><em>Microsoft Sentinel Overview page after successful deployment</em></figcaption></figure><h4>Step 5: Onboard the Windows Endpoint to Azure Arc</h4><p><strong>Objective:</strong> Onboard the organization’s Windows endpoint to Azure Arc to enable centralized management and facilitate the deployment of Azure services, including Azure Monitor Agent.</p><p>Azure Arc allows machines hosted outside Microsoft Azure to be managed as native Azure resources, extending Azure’s governance, monitoring, and security capabilities to hybrid environments.</p><p><strong>Procedure</strong></p><ol><li>From the Azure Portal, search for Azure Arc and select Azure Arc.</li><li>Navigate to Machines and click Add/Create.</li><li>Select Add a machine, then choose Generate script.</li><li>Configure the onboarding script by selecting the appropriate Azure Subscription, RG-EnterpriseSOC-Lab as the Resource Group, East US as the Region, and Windows as the operating system.</li><li>Generate and copy the PowerShell onboarding script.</li><li>On the Windows endpoint, open Windows PowerShell as Administrator.</li><li>Paste and execute the generated onboarding script.</li><li>Wait for the installation and registration process to complete successfully.</li><li>Return to the Azure Portal and verify that the Windows endpoint appears under Azure Arc- Machines with a Connected status.</li></ol><p><strong>Outcome:</strong> The Windows endpoint was successfully onboarded to Azure Arc and became manageable as an Azure resource. This provided the foundation for deploying Azure Monitor Agent and centralizing endpoint telemetry within Microsoft Sentinel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5VE-0MLElG2fRgQJhpKqmw.jpeg" /><figcaption><em>PowerShell onboarding script generated by Azure Arc.</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*vO3DBmH5xK70phAHG-Lbjw.jpeg" /><figcaption><em>Windows PowerShell executing the Azure Arc onboarding script.</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/1*UKYWOD0j9FzLdlVGFwZJ6w.jpeg" /><figcaption><em>Windows Endpoint Successfully Connected</em></figcaption></figure><h4>Step 6: Install and Configure Sysmon</h4><p><strong>Objective:</strong> Deploy Sysmon (System Monitor) on the Windows endpoint to generate enhanced security telemetry for endpoint monitoring and threat detection.</p><p>Unlike native Windows Event Logs, Sysmon provides detailed information about process creation, network connections, registry modifications, file creation, driver loading, and other security-relevant activities. This additional telemetry significantly improves detection capabilities within Microsoft Sentinel.</p><p><strong>Procedure</strong></p><ol><li>Download Sysmon from the Microsoft Sysinternals Suite.</li><li>Extract the downloaded archive to a local directory (C:\Sysmon).</li><li>Copy the Sysmon configuration file (sysmonconfig.xml) into the same directory.</li><li>Open Windows PowerShell as Administrator.</li><li>Navigate to the Sysmon installation directory</li></ol><pre>cd C:\Sysmon</pre><p>6. Install Sysmon using the configuration file.</p><pre>.\Sysmon64.exe -i sysmonconfig.xml</pre><p>7. Accept the Sysinternals license agreement when prompted.</p><p><strong>Outcome:</strong> Sysmon was successfully installed and configured on the Windows endpoint. The endpoint now generates enhanced security telemetry, providing detailed endpoint visibility that will later be collected and analyzed by Microsoft Sentinel.</p><h4>Step 7: Deploy Azure Monitor Agent (AMA)</h4><p><strong>Objective: </strong>Deploy Azure Monitor Agent (AMA) to the Azure Arc-connected Windows endpoint to enable the collection and transmission of Windows Event Logs and Sysmon telemetry to Azure.</p><p>Azure Monitor Agent is Microsoft’s modern data collection agent and serves as the bridge between the endpoint and the Log Analytics Workspace.</p><p><strong>Procedure</strong></p><ol><li>From the Azure Portal, navigate to Azure Arc and select Machines.</li><li>Select the onboarded Windows endpoint.</li><li>From the left navigation pane, select Extensions.</li><li>Click Add.</li><li>Search for Azure Monitor Windows Agent.</li><li>Select the extension and click Next.</li><li>Leave the default configuration unchanged.</li><li>Click Review + Create, then select Create to begin the deployment.</li><li>Wait for the extension deployment to complete successfully.</li></ol><p><strong>Outcome:</strong> Azure Monitor Agent was successfully deployed to the Windows endpoint through Azure Arc. The endpoint is now capable of forwarding Windows Event Logs and Sysmon telemetry once Data Collection Rules are configured.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BBsdo4t6o-EwgZbzvoNBfw.jpeg" /><figcaption><em>Azure Monitor Agent Successfully Installed</em></figcaption></figure><h4>Step 8: Configure Data Collection Rules (DCR)</h4><p><strong>Objective:</strong> Create and configure a Data Collection Rule (DCR) to define which security events should be collected from the Windows endpoint and forwarded to the Log Analytics Workspace.</p><p>Data Collection Rules provide centralized control over log collection, ensuring that only relevant security telemetry is ingested into Microsoft Sentinel.</p><p><strong>Procedure</strong></p><p>Create the Data Collection Rule</p><ol><li>From the Azure Portal, search for Data Collection Rules.</li><li>Click Create.</li><li>Configure the Data Collection Rule using the following settings:</li></ol><ul><li>Name: DCR-Windows11-Sentinel</li><li>Resource Group: RG-EnterpriseSOC-Lab</li><li>Region: East US</li></ul><ol><li>Click Next until you reach the Resources page.</li><li>Select Add Resources.</li><li>Choose the Azure Arc-connected Windows endpoint.</li><li>Click Apply.</li></ol><p><strong>Configure Windows Event Logs</strong></p><ol><li>Navigate to the Collect and Deliver tab.</li><li>Click Add Data Source.</li><li>Select Windows Event Logs.</li><li>Add the following event channels:</li></ol><pre>Security<br>System<br>Application</pre><p><strong>Configure Sysmon Event Collection</strong></p><ol><li>Add another Windows Event Logs data source.</li><li>Enter the following XPath query:</li></ol><pre>Microsoft-Windows-Sysmon/Operational!*</pre><p><strong>Configure Destination</strong></p><ol><li>Under Destination, select Azure Monitor Logs.</li><li>Choose the previously created Log Analytics Workspace (LAW-EnterpriseSOC).</li><li>Click Review + Create.</li><li>Select Create to deploy the Data Collection Rule.</li></ol><p><strong>Outcome:</strong> The Data Collection Rule was successfully deployed and associated with the Azure Arc-connected Windows endpoint. Windows Event Logs and Sysmon telemetry are now configured to be forwarded to the Log Analytics Workspace for analysis within Microsoft Sentinel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nt0dCWFdnVIXK40jJL80Nw.jpeg" /><figcaption><em>Data Collection Rule configuration page.</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Aou3wkGf_IUu0EmJHXAfRg.jpeg" /><figcaption>Windows Event Log Configuration</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m-ITE2Wiksy_jC0c0LhXxA.jpeg" /><figcaption>Sysmon Event Configuration</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4HJGlr01iZJZfvxkwBsxMA.jpeg" /><figcaption>Data Collection Rule Successfully Created</figcaption></figure><h4>Step 9: Validate Log Ingestion into Microsoft Sentinel</h4><p><strong>Objective:</strong> Validate that Windows Event Logs and Sysmon telemetry are successfully collected from the Windows endpoint and ingested into Microsoft Sentinel through the Log Analytics Workspace.</p><p>Successful log ingestion confirms that the Security Operations Center has been correctly configured and is ready for threat detection and incident monitoring.</p><p><strong>Procedure</strong></p><p><strong>Verify Event Generation on the Windows Endpoint</strong></p><p>Before validating Microsoft Sentinel, I first confirmed that the Windows endpoint was actively generating both Windows Event Logs and Sysmon events.</p><p><strong>To verify Sysmon events, I executed the following PowerShell command:</strong></p><pre>Get-WinEvent -LogName &quot;Microsoft-Windows-Sysmon/Operational&quot; -MaxEvents 5</pre><p>The command returned recent Sysmon events, confirming that Sysmon had been successfully installed and was actively monitoring endpoint activity.</p><p><strong>Validate Windows Event Logs</strong></p><p>From the Microsoft Sentinel Logs page, I executed the following Kusto Query Language (KQL) query to verify that Windows Event Logs were successfully reaching the Log Analytics Workspace.</p><pre>Event<br>| where TimeGenerated &gt; ago(30m)<br>| order by TimeGenerated desc</pre><p>The query returned Windows Security, System, and Application events generated by the onboarded endpoint.</p><p><strong>Validate Sysmon Logs</strong></p><p>To confirm that Sysmon telemetry was also being collected successfully, I executed the following query.</p><pre>Event<br>| where EventLog == &quot;Microsoft-Windows-Sysmon/Operational&quot;<br>| order by TimeGenerated desc</pre><p>The query successfully returned Sysmon Operational events, confirming that endpoint telemetry was flowing correctly into Microsoft Sentinel.</p><p><strong>Outcome:</strong> Both Windows Event Logs and Sysmon telemetry were successfully ingested into Microsoft Sentinel. This confirmed that the endpoint monitoring pipeline from Sysmon and Windows Event Logs through Azure Monitor Agent, Azure Arc, Data Collection Rules, and the Log Analytics Workspace was functioning as expected.</p><p>The Security Operations Center was now fully operational and ready for security monitoring, threat detection, and incident response activities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/712/1*4r2Yewgy2kxPx1PLh5uNNw.jpeg" /><figcaption>Sysmon Event Verification</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tGbCSVgPr6-S_T6ehf6c0w.jpeg" /><figcaption>Windows Event Logs in Microsoft Sentinel</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lK4cNtJbHic2mROJpTHxpQ.jpeg" /><figcaption>Sysmon Events in Microsoft Sentinel</figcaption></figure><h4>Validation</h4><p>Following the implementation, end-to-end validation was performed to confirm that the Security Operations Center was functioning as expected.</p><p>The validation confirmed:</p><ul><li>Successful Azure Arc onboarding.</li><li>Successful Azure Monitor Agent deployment.</li><li>Successful Windows Event Log ingestion.</li><li>Successful Sysmon telemetry collection.</li><li>Successful log ingestion into Microsoft Sentinel.</li><li>Successful execution of KQL queries against collected security events.</li></ul><p>To provide a complete demonstration of the deployed environment, a walkthrough video was created showcasing the Microsoft Sentinel workspace, deployed architecture, connected resources, Data Collection Rules, and successful log ingestion.</p><p><strong>Video Demonstration</strong></p><p>A complete walkthrough of the deployed SOC environment can be viewed here: <a href="https://youtu.be/FFpa01xFL9o">Microsoft Sentinel Walkthrough</a></p><h4>Challenges Encountered and Resolution</h4><p>No enterprise security deployment is completed without challenges. Throughout this implementation, several technical issues were encountered that required investigation and troubleshooting before the Security Operations Center (SOC) became fully operational. Resolving these challenges provided valuable practical experience and reinforced the importance of systematic troubleshooting during enterprise deployments.</p><h4><strong>Challenge 1: Azure Monitor Agent Was Not Installe</strong>d Successfully</h4><p><strong>Issue:</strong> After deploying the Azure Monitor Agent (AMA) through Azure Arc, the extension did not appear on the Windows endpoint and no telemetry was being forwarded to Microsoft Sentinel.</p><p><strong>Root Cause:</strong> The Windows virtual machine had previously been suspended, which affected the Azure Monitor Agent deployment while Azure Arc remained connected.</p><p><strong>Resolution:</strong> To resolve the issue, the existing Azure Monitor Agent deployment was removed and redeployed through Azure Arc. Once the deployment completed successfully, the extension appeared with a Succeeded provisioning state.</p><p><strong>Outcome:</strong> The Windows endpoint successfully established communication with Azure Monitor and became capable of forwarding security telemetry.</p><h4>Challenge 2: Sysmon Logs Were Not Appearing in Microsoft Sentinel</h4><p><strong>Issue: </strong>Although Sysmon was successfully installed on the Windows endpoint, no Sysmon events were visible within Microsoft Sentinel.</p><p><strong>Root Cause:</strong> The Data Collection Rule responsible for collecting Sysmon Operational events had not yet been configured.</p><p><strong>Resolution:</strong> A dedicated Data Collection Rule (DCR-Sysmon-Sentinel) was created and associated with the Azure Arc-connected machine. The Sysmon Operational log channel was then configured using the appropriate XPath query before being linked to the Log Analytics Workspace.</p><p><strong>Outcome:</strong> Sysmon Operational events were successfully ingested into Microsoft Sentinel and became available for analysis using Kusto Query Language (KQL).</p><h4>Challenge 3: Azure Monitor Agent Provisioning Delay</h4><p><strong>Issue:</strong> During deployment, the Azure Monitor Agent remained in a Creating state for an extended period, giving the impression that the deployment had stalled.</p><p><strong>Root Cause:</strong> The extension installation process was still executing in the background while Azure completed provisioning.</p><p><strong>Resolution:</strong> The Azure Connected Machine Agent logs were reviewed to confirm that communication with Azure remained healthy. After allowing the deployment to complete naturally, the extension status changed to Succeeded without requiring further intervention.</p><p><strong>Outcome:</strong> The Azure Monitor Agent was successfully deployed and became fully operational.</p><h4>Lessons Learned</h4><p>Implementing Microsoft Sentinel in a hybrid environment provided valuable practical experience beyond simply deploying Azure resources. Throughout the project, several key lessons emerged that reinforced both technical and operational best practices for enterprise SOC deployments.</p><ol><li><strong>Careful planning simplifies implementation</strong></li></ol><p>A successful SIEM deployment begins long before the first resource is created. Clearly defining the architecture, log sources, resource organization, and monitoring requirements significantly reduces deployment complexity and improves long-term maintainability.</p><p><strong>2. Azure Arc is essential for hybrid environments</strong></p><p>Azure Arc extends Azure management capabilities beyond the cloud by enabling on-premises and non-Azure machines to be managed as native Azure resources. Its successful deployment formed the foundation for the entire monitoring solution.</p><p><strong>3. Endpoint visibility depends on high-quality telemetry</strong></p><p>Native Windows Event Logs provide useful operating system information, but Sysmon significantly enhances endpoint visibility by capturing detailed process, network, registry, and file activity. Combining both sources provides a richer dataset for security monitoring and investigations.</p><p><strong>4. Data Collection Rules should be carefully designed</strong></p><p>Properly configured Data Collection Rules ensure that only relevant security events are collected. This improves visibility while reducing unnecessary data ingestion and storage costs.</p><p><strong>5. Validation should never be overlooked</strong></p><p>Completing the deployment is only one part of the implementation process. Verifying endpoint connectivity, agent health, log collection, and successful ingestion into Microsoft Sentinel is equally important to ensure that the solution is operating as intended.</p><p><strong>6. Troubleshooting is a critical engineering skill</strong></p><p>The challenges encountered during this implementation reinforced the importance of structured troubleshooting. Reviewing logs, validating configurations, understanding component dependencies, and resolving issues methodically proved just as valuable as the deployment itself.</p><p>Overall, this project strengthened my understanding of enterprise SIEM implementation and provided hands-on experience with Microsoft Sentinel, Azure Arc, Azure Monitor Agent, Sysmon, and centralized security monitoring within a hybrid environment.</p><h4>Future Enhancements</h4><p>While the implemented Security Operations Center provides centralized security monitoring capabilities, several enhancements can further improve the organization’s detection and response maturity.</p><p><strong>Integrate Microsoft Defender XDR</strong></p><p>Integrating Microsoft Defender XDR would provide unified visibility across endpoints, identities, email, and cloud workloads, enabling faster investigation through correlated security incidents.</p><p><strong>Implement Security Automation</strong></p><p>Automation Rules and Logic Apps can be introduced to automate alert enrichment, incident creation, analyst notifications, and predefined response actions, reducing manual effort and improving response times.</p><p><strong>Expand Threat Detection Capabilities</strong></p><p>Future work will focus on developing advanced Analytics Rules, proactive threat hunting using Kusto Query Language (KQL), and onboarding additional enterprise data sources to strengthen detection coverage across the organization.</p><p>These enhancements will transform the current foundational SOC implementation into a more mature, automated, and enterprise-ready security operations capability.</p><h4><strong>Conclusion</strong></h4><p>This project demonstrated the end-to-end deployment of a cloud-native Security Operations Center (SOC) using Microsoft Sentinel. By integrating Azure Arc, Azure Monitor Agent, Sysmon, and Data Collection Rules, Apex Digital Finance Ltd. established centralized security visibility and a scalable SIEM platform capable of supporting modern security operations.</p><p>Although implemented in a controlled lab environment, the architecture, deployment methodology, and operational workflows closely reflect enterprise best practices. The solution provides a strong foundation for future enhancements, including advanced threat detection, security automation, and extended detection and response (XDR) capabilities.</p><p>Beyond the technical implementation, this project strengthened my practical understanding of enterprise SOC deployment, hybrid cloud monitoring, and Microsoft security technologies, while reinforcing the importance of structured planning, validation, and troubleshooting in delivering effective security solutions.</p><p>Beyond this implementation, the SOC lab will be continuously used to develop and validate detection use cases, evaluate security controls, perform threat hunting, simulate cyberattacks, and strengthen overall Security Operations Center capabilities.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d08d6ff04de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Full System Compromise via Chained API Vulnerabilities - OpenVault Bank]]></title>
            <link>https://medium.com/@nanaaisha1030/full-system-compromise-via-chained-api-vulnerabilities-openvault-bank-c8980c901b93?source=rss-234a77c1a817------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8980c901b93</guid>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[web-app-security]]></category>
            <dc:creator><![CDATA[Aishat Olayinka Yusuf]]></dc:creator>
            <pubDate>Thu, 23 Apr 2026 20:53:31 GMT</pubDate>
            <atom:updated>2026-04-23T20:55:13.057Z</atom:updated>
            <content:encoded><![CDATA[<p>APIs are at the core of modern applications, especially in systems like banking where data needs to move quickly and securely between services. They make things efficient, scalable, and easy to integrate. But if security is not properly enforced, APIs can quickly become one of the weakest points in an application.</p><p>In this assessment, I tested the OpenVault Bank API, a deliberately vulnerable environment from APISec University, to understand how real-world API flaws can be discovered and chained together based on the OWASP Top 10 (2023). What started as a normal user session quickly escalated into full administrative control and unauthorized financial manipulation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kK13lwUtypkmraiRWY38_g.jpeg" /></figure><h3><strong>OWASP Vulnerabilities Exploited</strong></h3><ol><li><strong>API1:2023- </strong>Broken Object Level Authorization (BOLA)</li><li><strong>API2:2023- </strong>Broken Authentication</li><li><strong>API3:2023- </strong>Broken Object Property Level Authorization (BOPLA)</li><li><strong>API5:2023- </strong>Broken Function Level Authorization (BFLA)</li></ol><h3><strong>Attack Chain Analysis</strong></h3><p><strong>Step 1: Creating a Normal User Account</strong></p><p>I began the assessment by registering a new user account:</p><pre>POST {{baseUrl}}/api/v1/auth/register</pre><p>Using:</p><pre>{<br> &quot;email&quot;: &quot;user1@mail.com&quot;,<br> &quot;password&quot;: &quot;******&quot;<br> }</pre><p>The API successfully created the account and returned a JWT access token. This token immediately granted authenticated access as a standard customer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/1*27ptDPiJ3Fh_1Gn_gQUAHQ.jpeg" /></figure><p><strong>Step 2: Creating a Second Test User</strong></p><p>To validate how the system handles multiple accounts, I created a second user:</p><pre>{<br> &quot;email&quot;: &quot;user@mail.com&quot;,<br> &quot;password&quot;: &quot;******&quot;<br> }</pre><p>This also returned a valid access token. This token is what grants access to other endpoints, so at this point, I was operating strictly as a normal customer.</p><p><strong>Step 3: Testing Access to Transaction Details</strong></p><p><strong>OWASP API1:2023 -Broken Object Level Authorization (BOLA)</strong></p><p>Next, I wanted to see how well the API enforces ownership of resources. I started by viewing transactions tied to my account:</p><pre>GET {{baseUrl}}/api/v1/accounts/:account_id/transactions</pre><p>At this point, everything worked as expected. However, instead of stopping there, I changed the account_id from my own ID to another user’s ID.</p><p>Surprisingly, the API still returned valid transaction data of the other users.</p><p>I repeated this with multiple IDs (2002, 2003, 2005), and each time I was able to see transactions that did not belong to me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/955/1*dJ0pHvssNqMU_weYVxYRZA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/1*mFrL8TWixZMREMjVXE29Dg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/949/1*_jJSDcD3KM8wOsmRZm2_oQ.jpeg" /></figure><p>This clearly showed that the API was not verifying whether I actually owned the account I was requesting.</p><p><strong>Step 4: Accessing Other Users’ Account Details</strong></p><p>After confirming I could access transactions, I moved on to retrieving full account details:</p><pre>GET {{baseUrl}}/api/v1/accounts/:account_id</pre><p>By simply changing the account_id, I was able to view sensitive information belonging to other users, including account numbers, routing numbers, balances, credit limits, and even partial SSN data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/946/1*nuyAA8yb09MIiH5EyPQZgQ.jpeg" /></figure><p>At this point, it was clear that not only was authorization missing, but the API was also exposing far more data than necessary.</p><p><strong>OWASP API1:2023- Broken Object Level Authorization (BOLA)</strong></p><p><strong>OWASP API3:2023- Broken Object Property Level Authorization (BOPLA)</strong></p><p><strong>Step 5: Manipulating Account Balances (Critical Impact)</strong></p><p>This is where things became much more serious.</p><p>Since I could access other users’ accounts, I tested whether I could also modify them:</p><pre>PUT {{baseUrl}}/api/v1/accounts/:account_id</pre><p>I targeted account <strong>2002</strong> and changed the balance:</p><ul><li>From its original value → <strong>5,000,000</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/963/1*7fm1AV28eY40D0O_np7IlA.jpeg" /></figure><ul><li>Then increased it further → <strong>9,000,000</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*b1ILLDQm3r2yMY8_Ta50uQ.jpeg" /></figure><p>I repeated the same action on account <strong>2003</strong>, successfully setting its balance to <strong>9,000,000</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/943/1*yhMFOqTJb94h852IzqE3bA.jpeg" /></figure><p>All changes were accepted by the API and reflected immediately when I retrieved the account again.</p><p>This confirmed that I wasn’t just viewing data, I had full control over it.</p><p>At this point, the vulnerability escalates from data exposure to financial manipulation.</p><p><strong>OWASP API1:2023 — Broken Object Level Authorization (BOLA)</strong></p><p><strong>OWASP API3:2023 — Broken Object Property Level Authorization (BOPLA)</strong></p><p><strong>Step 6: Listing All Accounts</strong></p><p>I then called:</p><pre>GET {{baseUrl}}/api/v1/accounts</pre><p>Instead of limiting results to my own accounts, the API returned multiple accounts, further confirming weak access control.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/955/1*9pU_mhcUxpVhwRou-r3WdQ.jpeg" /></figure><p><strong>OWASP API1:2023- Broken Object Level Authorization (BOLA)</strong></p><p><strong>Step 7: Privilege Escalation via Profile Update</strong></p><p><strong>OWASP API3:2023- Broken Object Property Level Authorization (BOPLA)</strong></p><p>Next, I explored whether I could modify my own profile:</p><pre>PUT {{baseUrl}}/api/v1/profile</pre><p>In the body of the request, I included:</p><pre>{<br>&quot;role&quot;: &quot;admin&quot;<br>}</pre><p>The request returned a success response. To confirm, I fetched my profile again and my role had been updated from customer to admin. There were no restrictions preventing me from modifying a sensitive field like role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/954/1*VXqu9Z8wovxZTG7zqzSCMQ.jpeg" /></figure><p>This is a classic case of mass assignment leading to privilege escalation.</p><p><strong>Step 8: Accessing Admin-Only Endpoints</strong></p><p>With my new privileges, I attempted to access admin endpoints:</p><pre>GET {{baseUrl}}/api/v1/admin/accounts</pre><p>The API returned a full list of accounts without any restriction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*vwVAhwxF4JEfUR7it0NcpQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/963/1*RIA12HmU2jZtbBqNIsT2MA.jpeg" /></figure><p>This confirmed that the system trusted my modified role without performing deeper authorization checks.</p><p><strong>OWASP API5:2023- Broken Function Level Authorization (BFLA)</strong></p><p><strong>Step 9: Retrieving All Users and Hashed Passwords</strong></p><p>Finally, I accessed:</p><pre>GET {{baseUrl}}/api/v1/admin/users</pre><p>This returned a complete list of users, including:</p><ul><li>Email addresses</li><li>Full names</li><li>Roles</li><li>Hashed passwords</li></ul><pre>[<br>    {<br>        &quot;id&quot;: 1001,<br>        &quot;email&quot;: &quot;alice@ovb.com&quot;,<br>        &quot;full_name&quot;: &quot;Alice Johnson&quot;,<br>        &quot;role&quot;: &quot;customer&quot;,<br>        &quot;hashed_password&quot;: &quot;[REDACTED]&quot;,<br>        &quot;created_at&quot;: &quot;2026-04-23T07:24:18.254722&quot;<br>    },<br>    {<br>        &quot;id&quot;: 1002,<br>        &quot;email&quot;: &quot;bob@ovb.com&quot;,<br>        &quot;full_name&quot;: &quot;Bob Smith&quot;,<br>        &quot;role&quot;: &quot;customer&quot;,<br>        &quot;hashed_password&quot;: &quot;[REDACTED]&quot;,<br>        &quot;created_at&quot;: &quot;2026-04-23T07:24:18.254731&quot;<br>    },<br>    {<br>        &quot;id&quot;: 1003,<br>        &quot;email&quot;: &quot;carol@ovb.com&quot;,<br>        &quot;full_name&quot;: &quot;Carol Williams&quot;,<br>        &quot;role&quot;: &quot;customer&quot;,<br>        &quot;hashed_password&quot;: &quot;[REDACTED]&quot;,<br>        &quot;created_at&quot;: &quot;2026-04-23T07:24:18.254732&quot;<br>    },<br>    {<br>        &quot;id&quot;: 1004,<br>        &quot;email&quot;: &quot;admin@ovb.com&quot;,<br>        &quot;full_name&quot;: &quot;System Admin&quot;,<br>        &quot;role&quot;: &quot;admin&quot;,<br>        &quot;hashed_password&quot;: &quot;[REDACTED]&quot;,<br>        &quot;created_at&quot;: &quot;2026-04-23T07:24:18.254733&quot;<br>    },<br>    {<br>        &quot;id&quot;: 1005,<br>        &quot;email&quot;: &quot;user@mail.com&quot;,<br>        &quot;full_name&quot;: &quot;User Me&quot;,<br>        &quot;role&quot;: &quot;admin&quot;,<br>        &quot;hashed_password&quot;: &quot;[REDACTED]&quot;,<br>        &quot;created_at&quot;: &quot;2026-04-23T09:20:40.300230&quot;<br>    },<br>    {<br>        &quot;id&quot;: 1006,<br>        &quot;email&quot;: &quot;user1@mail.com&quot;,<br>        &quot;full_name&quot;: &quot;User Me&quot;,<br>        &quot;role&quot;: &quot;customer&quot;,<br>        &quot;hashed_password&quot;: &quot;[REDACTED]&quot;,<br>        &quot;created_at&quot;: &quot;2026-04-23T09:26:40.674028&quot;<br>    }<br>]</pre><p>At this stage, the entire system was effectively exposed.</p><p><strong>OWASP API5:2023- Broken Function Level Authorization (BFLA)</strong></p><p><strong>OWASP API2:2023- Broken Authentication</strong></p><h3><strong>Impact</strong></h3><p>By chaining these vulnerabilities together, I was able to:</p><ul><li>Access other users’ financial data</li><li>Modify account balances arbitrarily</li><li>Escalate privileges from a “customer” to “admin”</li><li>Retrieve all users and hashed passwords</li><li>Achieve full control over the system</li></ul><h3><strong>Conclusion</strong></h3><p>This exercise clearly shows how dangerous poorly secured APIs can be. What started as a simple test of endpoints quickly turned into a full system compromise. The lack of proper authorization checks, combined with excessive data exposure and insecure input handling, made it possible to move from a normal user to full administrative control.</p><h3><strong>Recommendations</strong></h3><ul><li>Enforce strict object-level authorization checks</li><li>Prevent modification of sensitive fields like ‘role’</li><li>Implement proper role-based access control (RBAC)</li><li>Limit sensitive data exposure in API responses</li><li>Validate and whitelist user inputs</li><li>Monitor and log suspicious activity</li></ul><p>This wasn’t just about finding bugs, it really showed me how small gaps in API security can quickly turn into major vulnerabilities when chained together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8980c901b93" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hybrid Cloud SOC Lab: Detecting AWS IAM Abuse with Wazuh]]></title>
            <link>https://medium.com/@nanaaisha1030/hybrid-cloud-soc-lab-detecting-aws-iam-abuse-with-wazuh-b53c4bac5880?source=rss-234a77c1a817------2</link>
            <guid isPermaLink="false">https://medium.com/p/b53c4bac5880</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[wazuh]]></category>
            <category><![CDATA[siem]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Aishat Olayinka Yusuf]]></dc:creator>
            <pubDate>Fri, 27 Mar 2026 16:43:50 GMT</pubDate>
            <atom:updated>2026-03-27T16:43:50.944Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introduction</strong></p><p>As organizations move more of their infrastructure to the cloud, security monitoring must adapt as well. In traditional environments, security teams mainly monitor servers, endpoints, and network traffic. In cloud platforms like AWS, however, most activity happens through API calls and identity-based actions, making identity monitoring a key part of cloud security.</p><p>AWS CloudTrail records these activities by logging every API call made in an AWS account, including details such as the user involved, the time of the action, the source IP address, and the affected resources. While these logs are valuable, they still need to be centralized and analyzed so that suspicious behavior can be detected.</p><p>For this lab, I built a hybrid Security Operations Center (SOC) environment to actively monitor cloud activity using Wazuh. See how to set up Wazuh <a href="https://medium.com/@nanaaisha1030/wazuh-siem-deployment-with-multi-os-agents-09e80e1821e9">here</a></p><p>The focus is on AWS CloudTrail logs and IAM activity, which are central to cloud security. Identity is the new perimeter in cloud environments, and almost every attack involves misuse or abuse of IAM permissions.</p><p>This lab is designed to simulate real-world cloud attacks and show how a SOC can detect them. By the end, I had a fully functional AWS &gt; CloudTrail &gt; S3 &gt; Wazuh pipeline, giving me hands-on experience in cloud security monitoring.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z5yhJ_Xy1XFOpbdn8dW7ig.jpeg" /><figcaption>Wazuh showing AWS logs</figcaption></figure><p><strong>Why This Project Is Important</strong></p><ul><li>Cloud security is essential as organizations increasingly move critical workloads to the cloud.</li><li>IAM abuse is a major risk, and misconfigurations or misuse can lead to full account compromise.</li><li>Having the ability to ingest CloudTrail logs into a SIEM like Wazuh allows security engineers to detect attacks in real time.</li><li>This lab bridges the gap between theory and practice: it is the type of work security engineers actually do in enterprise environments.</li></ul><p><strong>Problem / Issue It Solves</strong></p><p>CloudTrail logs exist, but without a centralized SOC or automated alerting, suspicious activity may go unnoticed. The lab addresses this problem by:</p><ul><li>Collecting IAM and management events from AWS CloudTrail.</li><li>Storing them in S3 for centralized access.</li><li>Using Wazuh to fetch, process, and alert on abnormal IAM activity.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kpJ7bhTtr4xOYE6EGoR85w.jpeg" /><figcaption><em>CloudTrail logs in AWS console</em></figcaption></figure><p><strong>Tools Used</strong></p><ul><li>AWS CloudTrail: Tracks all IAM and management API calls</li><li>AWS S3: Stores CloudTrail logs</li><li>Wazuh Manager (Ubuntu): Central SIEM for processing logs</li><li>Wazuh Agent (Windows VM): Optional for hybrid monitoring</li><li>AWS CLI: To verify logs and test events</li><li>IAM Users / Policies: For simulating attacks</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iUtCuzo7P24lyYp-NxvOgw.png" /></figure><p><strong>LAB WORKFLOW</strong></p><p><strong>Step 1: Create an S3 Bucket for CloudTrail Logs</strong></p><p>CloudTrail needs a storage location where it can deliver logs. In AWS, this is usually an S3 bucket.</p><ol><li>Open the AWS Console</li><li>Go to S3</li><li>Click Create Bucket</li></ol><pre>Bucket name: nana-wazuh-cloudtrail-us<br>Region: US East (N. Virginia) - us-east-1</pre><p>Finish creating the bucket.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SaIwuRyYAz-fBIyRwcagKw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8mnhRo8aYgYeFHGRkvKJ2w.jpeg" /></figure><p><strong>Step 2: Create a CloudTrail Trail</strong></p><p>Next, enable CloudTrail so AWS activities are logged.</p><ol><li>Open CloudTrail</li><li>Click Create trail</li></ol><pre>Trail name: wazuh-cloudtrail-us<br>Storage location: nana-wazuh-cloudtrail-us</pre><p>Under Management events, enable:</p><ul><li>Read events</li><li>Write events</li></ul><p>Finish creating the trail.</p><p>CloudTrail will now start sending logs to the S3 bucket.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zM9AktZFahsoqsV-gnEHfg.jpeg" /></figure><p><strong>Step 3: Install AWS CLI on the Wazuh Server</strong></p><p>The Wazuh server needs AWS CLI so it can access AWS services.</p><p>Download the AWS CLI installer:</p><pre>curl &quot;https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip&quot; -o &quot;awscliv2.zip&quot;</pre><p>Install unzip:</p><pre>sudo apt install unzip -y</pre><p>Extract the installer:</p><pre>unzip awscliv2.zip</pre><p>Install AWS CLI:</p><pre>sudo ./aws/install</pre><p>Verify the installation:</p><pre>aws - version</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*xWgpnd4NWQAhdUbqnwQ9Mw.jpeg" /></figure><p><strong>Step 4: Create an IAM User for Wazuh</strong></p><ol><li>Go to AWS Management Console &gt;IAM &gt;Users &gt;Add user.</li><li>Give the user a name: soc-test-user.</li><li>Assign permissions to allow reading CloudTrail logs from the S3 bucket (either AmazonS3ReadOnlyAccess or a custom policy).</li><li>Save the credentials AWS will show:</li></ol><ul><li>Access Key ID: xxxxxxxxxx</li><li>Secret Access Key: xxxxxxxxxx</li></ul><p>These keys are needed to allow Wazuh to authenticate and retrieve CloudTrail logs. Copy them immediately, as the Secret Access Key is only shown once.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O8H0Yy4PyrYjwZLfEXEQHA.jpeg" /></figure><p><strong>Step 5: Configure AWS CLI on Wazuh</strong></p><p>Next, configure the AWS credentials.</p><pre>aws configure</pre><p>Enter the following values:</p><pre>AWS Access Key ID: xxxxxxxxxxxxx<br>AWS Secret Access Key: xxxxxxxxxxxxxxxx<br>Default region: us-east-1<br>Output format: json</pre><p>This allows the Wazuh server to authenticate to AWS.</p><p><strong>Step 6: Configure Wazuh to Fetch CloudTrail Logs</strong></p><p>Edit the Wazuh configuration file.</p><pre>sudo nano /var/ossec/etc/ossec.conf</pre><p>Add the AWS S3 module configuration.</p><pre>&lt;wodle name=&quot;aws-s3&quot;&gt;<br>  &lt;disabled&gt;no&lt;/disabled&gt;<br>  &lt;interval&gt;1m&lt;/interval&gt; &lt;!-- fetch logs every 1 min --&gt;<br>  &lt;run_on_start&gt;yes&lt;/run_on_start&gt;<br>  &lt;bucket type=&quot;cloudtrail&quot;&gt;<br><br>    &lt;name&gt;nana-wazuh-cloudtrail-us&lt;/name&gt;<br>    &lt;aws_profile&gt;default&lt;/aws_profile&gt;<br>  &lt;/bucket&gt;<br>&lt;/wodle&gt;</pre><p>This tells Wazuh to check the S3 bucket every minute for new CloudTrail logs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/597/1*KDZ_2jAM6kqYSSHTiE5mrQ.jpeg" /></figure><p><strong>Step 7: Restart Wazuh</strong></p><p>Restart the Wazuh manager so the new configuration takes effect:</p><pre>sudo systemctl restart wazuh-manager</pre><p>Check the logs to confirm the AWS module is running:</p><pre>sudo tail -f /var/ossec/logs/ossec.log</pre><p>You should see Wazuh analyzing the S3 bucket.</p><p><strong>Step 8: Testing the Setup with IAM Activity</strong></p><p>To confirm the setup works, I generated IAM activity in AWS.</p><p>Examples of actions performed:</p><ul><li>Listing IAM users</li><li>Creating a new IAM user</li><li>Attaching policies</li><li>Add User to Group</li></ul><p>These actions trigger CloudTrail events such as:</p><p>ListUsers, CreateUser, AttachUserPolicy, AddUserToGroup</p><p>After a few minutes, these logs should appear in Wazuh.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kpJ7bhTtr4xOYE6EGoR85w.jpeg" /></figure><p><strong>Step 9: View Logs in Wazuh</strong></p><p>Open the Wazuh dashboard, go to Discover and filter for AWS logs.</p><p>You should see events like:</p><p>• ListUsers<br> • IAM activity logs<br> • Source IP address<br> • AWS account information</p><p>This confirms that Wazuh is successfully ingesting CloudTrail logs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NhtDwiHdpwVK25eOAZSNeA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9aw0oBoOnDhfNOmhmAHPjw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JQ796tdh2k0YxDzI01aR_g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E8ktSbJCWnWzdyab_4xlIw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hw-JLys-RDKcXRd4ZGceFA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*21JDm4c2zrsUrQYQVuMy7w.jpeg" /></figure><p><strong>Challenge Encountered</strong></p><p>One challenge I encountered during the setup involved AWS regions.</p><p>Initially, the S3 bucket was created in EU North (Stockholm) while the rest of the setup used US East (N. Virginia). Because of this mismatch, Wazuh could not find any logs in the bucket.</p><p>The solution was to create a new S3 bucket in the correct region and update the CloudTrail trail.</p><p>After fixing the region issue, Wazuh started retrieving logs successfully.</p><p><strong>Conclusion</strong></p><p>In this project, I built a monitoring pipeline that connects AWS CloudTrail with Wazuh. CloudTrail records AWS activity, the logs are stored in S3, and Wazuh retrieves and analyzes those logs.</p><p>By generating IAM actions and observing them in Wazuh, I confirmed that the integration works and can be used to monitor cloud activity. This lab helped me better understand how cloud security monitoring works in real environments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b53c4bac5880" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[API Security Is Not a Feature- It’s a Responsibility]]></title>
            <link>https://medium.com/@nanaaisha1030/api-security-is-not-a-feature-its-a-responsibility-7081cbb01578?source=rss-234a77c1a817------2</link>
            <guid isPermaLink="false">https://medium.com/p/7081cbb01578</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Aishat Olayinka Yusuf]]></dc:creator>
            <pubDate>Fri, 27 Feb 2026 13:30:55 GMT</pubDate>
            <atom:updated>2026-02-27T13:30:55.445Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first started learning API security, I saw it as a technical layer; something you configure, test, and move on from. Authentication, authorization, rate limiting… it all felt like checklist items. If the endpoint returned a 200 OK and didn’t crash, I thought things were fine.</p><p>But that mindset changed.</p><p><strong>The Mindset Shift</strong></p><p>The biggest shift for me was realizing that APIs are not just backend functions they are direct access points to data, logic, and trust. Every endpoint is a door. And if that door is poorly designed, misconfigured, or unmonitored, it becomes an entry point for abuse.</p><p>When I moved from learning fundamentals to actually exploiting APIs- mass assignment, broken authentication, excessive data exposure, I stopped thinking like a developer and started thinking like an attacker. That shift changed everything. I began to see how small oversights could become major breaches.</p><p>Later, when I started exploring applications and how they rely heavily on APIs, it became even clearer: insecure APIs don’t just leak data, they can manipulate models, poison workflows, and automate attacks at scale.</p><p>Security is no longer optional hardening. It is architectural responsibility.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_R9mQfwqO-puVDGM58XD0g.png" /></figure><p><strong>One Principle I Now Strongly Believe</strong></p><p>Security must be designed, not patched.</p><p>You cannot bolt security onto an API after deployment and expect it to be resilient. Proper access control, strict input validation, least privilege, logging, monitoring, and rate limiting must be intentional from the design phase.</p><p>Through exploitation exercises, I learned that most vulnerabilities aren’t caused by complex zero-days; they’re caused by assumptions. Assumptions that users will behave correctly. Assumptions that hidden endpoints won’t be found. Assumptions that “no one will notice.”</p><p>Attackers always notice.</p><p><strong>One Responsibility API Security Professionals Should Never Ignore</strong></p><p>Never ignore logging and monitoring.</p><p>One of the most eye-opening lessons for me was seeing how an API could be exploited repeatedly without detection simply because no one was watching. If you don’t log properly, you cannot detect abuse. If you cannot detect abuse, you cannot respond. And if you cannot respond, the attacker controls the timeline.</p><p>API security professionals are not just defenders of endpoints, they are guardians of visibility. Without monitoring, security becomes blind.</p><p>API security is not a feature you toggle on. It’s not just an item in a sprint backlog. It’s a responsibility to users, to organizations, and to the systems that increasingly depend on interconnected APIs including AI.</p><p>And once you truly understand that, you can never look at an endpoint the same way again.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7081cbb01578" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thinking Like an Attacker: How API Pen-Testers Identify IDOR]]></title>
            <link>https://medium.com/@nanaaisha1030/thinking-like-an-attacker-how-api-pen-testers-identify-idor-300cae37cff2?source=rss-234a77c1a817------2</link>
            <guid isPermaLink="false">https://medium.com/p/300cae37cff2</guid>
            <category><![CDATA[idor]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bola]]></category>
            <category><![CDATA[api-sec]]></category>
            <dc:creator><![CDATA[Aishat Olayinka Yusuf]]></dc:creator>
            <pubDate>Sun, 22 Feb 2026 10:51:47 GMT</pubDate>
            <atom:updated>2026-02-22T10:51:47.056Z</atom:updated>
            <content:encoded><![CDATA[<p>IDOR (Insecure Direct Object Reference) is a type of vulnerability where an API fails to properly check whether the user requesting a resource is authorized to access it. In simpler terms, it lets an attacker access data they shouldn’t be able to see by changing an object identifier (like a user ID) in the request.</p><p>In modern APIs, this is basically the same as what is called BOLA (Broken Object Level Authorization) except in today’s API-driven systems, it’s far more common and impactful because APIs expose so many objects directly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3GchUJ07d3ZEOPFMhdzWBg.png" /></figure><p>When I started testing vAPI, I wanted to put myself in the attacker’s shoes. The goal was simple: see how far I could go by manipulating API requests. I created a test account using the registration endpoint with this payload:</p><pre>{<br>  &quot;username&quot;: &quot;agent1&quot;,<br>  &quot;password&quot;: &quot;agent&quot;,<br>  &quot;name&quot;: &quot;pen&quot;,<br>  &quot;address&quot;: &quot;space&quot;,<br>  &quot;mobileno&quot;: &quot;765468432&quot;<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/973/1*PFd5dTCLwDxg-2QV2wmLxQ.jpeg" /></figure><p>Once the account was created, I explored the user endpoint /vapi/api5/user. Out of curiosity, I added an “s” to make /users, and without logging in, it returned all users in the system, including the admin account with a flag and its sensitive data:</p><pre>{<br>    &quot;id&quot;: 1,<br>    &quot;username&quot;:&quot;admin&quot;,<br>    &quot;password&quot;:&quot;Admin User&quot;,<br>    &quot;name&quot;:&quot;pen&quot;,<br>    &quot;address&quot;:&quot;flag{api5_76dd9900a97ff1563ae76}&quot;,<br>    &quot;mobileno&quot;:&quot;8080808080&quot;<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rFHXzo8vdcvCp4fR015WLA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*DB2mnoL8pGWMLLeil3WH1Q.jpeg" /></figure><h3>How the Vulnerability Occurs</h3><p>IDOR occurs because the API does not enforce authorization at the object level. Any user can access objects (here, user accounts) that don’t belong to them simply by changing the ID or endpoint path.</p><h3>What a Tester Looks For</h3><ol><li>Create a test account.</li><li>Access endpoints that return user-specific or sensitive data.</li><li>Modify object identifiers (IDs, paths, or parameters).</li><li>Observe whether the API returns unauthorized data.</li></ol><h3>Potential Impact</h3><ul><li>Exposure of sensitive information (personal info, flags, API keys).</li><li>Unauthorized access to admin or privileged accounts.</li><li>Potential account takeover or data breaches.</li></ul><h3>Attacker Mindset</h3><p>Attackers look for simple manipulations. Changing IDs or parameters in requests can reveal information that wasn’t meant to be public. APIs are particularly vulnerable because they are data-focused and often expose numerous objects directly.</p><h3>Why APIs Are Vulnerable</h3><ul><li>APIs often trust the client request and assume correct usage.</li><li>Developers may forget object-level access checks.</li><li>Sensitive fields are sometimes exposed unnecessarily.</li></ul><h3>How Developers Can Prevent It</h3><ul><li>Always check object-level permissions.</li><li>Use role-based or attribute-based access control</li><li>Avoid exposing sensitive fields in responses unless required.</li><li>Test APIs regularly for IDOR/BOLA vulnerabilities.</li></ul><p>In conclusion, this lab demonstrates how a single oversight in API access control in this case, failing to enforce object-level authorization can expose sensitive data to anyone, even without logging in.</p><p>It highlights why IDOR/BOLA vulnerabilities are critical to identify and fix, and why developers must always enforce proper authentication and authorization at every endpoint to protect user data.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=300cae37cff2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wazuh + VirusTotal + Slack: Automated Threat Detection, Enrichment and Alerting]]></title>
            <link>https://themalwarefiles.com/wazuh-virustotal-slack-automated-threat-detection-enrichment-and-alerting-300898b0f4fd?source=rss-234a77c1a817------2</link>
            <guid isPermaLink="false">https://medium.com/p/300898b0f4fd</guid>
            <category><![CDATA[virustotal]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[siem]]></category>
            <category><![CDATA[wazuh]]></category>
            <category><![CDATA[slack]]></category>
            <dc:creator><![CDATA[Aishat Olayinka Yusuf]]></dc:creator>
            <pubDate>Fri, 06 Feb 2026 16:22:49 GMT</pubDate>
            <atom:updated>2026-02-08T18:44:19.141Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Executive Summary</strong></p><p>In this modern age of automation, Wazuh, VirusTotal, and Slack play a vital role in supporting Security Operations Center (SOC) activities by improving threat visibility, accelerating detection, and enabling rapid communication. SOC teams are often overwhelmed by large volumes of alerts, making automation and threat intelligence integration essential for prioritizing real security incidents and reducing response time. By combining monitoring, enrichment, and alerting tools, SOC analysts can make faster and more informed decisions.</p><p>In this project, I integrated VirusTotal and Slack with Wazuh to design an automated SOC-style threat detection, enrichment, and alerting workflow. Wazuh served as the central SIEM platform, using File Integrity Monitoring (FIM) to detect file creation and modification events on monitored endpoints. These events were automatically enriched with threat intelligence from VirusTotal, allowing malicious files to be quickly identified based on detection ratios and reputation analysis. To support rapid incident response, Slack was integrated to deliver real-time alerts to a SOC communication channel, ensuring analysts are immediately notified of high-risk events.</p><p>This project demonstrates how automation and intelligence-driven alerting can improve SOC efficiency by reducing manual analysis, minimizing alert fatigue, and enabling quicker incident response. The implemented solution reflects real-world SOC practices and highlights how open-source security tools can be effectively combined to enhance threat detection and operational awareness.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X37r0VC2tTaq0cl1pKqkiQ.jpeg" /></figure><h3>Steps to Integrate VirusTotal with Wazuh</h3><p><strong>1. Obtain a VirusTotal API key</strong></p><p>I first created a VirusTotal account and generated an API key from the VirusTotal API page. This API key allows Wazuh to query VirusTotal for file hash reputation.</p><p>2. Enable File Integrity Monitoring (FIM)</p><p>VirusTotal integration in Wazuh works based on file change events, I ensured that File Integrity Monitoring (syscheck) was enabled on the endpoint.</p><p>Read previous post about File Integrity Monitoring <a href="https://medium.com/@nanaaisha1030/wazuh-file-integrity-monitoring-tracking-endpoint-modifications-in-real-time-269e384f3fa7">here</a></p><p>3. Configure VirusTotal integration in Wazuh</p><p>On the Wazuh Manager, I edited the main configuration file:</p><pre>sudo nano /var/ossec/etc/ossec.conf</pre><p>Inside the &lt;ossec_config&gt; block, I added the VirusTotal integration configuration:</p><pre>&lt;integration&gt;<br>&lt;name&gt;virustotal&lt;/name&gt;<br>&lt;api_key&gt;YOUR_VIRUSTOTAL_API_KEY&lt;/api_key&gt;<br>&lt;group&gt;syscheck&lt;/group&gt;<br>&lt;alert_format&gt;json&lt;/alert_format&gt;<br>&lt;/integration&gt;</pre><ul><li>The API key was placed between the &lt;api_key&gt; tags</li></ul><p>4. Validate the configuration</p><p>Before restarting the manager, I validated the configuration to ensure there were no XML errors:</p><pre>sudo /var/ossec/bin/wazuh-control check-config</pre><p>A successful validation confirmed that the configuration was correct.</p><p>5. Restart the Wazuh Manager</p><p>After confirming the configuration was valid, I restarted the Wazuh Manager to apply the changes:</p><pre>sudo systemctl restart wazuh-manager</pre><p>7. Verify VirusTotal events in the Wazuh dashboard</p><p>In the Wazuh Dashboard, I navigated to:</p><ul><li>Endpoint Security, Malware Detection</li><li>Filtered alerts by VirusTotal</li></ul><p>The alert included VirusTotal information such as:</p><ul><li>Detection ratio (positives vs total engines)</li><li>File hash (SHA256)</li><li>VirusTotal analysis result</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R8_p0neYI65bT3hZpStqQw.jpeg" /></figure><p>This confirmed that the VirusTotal integration was successfully working.</p><h3>Steps to Integrate Slack with Wazuh</h3><p><strong>Step 1: Set up the Slack Application</strong></p><ol><li>Create a slack account or sign into a pre existing one</li></ol><ul><li>Go to slack.com</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MBCMqmr5UoGKgM75K2tiqA.jpeg" /></figure><p>2. Input the 6 digit verification code sent to your email</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C1Gs0bqIOqg1RjS1GmRTfQ.jpeg" /></figure><p>3. Create a workspace</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kekTNHFRK7k1LVoZb6l_Rg.jpeg" /></figure><p>4. Name your work space</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z9q7QB2qOVV-KsBMcURpnA.jpeg" /></figure><p>5. Add your name</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a_kypXlFx826RNDYVgYwXw.jpeg" /></figure><p>6. Add team members and if there is non, click on skip</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-l25_BrZyv6vukGzynhAXg.jpeg" /></figure><p>7. Select “Start with free” plan</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Defo5XjMQRDJWrfbUExeA.jpeg" /></figure><p>8. Slack is up and running</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PYEG5uW0cuUEKNCtvHca7Q.jpeg" /></figure><p><strong>Step 2: Get a Slack Webhook URL</strong></p><p>1. Sign in to Slack</p><ul><li>Sign in to your Slack workspace (or create one if you don’t have it)</li></ul><p>2. Create a Slack App</p><ul><li>Go to <a href="https://docs.slack.dev/">https://docs.slack.dev/</a></li></ul><p>· Select messaging — Sending messages using incoming webhooks</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SOhsti50E1OfJz7BYV3ixw.jpeg" /></figure><ul><li>Click Create New App</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rUaDf1Tu8TtyCbAQt2vB5A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vsyKY2QTFnILc5g7V2IxrQ.jpeg" /></figure><ul><li>Choose From scratch</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*09DXFWpZzq3J_vM9fNeSHA.jpeg" /></figure><ul><li>App Name (e.g., <em>Wazuh Alerts</em>)</li><li>Workspace (select your Slack workspace)</li><li>Click Create App</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BIJvq12ayO8mYr587VVCQQ.jpeg" /></figure><p>3. Enable Incoming Webhooks</p><ul><li>In the app settings sidebar, click Incoming Webhooks</li><li>Toggle Activate Incoming Webhooks ON</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vLTS0bhSNOg2ygHmQpGS4w.jpeg" /></figure><p>4. Add a Webhook to a Channel</p><ul><li>Still under Incoming Webhooks, click Add New Webhook to Workspace</li><li>Choose the Slack channel where you want Wazuh alerts to be sent</li><li>Click Allow</li></ul><p>5. Copy the Webhook URL</p><ul><li>Slack will generate a webhook URL that looks like this:</li></ul><p><a href="https://hooks.slack.com/services/TXXXXXX/BXXXXXX/XXXXXXXXXXXXXXXX"><em>https://hooks.slack.com/services/TXXXXXX/BXXXXXX/XXXXXXXXXXXXXXXX</em></a></p><ul><li>Copy this URL, this is what you use in Wazuh</li></ul><p>6. Use the Webhook in Wazuh</p><p>In <em>/var/ossec/etc/ossec.conf</em>, place the webhook URL inside the Slack integration block:</p><pre>&lt;integration&gt;<br>&lt;name&gt;slack&lt;/name&gt;<br>&lt;hook_url&gt;PASTE_YOUR_SLACK_WEBHOOK_URL_HERE&lt;/hook_url&gt;<br>&lt;alert_format&gt;json&lt;/alert_format&gt;<br>&lt;/integration&gt;</pre><p>7. Restart and test</p><ul><li>Validate config:</li></ul><pre>sudo /var/ossec/bin/wazuh-control check-config</pre><ul><li>Restart Wazuh:</li></ul><pre>sudo systemctl restart wazuh-manager</pre><ul><li>Events inflow successful</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OU9zYhtmWxD6thdwZfld5A.jpeg" /><figcaption>Wazuh Security Alert (Desktop View)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9ayljiwkj52ZnaY9wmMwEQ.jpeg" /></figure><h3><strong>Implementation and Validation: Malware Detection Workflow Using a Real Malware Sample</strong></h3><p><strong>Implementation</strong></p><p>To validate the integrated security workflow, Wazuh was configured with File Integrity Monitoring (FIM) on a Windows endpoint, VirusTotal for threat intelligence enrichment, and Slack for real-time alerting. The monitored directory included the Desktop, where file creation and modification events were forwarded to the Wazuh Manager.</p><p>A real malware sample identified as “LockBit Ransomware” was used for this validation. The sample was not executed; instead, the compressed archive was extracted within the monitored directory. This action triggered a FIM event, prompting Wazuh to generate the file hash and submit it to VirusTotal for analysis.</p><p>VirusTotal classified the file as malicious, with 64 antivirus engines detecting the sample. Wazuh enriched the event with VirusTotal metadata, including detection count, file path, hashes, and a permalink to the VirusTotal report.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cei6hYAjDBdh68XdTGHwag.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LUzCGT1w2EvjmB83s3v-LA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u6OwGhjttisj_qlhjWZbaw.jpeg" /></figure><p><strong>Validation</strong></p><p>The workflow successfully generated a high-severity alert in the Wazuh dashboard, classified under the VirusTotal integration ruleset with a rule level of 12. The alert confirmed the presence of a known ransomware sample and provided actionable threat intelligence for investigation.</p><p>The alert was forwarded to Slack, demonstrating effective real-time notification and escalation. This validation confirms that the integrated solution can detect, enrich, and alert on real-world malware artifacts without requiring execution, aligning with industry-standard SOC detection and response practices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7YLLoXArVDdzkNcz88l7tA.jpeg" /><figcaption>Wazuh Security Alert (Desktop View)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*unBh_NvP3DQ-KyaRW5SJyg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Mib2JJNLqWe_S5pzCX9bw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B5YTrZXyjRzc4Ky2iHNzwQ.jpeg" /><figcaption>Wazuh Security Alert (Mobile View)</figcaption></figure><h3>Conclusion</h3><p>This project successfully demonstrated the integration of Wazuh, VirusTotal, and Slack to build an automated threat detection, enrichment, and alerting workflow aligned with real-world SOC operations. By combining endpoint visibility, external threat intelligence, and real-time notifications, the solution enhances an organization’s ability to detect and respond to malicious activity efficiently.</p><p>Through controlled validation using a real malware sample, the workflow proved effective in identifying malicious files via File Integrity Monitoring, enriching detections with VirusTotal intelligence, and escalating high-severity alerts to Slack for rapid analyst awareness. The ability to detect malware without execution highlights the strength of hash-based detection and intelligence-driven security monitoring.</p><p>Overall, this project reflects industry-standard security practices and demonstrates how automation and integration can improve detection accuracy, reduce response time, and support proactive security operations. The implemented solution provides a scalable foundation that can be extended with additional integrations, rule tuning, and response actions to further enhance SOC capabilities.</p><p>Project Inspiration: <a href="https://medium.com/u/f6fc6f913781">Efam Harris</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=300898b0f4fd" width="1" height="1" alt=""><hr><p><a href="https://themalwarefiles.com/wazuh-virustotal-slack-automated-threat-detection-enrichment-and-alerting-300898b0f4fd">Wazuh + VirusTotal + Slack: Automated Threat Detection, Enrichment and Alerting</a> was originally published in <a href="https://themalwarefiles.com/">The Malware Files</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wazuh File Integrity Monitoring: Tracking Endpoint Modifications in Real Time]]></title>
            <link>https://infosecwriteups.com/wazuh-file-integrity-monitoring-tracking-endpoint-modifications-in-real-time-269e384f3fa7?source=rss-234a77c1a817------2</link>
            <guid isPermaLink="false">https://medium.com/p/269e384f3fa7</guid>
            <dc:creator><![CDATA[Aishat Olayinka Yusuf]]></dc:creator>
            <pubDate>Wed, 28 Jan 2026 16:38:11 GMT</pubDate>
            <atom:updated>2026-07-06T06:34:21.760Z</atom:updated>
            <content:encoded><![CDATA[<h3>Overview</h3><p>In this project, I implemented File Integrity Monitoring (FIM) using Wazuh to detect file system and Windows Registry changes in a lab environment. Custom FIM rules was configured to monitor user directories and registry Run keys, then validated the setup by manually creating, modifying, and deleting files and folders, and by running a benign malware simulation that triggered Windows processes leading to registry updates. This demonstrated how FIM detects not only direct malicious modifications but also related system-level activity that occurs during suspicious endpoint behavior, supporting incident investigation and root-cause analysis.</p><p>File Integrity Monitoring (FIM) is a security control used to track changes made to files and system configurations. It helps detect when files are created, modified, or deleted, and when critical system areas like the Windows Registry are altered. Since many attacks rely on changing files or registry keys to maintain persistence or evade detection, FIM provides an important layer of visibility into what’s happening on an endpoint. For this project, i used Windows endpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IgesWE_x72ThLyu7T2u6Zg.jpeg" /></figure><p>You can read more about File Integrity Monitoring in official Wazuh Documentation <a href="https://documentation.wazuh.com/current/user-manual/capabilities/file-integrity/how-to-configure-fim.html">here</a></p><h3>Configuration &amp; Detection</h3><ol><li><strong>Edit the agent’s ossec.conf file</strong></li></ol><ul><li>On the Windows endpoint, the Wazuh agent configuration file is located at</li></ul><pre>C:\Program Files (x86)\ossec-agent\ossec.conf</pre><p>and edit the ossec.conf file using notepad (open as an administrator).</p><ul><li>Add the directories you want to monitor within the &lt;syscheck&gt; block</li></ul><pre>&lt;directories check_all=&quot;yes&quot; report_changes=&quot;yes&quot; realtime=&quot;yes&quot;&gt;C:\Users\Public&lt;/directories&gt;<br>&lt;directories check_all=&quot;yes&quot; report_changes=&quot;yes&quot; realtime=&quot;yes&quot;&gt;C:\Users\Public\Downloads&lt;/directories&gt;<br>&lt;directories check_all=&quot;yes&quot; report_changes=&quot;yes&quot; realtime=&quot;yes&quot;&gt;C:\Users\Lily\Desktop&lt;/directories&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FvCOZ9zsrpNFIJueyym_mg.jpeg" /><figcaption>ossec.conf</figcaption></figure><ul><li>Restart the Wazuh agent to apply changes</li></ul><pre>Restart-Service wazuh-agent</pre><p><strong>2. Test the Configuration</strong></p><ul><li><strong>Create files</strong></li></ul><p>I created a file on Desktop named “Malware Docs”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/309/1*t2EqYJ5s-CzT5CPjy3XF7Q.jpeg" /></figure><p><strong>Alert Visualization</strong></p><p>Navigate to Endpoint security &gt; File Integrity Monitoring &gt; Events on the Wazuh dashboard to view the alert generated when the FIM module detects changes in the monitored file. The created file was logged as ‘file added’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GovN3S1Zqm5TfSX4swCExw.jpeg" /><figcaption>files created</figcaption></figure><ul><li><strong>Modify Files</strong></li></ul><p>To demonstrate file modification detection, I edited the contents of a file in the Downloads folder named “Malicious.txt”</p><p><strong>Alert Visualization</strong></p><p>This action was detected by Wazuh File Integrity Monitoring and logged as a “file modification” event in the dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U69WhITQ5XSQt_M2gCvdEw.jpeg" /><figcaption>file modified</figcaption></figure><ul><li><strong>Delete Files</strong></li></ul><p>Several files were deleted, and this activity was detected by Wazuh File Integrity Monitoring and logged as “File deleted” events.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d5uYJbK7Lj43OfFAV4yLBQ.jpeg" /><figcaption>files deleted</figcaption></figure><ul><li><strong>Registry Modification</strong></li></ul><p>To demonstrate registry monitoring, I ran a benign malware simulation that attempted to establish persistence. This action triggered legitimate Windows system processes, which in turn updated related registry keys in the background. Wazuh detected these changes and logged them as registry modification events, demonstrating how File Integrity Monitoring can capture both direct malware activity and the secondary system behaviors it provokes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WjRpltYtUzY_kx0L1hWpkg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xAQRxfW3ATRLAkQTG0PXFA.jpeg" /></figure><h3>Dashboard Insights &amp; Key Takeaways</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BqYTVh5qn5LCmGvzoPlpMA.jpeg" /><figcaption>FIM Dashboard</figcaption></figure><p>This project demonstrated the practical value of File Integrity Monitoring through hands-on configuration, testing, and analysis using Wazuh. I successfully monitored file systems and Windows Registry keys, validated detection with manual changes and a malware simulation, and used the Wazuh dashboard to turn raw alerts into actionable insights.</p><p>FIM proved to be a critical visibility tool not just for compliance, but for real-time detection, rapid investigation, and understanding attack behaviors through change analysis. By capturing both legitimate and malicious modifications, it serves as a foundational layer in a proactive security posture.</p><p>Many thanks to <a href="https://medium.com/u/f6fc6f913781">Efam Harris</a> for inspiring me to take on this project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=269e384f3fa7" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/wazuh-file-integrity-monitoring-tracking-endpoint-modifications-in-real-time-269e384f3fa7">Wazuh File Integrity Monitoring: Tracking Endpoint Modifications in Real Time</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[API Security & PCI DSS: What API Developers Need to Know]]></title>
            <link>https://medium.com/@nanaaisha1030/api-security-pci-dss-what-api-developers-need-to-know-c8e18e640385?source=rss-234a77c1a817------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8e18e640385</guid>
            <dc:creator><![CDATA[Aishat Olayinka Yusuf]]></dc:creator>
            <pubDate>Sun, 25 Jan 2026 18:28:35 GMT</pubDate>
            <atom:updated>2026-01-25T18:28:35.249Z</atom:updated>
            <content:encoded><![CDATA[<p>APIs (Application Programming Interfaces) are at the heart of how modern software interacts with payment systems, banking services, and online commerce. Because APIs often handle sensitive<strong> </strong>payment card data or connect to systems that do, they are now specifically addressed in the latest PCI DSS (Payment Card Industry Data Security Standard) requirements. For API developers, this means that secure API design isn’t optional, it’s part of building systems that protect payment data and comply with industry standards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/853/1*jRTX4nlKUc_BUweK0kxH4w.jpeg" /></figure><p><strong>3 Key PCI DSS Requirements for APIs</strong></p><p>PCI DSS doesn’t have rules just for “APIs,” but it explicitly includes API security requirements within its broader software and application security sections. Let’s look at three important requirements you should know:</p><p><strong>1. PCI DSS Requirement 6.2.1: Secure Software Development</strong></p><p><strong>What it addresses:</strong> Risks from insecure coding and logical vulnerabilities in APIs that could expose payment data or allow unauthorized access.<br> <strong>API Risk:</strong> APIs that are coded without security in mind can leak cardholder data, allow attackers to bypass authentication, or contain logic flaws that expose sensitive operations. <br> <strong>Security Control:</strong> Follow secure development practices from the design stage through testing and deployment. This means using recognized secure coding standards, understanding data flow in your API, and building protections like parameter validation and safe authentication hooks into every endpoint.</p><p><strong>2. PCI DSS Requirement 6.2.2: Developer Security Training</strong></p><p><strong>What it addresses:</strong> Knowledge gaps among developers about API risks and how secure coding prevents vulnerabilities.<br> <strong>API Risk:</strong> Without proper training, developers may unintentionally introduce weak authentication, poor access control, or unsafe data handling. <br> <strong>Security Control:</strong> Provide annual secure coding and API security training to developers.</p><p><strong>3. PCI DSS Requirement 6.2.4: Preventing Common Vulnerabilities</strong></p><p><strong>What it addresses:</strong> Risks from well-known security weaknesses in APIs like injection attacks, broken authentication, or insecure configurations.<br> <strong>API Risk:</strong> APIs are frequent targets because attackers exploit common vulnerabilities to manipulate API behavior or access data they shouldn’t. <br> <strong>Security Control:</strong> Implement secure coding patterns and defenses such as input validation, output encoding, authentication checks, and OWASP API Security Top 10 mitigation strategies. These controls reduce the chance that common attacks succeed.</p><p><strong>Why PCI DSS Matters for APIs</strong></p><p>PCI DSS is a global standard for protecting payment card data. In its Version 4.0 update, PCI DSS explicitly extended its scope to include APIs, especially those that process, transmit, or store cardholder data or could affect its security. This means that APIs are no longer treated as “just internal code” they are recognized as potential attack surfaces that must be secure.</p><p><strong>Why this matters for developers:</strong></p><ul><li>APIs are the new frontline of attacks attackers often target APIs directly to avoid user interfaces and find business logic weaknesses.</li><li>PCI DSS compliance helps protect users and organizations from data breaches that could lead to fines, loss of trust, and operational issues.</li><li>APIs are now part of audit scope so meeting PCI DSS requirements isn’t just good practice, it’s part of ensuring your systems pass compliance reviews.</li></ul><p><strong>How PCI DSS Compliance Influences Secure API Design</strong></p><p>Rather than being a checklist added to facts, PCI DSS shapes how APIs are designed from the beginning:</p><p><strong>1. Security Starts at Design</strong></p><p>Compliance requires understanding how data flows through your API and implementing controls like <strong>l</strong>east privilege, authentication, and validation from the start. This means thinking like an attacker, not just a developer.</p><p><strong>2. Encryption is Mandatory</strong></p><p>PCI DSS expects cardholder data to be protected in transit and at rest, so your API must enforce HTTPS/TLS, avoid legacy ciphers, and encrypt any sensitive information.</p><p><strong>3. Continuous Testing</strong></p><p>APIs must be tested routinely not just once before release. PCI DSS calls for regular vulnerability scanning and assessments, including all your API endpoints.</p><p><strong>Practical API Security Practices Driven by PCI DSS</strong></p><p>Here are some real design and coding habits PCI DSS encourages:</p><p><strong>Inventory All APIs</strong></p><p>You must know <em>every</em> API you run, including internal, third-party, and shadow endpoints. Documentation and discovery help ensure nothing slips outside security review.</p><p><strong>Strong Authentication &amp; Authorization</strong></p><p>Use robust methods (e.g., OAuth, short-lived tokens) and enforce authorization checks per API call, not just at login.</p><p><strong>Input Validation</strong></p><p>Every request should be validated against strict schemas (e.g., OpenAPI) to prevent injection or unexpected data manipulation.</p><p><strong>Rate Limiting &amp; Gateway Tools</strong></p><p>API gateways help enforce policies like rate limiting, authentication, and unified logging, protecting APIs from abuse and helping meet PCI DSS expectations</p><p><strong>Logs &amp; Monitoring</strong></p><p>Centralize logs from API gateways and services to detect suspicious behavior (multiple failed requests, token misuse), which supports PCI DSS monitoring requirements.</p><p><strong>Conclusion</strong></p><p>For API developers working with payment systems, PCI DSS is more than compliance, it’s a blueprint for building secure APIs that handle sensitive data safely. By understanding how specific requirements apply to APIs, thinking defensively in design, and applying secure coding and testing practices, you can build APIs that protect customers and keep your organization compliant.</p><p><strong>References</strong></p><p>APIsec University. (n.d.). <em>API Security for PCI Compliance</em>. Retrieved from <a href="https://www.apisecuniversity.com/courses/api-security-for-pci-compliance?utm_source=chatgpt.com">https://www.apisecuniversity.com/courses/api-security-for-pci-compliance</a></p><p>APIsec. (2024). <em>Upcoming DSS 4.0 deadline for PCI compliance</em>. Retrieved from <a href="https://www.apisec.ai/blog/upcoming-dss-4-0-deadline-for-pci-compliance?utm_source=chatgpt.com">https://www.apisec.ai/blog/upcoming-dss-4-0-deadline-for-pci-compliance</a></p><p>APIsec. (2025). <em>Financial services API security compliance guide</em>. Retrieved from <a href="https://www.apisec.ai/blog/financial-services-api-security-compliance?utm_source=chatgpt.com">https://www.apisec.ai/blog/financial-services-api-security-compliance</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8e18e640385" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wazuh SIEM Deployment with Multi-OS Agents]]></title>
            <link>https://infosecwriteups.com/wazuh-siem-deployment-with-multi-os-agents-09e80e1821e9?source=rss-234a77c1a817------2</link>
            <guid isPermaLink="false">https://medium.com/p/09e80e1821e9</guid>
            <category><![CDATA[wazuh]]></category>
            <category><![CDATA[siem]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[information-security]]></category>
            <dc:creator><![CDATA[Aishat Olayinka Yusuf]]></dc:creator>
            <pubDate>Wed, 21 Jan 2026 14:59:41 GMT</pubDate>
            <atom:updated>2026-07-05T06:15:16.672Z</atom:updated>
            <content:encoded><![CDATA[<h3>Project Overview</h3><p>This project demonstrates the deployment of Wazuh, an open-source,<strong> </strong>industry-recognized SIEM and host-based intrusion detection platform, in a virtualized lab environment. Wazuh was selected for this project due to its wide adoption in security operations, strong community support, and alignment with real-world SOC practices.</p><p>A Wazuh Manager was installed on an Ubuntu system and configured to centrally monitor three endpoints: Windows, Kali Linux, and Ubuntu. Each endpoint was successfully enrolled as a Wazuh agent and configured to forward system logs and security events to the manager for analysis.</p><p>The project validates end-to-end log collection and visibility through the Wazuh web dashboard, demonstrating how security events from multiple operating systems can be centrally analyzed. This setup reflects a realistic enterprise monitoring scenario and highlights the effectiveness of Wazuh as a cost-effective, open-source security monitoring solution used across modern SOC environments.</p><h3>Tools Used</h3><ul><li><strong>Wazuh SIEM (Open Source):</strong> Centralized security monitoring, log collection, and host-based intrusion detection platform</li><li><strong>Ubuntu Server: </strong>Hosting the Wazuh Manager, Indexer, and Web Dashboard</li><li><strong>Windows</strong> : Endpoint monitored using the Wazuh agent (Agent 1)</li><li><strong>Kali Linux: </strong>Linux endpoint monitored using the Wazuh agent (Agent 2)</li><li><strong>Ubuntu: </strong>Linux endpoint monitored using the Wazuh agent (Agent 3)</li><li><strong>VMware Workstation: </strong>Virtualization platform used to host all systems</li><li><strong>Web Browser (Windows): </strong>Used to access the Wazuh web dashboard over HTTPS</li></ul><h3><strong>Wazuh Deployment</strong></h3><p>Wazuh was deployed on Ubuntu Server using the official all-in-one installation script, following the Wazuh deployment guide. <a href="https://documentation.wazuh.com/current/quickstart.html">Read here</a></p><pre>curl -sO https://packages.wazuh.com/4.14/wazuh-install.sh &amp;&amp; sudo bash ./wazuh-install.sh -a</pre><p>This command installs all required dependencies along with the Wazuh Manager, Indexer, and Dashboard. Upon completion of the installation, a username and password are automatically generated for accessing the Wazuh web interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0AEIg9diazhMdLr1tFCj2Q.jpeg" /></figure><h3><strong>Firewall Configuration</strong></h3><p>The firewall on the Wazuh server was configured to allow all Wazuh components to communicate properly, including agents, the dashboard, indexer, and Syslog. The following UFW rules were applied:</p><pre># Essential Wazuh ports<br>sudo ufw allow 1514/tcp   # Agent → Manager communication<br>sudo ufw allow 1515/tcp   # Agent enrollment<br>sudo ufw allow 443/tcp    # Wazuh Web Dashboard (HTTPS)<br><br># Optional ports for future use<br>sudo ufw allow 55000/tcp  # Wazuh API<br>sudo ufw allow 514/tcp    # Syslog collector<br>sudo ufw allow 22/tcp     # SSH access to server<br><br>sudo ufw enable - Enables the UFW firewall<br>sudo ufw status numbered - Displays the current firewall status and lists all active rules with numbering</pre><p><strong>Accessing the Wazuh Web Interface</strong></p><p>After the firewall was configured to allow all essential ports, the Wazuh web dashboard was accessed via a web browser. This interface provides centralized visibility into all connected agents, system events, and security alerts.</p><pre>https://192.168.79.145:443</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IgesWE_x72ThLyu7T2u6Zg.jpeg" /></figure><p>Log in using the username and password generated during installation.</p><h3><strong>Agents Enrollment</strong></h3><p>To enroll an agent, navigate to Endpoints, Deploy new agents.</p><p><strong>Agent 1: Windows</strong></p><p>Step 1: Select windows architecture</p><p>Step 2: Enter the Wazuh Manager IP Address</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6XDcpPc3wF4_3kHmaFA46g.jpeg" /></figure><p>Step 3: Set agent name (optional)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Pt49xAxtkU_j3ZPIQJANw.jpeg" /></figure><p>Step 4: Copy and Run the Installation Command in Powershell. Run<strong> </strong>Powershell with administrator privileges</p><pre>Invoke-WebRequest -Uri https://packages.wazuh.com/4.x/windows/wazuh-agent-4.14.2-1.msi -OutFile $env:tmp\wazuh-agent; msiexec.exe /i $env:tmp\wazuh-agent /q WAZUH_MANAGER=&#39;192.168.79.145&#39; WAZUH_AGENT_GROUP=&#39;default&#39; WAZUH_AGENT_NAME=&#39;Windows&#39;</pre><p>Step 5: Still in Powershell, run this command to start Wazuh agent</p><pre>NET START Wazuh</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Pip8lFhljVYCDMXbfWSTA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*PKtqPkx1byKQ7hbNWB3qSg.jpeg" /></figure><p><strong>Agent 2: Kali Linux</strong></p><p>On the Deploy new agent;</p><p><strong>Step 1: Select the Operating System</strong></p><ul><li>Choose <strong>Linux</strong> as the target OS.</li><li>For Kali Linux, choose DEB amd64.</li></ul><p><strong>Step 2: Assign Server Address</strong></p><ul><li>Enter your Wazuh manager’s IP address:</li></ul><p><strong>Step 3: Set Agent Name (Optional)</strong></p><ul><li>Enter a unique agent name (Kali)</li></ul><p><strong>Step 4: Copy and run the installation command</strong></p><ul><li>The UI generates a command tailored to your inputs. Run it in your Kali terminal:</li></ul><pre>wget https://packages.wazuh.com/4.x/apt/pool/main/w/wazuh-agent/wazuh-agent_4.14.2-1_amd64.deb &amp;&amp; sudo WAZUH_MANAGER=&#39;192.168.79.145&#39; WAZUH_AGENT_GROUP=&#39;default&#39; WAZUH_AGENT_NAME=&#39;Kali&#39; dpkg -i ./wazuh-agent_4.14.2–1_amd64.deb</pre><p><strong>Step 5: Start and Enable the Agent</strong></p><p>Run the following commands to activate the agent:</p><pre>sudo systemctl daemon-reload<br>sudo systemctl enable wazuh-agent<br>sudo systemctl start wazuh-agent</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/931/1*yXEvvJC8fb3hn9POaHkGdA.jpeg" /></figure><p><strong>Agent 3: Ubuntu</strong></p><p>Repeat the same steps as Agent 2</p><p><strong>Copy and run the installation command</strong></p><ul><li>The UI generates a command tailored to your inputs. Run it in your Ubuntu terminal:</li></ul><pre>wget https://packages.wazuh.com/4.x/apt/pool/main/w/wazuh-agent/wazuh-agent_4.14.2-1_amd64.deb &amp;&amp; sudo WAZUH_MANAGER=&#39;192.168.79.145&#39; WAZUH_AGENT_GROUP=&#39;default&#39; WAZUH_AGENT_NAME=&#39;Ubuntu&#39; dpkg -i ./wazuh-agent_4.14.2-1_amd64.deb</pre><p><strong>Start and Enable the Agent</strong></p><p>Run the following commands to activate the agent:</p><pre>sudo systemctl daemon-reload<br>sudo systemctl enable wazuh-agent<br>sudo systemctl start wazuh-agent</pre><p><strong>Dashboard of all Enrolled Agents</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NVedJg8zql98glxWBS5wZg.jpeg" /></figure><h3>Conclusion</h3><p>Through the deployment and configuration of Wazuh, I successfully set up a centralized security monitoring environment with multiple agents across Windows, Kali Linux, and Ubuntu. Wazuh provides real-time visibility into system events, log collection, and threat detection, making it a robust and open-source industry-standard SIEM solution. Beyond log monitoring, Wazuh can be leveraged for File Integrity Monitoring (FIM) to track changes in critical files and directories, detect unauthorized modifications, and alert security teams.</p><p>Additionally, it integrates seamlessly with other security tools and services, such as Syslog for centralized logging, SSH for remote administration, and custom APIs for automated workflows, enabling comprehensive and proactive security operations.</p><p>This setup serves as a foundation for future projects, where I plan to expand Wazuh’s capabilities with additional agents, advanced detection rules, integrations with threat intelligence feeds, and custom security automation workflows to simulate real-world SOC scenarios.</p><p>Many thanks to <a href="https://medium.com/u/f6fc6f913781">Efam Harris</a> 🫡</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=09e80e1821e9" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/wazuh-siem-deployment-with-multi-os-agents-09e80e1821e9">Wazuh SIEM Deployment with Multi-OS Agents</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Securing API Servers: What Cross-Origin Resource Sharing (CORS), Headers, and Error Messages Reveal…]]></title>
            <link>https://medium.com/@nanaaisha1030/securing-api-servers-what-cross-origin-resource-sharing-cors-headers-and-error-messages-reveal-3ea5c9c1cb8c?source=rss-234a77c1a817------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ea5c9c1cb8c</guid>
            <dc:creator><![CDATA[Aishat Olayinka Yusuf]]></dc:creator>
            <pubDate>Sun, 18 Jan 2026 15:54:09 GMT</pubDate>
            <atom:updated>2026-01-18T16:38:23.206Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Securing API Servers: What Cross-Origin Resource Sharing (CORS), Headers, and Error Messages Reveal About API Security</strong></h3><h3><strong>Introduction</strong></h3><p>Application Programming Interfaces (APIs) are exposed directly to the internet and are commonly consumed by browsers, mobile applications, and backend services. Because APIs often handle critical data and functionality, server-level security configuration plays a vital role in protecting them.</p><p>Even when application logic is implemented correctly, weaknesses in Cross-Origin Resource Sharing (CORS) policies, HTTP response headers, or error handling mechanisms can expose APIs to unnecessary risk. This article presents a walkthrough of a public API inspection to demonstrate what these configurations reveal about an API’s security posture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u0UmZ8t57-Z_THTxrTER7A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ffqqmznorWX67SWs9AjqmA.jpeg" /></figure><p><strong>API Reviewed and Walkthrough</strong></p><p>The API reviewed in this analysis is a public endpoint from the GitHub REST API:</p><pre>https://api.github.com/repos/github/docs</pre><p>The inspection was performed using Postman. A GET request was sent to the endpoint, and the returned response headers were analyzed. Although the request resulted in a 404 Not Found response, the server still returned full response headers, making it possible to analyze CORS configuration, security-related headers, and error handling behavior.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zJbBLZyKoo_s0TwUNhnnIg.jpeg" /></figure><p>A total of 22 response headers were returned by the server, from which relevant security and CORS-related headers were identified.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dd_8hWikQVCHBVR2cwS6kA.jpeg" /></figure><p><strong>What Cross-Origin Resource Sharing (CORS) Is</strong></p><p>Cross-Origin Resource Sharing (CORS) is a browser-enforced security mechanism that controls whether a web application running on one origin (defined by scheme, domain, and port) is allowed to read responses from an API hosted on a different origin.</p><p>CORS operates through specific HTTP response headers sent by the server. These headers instruct the browser which origins are trusted and which response headers may be accessed by client-side JavaScript. Importantly, CORS does not protect the API server itself; rather, it protects users by preventing malicious websites from reading cross-origin responses through a victim’s browser.</p><p><strong>CORS Configuration (Captured)</strong></p><p>To identify the Cross-Origin Resource Sharing (CORS) configuration of the API, response headers beginning with Access-Control- were examined.</p><p><strong>Observed CORS Headers</strong></p><ul><li><strong>Access-Control-Allow-Origin:</strong> *</li><li><strong>Access-Control-Expose-Headers:</strong> ETag, Link, Location, X-GitHub-OTP, X-RateLimit-*</li></ul><p><strong>Interpretation</strong></p><p>The Access-Control-Allow-Origin header is set to *, which instructs browsers to allow any origin to read responses from the API. This represents a permissive CORS policy that is commonly used for public, unauthenticated, read-only APIs.</p><p>The Access-Control-Expose-Headers header shows that the server explicitly limits which headers are accessible to client-side JavaScript, helping to reduce unnecessary information exposure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*buctcwcrJmM8nU6QLpLOzw.jpeg" /></figure><p><strong>Security-Related Response Headers (Captured)</strong></p><p>Among the 22 response headers returned by the API, several demonstrate deliberate server-side security hardening. Notable examples include:</p><ul><li><strong>Strict-Transport-Security</strong><br> Enforces HTTPS connections and protects against downgrade and man-in-the-middle attacks.</li><li><strong>X-Frame-Options: deny</strong><br> Prevents the API from being embedded in frames, reducing the risk of clickjacking attacks.</li><li><strong>X-Content-Type-Options: nosniff</strong><br> Prevents browsers from guessing content types, reducing the risk of MIME-type confusion and certain injection attacks.</li></ul><p>Additional headers such as Referrer-Policy further strengthen the API’s security posture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mJ23z4nKRJpRj7qOzPe6tw.jpeg" /></figure><p><strong>Error Message Handling (Captured)</strong></p><p>To evaluate error handling behavior, an invalid request was issued to the API.</p><p><strong>Observed Behavior</strong></p><ul><li><strong>Status Code:</strong> 404 Not Found</li><li><strong>Response Format:</strong> JSON</li><li><strong>Message:</strong> Generic “Not Found”</li><li><strong>Internal Details:</strong> None exposed</li></ul><p><strong>Interpretation</strong></p><p>The API correctly returns a 404 response when an invalid resource or method is requested. The error message is minimal and does not reveal backend logic, stack traces, or implementation details. This indicates secure error handling and reduces the risk of information disclosure to attackers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wKE2AMziFul9sCqTXUJUDQ.jpeg" /></figure><p><strong>Identified Insecure or Risky Configuration and Suggested Fix</strong></p><p><strong>Risky Configuration Identified</strong></p><ul><li><strong>Access-Control-Allow-Origin: *</strong></li></ul><p><strong>Why This Is Considered a Risk</strong></p><p>This configuration tells browsers that any origin is trusted to read responses from the API. While this is acceptable for the reviewed endpoint because it serves public data, it becomes risky if the same CORS policy is reused for endpoints that:</p><ul><li>Require authentication</li><li>Use cookies, session tokens, or API keys</li><li>Return user-specific or sensitive data</li></ul><p>In such scenarios, a malicious website could make cross-origin requests from a victim’s browser and read the responses, potentially leading to data leakage or unauthorized access. The risk is therefore contextual and architectural, rather than an immediate vulnerability.</p><p><strong>Suggested Fix</strong></p><p>For authenticated or sensitive endpoints:</p><ul><li>Restrict CORS to trusted origins only</li><li>Avoid wildcard origins when credentials are involved</li><li>Separate public and private APIs with distinct CORS policies</li></ul><p><strong>Example:</strong></p><p>Access-Control-Allow-Origin</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZXgB0qRahFr5T2abfH8DfA.jpeg" /></figure><p><strong>Why Server-Level Configuration Matters</strong></p><p>Server-level security controls provide protection independent of application logic. Headers such as HSTS, frame protection, and content-type enforcement mitigate common web-based attacks, while carefully designed CORS policies prevent unintended cross-origin data access. Secure error handling further limits information leakage during failure conditions, forming a critical part of a defense-in-depth strategy.</p><p><strong>Common Mistakes Teams Make</strong></p><p>Common mistakes when securing APIs include:</p><ul><li>Leaving permissive CORS policies enabled in production</li><li>Failing to audit exposed response headers</li><li>Returning verbose or debug-level error messages</li><li>Assuming public APIs do not require security hardening</li></ul><p><strong>What I Observed in the API Reviewed</strong></p><p>The GitHub REST API demonstrates strong security practices through the use of modern security headers and controlled error handling. However, the permissive CORS configuration illustrates how even well-secured APIs can introduce potential risk if server-level settings are not reviewed as API requirements and usage evolve.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ea5c9c1cb8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>