<?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 Oyinkansola Talabi on Medium]]></title>
        <description><![CDATA[Stories by Oyinkansola Talabi on Medium]]></description>
        <link>https://medium.com/@oyinkansolatalabi_10825?source=rss-181fccee8a75------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jdudu8uBNZX8CKJUWd8_qQ@2x.jpeg</url>
            <title>Stories by Oyinkansola Talabi on Medium</title>
            <link>https://medium.com/@oyinkansolatalabi_10825?source=rss-181fccee8a75------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 05:26:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@oyinkansolatalabi_10825/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[From Detection to Remediation: Building a Complete Vulnerability Management Workflow with Nessus…]]></title>
            <link>https://medium.com/@oyinkansolatalabi_10825/from-detection-to-remediation-building-a-complete-vulnerability-management-workflow-with-nessus-9f71f6270b62?source=rss-181fccee8a75------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f71f6270b62</guid>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Oyinkansola Talabi]]></dc:creator>
            <pubDate>Wed, 13 May 2026 09:22:24 GMT</pubDate>
            <atom:updated>2026-05-13T09:22:24.915Z</atom:updated>
            <content:encoded><![CDATA[<h3>From Detection to Remediation: Building a Complete Vulnerability Management Workflow with Nessus Essentials and Ansible</h3><p>Every secure system has a story.</p><p>Sometimes, it is the story of a hidden vulnerability quietly waiting to be exploited. Other times, it is the story of a security analyst who finds that weakness before an attacker does. This project was both.</p><p>What began as a straightforward vulnerability assessment evolved into a full end-to-end simulation of how security teams discover, prioritize, remediate, and validate vulnerabilities across enterprise systems.</p><p>I intentionally deployed vulnerable software on a Linux server, configured automated email reporting, ran both credentialed and web application scans using Nessus Essentials, and remediated the findings using Ansible and package upgrades.</p><p>By the end of the exercise, multiple high and medium severity vulnerabilities affecting the operating system, monitoring tools, security applications, and the web server had been successfully resolved.</p><h3>Objective</h3><p>To;</p><ol><li>Assess the security posture of a linux system</li><li>Discover Vulnerabilities.</li><li>Understand the associated risk</li><li>Apply remediation</li><li>Verify the remediation.</li><li>Communicate the results.</li></ol><h3>Lab Environment</h3><p>The lab environment on which this vulnerability assessment and remediation was performed consists of;</p><ul><li>Ubuntu Server</li><li>OpenSSH</li><li>Nginx 1.15.5</li><li>Suricata</li><li>Splunk Universal Forwarder</li><li>Nessus Essentials</li><li>Ansible</li></ul><p>The environment was intentionally configured with outdated software versions to generate realistic findings during the assessment.</p><h3>Phase 1: Preparing the Target Environment</h3><p>Before any assessment could begin, the target server had to be configured with the services and applications that would later be scanned.</p><h3>Installing OpenSSH</h3><p>Credentialed scans require secure remote access, so I installed and enabled OpenSSH:</p><pre>sudo apt update<br>sudo apt install openssh-server -y<br>sudo systemctl enable --now ssh<br>ssh -V</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8cUAjNHWPbWwgMSSh3T3zg.png" /></figure><h3>Installing Nessus Essentials</h3><p>I installed Nessus Essentials to perform both internal credentialed scans and web application assessments.</p><p>After installation, I activated the scanner and completed the initial setup through the web interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I8hJVqwHgRW-7xzDKCsHkQ.png" /></figure><h3>Phase 2: Configuring the Credentialed Scan</h3><p>To give Nessus Essentials full visibility into the operating system, I configured an authenticated SSH scan.</p><p>Settings used:</p><ul><li>Authentication Type: SSH</li><li>Username: root</li><li>Privilege Escalation: su</li><li>Password Prompt: password</li></ul><p>This allowed Nessus to inspect installed packages, libraries, permissions, and system configurations from within the host rather than relying solely on externally visible services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*paR_nsuhKAvmDcEPeJ84vQ.png" /></figure><h3>Phase 3: Configuring Automated Email Reporting</h3><p>Before launching any scans, I configured Nessus to automatically send scan reports through Gmail SMTP. I wanted every assessment result to be delivered immediately after the scan completed, replicating how enterprise security teams automate reporting and notification workflows.</p><p>SMTP Settings Used</p><ul><li>SMTP Host: smtp.gmail.com</li><li>Encryption: SSL</li><li>Port: 465</li><li>Username: Gmail address</li><li>Password: Gmail App Password</li><li>From Address: Security mailbox</li><li>To Address: Recipient mailbox</li></ul><p>After sending a successful test email, Nessus was fully configured to deliver vulnerability reports automatically after each scan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R4qBWzlQYWvcSEFjGB_KuA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/585/1*CSKms6aa-Ll8xEHt5ES5Jw@2x.jpeg" /></figure><h3>Phase 4: Running the Internal Credentialed Scan</h3><p>With credentialed access and automated reporting configured, I launched the internal credentialed scan. The scan authenticated to the server and performed a deep inspection of installed software and libraries.</p><h3>Vulnerabilities Identified</h3><ul><li>Vim Multiple Vulnerabilities</li><li>Suricata Multiple Vulnerabilities</li><li>Splunk Universal Forwarder Multiple Vulnerabilities</li><li>Ubuntu libhtp Vulnerabilities</li></ul><p>These findings highlighted that critical issues can exist in utilities, security tools, and libraries — not just internet-facing applications.</p><p>Because automated email reporting was already enabled, detailed scan reports were delivered directly to my inbox as soon as each scan completed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zWLS-nlxADdru8W8oirvIg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/585/1*jH6Ba_tSvqxT3s9gRRHUjg@2x.jpeg" /></figure><h3>Phase 5: Deploying a Vulnerable Web Server</h3><p>To perform a dedicated web application assessment, I intentionally installed an outdated version of Nginx (version 1.15.5).</p><pre>wget http://nginx.org/download/nginx-1.15.5.tar.gz<br>tar -zxvf nginx-1.15.5.tar.gz<br>cd nginx-1.15.5<br>./configure<br>make<br>sudo make install<br>sudo /usr/local/nginx/sbin/nginx</pre><p>Although the server functioned normally, it contained known vulnerabilities that would be detected during the web scan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZXepDqVMKerczyImmJSXVw.png" /></figure><h3>Phase 6: Running the Web Application Scan</h3><p>I created a Web Application Test in Nessus Essentials and scanned the Nginx service.</p><p>The scan detected:</p><ul><li>Nginx Multiple Vulnerabilities</li><li>Associated CVEs and CVSS scores</li><li>Vendor remediation recommendations</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ASR6BeBPB_nx-N3pCOkRPw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/585/1*wrMh-oc13KW4jPwh-tniXA@2x.jpeg" /></figure><h3>Phase 7: Findings and Risk Analysis</h3><p>For every vulnerability, I documented and analyzed:</p><ul><li>Severity level</li><li>CVE identifiers</li><li>CVSS scores</li><li>Exploit availability</li><li>Exploit complexity</li><li>Vulnerability publication date</li><li>Patch publication date</li><li>NIST descriptions</li><li>Recommended remediation</li></ul><p>This transformed raw scan data into actionable intelligence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BoMblu5scfTnkYst6uVPxg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*R38sw6jfRYUZUJZ6EzYjOg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hUbTLOHEnKXmdQxW60va6A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/537/1*4_aW6kXI-5KBr2c-CGVZQw.png" /></figure><h3>Phase 8: Remediation and Patch Management</h3><p>Once the vulnerabilities were identified and prioritized, the next step was remediation. I followed the recommendations in the nessus report for addressing the vulnerabilities and patched each of the softwares found with vulnerabilities, one by one, using Ansible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AgxAH6VFq_rS1wTYsRCTXg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SbShr-7-ORX4XpYK7PuAOQ.png" /></figure><h3>Installing Ansible</h3><p>To automate remediation, I installed Ansible.</p><pre>sudo apt update<br>sudo apt install ansible -y<br>ansible --version</pre><h3>Automating patching with Ansible</h3><p>Although the vulnerabilities affected different applications — including Nginx, Vim, Suricata, Splunk Universal Forwarder, and Ubuntu libhtp—the remediation process followed the same structured workflow for each one. I created separate Ansible playbooks, each tailored to remove the outdated version of a specific application and install a patched release.</p><p>For every vulnerable software component, I followed the same five-step process.</p><h3>Step 1: Create a Dedicated YAML Playbook</h3><p>I created a separate YAML file for each affected application:</p><ul><li>update_nginx.yml</li><li>update_vim.yml</li><li>update_suricata.yml</li><li>update_splunk.yml</li><li>update_libhtp.yml</li></ul><pre>nano update_nginx.yml</pre><h3>Step 2: Define the Remediation Tasks</h3><p>Each playbook contained instructions to:</p><ol><li>Remove the vulnerable version.</li><li>Refresh the package repository metadata.</li><li>Install the latest secure version.</li><li>Start and enable the service if required.</li></ol><p>The playbooks followed this structure:</p><pre>---<br>- name: Patch Vulnerable Software<br>  hosts: localhost<br>  become: yes<br>tasks:<br>    - name: Remove outdated software<br>      # Removal task specific to the application<br>    - name: Update package cache<br>      apt:<br>        update_cache: yes<br>    - name: Install latest secure version<br>      # Installation task specific to the application<br>    - name: Start and enable service<br>      # Included only when the software runs as a service4</pre><p>Although the exact tasks varied depending on the application, the workflow remained consistent across all playbooks.</p><h3>Step 3: Save the Playbook</h3><p>After adding the automation tasks, I saved the YAML file and exited the editor.</p><h3>Step 4: Execute the Playbook</h3><p>I ran each playbook individually using:</p><pre>ansible-playbook update_nginx.yml --ask-become-pass</pre><p>The same command format was used for every playbook, changing only the filename.</p><h3>Step 5: Verify the Updated Versions</h3><p>After each playbook completed, I confirmed that the software had been upgraded successfully by checking its installed version.</p><p>This validation ensured that:</p><ul><li>The outdated package was removed.</li><li>The patched version was installed.</li><li>Services were running correctly.</li><li>The system was ready for rescanning</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/505/1*nfrhbf12S-8ZFMGuv2Fm8w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bxhzxC7H5mJdhdhfn6tYmQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SkUUxWttZx_QpN8xaPe5qQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WqBbrmxA4u4zBQbg9G7iWA.png" /></figure><h3>Final Reflection</h3><p>What made this project especially rewarding was experiencing vulnerability management as a complete operational cycle rather than a single scanning exercise.</p><p>The journey began with environment preparation and tool installation, progressed through credentialed scanning, automated reporting, risk analysis, and remediation, and concluded with validated proof that the environment was more secure than when I started.</p><p>Security is not just about identifying weaknesses.</p><p>It is about understanding them, fixing them efficiently, and demonstrating measurable improvement in an organization’s security posture.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f71f6270b62" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[End-to-End SOC Lab: Simulating and Detecting an SSH Brute Force Attack with Splunk]]></title>
            <link>https://medium.com/@oyinkansolatalabi_10825/end-to-end-soc-lab-simulating-and-detecting-an-ssh-brute-force-attack-with-splunk-f9554ccf79b8?source=rss-181fccee8a75------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9554ccf79b8</guid>
            <dc:creator><![CDATA[Oyinkansola Talabi]]></dc:creator>
            <pubDate>Sat, 24 Jan 2026 16:08:21 GMT</pubDate>
            <atom:updated>2026-01-24T16:08:21.982Z</atom:updated>
            <content:encoded><![CDATA[<p>SSH brute force attacks are one of the most common threats facing Linux servers exposed to the internet. As an aspiring SOC analyst, I wanted more than theory — I wanted to <strong>see how an attack looks in logs</strong>, understand how attackers behave, and practice detecting it manually using a SIEM.</p><p>This project documents a <strong>complete, step-by-step SOC lab</strong> where I:</p><ul><li>Simulated an SSH brute force attack</li><li>Collected authentication logs</li><li>Investigated the attack using Splunk</li></ul><h3>Lab Architecture Overview</h3><h3>Systems Used</h3><ul><li><strong>Kali Linux</strong> — Attacker machine</li><li><strong>Ubuntu Server</strong> — Target system running SSH and Splunk Enterprise</li><li><strong>Windows Host</strong> — Used to access Splunk Web through a browser</li></ul><p>Splunk Enterprise was installed <strong>directly on the Ubuntu Server</strong>, while the Splunk Web interface was accessed remotely from the Windows host.</p><h3>Step 1: Network Verification (All Machines)</h3><h3>On Ubuntu Server</h3><pre>ip a</pre><p>Note the IPv4 address.</p><h3>On Kali Linux</h3><pre>ping &lt;ubuntu_ip&gt;</pre><h3>Step 2: Prepare Ubuntu Server (SSH Target)</h3><h3>Install and enable SSH</h3><pre>sudo apt update<br>sudo apt install -y openssh-server<br>sudo systemctl enable ssh<br>sudo systemctl start ssh</pre><h3>Verify SSH is listening</h3><pre>sudo systemctl status ssh</pre><h3>Create test user</h3><pre>sudo adduser testuser</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*Wt2RfBLJYYjRhVXyfhjwAA.png" /></figure><h3>Step 3: Install Splunk Enterprise on Ubuntu Server</h3><h3>Download Splunk</h3><pre>wget -O splunk.deb https://download.splunk.com/products/splunk/releases/9.2.0/linux/splunk-9.2.0-linux-2.6-amd64.deb</pre><h3>Install</h3><pre>sudo dpkg -i splunk.deb</pre><h3>Start Splunk and accept license</h3><pre>sudo /opt/splunk/bin/splunk start --accept-license</pre><h3>Enable Splunk at boot</h3><pre>sudo /opt/splunk/bin/splunk enable boot-start</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*6e5qvhtO1T6TFjnTH0pEmg.png" /></figure><p>Splunk Web:</p><pre>http://&lt;ubuntu_ip&gt;:8000</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B-ziuUCczOfz0a_7LiUYWw.png" /></figure><h3>STEP 4: Install Splunk Universal Forwarder (Ubuntu)</h3><p>Even though Splunk runs locally, using a forwarder mirrors real SOC deployments.</p><h3>Download Forwarder</h3><pre>wget -O splunkforwarder.deb https://download.splunk.com/products/universalforwarder/releases/9.2.0/linux/splunkforwarder-9.2.0-linux-2.6-amd64.deb</pre><h3>Install</h3><pre>sudo dpkg -i splunkforwarder.deb</pre><h3>Start and accept license</h3><pre>sudo /opt/splunkforwarder/bin/splunk start --accept-license</pre><h3>Enable at boot</h3><pre>sudo /opt/splunkforwarder/bin/splunk enable boot-start</pre><h3>Step 5: Connect Forwarder to Splunk Enterprise</h3><pre>sudo /opt/splunkforwarder/bin/splunk add forward-server &lt;ubuntu_ip&gt;:9997</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OoMRnH-qSC6bkrFNsvrtDg.png" /></figure><p>Enable receiving on Splunk:</p><pre>sudo /opt/splunk/bin/splunk enable listen 9997</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XIl0Hd4-PmXx1mJJxgm8rA.png" /></figure><h3>Step 6: Configure Log Monitoring (auth.log)</h3><pre>sudo /opt/splunkforwarder/bin/splunk add monitor /var/log/auth.log</pre><p>Restart forwarder:</p><pre>sudo /opt/splunkforwarder/bin/splunk restart</pre><h3>Step 7: Verify Log Ingestion (Baseline)</h3><p>In Splunk Web:</p><pre>index=main source=&quot;/var/log/auth.log&quot;</pre><p>Confirm normal SSH activity.</p><h3>Step 8: Simulate SSH Brute Force Attack (Kali Linux)</h3><h3>Install Hydra (if needed)</h3><pre>sudo apt update<br>sudo apt install -y hydra</pre><h3>Launch brute force attack</h3><pre>hydra -l testuser -P /usr/share/wordlists/rockyou.txt ssh://&lt;ubuntu_ip&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/765/1*mVObbOYfgowzYa5nICiAJQ.png" /></figure><h3>Step 9: Detect Brute Force Activity in Splunk</h3><h3>Failed password search</h3><pre>index=main source=&quot;/var/log/auth.log&quot; &quot;Failed password&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yQC0f7W1ijN0aYqXSBrvCg.png" /></figure><h3>Step 10: Identify Attacker IP</h3><pre>index=main source=&quot;/var/log/auth.log&quot; &quot;Failed password&quot;<br>| stats count by src_ip</pre><p>This reveals the Kali Linux IP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c3DTrYdyOqo8uEkhEGIDmA.png" /></figure><h3>Step 11: Findings</h3><p>Indicators of brute force:</p><ul><li>High-frequency failures</li><li>Single source IP</li><li>Short intervals</li></ul><p>Mapped to <strong>MITRE ATT&amp;CK — Brute Force (T1110)</strong>.</p><h3>MITRE ATT&amp;CK Mapping</h3><p>To better understand how attackers behave and how this can be aligned to real-world threat intelligence frameworks, I mapped the brute force attack to the MITRE ATT&amp;CK Matrix.</p><h3>Tactic: Credential Access</h3><p>This attack falls under the <strong>Credential Access</strong> tactic because the attacker’s goal was to obtain valid login credentials by repeatedly guessing passwords for an SSH user account.</p><h3>Technique: Brute Force (T1110)</h3><p><strong>Technique ID:</strong> T1110 – Brute Force<strong> </strong><br>The attacker (Kali Linux) used <strong>automated password guessing</strong> against the Ubuntu Server’s SSH service to try multiple credentials rapidly until access is gained.</p><p><strong>Evidence:</strong></p><ul><li>Large number of authentication failures generated within a short time</li><li>Repeated “Failed password” log entries in /var/log/auth.log</li><li>One source IP responsible for most failures</li></ul><p><strong>Splunk query used to validate brute force behavior:</strong></p><pre>index=main source=&quot;/var/log/auth.log&quot; &quot;Failed password&quot;<br>| stats count by src_ip</pre><h3>Sub-Technique: Password Guessing (T1110.001)</h3><p><strong>Sub-Technique ID:</strong> T1110.001 – Password Guessing<br>Hydra was used to attempt multiple passwords for a known username using a password list (rockyou.txt), which fits the definition of password guessing.</p><p><strong>Evidence:</strong></p><ul><li>Rapid login attempts against a single account</li><li>Continuous SSH authentication failures</li><li>Attempt pattern consistent with an automated brute force tool</li></ul><p><strong>Splunk query used to observe failed attempts:</strong></p><pre>index=main source=&quot;/var/log/auth.log&quot; &quot;Failed password&quot;</pre><h3>Conclusion</h3><p>This project demonstrated an end-to-end SOC investigation workflow by simulating a real-world SSH brute force attack and detecting it through centralized log analysis in Splunk. Rather than relying on pre-built alerts, the focus was placed on <strong>understanding how attacks manifest in logs</strong>, how telemetry is collected, and how an analyst identifies malicious behavior through evidence.</p><p>By configuring SSH logging, deploying Splunk Enterprise and the Splunk Universal Forwarder, verifying ingestion, and analyzing authentication failures generated by an active attack, this lab mirrors the investigative tasks routinely performed by Tier 1 SOC analysts. The project reinforces that effective detection starts with <strong>proper log collection, visibility, and context</strong>, not just alert triggers.</p><p>More importantly, this lab reflects real operational challenges: installation issues, forwarding misconfigurations, and the need to validate data pipelines before any meaningful analysis can occur. Successfully resolving these issues is a core SOC skill and a prerequisite to reliable threat detection.</p><h3>Why This Project Matters</h3><p>SSH brute force attacks remain one of the most common and persistent threats against Linux systems, cloud workloads, and exposed servers. Despite their simplicity, they are frequently involved in larger attack chains that lead to unauthorized access, lateral movement, and data compromise.</p><p>This project matters because it focuses on <strong>fundamentals that many overlook</strong>:</p><ul><li>Logs do not magically appear in a SIEM — they must be <strong>intentionally collected and validated</strong></li><li>Attack detection begins with <strong>visibility</strong>, not automation</li><li>Analysts must be able to <strong>explain why an event is malicious</strong>, not just acknowledge an alert</li></ul><p>By building the entire pipeline from attack simulation to investigation, this project demonstrates practical blue team skills that are directly transferable to real SOC environments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9554ccf79b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>