<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Projects on Chief Dennis' Blog</title><link>https://chiefdennis.github.io/projects/</link><description>Recent content in Projects on Chief Dennis' Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 01 Jun 2025 15:43:16 +0100</lastBuildDate><atom:link href="https://chiefdennis.github.io/projects/index.xml" rel="self" type="application/rss+xml"/><item><title> WPA/WPA2 Protocol: Packet format analysis and attacks against it</title><link>https://chiefdennis.github.io/projects/wpa_protocol_attacks/</link><pubDate>Sun, 01 Jun 2025 15:43:16 +0100</pubDate><guid>https://chiefdennis.github.io/projects/wpa_protocol_attacks/</guid><description>&lt;p>&lt;img src="https://chiefdennis.github.io/projects/wpa_protocol_attacks/image1.png" alt="">&lt;/p>
&lt;h2 id="identification-of-the-different-types-of-wpa-protocol-packets">
 Identification of the different types of WPA protocol packets.
 &lt;a class="heading-link" href="#identification-of-the-different-types-of-wpa-protocol-packets">
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
 &lt;span class="sr-only">Link to heading&lt;/span>
 &lt;/a>
&lt;/h2>
&lt;p>In this first phase, the analysis of a traffic capture corresponding to a WiFi network with WPA2-PSK authentication has been carried out. The tool used has been Wireshark, due to its ability to interpret and decompose network protocols in a detailed way. The purpose of this point is to identify the different types of packets involved in the WPA2 connection and authentication process, as well as to examine the most relevant fields of each and understand their function within the overall context of the capture.&lt;/p></description></item><item><title>Operational installation of a VPN with OpenVPN</title><link>https://chiefdennis.github.io/projects/operational_installation_openvpn/</link><pubDate>Tue, 20 May 2025 15:43:16 +0100</pubDate><guid>https://chiefdennis.github.io/projects/operational_installation_openvpn/</guid><description>&lt;p>&lt;img src="https://chiefdennis.github.io/projects/operational_installation_openvpn/image1.png" alt="">&lt;/p>
&lt;h2 id="introduction">
 Introduction
 &lt;a class="heading-link" href="#introduction">
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
 &lt;span class="sr-only">Link to heading&lt;/span>
 &lt;/a>
&lt;/h2>
&lt;p>Currently, Virtual Private Networks (VPNs) are a widely used solution to establish secure communication channels over public or shared networks. Its main objective is to offer confidentiality, authentication and integrity in the transmission of data between different devices, simulating a private local network by encrypting the information that circulates through the network.&lt;/p>
&lt;p>In this practice, a VPN has been implemented using OpenVPN, an open-source toolthat allows you to create encrypted tunnels based on the SSL/TLS protocol. The work environment is composed of three Kali Linux virtual machines:&lt;/p></description></item><item><title>WifiChallenge Lab CTF</title><link>https://chiefdennis.github.io/projects/wifi_challenge_lab/</link><pubDate>Thu, 15 May 2025 15:43:16 +0100</pubDate><guid>https://chiefdennis.github.io/projects/wifi_challenge_lab/</guid><description>&lt;p>&lt;img src="https://chiefdennis.github.io/projects/wifi_challenge_lab/image1.png" alt="">&lt;/p>
&lt;h2 id="introduction">
 Introduction
 &lt;a class="heading-link" href="#introduction">
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
 &lt;span class="sr-only">Link to heading&lt;/span>
 &lt;/a>
&lt;/h2>
&lt;p>This write-up summarizes the completion of the WiFiChallenge Lab, a practical cybersecurity exercise focused on wireless network security. Throughout the lab, various Wi-Fi attack techniques were explored and executed, including packet capture, handshake extraction, password cracking, and exploiting common vulnerabilities in WEP and WPA/WPA2 networks. The objective was to simulate real-world scenarios, enhance practical skills in wireless penetration testing, and deepen understanding of Wi-Fi security protocols and their weaknesses. This walkthrough outlines the methodology, tools used, challenges encountered, and key takeaways from the experience.&lt;/p></description></item><item><title>Reconnaissance of Vulnerable Software with Nessus and OpenVAS</title><link>https://chiefdennis.github.io/projects/reconnaisance_vulnerabilities_nessus_openvas/</link><pubDate>Sun, 23 Feb 2025 15:43:16 +0100</pubDate><guid>https://chiefdennis.github.io/projects/reconnaisance_vulnerabilities_nessus_openvas/</guid><description>&lt;p>&lt;strong>&lt;img src="#ZgotmplZ" alt="">&lt;/strong>&lt;/p>
&lt;p>&lt;a href="#introduction" >1. Introduction&lt;/a>&lt;/p>
&lt;p>&lt;a href="#analysis-tools" >2. Analysis Tools&lt;/a>&lt;/p>
&lt;p>&lt;a href="#scan-settings" >3. Scan Settings&lt;/a>&lt;/p>
&lt;p>&lt;a href="#nessus-scanning-parameters" >3.1. Nessus Scanning Parameters&lt;/a>&lt;/p>
&lt;p>&lt;a href="#openvas-scanning-parameters" >3.2. OpenVAS Scanning Parameters&lt;/a>&lt;/p>
&lt;p>&lt;a href="#analysis-process" >4. Analysis Process&lt;/a>&lt;/p>
&lt;p>&lt;a href="#running-the-scan-with-nessus" >4.1. Running the Scan with Nessus&lt;/a>&lt;/p>
&lt;p>&lt;a href="#running-the-scan-with-openvas" >4.2. Running the Scan with OpenVAS&lt;/a>&lt;/p>
&lt;p>&lt;a href="#comparison-of-results" >5. Comparison of Results&lt;/a>&lt;/p>
&lt;p>&lt;a href="#conclusions" >6. Conclusions&lt;/a>&lt;/p>
&lt;h2 id="introduction">
 Introduction
 &lt;a class="heading-link" href="#introduction">
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
 &lt;span class="sr-only">Link to heading&lt;/span>
 &lt;/a>
&lt;/h2>
&lt;p>The purpose of this report is to examine the security of a system through specialized tools for detecting vulnerabilities. To do this, exhaustive scans have been carried out using Nessus and OpenVAS on the &lt;a href="https://github.com/rapid7/metasploitable3" class="external-link" target="_blank" rel="noopener">Metasploitable3 virtual machine (Linux)&lt;/a>. After data collection, the findings will be analyzed and a detailed comparison of both tools will be made.&lt;/p></description></item><item><title>ARP and DNS spoofing with Bettercap</title><link>https://chiefdennis.github.io/projects/arp_and_dns_spoofing_bettercap/</link><pubDate>Sun, 09 Feb 2025 15:43:16 +0100</pubDate><guid>https://chiefdennis.github.io/projects/arp_and_dns_spoofing_bettercap/</guid><description>&lt;p>&lt;img src="https://chiefdennis.github.io/projects/arp_and_dns_spoofing_bettercap/Picture0.png" alt="">&lt;/p>
&lt;p>&lt;a href="#introduction" >1. Introduction&lt;/a>&lt;/p>
&lt;p>&lt;a href="#arp-spoofing-attack" >2. Attack Execution&lt;/a>&lt;/p>
&lt;p>&lt;a href="#arp-spoofing-attack" >2.1. ARP Poisoning&lt;/a>&lt;/p>
&lt;p>&lt;a href="#dns-spoofing-attack" >2.2. DNS Spoofing&lt;/a>&lt;/p>
&lt;p>&lt;a href="#fake-web-page-setup" >2.3. Fake Web Page Setup&lt;/a>&lt;/p>
&lt;p>&lt;a href="#credential-theft" >2.4. Credential Theft&lt;/a>&lt;/p>
&lt;p>&lt;a href="#stopping-the-attack" >3. Stopping the attack&lt;/a>&lt;/p>
&lt;p>&lt;a href="#conclusions" >4. Conclusions&lt;/a>&lt;/p>
&lt;h1 id="introduction">
 Introduction
 &lt;a class="heading-link" href="#introduction">
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
 &lt;span class="sr-only">Link to heading&lt;/span>
 &lt;/a>
&lt;/h1>
&lt;p>In the field of cybersecurity, analyzing vulnerabilities in local networks is a fundamental task for understanding potential threats and designing appropriate defense mechanisms. Among the most common attacks affecting the integrity and confidentiality of information in a network are ARP Spoofing and DNS Spoofing, techniques used to intercept, modify, and redirect traffic from devices connected to a LAN.&lt;/p></description></item><item><title>Steganographic techniques, analysis, and usage of S-Tools</title><link>https://chiefdennis.github.io/projects/steganography_and_s-tools/</link><pubDate>Wed, 01 Jan 2025 15:43:16 +0100</pubDate><guid>https://chiefdennis.github.io/projects/steganography_and_s-tools/</guid><description>&lt;h1 id="1--introduction">
 1.- Introduction
 &lt;a class="heading-link" href="#1--introduction">
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
 &lt;span class="sr-only">Link to heading&lt;/span>
 &lt;/a>
&lt;/h1>
&lt;p>This post is about steganographic tools and analysis techniques in search of hidden information. In this case, the S-Tools tool is used. We will also use a custom python script to help us analyze the images bit by bit in search for hidden information. Lastly, we will also perform a histogram analysis, coding another custom python script.&lt;/p>
&lt;p>S-Tools is a very powerful tool developed by Andy Brown. It allows you to hide messages using steganography in BMP, GIF, and WAV images. It is a very simple tool that allows drag-and-drop to process the relevant files. Additionally, it can encrypt the hidden information so that even if the message is discovered, the information cannot be decrypted without the password.&lt;/p></description></item><item><title>Configure and deploy Azure Firewall Manager Part 3: Test the Firewall</title><link>https://chiefdennis.github.io/projects/configure_deploy_azure_fw_manager_3/</link><pubDate>Thu, 11 Apr 2024 08:43:16 +0100</pubDate><guid>https://chiefdennis.github.io/projects/configure_deploy_azure_fw_manager_3/</guid><description>&lt;p>For part 3 of the series, test the firewall in two steps. First, we’ll test the application rule; then, we’ll test the network rule. To test the firewall rules, we’ll connect a remote desktop using the firewall’s public IP address, which is NATed to Workload-1. From there, we’ll use a browser to test the application rule and connect a remote desktop to Workload-2 to test the network rule. It is important to remember, as with all testing, firewall testing is essential to maintaining a secure network and mustn’t be overlooked.&lt;/p></description></item><item><title>Configure and deploy Azure Firewall Manager Part 2: Deploy the servers</title><link>https://chiefdennis.github.io/projects/configure_deploy_azure_fw_manager_2/</link><pubDate>Sat, 09 Mar 2024 08:43:16 +0100</pubDate><guid>https://chiefdennis.github.io/projects/configure_deploy_azure_fw_manager_2/</guid><description>&lt;p>For part 2 of the series, we will deploy our workloads/servers. This process is similar as to any virtual machine deployment in the Azure Cloud.&lt;/p>
&lt;h3 id="deploy-the-servers">
 Deploy the servers
 &lt;a class="heading-link" href="#deploy-the-servers">
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
 &lt;span class="sr-only">Link to heading&lt;/span>
 &lt;/a>
&lt;/h3>
&lt;p>Deploying servers involves setting up and preparing a server to host and run applications or services. When discussing deploying servers in a cloud environment, this process often consists of creating and configuring virtual machines, setting up network connectivity and security, and installing and configuring software, all done within the cloud provider&amp;rsquo;s management interface or using infrastructure as code (IaC) tools such as Terraform.&lt;/p></description></item><item><title>Configure and deploy Azure Firewall Manager Part 1: Create a hub and spoke architecture</title><link>https://chiefdennis.github.io/projects/configure_deploy_azure_fw_manager_1/</link><pubDate>Mon, 26 Feb 2024 08:43:16 +0100</pubDate><guid>https://chiefdennis.github.io/projects/configure_deploy_azure_fw_manager_1/</guid><description>&lt;p>Azure Firewall Manager is a central network security policy and route management service for globally distributed, software-defined perimeters. It can provide security management for two network architecture types, the secured virtual hub and the hub virtual network.&lt;/p>
&lt;p>Using Azure Firewall Manager, you can create secured virtual hubs to secure your cloud network traffic destined to private IP addresses, Azure PaaS, and the Internet. Traffic routing to the firewall is automated, so there&amp;rsquo;s no need to create user-defined routes (UDRs).&lt;/p></description></item><item><title>GPS NMEA TCP/IP stream to COM port via com0com and com2tcp</title><link>https://chiefdennis.github.io/projects/nmea_ip_to_google_earth/</link><pubDate>Fri, 29 Dec 2023 15:43:16 +0100</pubDate><guid>https://chiefdennis.github.io/projects/nmea_ip_to_google_earth/</guid><description>&lt;p>In this project we will explore how we can serve TCP/IP data coming in through an open port, and turn it into a virtual serial port or COM port.
In this case, I have a router that has an internal GPS that can serve the NMEA sentences to a given IP and port via TCP/IP. However, most programs that use GPS (like Google Earth) do it through a COM port. So, how can we &amp;rsquo;translate&amp;rsquo; the TCP/IP data into a serial COM stream?&lt;/p></description></item><item><title>Manage Entra ID users via Azure Portal</title><link>https://chiefdennis.github.io/projects/manage_entra_id_users/</link><pubDate>Sun, 03 Dec 2023 15:43:16 +0100</pubDate><guid>https://chiefdennis.github.io/projects/manage_entra_id_users/</guid><description>&lt;p>In this post we will learn how to create, edit and delete Microsoft Entra ID users. &lt;a href="https://www.microsoft.com/en-us/security/business/identity-access/microsoft-entra-id" class="external-link" target="_blank" rel="noopener">Microsoft Entra ID&lt;/a> is an integrated cloud identity and access solution, and a leader in the market for managing directories, enabling access to applications, and protecting identities.&lt;/p>
&lt;p>&lt;img src="https://chiefdennis.github.io/projects/manage_entra_id_users/Entra_ID_Diagram.avif" alt="image">&lt;/p>
&lt;p>To create a user, first navigate to Microsoft Entra ID in the Azure Portal.&lt;/p>
&lt;p>&lt;img src="https://chiefdennis.github.io/projects/manage_entra_id_users/1.png" alt="image">&lt;/p>
&lt;p>Then click on Users.&lt;/p>
&lt;p>&lt;img src="https://chiefdennis.github.io/projects/manage_entra_id_users/2.png" alt="image">&lt;/p>
&lt;p>You will be seeing the Users page. On the left hand menu, we can see the following tabs:&lt;/p></description></item></channel></rss>