<?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 Yunusemreerten on Medium]]></title>
        <description><![CDATA[Stories by Yunusemreerten on Medium]]></description>
        <link>https://medium.com/@yunusemreerten08?source=rss-7493fd34a983------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*1uE6N2FThJHtRal7</url>
            <title>Stories by Yunusemreerten on Medium</title>
            <link>https://medium.com/@yunusemreerten08?source=rss-7493fd34a983------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:29:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yunusemreerten08/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[Wireless Network Defense: A Practical Guide to Kismet, Wireshark, and Bettercap]]></title>
            <link>https://medium.com/@yunusemreerten08/wireless-network-defense-a-practical-guide-to-kismet-wireshark-and-bettercap-0d4a5b0bb3c6?source=rss-7493fd34a983------2</link>
            <guid isPermaLink="false">https://medium.com/p/0d4a5b0bb3c6</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[wireshark]]></category>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[kali-linux]]></category>
            <category><![CDATA[wireless-security]]></category>
            <dc:creator><![CDATA[Yunusemreerten]]></dc:creator>
            <pubDate>Thu, 12 Nov 2026 21:41:11 GMT</pubDate>
            <atom:updated>2026-11-12T21:41:11.373Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Discovering wireless networks, investigating security alerts, and comparing Wi-Fi security configurations in a hands-on Kali Linux laboratory.</em></p><h3>1. Introduction</h3><p>Wireless networks are an essential part of modern communication. Homes, businesses, universities, and public environments rely on Wi-Fi to provide convenient network access.</p><p>However, wireless connectivity also introduces unique security challenges. Unlike wired networks, wireless networks transmit information through radio signals, allowing devices within range to observe wireless transmissions.</p><p>For cybersecurity professionals, understanding what is happening in the wireless environment is an important part of protecting it.</p><p>In my previous article, I explored WPA3-Personal and Wi-Fi Enhanced Open, focusing on SAE authentication, Opportunistic Wireless Encryption (OWE), and wireless key establishment.</p><p>In this article, I take a different approach. Instead of focusing only on how wireless security protocols work, I examine how security professionals can discover, monitor, and investigate wireless networks using practical security tools.</p><p>The three tools covered in this article are:</p><ul><li><strong>Kismet:</strong> Wireless network discovery, monitoring, and intrusion detection.</li><li><strong>Wireshark:</strong> Detailed network packet capture and protocol analysis.</li><li><strong>Bettercap:</strong> Wireless reconnaissance and security assessment.</li></ul><p>To demonstrate their capabilities, I created an isolated virtual Wi-Fi laboratory using Kali Linux.</p><p>During the experiments, I discovered wireless access points and clients, investigated a recurring security alert, and compared three different wireless security configurations.</p><p>The results also revealed an important lesson:</p><p><strong>A security tool’s alert or classification should not automatically be treated as the final answer. Security findings need to be validated using additional evidence.</strong></p><h3>2. Why Are Wireless Network Defense Tools Important?</h3><p>Wireless security begins with understanding the environment that needs to be protected.</p><p>Imagine a company operating several authorized wireless access points. An employee connects an unauthorized wireless device to the corporate network without informing the IT department.</p><p>This device could introduce a security weakness, create an unexpected connection path, or expose internal resources through an insecure wireless configuration.</p><p>Without wireless monitoring, security administrators may not immediately discover it.</p><p>Wireless defense tools can help identify:</p><ul><li>Unauthorized or rogue access points.</li><li>Weak or outdated wireless security protocols.</li><li>Unexpected wireless clients.</li><li>Suspicious management frame activity.</li><li>Changes in advertised security configurations.</li><li>Potential wireless security policy violations.</li><li>Wireless coverage and channel-related issues.</li></ul><p>However, discovering a device or generating an alert does not automatically prove that an attack is taking place.</p><p>For example, an unfamiliar BSSID could belong to a legitimate access point that was recently installed. Similarly, a security alert could be caused by an unusual but harmless protocol implementation.</p><p>This is why wireless defense requires both monitoring and investigation.</p><h3>3. From Legacy to Modern Wireless Security Tools</h3><p>Several tools played important roles in the historical development of wireless security assessment.</p><h3>Aircrack-ng</h3><p>Aircrack-ng is a well-known suite of command-line tools for wireless security assessment.</p><p>Its utilities include airmon-ng for monitor-mode management, airodump-ng for wireless packet capture, and aircrack-ng for evaluating supported WEP and WPA/WPA2-PSK security mechanisms.</p><p>Aircrack-ng remains useful in many wireless security laboratories, particularly when studying legacy protocols and password security.</p><p>However, its traditional password assessment capabilities should not be interpreted as a universal method for compromising modern wireless security protocols such as WPA3-SAE.</p><h3>NetStumbler</h3><p>NetStumbler is a historical Windows-based wireless network discovery application.</p><p>It was primarily designed to identify wireless networks and collect information such as SSIDs, channels, and signal measurements.</p><p>Its graphical interface made wireless discovery and basic site surveys accessible to users.</p><p>However, its well-known 0.4.0 release dates back to 2004. The tool predates modern Wi-Fi security technologies such as WPA3 and Enhanced Open.</p><h3>KisMAC</h3><p>KisMAC is a historical wireless network discovery and monitoring application developed for Mac OS X.</p><p>It provided graphical wireless discovery, passive monitoring with compatible hardware, and additional wireless security assessment capabilities.</p><p>Although it was an important tool in earlier wireless security environments, the project is no longer actively maintained.</p><h3>Why Focus on Kismet, Wireshark, and Bettercap?</h3><p>Rather than attempting to reproduce experiments using outdated operating systems and legacy wireless drivers, I selected three tools that are suitable for contemporary wireless security workflows.</p><ul><li><strong>Kismet:</strong> Wireless monitoring and intrusion detection.</li><li><strong>Wireshark:</strong> Packet-level protocol analysis.</li><li><strong>Bettercap:</strong> Wireless reconnaissance and security assessment.</li></ul><p>These tools complement one another.</p><p>Kismet can identify devices and generate security alerts. Wireshark can examine the packets behind network activity. Bettercap can provide another perspective on wireless discovery and security classification.</p><p>Together, they support a practical wireless defense workflow.</p><h3>4. Essential Wireless Security Concepts</h3><p>Before exploring the tools, it is useful to understand several wireless networking concepts that appear throughout the experiments.</p><h3>SSID — Service Set Identifier</h3><p>The SSID is the name of a wireless network.</p><p>For example, a network may be named Company-WiFi, Guest-Network, or WPA3-Lab.</p><p>Multiple access points can advertise the same SSID.</p><h3>BSSID — Basic Service Set Identifier</h3><p>The BSSID identifies a particular wireless basic service set.</p><p>It is typically represented as a MAC address.</p><p>While the SSID represents the network name, the BSSID helps distinguish individual access points or wireless service sets.</p><h3>Channel and Frequency</h3><p>Wireless devices communicate over radio frequencies organized into channels.</p><p>For example, channel 6 in the 2.4 GHz band corresponds to 2.437 GHz.</p><p>Monitoring the correct channel is important because an interface listening on one channel may miss transmissions occurring on another.</p><h3>RSSI — Received Signal Strength Indicator</h3><p>RSSI provides information about the received wireless signal level.</p><p>It is commonly displayed in dBm.</p><p>In a physical wireless environment, RSSI can help investigate coverage and signal conditions. However, it is influenced by many factors and should not be treated as an exact distance measurement.</p><p>In our simulated laboratory, the reported signal values are not physical radio measurements.</p><h3>Monitor Mode</h3><p>Monitor mode allows a compatible wireless interface to observe raw IEEE 802.11 frames on its configured channel.</p><p>Unlike ordinary managed mode, it does not require the monitoring device to associate with the observed access point.</p><p>This makes monitor mode useful for wireless packet capture and security monitoring.</p><h3>Protected Management Frames (PMF)</h3><p>PMF helps protect certain robust management frames against forgery and unauthorized modification.</p><p>The mechanism is also referred to as Management Frame Protection (MFP).</p><p>WPA3 requires PMF for WPA3 associations.</p><p>Two important RSN capability flags are:</p><ul><li><strong>MFPC — Management Frame Protection Capable:</strong> Indicates support for management frame protection.</li><li><strong>MFPR — Management Frame Protection Required:</strong> Indicates that management frame protection is required.</li></ul><p>These flags become particularly important during the security alert investigation later in this article.</p><h3>5. Understanding the Three Security Tools</h3><h3>Kismet</h3><p>Kismet is a wireless network discovery, monitoring, and intrusion detection platform.</p><p>It can observe supported wireless technologies, identify devices, collect network characteristics, and generate alerts about suspicious or unexpected activity.</p><p>For Wi-Fi security monitoring, Kismet can provide visibility into access points, clients, channels, advertised encryption mechanisms, and observed packet statistics.</p><p>Its web interface provides a centralized view of the monitored wireless environment.</p><p>In this laboratory, Kismet is used for device discovery and security alert analysis.</p><h3>Wireshark</h3><p>Wireshark is a network protocol analyzer that allows users to inspect captured packets in detail.</p><p>When provided with IEEE 802.11 traffic, Wireshark can examine wireless management, control, and data frames.</p><p>Examples include:</p><ul><li>Beacon frames.</li><li>Probe Request and Probe Response frames.</li><li>Authentication frames.</li><li>Association Request and Association Response frames.</li><li>EAPOL messages.</li><li>RSN Information Elements.</li></ul><p>Wireshark is especially useful when a security analyst needs to validate a finding at the protocol level.</p><p>In this article, I use Wireshark to investigate a management frame protection alert generated by Kismet.</p><h3>Bettercap</h3><p>Bettercap is a network reconnaissance and security assessment framework with support for wireless monitoring and testing.</p><p>Its Wi-Fi module can discover access points and observed clients, display wireless security information, and support additional authorized assessment functions.</p><p>Unlike Kismet, Bettercap provides an interactive command-line workflow for its Wi-Fi reconnaissance features.</p><p>In this laboratory, I use Bettercap only for wireless discovery and security configuration comparison.</p><p>No deauthentication attacks, password attacks, or unauthorized wireless testing are performed.</p><h3>6. Building the Virtual Wireless Security Laboratory</h3><p>The experiments were conducted using Kali Linux inside VMware Workstation.</p><p>Instead of relying on a physical Wi-Fi adapter, I used the Linux mac80211_hwsim kernel module to create simulated IEEE 802.11 radios.</p><p>This approach allowed me to investigate wireless protocols without transmitting real radio signals or interacting with neighboring wireless networks.</p><h3>Laboratory Components</h3><p>The following tools and components were used to build the virtual wireless security laboratory:</p><ul><li><strong>Kali Linux:</strong> The operating system used for wireless security testing and analysis.</li><li><strong>VMware Workstation:</strong> The virtualization platform hosting the Kali Linux environment.</li><li><strong>mac80211_hwsim:</strong> A Linux kernel module used to simulate IEEE 802.11 wireless radios.</li><li><strong>hostapd:</strong> Used to create and configure virtual wireless access points.</li><li><strong>wpa_supplicant:</strong> Used to establish wireless client connections.</li><li><strong>Kismet (2025.09.R1):</strong> Used for wireless network discovery, monitoring, and intrusion detection.</li><li><strong>Wireshark:</strong> Used for detailed packet-level analysis and security alert verification.</li><li><strong>Bettercap (v2.41.5):</strong> Used for wireless reconnaissance and security configuration comparison.</li></ul><h3>Step 1: Creating Three Wireless Radios</h3><p>I loaded the simulation module using:</p><pre>modprobe mac80211_hwsim radios=3</pre><p>I then verified the interfaces:</p><pre>iw dev</pre><p>The laboratory used the following interfaces:</p><ul><li><strong>wlan0:</strong> Simulated wireless access point, configured using hostapd.</li><li><strong>wlan1:</strong> Simulated wireless client, connected using wpa_supplicant.</li><li><strong>wlan2:</strong> Dedicated wireless interface for monitoring and reconnaissance with Kismet and Bettercap.</li><li><strong>hwsim0:</strong> Additional virtual packet capture interface used for IEEE 802.11 packet analysis in Wireshark.</li></ul><p>During its operation, Kismet automatically created a monitor-mode interface named <strong>wlan2mon</strong> from wlan2 to capture wireless traffic without connecting to the access point.</p><h3>Step 2: Preparing the Network Interfaces</h3><p>To prevent NetworkManager from interfering with the laboratory interfaces, I configured them as unmanaged:</p><pre>nmcli device set wlan0 managed no<br>nmcli device set wlan1 managed no<br>nmcli device set wlan2 managed no</pre><h3>Step 3: Reusing the Previous Laboratory</h3><p>I reused the WPA3 and OWE configuration files from my previous wireless security experiment.</p><p>These files were stored in:</p><pre>/etc/wifi-lab/</pre><p>The existing configuration files were:</p><pre>wpa3.conf<br>wpa3-client.conf<br>owe.conf<br>owe-client.conf</pre><p>The laboratory later included a traditional open wireless network for comparison.</p><h3>7. Lab 1 — Wireless Network Discovery with Kismet</h3><p>The first experiment focused on discovering a wireless access point and its associated client using Kismet.</p><h3>Step 1: Starting the WPA3 Access Point</h3><p>I started the simulated WPA3-Personal access point:</p><pre>hostapd /etc/wifi-lab/wpa3.conf</pre><p>The access point was configured with:</p><ul><li>SSID: WPA3-Lab</li><li>Channel: 6</li><li>Authentication and key management: SAE</li><li>Pairwise encryption: CCMP</li><li>Protected Management Frames: Required</li></ul><h3>Step 2: Starting Kismet</h3><p>In a separate terminal, I launched Kismet with the third simulated radio:</p><pre>kismet -c &#39;wlan2:type=linuxwifi,name=Lab-Monitor,channel_hop=false,channel=6&#39;</pre><p>The source configuration selected the Linux Wi-Fi capture driver and restricted monitoring to channel 6.</p><p>Kismet successfully configured the wlan2mon interface and started collecting wireless frames.</p><p>I then opened its web interface at:</p><pre>http://localhost:2501</pre><h3>Step 3: Discovering the Wireless Access Point</h3><p>Kismet successfully identified the WPA3-Lab network.</p><p>The device list displayed the following information:</p><ul><li><strong>SSID:</strong> WPA3-Lab</li><li><strong>Device Type:</strong> Wi-Fi AP</li><li><strong>Encryption:</strong> WPA3, WPA3-SAE, AES-CCMP</li><li><strong>Channel:</strong> 6</li><li><strong>Signal Strength:</strong> -30 dBm</li><li><strong>Connected Clients:</strong> 0</li></ul><p>At this stage, no client had been connected to the access point.</p><p>The results confirmed that Kismet could successfully discover the simulated access point and identify its advertised security configuration without connecting to the network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s3GZZRfP5DtqdrAimkMEgA.png" /><figcaption><em>Figure 1 — Kismet successfully detecting a simulated WPA3-Personal access point, including its SAE authentication mechanism, AES-CCMP encryption, and operating channel.</em></figcaption></figure><h3>Step 4: Connecting and Discovering a Wireless Client</h3><p>To generate additional wireless activity, I started the simulated client:</p><pre>wpa_supplicant -i wlan1 -D nl80211 \<br>-c /etc/wifi-lab/wpa3-client.conf</pre><p>After the connection was established, Kismet detected a second wireless device.</p><p>The client count associated with WPA3-Lab increased from zero to one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wKYfvZXc2NRfLwF-agI7xQ.png" /><figcaption><em>Figure 2 — Kismet detecting a wireless access point and its associated client through passive IEEE 802.11 monitoring in a simulated Wi-Fi environment.</em></figcaption></figure><p>This demonstrated that Kismet could identify both the access point and an observed client without the monitoring interface joining the network.</p><h3>Security Perspective</h3><p>In an organizational environment, this capability can help build a wireless device inventory.</p><p>Administrators can compare observed access points and clients against authorized infrastructure records.</p><p>Unexpected devices can then be investigated further.</p><p>However, an unexpected device is not automatically a malicious device. Its identity and role must be validated before reaching a security conclusion.</p><h3>8. Detailed Access Point Analysis with Kismet</h3><p>After discovering the access point, I opened its device information panel.</p><p>Kismet displayed several characteristics of the monitored device.</p><h3>Device Information</h3><p>The access point information included the following details:</p><ul><li><strong>Network Name:</strong> WPA3-Lab</li><li><strong>MAC Address / BSSID:</strong> 02:00:00:00:00:00</li><li><strong>Device Type:</strong> Wi-Fi AP</li><li><strong>Channel:</strong> 6</li><li><strong>Main Frequency:</strong> 2.437 GHz</li><li><strong>Manufacturer:</strong> Unknown</li></ul><p>The interface also displayed a packet frequency distribution graph.</p><p>Since the experiment was restricted to channel 6, the observed packets were concentrated at 2.437 GHz.</p><p>This information demonstrates how Kismet can identify and analyze wireless access point characteristics without requiring a direct connection to the network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/629/1*N9lxZsqhzWvMDKOQLkyTcg.png" /><figcaption><em>Figure 3.1 — Detailed access point information collected by Kismet, including the BSSID, operating channel, frequency, and packet frequency distribution.</em></figcaption></figure><h3>Wireless Packet Statistics</h3><p>The IEEE 802.11 information panel provided additional packet statistics.</p><p>At the time of observation, the recorded values were:</p><ul><li><strong>Total Packets:</strong> 5,339</li><li><strong>LLC/Management Packets:</strong> 5,337</li><li><strong>Data Packets:</strong> 2</li><li><strong>Error/Invalid Packets:</strong> 0</li></ul><p>The management-related packet count was significantly higher than the data packet count.</p><p>This was consistent with the laboratory’s limited data traffic and the access point’s repeated transmission of management frames, including Beacon frames.</p><p>Beacon frames advertise the presence of a wireless network and contain information about its capabilities, such as the SSID, supported data rates, and security configuration.</p><p>Kismet uses these frames to collect information about the wireless environment and identify observed access points.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*xt0uPVwUWVjHgCf2IWqKZA.png" /><figcaption><em>Figure 3.2 — IEEE 802.11 packet statistics in Kismet, showing the distribution of management and data frames captured from the simulated WPA3 access point.</em></figcaption></figure><h3>Laboratory Observation</h3><p>The displayed RSSI and access point uptime values were influenced by the simulated environment.</p><p>In particular, an unusually large uptime value appeared in the interface.</p><p>These measurements should not be interpreted as the actual operating time of a physical access point or as real-world radio coverage measurements.</p><h3>9. Kismet Wireless Intrusion Detection: Investigating Security Alerts</h3><p>The next stage of the experiment focused on Kismet’s security alerts.</p><p>When I opened the Alerts panel, I discovered two warnings that had already been generated.</p><p><strong>Alert 1 — ROOTUSER</strong></p><ul><li><strong>Classification:</strong> SYSTEM</li><li><strong>Severity:</strong> HIGH</li><li><strong>Description:</strong> Kismet was running with root privileges, which increases the potential security impact of software vulnerabilities.</li></ul><p><strong>Alert 2 — NOCLIENTMFP</strong></p><ul><li><strong>Classification:</strong> SPOOF</li><li><strong>Severity:</strong> LOW</li><li><strong>Description:</strong> Kismet reported that the observed wireless client did not support Management Frame Protection (MFP), potentially making it more vulnerable to spoofed management frames.</li></ul><p>These two alerts represent different types of security concerns. The first relates to application privileges, while the second concerns a potential wireless security issue that requires further investigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lj2EliS2zrHnZHd-gLeSXA.png" /><figcaption><em>Figure 4 — Kismet security alerts identifying elevated application privileges (ROOTUSER) and a potential management frame protection issue (NOCLIENTMFP) in the simulated wireless environment.</em></figcaption></figure><h3>Alert 1: ROOTUSER</h3><p>The ROOTUSER alert indicated that Kismet was running with root privileges.</p><p>Although elevated privileges may be needed for certain wireless interface operations, running the entire monitoring application as root increases the potential impact of software vulnerabilities or unexpected behavior.</p><p>This relates to the security principle of <strong>Least Privilege</strong>.</p><p>Applications should operate with only the permissions needed to perform their tasks.</p><p>In a production environment, Kismet should be deployed with an appropriate non-root server configuration and the necessary permissions for its capture components.</p><p>In this isolated laboratory, I continued with the existing root session for the experiment.</p><h3>Alert 2: NOCLIENTMFP</h3><p>The second alert reported that the observed wireless client did not support Management Frame Protection.</p><p>The alert referenced:</p><pre>Access Point: 02:00:00:00:00:00<br>Client:       02:00:00:00:01:00</pre><p>This was an unexpected result.</p><p>The WPA3-Personal access point and client had both been configured to require PMF.</p><p>The relevant configuration parameter was:</p><pre>ieee80211w=2</pre><p>According to the laboratory configuration, management frame protection should have been required.</p><p>Rather than immediately accepting the alert as a confirmed vulnerability, I decided to investigate it further.</p><p>This became the central security investigation of the laboratory.</p><h3>10. Lab 2 — Validating a Kismet Security Alert with Wireshark</h3><p>A security alert is a starting point for investigation, not necessarily a final conclusion.</p><p>To investigate NOCLIENTMFP, I used two independent sources of evidence:</p><ol><li>The client connection status reported by wpa_supplicant.</li><li>The RSN capability information contained in an actual IEEE 802.11 Association Request frame.</li></ol><h3>Step 1: Verifying the Client Connection</h3><p>I first inspected the client connection:</p><pre>wpa_cli -i wlan1 status</pre><p>The output included:</p><pre>ssid=WPA3-Lab<br>key_mgmt=SAE<br>pairwise_cipher=CCMP<br>group_cipher=CCMP<br>pmf=2<br>mgmt_group_cipher=BIP<br>sae_group=19<br>wpa_state=COMPLETED</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/421/1*TD9P5Ve2TLJaKaQR03XD4g.png" /><figcaption><em>Figure 5 — Verification of the WPA3-Personal client connection showing SAE authentication, mandatory Protected Management Frames, BIP protection, and a completed connection state.</em></figcaption></figure><p>Several fields were particularly important.</p><p><strong>key_mgmt=SAE</strong></p><p>This confirmed that the connection used SAE, the password-authenticated key agreement mechanism of WPA3-Personal.</p><p><strong>pmf=2</strong></p><p>This indicated that the client reported management frame protection as required.</p><p><strong>mgmt_group_cipher=BIP</strong></p><p>BIP, or Broadcast/Multicast Integrity Protocol, provides integrity and authenticity protection for applicable group-addressed robust management frames.</p><p><strong>wpa_state=COMPLETED</strong></p><p>This indicated that the wireless connection and key establishment process had completed successfully.</p><p>Together, these results provided evidence that the current connection was using WPA3 with PMF.</p><p>However, I wanted to verify this behavior directly in the wireless traffic.</p><h3>Step 2: Capturing IEEE 802.11 Traffic</h3><p>I enabled the additional virtual capture interface:</p><pre>ip link set hwsim0 up</pre><p>I then started Wireshark and captured packets from hwsim0.</p><p>To isolate Association Request frames, I applied the following display filter:</p><pre>wlan.fc.type_subtype == 0x00</pre><p>This filter displays IEEE 802.11 Association Request frames.</p><p>These frames are particularly useful because they contain information about the client’s selected security capabilities.</p><h3>Step 3: Reconnecting the Wireless Client</h3><p>While Wireshark was capturing traffic, I disconnected and reconnected the client:</p><pre>wpa_cli -i wlan1 disconnect<br>wpa_cli -i wlan1 reconnect</pre><p>This generated a new wireless association exchange.</p><p>Wireshark captured an Association Request sent from the simulated client to the WPA3 access point.</p><h3>Step 4: Analyzing the RSN Information Element</h3><p>I selected frame 407 and expanded the wireless management parameters:</p><pre>IEEE 802.11 Wireless Management<br>  Tagged parameters<br>    RSN Information<br>      RSN Capabilities</pre><p>The captured packet contained the following information:</p><ul><li><strong>Source:</strong> 02:00:00:00:01:00</li><li><strong>Destination:</strong> 02:00:00:00:00:00</li><li><strong>SSID:</strong> WPA3-Lab</li><li><strong>Pairwise Cipher:</strong> AES (CCM)</li><li><strong>Authentication and Key Management (AKM):</strong> SAE (SHA256)</li><li><strong>RSN Capabilities:</strong> 0x00c0</li><li><strong>MFPC (Management Frame Protection Capable):</strong> Capable (1)</li><li><strong>MFPR (Management Frame Protection Required):</strong> Required (1)</li><li><strong>Group Management Cipher:</strong> BIP (128)</li></ul><p>The most important observations were the two Management Frame Protection capability flags.</p><p>These findings provided packet-level evidence that the client supported and required Protected Management Frames, despite the NOCLIENTMFP alert generated by Kismet.</p><pre>Management Frame Protection Required: Required</pre><pre>Management Frame Protection Capable: Capable</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qsdWj0SV5mpKm4m2UIgv4w.png" /><figcaption><em>Figure 6 — Wireshark analysis of a WPA3-Personal Association Request confirming that Management Frame Protection is both supported (MFPC=1) and required (MFPR=1).</em></figcaption></figure><p>The two capability flags indicated that the client advertised both support for PMF and a requirement to use it.</p><p>This packet-level evidence was consistent with the client connection status.</p><h3>Understanding the RSN Capability Flags</h3><p>MFPC and MFPR represent different aspects of management frame protection.</p><p>A device can advertise support for PMF without requiring every compatible connection to use it.</p><p>In our experiment, both flags were set.</p><ul><li><strong>MFPC (1):</strong> Management Frame Protection is supported.</li><li><strong>MFPR (1):</strong> Management Frame Protection is required.</li></ul><p>The combined RSN Capabilities value was 0x00c0.</p><p>These observations did not support the interpretation that the client lacked PMF capability.</p><h3>11. Reproducing the NOCLIENTMFP Alert</h3><p>After completing the Wireshark analysis, I returned to Kismet’s Alerts panel.</p><p>The objective was to determine whether the alert would appear again after reconnecting the client.</p><p>A second NOCLIENTMFP alert had been generated.</p><p>The two recorded events were:</p><ul><li><strong>Initial NOCLIENTMFP Alert:</strong> 15:21:26 — Kismet generated the first warning during the initial WPA3 client connection.</li><li><strong>Repeated NOCLIENTMFP Alert:</strong> 15:34:00 — Kismet generated the same warning after disconnecting and reconnecting the wireless client.</li></ul><p>Both alerts referenced the same simulated access point and client.</p><p>The repeated occurrence of the alert demonstrated that the behavior was reproducible within the laboratory environment, providing additional evidence for the ongoing security investigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GLkdb5o1M9FRr7ZQhilXTQ.png" /><figcaption><em>Figure 7 — Kismet reproducing the NOCLIENTMFP alert after reconnecting the WPA3-Personal client, despite packet-level evidence confirming management frame protection capability and requirements.</em></figcaption></figure><h3>Interpreting the Results</h3><p>The investigation produced three important observations:</p><ul><li>Kismet reported a potential MFP issue on two occasions.</li><li>The client status showed a completed SAE connection with required PMF.</li><li>Wireshark confirmed MFPC=1 and MFPR=1 in the Association Request.</li></ul><p>Based on these observations, I classified the alert as a <strong>reproducible potential false positive within this laboratory environment</strong>.</p><p>However, this conclusion has an important limitation.</p><p>The Association Request examined in Wireshark was generated during a new connection attempt. Although Kismet also produced another alert during the reconnection experiment, I did not establish which exact captured frame triggered that alert or trace the relevant detection logic in Kismet’s source code.</p><p>Therefore, I cannot determine the precise technical cause of the warning.</p><p>It may involve packet interpretation, device-state tracking, or behavior specific to the simulated environment. These are possible explanations, not experimentally verified conclusions.</p><p>The results also do not establish that every NOCLIENTMFP alert produced by Kismet is a false positive.</p><h3>Why This Investigation Matters</h3><p>This experiment demonstrates an important principle of security operations.</p><p>Security alerts must be investigated in context.</p><p>A monitoring tool may report suspicious behavior, but analysts should validate the finding using packet captures, endpoint information, network configuration, and other available evidence.</p><p>In this laboratory, Kismet identified the alert, wpa_supplicant provided connection information, and Wireshark allowed examination of the underlying wireless protocol.</p><p>Combining these tools produced a stronger security assessment than relying on a single alert.</p><h3>12. Lab 3 — Wireless Reconnaissance with Bettercap</h3><p>The final experiment focused on Bettercap.</p><p>I wanted to compare its wireless discovery capabilities with the information obtained through Kismet and Wireshark.</p><p>Bettercap was installed from the Kali Linux package repository:</p><pre>apt install bettercap -y</pre><p>I verified the installed version:</p><pre>bettercap -version</pre><p>The output confirmed:</p><pre>bettercap v2.41.5</pre><p>Before starting Bettercap, I stopped Kismet to avoid competing wireless interface management.</p><p>The simulated access point and client continued running.</p><h3>Step 1: Starting Bettercap</h3><p>I launched Bettercap using the monitoring radio:</p><pre>bettercap -iface wlan2</pre><p>Inside the interactive session, I configured the wireless interface and discovery channel:</p><pre>set wifi.interface wlan2<br>set wifi.region TR<br>wifi.recon.channel 6<br>wifi.recon on</pre><p>I then displayed the discovered wireless devices:</p><pre>wifi.show</pre><p>These commands were used to observe the isolated laboratory network.</p><p>No active attack commands were executed.</p><h3>Step 2: Discovering the WPA3 Network</h3><p>Bettercap successfully detected the simulated WPA3 access point.</p><p>The output included the following information:</p><ul><li><strong>SSID:</strong> WPA3-Lab</li><li><strong>BSSID:</strong> 02:00:00:00:00:00</li><li><strong>Encryption:</strong> WPA3 (AES-CCM, SAE)</li><li><strong>Channel:</strong> 6</li><li><strong>Observed Clients:</strong> 1</li><li><strong>RSSI:</strong> -30 dBm</li></ul><p>Bettercap successfully identified the simulated WPA3-Personal access point, including its SAE authentication mechanism, AES-CCM encryption, and associated wireless client.</p><p>These results were consistent with the information previously collected by Kismet. Both tools identified the same wireless network, security configuration, and observed client count.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*xdcS6j7Y4NJfDZNGGQUbGw.png" /><figcaption><em>Figure 8 — Bettercap successfully discovering a simulated WPA3-Personal access point, displaying its BSSID, SSID, SAE authentication, AES-CCM encryption, operating channel, and observed client count.</em></figcaption></figure><h3>AES-CCM vs. AES-CCMP</h3><p>An interesting difference was the terminology used by the tools.</p><p>Kismet displayed AES-CCMP, while Bettercap displayed AES-CCM.</p><p>These terms are closely related.</p><p>CCMP is a wireless security protocol that uses the AES block cipher in CCM mode to provide data confidentiality and integrity.</p><p>The different labels did not indicate that the tools had discovered fundamentally different encryption mechanisms.</p><p>This observation illustrates why security analysts need to understand the meaning behind tool-specific terminology.</p><h3>13. Discovering Wi-Fi Enhanced Open with Bettercap</h3><p>The next experiment examined whether Bettercap could identify an OWE-enabled wireless network.</p><p>I stopped the WPA3 access point and client, then reused the Enhanced Open configuration from my previous laboratory.</p><p>The OWE access point was started with:</p><pre>hostapd /etc/wifi-lab/owe.conf</pre><p>The wireless client was connected using:</p><pre>wpa_supplicant -i wlan1 -D nl80211 \<br>-c /etc/wifi-lab/owe-client.conf</pre><p>Unlike WPA3-Personal, OWE does not require a shared Wi-Fi password.</p><p>However, it establishes encryption keys through an unauthenticated Diffie-Hellman exchange.</p><h3>Refreshing Bettercap’s Discovery Results</h3><p>Because the same simulated access point was reused with a different security configuration, I refreshed Bettercap’s discovery state.</p><pre>wifi.recon off<br>wifi.clear<br>wifi.recon on<br>wifi.show</pre><p>The updated result displayed OWE-Lab.</p><h3>Observed Results</h3><p>Bettercap successfully discovered the OWE-enabled wireless network and displayed the following information:</p><ul><li><strong>SSID:</strong> OWE-Lab</li><li><strong>BSSID:</strong> 02:00:00:00:00:00</li><li><strong>Encryption:</strong> WPA2 (AES-CCM, Opportunistic Wireless Encryption)</li><li><strong>Channel:</strong> 6</li><li><strong>Observed Clients:</strong> 1</li><li><strong>RSSI:</strong> -30 dBm</li></ul><p>The results confirmed that Bettercap could identify an OWE-enabled network and its advertised encryption mechanism.</p><p>However, an interesting observation was that Bettercap displayed the network under a WPA2 security label while correctly identifying Opportunistic Wireless Encryption as its key management mechanism.</p><p>This distinction highlights the importance of examining detailed security parameters rather than relying solely on broad protocol labels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WmIB9-yQEmbNyBRnQvmvTg.png" /><figcaption><em>Figure 9 — Bettercap discovering an OWE-enabled wireless network, identifying AES-CCM encryption and Opportunistic Wireless Encryption while displaying the network under a WPA2 security label.</em></figcaption></figure><h3>Why Did Bettercap Display WPA2?</h3><p>This was one of the most interesting findings in the Bettercap experiment.</p><p>The security column displayed:</p><pre>WPA2 (AES-CCM, Opportunistic Wireless Encryption)</pre><p>However, the laboratory network was not configured as WPA2-Personal.</p><p>It was configured to use OWE.</p><p>OWE relies on the Robust Security Network framework but uses a different key management mechanism from WPA2-PSK.</p><p>Instead of establishing keys from a shared Wi-Fi password, OWE uses an unauthenticated Diffie-Hellman key exchange.</p><p>The detailed label correctly identified Opportunistic Wireless Encryption, even though the broader classification displayed WPA2.</p><p>This distinction is important.</p><p>A security analyst who only reads the general WPA2 label may incorrectly assume that the network uses traditional password-based WPA2-Personal authentication.</p><p>The experiment demonstrates why advertised cipher and key management information should be examined together.</p><p>I did not investigate Bettercap’s classification logic in its source code. Therefore, I report this behavior as an observed labeling difference rather than a confirmed software defect.</p><h3>14. Discovering a Traditional Open Wi-Fi Network</h3><p>To complete the comparison, I configured a third network without wireless link-layer encryption.</p><p>This allowed me to compare WPA3-Personal, Enhanced Open, and traditional Open Wi-Fi using the same simulated environment.</p><h3>Step 1: Configuring the Open Access Point</h3><p>I created a new hostapd configuration file:</p><pre>/etc/wifi-lab/open.conf</pre><p>The configuration contained:</p><pre>interface=wlan0<br>driver=nl80211<br>ssid=Open-Lab<br>hw_mode=g<br>channel=6<br>country_code=TR<br>auth_algs=1<br>wpa=0</pre><p>The important parameters were:</p><ul><li>auth_algs=1: Selects Open System authentication.</li><li>wpa=0: Disables WPA/RSN security mechanisms.</li></ul><p>This configuration created a traditional open wireless network.</p><p>I then started the access point:</p><pre>hostapd /etc/wifi-lab/open.conf</pre><p>During the initial startup attempt, hostapd reported an nl80211 driver configuration error.</p><p>After resolving the interface startup issue, the Open-Lab access point became visible to Bettercap.</p><h3>Step 2: Observing Open-Lab with Bettercap</h3><p>The discovery results were refreshed, and Bettercap successfully identified the new network.</p><pre>wifi.show</pre><p>The output showed the following information:</p><ul><li><strong>SSID:</strong> Open-Lab</li><li><strong>BSSID:</strong> 02:00:00:00:00:00</li><li><strong>Encryption:</strong> OPEN</li><li><strong>Channel:</strong> 6</li><li><strong>RSSI:</strong> -30 dBm</li></ul><p>Bettercap successfully identified the traditional open wireless network and classified it as OPEN, indicating that the access point did not provide wireless link-layer encryption.</p><p>Unlike the WPA3 and OWE experiments, the final screenshot did not display an associated client. Therefore, this experiment demonstrates the discovery and security classification of the open access point rather than a verified client connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/861/1*He6eSNb9dYtqGn--tV05nQ.png" /><figcaption><em>Figure 10 — Bettercap identifying a traditional open Wi-Fi network without wireless link-layer encryption, demonstrating the difference between unencrypted access and modern wireless security configurations.</em></figcaption></figure><h3>Security Analysis</h3><p>Traditional open Wi-Fi and Enhanced Open both allow password-free access.</p><p>However, they are not equivalent.</p><p>Traditional open Wi-Fi does not provide WPA/RSN link-layer data encryption.</p><p>Enhanced Open uses OWE to establish encryption keys without requiring a password.</p><p>OWE therefore provides protection against passive wireless eavesdropping that traditional open access does not provide.</p><p>Nevertheless, OWE does not authenticate the identity of the access point and does not replace application-layer security mechanisms such as HTTPS.</p><h3>15. Final Comparison of the Three Wireless Configurations</h3><p>After completing the Bettercap experiments, I compared the three wireless configurations.</p><h3>WPA3-Lab — WPA3-Personal</h3><ul><li><strong>Actual Security Configuration:</strong> WPA3-Personal</li><li><strong>Bettercap Label:</strong> WPA3</li><li><strong>Key Management:</strong> SAE</li><li><strong>Cipher:</strong> AES-CCM</li><li><strong>Wi-Fi Password:</strong> Required</li><li><strong>Wireless Link Encryption:</strong> Enabled</li><li><strong>Channel:</strong> 6</li><li><strong>Observed Clients:</strong> 1</li></ul><h3>OWE-Lab — Wi-Fi Enhanced Open</h3><ul><li><strong>Actual Security Configuration:</strong> Enhanced Open</li><li><strong>Bettercap Label:</strong> WPA2</li><li><strong>Key Management:</strong> OWE</li><li><strong>Cipher:</strong> AES-CCM</li><li><strong>Wi-Fi Password:</strong> Not Required</li><li><strong>Wireless Link Encryption:</strong> Enabled</li><li><strong>Channel:</strong> 6</li><li><strong>Observed Clients:</strong> 1</li></ul><h3>Open-Lab — Traditional Open Wi-Fi</h3><ul><li><strong>Actual Security Configuration:</strong> Traditional Open</li><li><strong>Bettercap Label:</strong> OPEN</li><li><strong>Key Management:</strong> None</li><li><strong>Cipher:</strong> None</li><li><strong>Wi-Fi Password:</strong> Not Required</li><li><strong>Wireless Link Encryption:</strong> Disabled</li><li><strong>Channel:</strong> 6</li><li><strong>Observed Clients:</strong> Not displayed</li></ul><h3>Key Observations</h3><p>All three configurations reused the same simulated access point radio. This explains why the BSSID remained unchanged across the experiments.</p><p>The networks were configured and observed sequentially rather than operating simultaneously.</p><p>The main finding was that a password-free network does not necessarily mean an unencrypted wireless network.</p><p>Enhanced Open and traditional Open Wi-Fi both provide convenient password-free access, but OWE adds link-layer encryption.</p><p>Another important observation was that Bettercap displayed the OWE network under a WPA2 label while correctly identifying Opportunistic Wireless Encryption as its key management mechanism.</p><p>This does not mean that OWE uses WPA2-Personal or password-based authentication. Instead, it demonstrates that security tools may use broad protocol labels that do not fully describe the underlying security configuration.</p><p>These experiments demonstrate that understanding the underlying security properties of a wireless network is more important than relying solely on a security tool’s displayed protocol label.</p><h3>16. Comparing Kismet, Wireshark, and Bettercap</h3><p>After completing the laboratory, I evaluated how the three tools contributed to the wireless defense workflow.</p><p><strong>Kismet</strong></p><ul><li><strong>Primary Focus:</strong> Wireless monitoring and intrusion detection</li><li><strong>Access Point and Client Discovery:</strong> Supported</li><li><strong>Security Classification:</strong> Supported</li><li><strong>Security Alerts:</strong> Built-in IDS alerts</li><li><strong>Packet-Level Inspection:</strong> Wireless monitoring and packet capture</li><li><strong>Laboratory Interface:</strong> Web UI</li></ul><p><strong>Wireshark</strong></p><ul><li><strong>Primary Focus:</strong> Network protocol analysis</li><li><strong>Access Point and Client Discovery:</strong> Through packet analysis</li><li><strong>Security Classification:</strong> Detailed protocol fields</li><li><strong>Security Alerts:</strong> Manual investigation</li><li><strong>Packet-Level Inspection:</strong> Extensive packet analysis</li><li><strong>Laboratory Interface:</strong> Desktop GUI</li></ul><p><strong>Bettercap</strong></p><ul><li><strong>Primary Focus:</strong> Wireless reconnaissance and security assessment</li><li><strong>Access Point and Client Discovery:</strong> Supported</li><li><strong>Security Classification:</strong> Supported</li><li><strong>Security Alerts:</strong> Event and assessment features</li><li><strong>Packet-Level Inspection:</strong> Reconnaissance-oriented output</li><li><strong>Laboratory Interface:</strong> Interactive CLI</li></ul><h3>Kismet: Discover and Detect</h3><p>Kismet provided an overview of the monitored wireless environment.</p><p>It identified the access point and client, displayed packet statistics, and generated security alerts.</p><p>Its most valuable contribution was identifying the unexpected NOCLIENTMFP alert that initiated the investigation.</p><h3>Wireshark: Inspect and Validate</h3><p>Wireshark provided detailed protocol evidence.</p><p>It allowed me to inspect the RSN Information Element and verify the MFPC and MFPR flags.</p><p>This helped evaluate whether the Kismet alert was consistent with the observed client behavior.</p><h3>Bettercap: Discover and Compare</h3><p>Bettercap provided a separate wireless reconnaissance perspective.</p><p>It successfully discovered the WPA3, OWE, and traditional open configurations.</p><p>Its OWE classification also demonstrated why analysts should inspect authentication and key management details rather than relying only on a broad security label.</p><p>These three tools are not direct replacements for one another.</p><p>Their strengths become more useful when they are combined into a structured security investigation.</p><h3>17. A Practical Wireless Defense Workflow</h3><p>Based on the experiments, a wireless security investigation can be organized into the following stages.</p><h3>Stage 1: Discover</h3><p>Identify wireless access points, network names, channels, and observed clients.</p><p>Kismet or Bettercap can help create an initial picture of the wireless environment.</p><h3>Stage 2: Detect</h3><p>Review security alerts and unexpected wireless activity.</p><p>Compare observed behavior with approved network configurations and security policies.</p><h3>Stage 3: Investigate</h3><p>Use packet analysis to inspect the relevant protocol fields.</p><p>For example, an alert involving management frame protection can be investigated by examining RSN capabilities in Wireshark.</p><h3>Stage 4: Correlate</h3><p>Compare the packet evidence with connection status, access point configuration, device inventory, and other available records.</p><p>Different data sources can help determine whether an alert represents a real issue.</p><h3>Stage 5: Reproduce</h3><p>When appropriate, repeat the behavior in an authorized environment to determine whether the observation is consistent.</p><p>In this laboratory, reconnecting the client produced another NOCLIENTMFP alert.</p><h3>Stage 6: Assess and Document</h3><p>Document the confirmed observations, potential risks, and remaining uncertainties.</p><p>A finding should not be reported as a confirmed vulnerability unless sufficient evidence supports that conclusion.</p><p>This structured process is particularly important in security operations, where incorrect assumptions can lead to unnecessary remediation or missed threats.</p><h3>18. Key Findings from the Laboratory</h3><p>The experiments produced two findings that were especially important.</p><h3>Finding 1: A Reproducible Potential False Positive</h3><p>Kismet generated NOCLIENTMFP alerts even though the WPA3 client reported mandatory management frame protection.</p><p>Wireshark also confirmed that the client’s Association Request advertised both MFPC and MFPR.</p><p>The alert appeared again after reconnecting the client.</p><p>These observations supported the assessment of a potential false positive within the simulated environment.</p><p>However, the exact detection mechanism responsible for the alert was not identified.</p><p>The finding demonstrates the importance of validating intrusion detection alerts before interpreting them as confirmed security issues.</p><h3>Finding 2: Differences in Wireless Security Classification</h3><p>Bettercap displayed the OWE-enabled network under a WPA2 label while correctly identifying its key management mechanism as Opportunistic Wireless Encryption.</p><p>This demonstrated that broad security labels may not communicate the complete security configuration.</p><p>Analysts should examine the specific authentication method, cipher suite, and relevant protocol information before reaching a conclusion.</p><h3>Additional Observation: Successful Virtual Wireless Monitoring</h3><p>Kismet, Wireshark, and Bettercap all provided useful results within the mac80211_hwsim environment.</p><p>The laboratory demonstrated that simulated Wi-Fi radios can support meaningful wireless security education without requiring physical wireless hardware.</p><h3>19. Defensive Recommendations</h3><p>The experiments highlight several practical recommendations for wireless security administrators.</p><p><strong>Maintain an authorized access point inventory.</strong></p><p>Document approved SSIDs, BSSIDs, security configurations, and network ownership.</p><p>Investigate unexpected devices instead of immediately assuming that every unfamiliar access point is malicious.</p><p><strong>Monitor wireless security configurations.</strong></p><p>Regularly review the authentication and encryption methods advertised by wireless networks.</p><p>Avoid legacy and insecure wireless configurations wherever possible.</p><p><strong>Use WPA3 when appropriate.</strong></p><p>WPA3-Personal strengthens password-based authentication, while WPA3-Enterprise provides enterprise authentication options.</p><p>Enhanced Open may be suitable for public guest networks when password-free access is required.</p><p><strong>Require appropriate management frame protection.</strong></p><p>PMF helps reduce certain management frame forgery risks.</p><p>Verify both the configured security policy and actual negotiated behavior.</p><p><strong>Validate intrusion detection alerts.</strong></p><p>Use packet captures, endpoint connection information, and other relevant evidence before declaring an alert a confirmed vulnerability.</p><p><strong>Follow the principle of Least Privilege.</strong></p><p>Wireless monitoring systems should be configured with appropriate permissions rather than unnecessarily running entire applications with elevated privileges.</p><p><strong>Protect monitoring data.</strong></p><p>Wireless captures may contain device identifiers, network information, authentication exchanges, and potentially sensitive traffic.</p><p>Store and share capture files according to organizational security and privacy requirements.</p><h3>20. Limitations of the Laboratory</h3><p>The experiments were conducted using simulated wireless interfaces inside Kali Linux.</p><p>Although the laboratory successfully demonstrated wireless discovery, security alert investigation, and protocol classification, several limitations should be considered.</p><p>First, the environment did not include physical wireless radio propagation.</p><p>Consequently, the observed signal strength values do not represent real-world wireless coverage.</p><p>Second, the experiments used a single simulated access point and a limited number of clients.</p><p>They do not measure the performance of the tools in a large enterprise wireless deployment.</p><p>Third, the three wireless security configurations were tested sequentially on the same access point radio.</p><p>The laboratory did not evaluate simultaneous multi-network discovery across multiple channels.</p><p>Fourth, the exact internal cause of Kismet’s NOCLIENTMFP alert was not established.</p><p>Similarly, Bettercap’s broader WPA2 classification of OWE was observed but not investigated at the source-code level.</p><p>Finally, no active wireless attacks, password recovery attempts, deauthentication attacks, or unauthorized network assessments were conducted.</p><p>The results should therefore be interpreted as controlled demonstrations of wireless monitoring and security investigation rather than a complete evaluation of wireless intrusion detection accuracy or attack resistance.</p><h3>21. Conclusion</h3><p>Wireless network defense is more than discovering nearby access points or capturing packets.</p><p>It requires understanding wireless protocols, recognizing suspicious behavior, validating security alerts, and interpreting network configurations correctly.</p><p>In this article, I examined Kismet, Wireshark, and Bettercap through a practical Kali Linux laboratory.</p><p>Using Kismet, I discovered a WPA3 access point, observed its associated client, examined device statistics, and investigated security alerts.</p><p>Using Wireshark, I verified management frame protection capabilities in an IEEE 802.11 Association Request and evaluated an unexpected NOCLIENTMFP alert.</p><p>Using Bettercap, I discovered and compared WPA3-Personal, Enhanced Open, and traditional Open Wi-Fi configurations.</p><p>The experiments revealed that different security tools may provide different perspectives on the same wireless environment.</p><p>More importantly, they demonstrated that security alerts and classification labels should not automatically be accepted without investigation.</p><p><strong>The main lesson from this laboratory is that effective wireless defense depends not only on the tools we use, but also on how we validate, correlate, and interpret their results.</strong></p><p>Understanding these principles helps transform wireless monitoring from a simple discovery activity into a meaningful cybersecurity investigation.</p><h3>References</h3><ol><li><a href="https://www.kismetwireless.net/">Kismet — Official Website</a></li><li><a href="https://www.kismetwireless.net/docs/readme/datasources/wifi-linux/">Kismet — Linux Wi-Fi Data Sources</a></li><li><a href="https://www.kismetwireless.net/docs/readme/alerts/">Kismet — Wireless Security Alerts Documentation</a></li><li><a href="https://www.wireshark.org/docs/">Wireshark — Official Documentation</a></li><li><a href="https://www.wireshark.org/docs/dfref/w/wlan.html">Wireshark — IEEE 802.11 Display Filter Reference</a></li><li><a href="https://www.bettercap.org/modules/wifi/">Bettercap — Wi-Fi Module Documentation</a></li><li><a href="https://wireless.docs.kernel.org/en/latest/en/users/drivers/mac80211_hwsim.html">Linux Wireless — mac80211_hwsim</a></li><li><a href="https://www.rfc-editor.org/rfc/rfc8110">RFC 8110 — Opportunistic Wireless Encryption</a></li><li><a href="https://www.aircrack-ng.org/">Aircrack-ng — Official Website</a></li><li><a href="https://www.netstumbler.com/downloads/">NetStumbler — Official Downloads</a></li><li><a href="https://kismac-ng.org/">KisMAC — Official Website</a></li></ol><p><em>All experiments described in this article were performed in an isolated, simulated wireless environment for educational and defensive security purposes. No neighboring wireless networks or unauthorized devices were targeted.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0d4a5b0bb3c6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WPA3 and Wi-Fi Enhanced Open: Understanding Modern Wi-Fi Security Through Practical Labs]]></title>
            <link>https://medium.com/@yunusemreerten08/wpa3-and-wi-fi-enhanced-open-understanding-modern-wi-fi-security-through-practical-labs-395b7afd44bc?source=rss-7493fd34a983------2</link>
            <guid isPermaLink="false">https://medium.com/p/395b7afd44bc</guid>
            <category><![CDATA[wifi-security]]></category>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[wpa3]]></category>
            <category><![CDATA[kali-linux]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Yunusemreerten]]></dc:creator>
            <pubDate>Tue, 03 Nov 2026 16:05:04 GMT</pubDate>
            <atom:updated>2026-11-03T16:05:04.861Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Exploring SAE authentication, Opportunistic Wireless Encryption, and wireless key exchange mechanisms through hands-on experiments using Kali Linux and Wireshark.</em></p><h3>1. Introduction</h3><p>Wi-Fi has become an essential part of everyday life. Whether we are connecting to the internet at home, at university, in an office, or at a café, wireless networks provide convenient access to online services.</p><p>However, wireless communication also introduces security challenges.</p><p>Unlike traditional wired communication, Wi-Fi transmits information through radio signals. Devices within range may be able to capture wireless frames, making authentication and encryption particularly important.</p><p>Earlier wireless security technologies, including WPA2, introduced important protections. However, weaknesses associated with password-based authentication, insecure configurations, and unencrypted public networks highlighted the need for improved security mechanisms.</p><p>Two technologies that address these challenges are <strong>WPA3 and Wi-Fi Enhanced Open</strong>.</p><p>Although both improve wireless security, they serve different purposes.</p><p>WPA3 strengthens authentication and encryption for protected wireless networks, while Wi-Fi Enhanced Open provides encrypted communication on networks that do not require passwords.</p><p>In this article, I will explain the motivation behind these technologies, examine their working principles, and compare their security characteristics.</p><p>I will also demonstrate WPA3-Personal and Wi-Fi Enhanced Open using a virtual wireless laboratory built with Kali Linux, hostapd, wpa_supplicant, and Wireshark.</p><h3>2. Why Do We Need Better Wi-Fi Security?</h3><p>To understand the importance of WPA3 and Enhanced Open, we first need to consider the security limitations of previous wireless networking approaches.</p><h3>Offline Password Guessing</h3><p>Traditional WPA2-Personal relies on a Pre-Shared Key (PSK).</p><p>When an attacker captures the necessary authentication handshake, they may attempt to guess the Wi-Fi password offline.</p><p>This means an attacker can test password candidates without repeatedly communicating with the wireless access point.</p><p>If the network uses a weak password, this becomes a significant security risk.</p><h3>Unencrypted Public Wi-Fi</h3><p>Another common problem involves public wireless networks.</p><p>Many cafés, hotels, and airports provide Wi-Fi access without requiring a password.</p><p>In traditional open Wi-Fi networks, wireless data frames are not encrypted at the link layer.</p><p>This creates opportunities for passive eavesdropping, particularly when applications transmit information without their own encryption.</p><p>Although HTTPS protects many modern web connections, link-layer encryption can provide another important layer of protection.</p><h3>Wireless Management Frame Attacks</h3><p>Wireless networks also exchange management frames to establish and maintain connections.</p><p>Historically, some of these frames could be spoofed to disrupt client connections.</p><p>Protected Management Frames (PMF) help reduce certain management frame forgery attacks.</p><p>These security challenges motivated the introduction and adoption of stronger wireless security technologies.</p><h3>3. What Is WPA3?</h3><p>WPA3 stands for <strong>Wi-Fi Protected Access 3</strong>.</p><p>It is a wireless security framework developed by the Wi-Fi Alliance to strengthen protection for personal and enterprise Wi-Fi networks.</p><p>WPA3 includes two major categories:</p><ul><li>WPA3-Personal</li><li>WPA3-Enterprise</li></ul><h3>WPA3-Personal</h3><p>WPA3-Personal is designed primarily for home networks and other environments that use a shared Wi-Fi password.</p><p>Its most important improvement is the introduction of <strong>Simultaneous Authentication of Equals (SAE)</strong>.</p><p>SAE replaces the traditional WPA2-Personal PSK authentication approach.</p><p>Instead of exposing a handshake suitable for passive offline password verification, SAE performs a password-authenticated key agreement.</p><p>This makes WPA3-Personal more resistant to passive offline dictionary attacks.</p><p>However, WPA3 does not eliminate the need for strong passwords, secure implementations, and updated devices.</p><h3>WPA3-Enterprise</h3><p>WPA3-Enterprise is intended for organizations that require centralized authentication and advanced security controls.</p><p>It commonly uses IEEE 802.1X and EAP-based authentication mechanisms.</p><p>WPA3-Enterprise also offers a 192-bit security mode for environments with more demanding protection requirements.</p><p>For example, an organization may use enterprise authentication infrastructure to manage employee Wi-Fi access without distributing one shared password to everyone.</p><p>This is closely related to centralized AAA concepts, including RADIUS-based authentication.</p><p>In this laboratory, I focused on WPA3-Personal rather than WPA3-Enterprise.</p><h3>4. How Does WPA3-Personal Work?</h3><p>WPA3-Personal uses SAE, a password-authenticated key agreement mechanism.</p><p>Imagine a laptop connecting to a WPA3-enabled router.</p><p>The process can be simplified into four stages.</p><h3>Step 1: Network Discovery</h3><p>The wireless access point advertises its network name and security capabilities.</p><p>The client detects the network and identifies the supported authentication method.</p><h3>Step 2: SAE Commit Exchange</h3><p>The client and access point participate in an SAE exchange using knowledge of the configured password.</p><p>Both sides exchange cryptographic values during the Commit phase.</p><p>These values allow the participants to derive shared key material without transmitting the actual password.</p><h3>Step 3: SAE Confirm Exchange</h3><p>After calculating the required cryptographic values, the client and access point exchange Confirm messages.</p><p>These messages help verify that both participants derived matching key material.</p><h3>Step 4: Four-Way Handshake</h3><p>Following successful SAE authentication, the devices use the established key material in the four-way handshake.</p><p>This process establishes and installs keys used to protect subsequent wireless communication.</p><p>WPA3-Personal also requires Protected Management Frames for WPA3 associations, helping protect certain management messages against spoofing.</p><h3>5. What Is Wi-Fi Enhanced Open?</h3><p>Wi-Fi Enhanced Open is a wireless security technology designed for networks that do not require passwords.</p><p>It is based on <strong>Opportunistic Wireless Encryption (OWE)</strong>.</p><p>Traditional open networks provide convenient access but do not encrypt wireless data frames at the link layer.</p><p>OWE addresses this problem by allowing the client and access point to establish encryption keys without a shared password.</p><p>For example, imagine connecting to a public Wi-Fi network at a café.</p><p>With Enhanced Open, a compatible device can establish encrypted wireless communication without the user entering a password.</p><p>This reduces the risk of passive eavesdropping compared with traditional unencrypted open Wi-Fi.</p><p>However, OWE does not authenticate the identity of the access point.</p><p>This distinction is important because encryption and authentication are not the same thing.</p><h3>6. How Does Wi-Fi Enhanced Open Work?</h3><p>OWE uses an unauthenticated Diffie-Hellman key exchange.</p><p>Unlike WPA3-Personal, it does not require both participants to know a shared password.</p><h3>Step 1: Network Discovery</h3><p>The client identifies an access point supporting OWE.</p><p>The access point advertises its wireless security capabilities.</p><h3>Step 2: Association and Key Exchange</h3><p>During the association process, the client and access point exchange Diffie-Hellman public key information.</p><p>Each participant uses its own private key and the other participant’s public key to derive shared secret material.</p><p>The private keys are not transmitted.</p><h3>Step 3: Key Derivation</h3><p>The resulting shared secret is used to derive a Pairwise Master Key (PMK).</p><p>The subsequent four-way handshake establishes the keys used to protect wireless data.</p><h3>Step 4: Encrypted Communication</h3><p>After the connection is established, data frames can be protected using the negotiated encryption algorithm.</p><p>The result is a password-free wireless connection with link-layer encryption.</p><p>However, because the key exchange is unauthenticated, OWE remains vulnerable to certain active attacks involving access point impersonation.</p><p>OWE protects the wireless link but does not replace HTTPS or other end-to-end security mechanisms.</p><h3>7. WPA3 vs. Wi-Fi Enhanced Open</h3><p>The fundamental difference between these technologies is the relationship between authentication and encryption.</p><p>FeatureWPA3-PersonalWi-Fi Enhanced OpenMain mechanismSAEOWEPassword requiredYesNoAuthenticationPassword-authenticatedNo peer authenticationKey agreementPassword-authenticated key exchangeDiffie-HellmanWireless encryptionYesYesProtection against passive eavesdroppingYesYesMain use casePrivate Wi-Fi networksPublic Wi-Fi networksMajor limitationPassword and implementation security still matterAccess point impersonation risk</p><p>WPA3-Personal provides password-based authentication and encrypted communication.</p><p>Enhanced Open provides encryption without authenticating the access point or client.</p><p>Therefore, the two technologies should not be treated as interchangeable.</p><h3>8. Practical Lab: Creating a Virtual Wi-Fi Environment</h3><p>To demonstrate these technologies, I created a virtual wireless laboratory using Kali Linux running inside VMware Workstation.</p><p>Instead of using a physical wireless adapter, I used the Linux mac80211_hwsim kernel module.</p><p>This module simulates IEEE 802.11 wireless radios, allowing Wi-Fi protocol experiments to be performed without actual radio transmissions.</p><p>The laboratory used:</p><ul><li><strong>Kali Linux:</strong> Laboratory operating system</li><li><strong>mac80211_hwsim:</strong> Virtual Wi-Fi radios</li><li><strong>hostapd:</strong> Wireless access point software</li><li><strong>wpa_supplicant:</strong> Wireless client software</li><li><strong>Wireshark:</strong> Network packet analysis</li></ul><p>I created two simulated wireless interfaces by running:</p><pre>sudo modprobe mac80211_hwsim radios=2</pre><p>The interfaces were assigned the following roles:</p><p>InterfaceRolewlan0Virtual Access Pointwlan1Virtual Wi-Fi Clienthwsim0Virtual 802.11 packet capture</p><p>This setup allowed me to experiment with WPA3 and OWE locally without interacting with surrounding wireless networks.</p><h3>9. Lab 1: WPA3-Personal Authentication Using SAE</h3><p>The first experiment focused on configuring a WPA3-Personal network.</p><h3>Step 1: Configuring the Access Point</h3><p>I created a hostapd configuration with the following important settings:</p><pre>interface=wlan0<br>driver=nl80211<br>ssid=WPA3-Lab<br>hw_mode=g<br>channel=6</pre><pre>wpa=2<br>wpa_key_mgmt=SAE<br>rsn_pairwise=CCMP<br>wpa_passphrase=LabWPA3Pass2026!<br>ieee80211w=2<br>sae_pwe=2</pre><p>The most important parameters were:</p><ul><li>wpa_key_mgmt=SAE: Enables SAE authentication.</li><li>rsn_pairwise=CCMP: Configures the pairwise encryption algorithm.</li><li>ieee80211w=2: Requires Protected Management Frames.</li><li>sae_pwe=2: Enables both supported SAE password-element derivation methods in this configuration.</li></ul><p>I started the access point using hostapd.</p><p>The output included:</p><pre>wlan0: AP-ENABLED</pre><p>This confirmed that the virtual access point had started successfully.</p><h3>Step 2: Connecting the Client</h3><p>Next, I configured wpa_supplicant on the second virtual interface.</p><p>The client configuration included:</p><pre>network={<br>    ssid=&quot;WPA3-Lab&quot;<br>    key_mgmt=SAE<br>    sae_password=&quot;LabWPA3Pass2026!&quot;<br>    ieee80211w=2<br>}</pre><p>After starting the client, I checked the connection using:</p><pre>sudo wpa_cli -i wlan1 status</pre><p>The output showed:</p><pre>ssid=WPA3-Lab<br>key_mgmt=SAE<br>pairwise_cipher=CCMP<br>pmf=2<br>sae_group=19<br>wpa_state=COMPLETED</pre><p>These values confirmed that the client successfully connected using SAE authentication.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/409/1*niwVE9Z6yE72o8K-Q_WuIA.png" /><figcaption><strong>Figure 1 — Successful WPA3-Personal connection showing SAE authentication, CCMP encryption, and mandatory Protected Management Frames.</strong></figcaption></figure><p>The connection operated on channel 6 at 2437 MHz in the simulated environment.</p><h3>What Did This Experiment Demonstrate?</h3><p>The test confirmed that a simulated wireless client and access point could establish a WPA3-Personal connection using SAE.</p><p>The wpa_state=COMPLETED value showed that the connection and key establishment process had completed.</p><p>The key_mgmt=SAE field confirmed the authentication mechanism.</p><p>However, this experiment did not attempt to recover passwords or evaluate resistance against actual password-guessing attacks.</p><h3>10. Lab 2: Wi-Fi Enhanced Open Using OWE</h3><p>The second experiment focused on creating a password-free but encrypted wireless network.</p><h3>Step 1: Configuring the OWE Access Point</h3><p>I stopped the WPA3 processes and reconfigured the virtual access point for OWE.</p><p>The main settings were:</p><pre>interface=wlan0<br>driver=nl80211<br>ssid=OWE-Lab<br>hw_mode=g<br>channel=6</pre><pre>wpa=2<br>wpa_key_mgmt=OWE<br>rsn_pairwise=CCMP<br>ieee80211w=2</pre><p>Unlike WPA3-Personal, this configuration did not contain a Wi-Fi password.</p><p>The important parameter was:</p><pre>wpa_key_mgmt=OWE</pre><p>This enabled Opportunistic Wireless Encryption.</p><h3>Step 2: Connecting Without a Password</h3><p>I configured the client to use OWE:</p><pre>network={<br>    ssid=&quot;OWE-Lab&quot;<br>    key_mgmt=OWE<br>    ieee80211w=2<br>}</pre><p>After connecting, I checked the status:</p><pre>sudo wpa_cli -i wlan1 status</pre><p>The output showed:</p><pre>ssid=OWE-Lab<br>key_mgmt=OWE<br>pairwise_cipher=CCMP<br>pmf=2<br>wpa_state=COMPLETED</pre><p>These results confirmed that the client successfully connected to the OWE network without using a password.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/364/1*7ozNgdX_L0JOQTPNNKbKfw.png" /><figcaption><strong>Figure 2 — Successful Wi-Fi Enhanced Open connection showing OWE key management, CCMP encryption, and completed association.</strong></figcaption></figure><h3>What Did This Experiment Demonstrate?</h3><p>The experiment showed that password-free wireless access does not necessarily mean unencrypted wireless communication.</p><p>OWE allowed the virtual client and access point to establish encryption keys without a shared Wi-Fi password.</p><p>However, successful OWE association does not prove that the access point’s identity is trustworthy.</p><p>That is an important limitation of Enhanced Open.</p><h3>11. Lab 3: Analyzing the OWE Diffie-Hellman Exchange</h3><p>After establishing the OWE connection, I used Wireshark to inspect the wireless management frames.</p><p>For this experiment, I enabled the virtual capture interface:</p><pre>sudo ip link set hwsim0 up</pre><p>I then captured traffic on hwsim0 and applied the following Wireshark display filter:</p><pre>wlan.fc.type_subtype == 0x00 || wlan.fc.type_subtype == 0x01</pre><p>This filter displayed Association Request and Association Response frames.</p><p>After reconnecting the client, Wireshark captured the OWE association exchange.</p><p>In the Association Request frame, I expanded the wireless management parameters.</p><p>The packet contained an OWE Diffie-Hellman Parameter element.</p><p>The important values were:</p><pre>Ext Tag: OWE Diffie-Hellman Parameter<br>Ext Tag Number: 32<br>Group: 256-bit random ECP group (19)<br>Public Key: [32-byte public key]</pre><p>Group 19 identifies a 256-bit elliptic curve group associated with NIST P-256.</p><p>The public key was visible in the wireless association frame.</p><p>This is expected behavior.</p><p>Diffie-Hellman key agreement relies on exchanging public values while keeping the private values secret.</p><p>The observed packet demonstrated that the client transmitted the public key material needed for OWE key agreement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lNYDbirtLDlyYUSSSPv7EQ.png" /><figcaption><strong>Figure 3 — Wireshark analysis of an OWE Association Request showing the Diffie-Hellman Parameter element, elliptic curve group 19, and public key.</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/876/1*mwHhyrLrZQ7_xkgu8nzbSg.png" /><figcaption><strong>Figure 3.1 — OWE Diffie-Hellman key exchange parameters showing elliptic curve group 19 and the public key transmitted during Wi-Fi association.</strong></figcaption></figure><h3>Security Analysis</h3><p>This experiment demonstrated an important aspect of Enhanced Open.</p><p>A password is not required to establish encrypted wireless communication because each participant can generate its own key material and exchange public values.</p><p>However, an unauthenticated Diffie-Hellman exchange does not establish the identity of the access point.</p><p>This is why OWE protects against passive eavesdropping but does not, by itself, prevent an active attacker from impersonating a wireless access point.</p><h3>12. Lab 4: Analyzing WPA3 SAE Commit and Confirm Messages</h3><p>The final experiment focused on the SAE authentication exchange used by WPA3-Personal.</p><p>I reconfigured the virtual access point and client to use WPA3-Personal again.</p><p>Using Wireshark on hwsim0, I applied the following filter:</p><pre>wlan.fc.type_subtype == 0x0b</pre><p>This displayed IEEE 802.11 Authentication frames.</p><p>The capture contained four authentication frames exchanged between the virtual client and access point.</p><h3>SAE Commit Analysis</h3><p>I selected the first authentication frame and expanded its fixed parameters.</p><p>Wireshark displayed:</p><pre>Authentication Algorithm: SAE (3)<br>Authentication SEQ: 0x0001<br>Status code: Successful (0x0000)<br>SAE Message Type: Commit (1)<br>Group Id: 256-bit random ECP group (19)<br>Scalar: [cryptographic value]<br>Finite Field Element: [cryptographic value]</pre><p>The most important field was:</p><pre>SAE Message Type: Commit (1)</pre><p>This confirmed that the captured frame belonged to the SAE Commit phase.</p><p>The Scalar and Finite Field Element fields represented cryptographic values exchanged during the password-authenticated key agreement.</p><p>These fields did not contain the Wi-Fi password itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WL_oAQzlDRj2S9jB13yiQA.png" /><figcaption><strong>Figure 4 — Wireshark analysis of a WPA3 SAE Commit message showing group 19, Scalar, and Finite Field Element values.</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KiowBCr-R6BZIKEbX5OOoQ.png" /><figcaption><strong>Figure 4.1 — WPA3-Personal SAE Commit message showing authentication algorithm SAE (3), elliptic curve group 19, and the cryptographic values exchanged during key agreement.</strong></figcaption></figure><h3>SAE Confirm Analysis</h3><p>Next, I selected a later authentication frame.</p><p>Wireshark displayed:</p><pre>Authentication Algorithm: SAE (3)<br>Authentication SEQ: 0x0002<br>Status code: Successful (0x0000)<br>SAE Message Type: Confirm (2)<br>Send-Confirm: 1<br>Confirm: [cryptographic confirmation value]</pre><p>The key observation was:</p><pre>SAE Message Type: Confirm (2)</pre><p>This verified that the frame belonged to the SAE Confirm phase.</p><p>The Confirm message is used to verify the cryptographic key agreement between the participants.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hXPbe3Le24l41izsB8_vfw.png" /><figcaption><strong>Figure 5 — Wireshark analysis of an SAE Confirm message showing authentication sequence 2 and the cryptographic confirmation value.</strong></figcaption></figure><h3>Understanding the SAE Exchange</h3><p>The captured authentication sequence was consistent with the following message flow:</p><p>DirectionMessageClient → Access PointSAE CommitAccess Point → ClientSAE CommitClient → Access PointSAE ConfirmAccess Point → ClientSAE Confirm</p><p>The client-side Commit and Confirm message types were directly verified in Wireshark.</p><p>Combined with the successful wpa_state=COMPLETED result, these observations demonstrated a completed WPA3-Personal connection using SAE.</p><p>The experiment did not evaluate attack resistance or perform cryptographic key recovery.</p><h3>13. Comparing Our Laboratory Results</h3><p>After completing both experiments, I compared the observed behavior.</p><p>ObservationWPA3-PersonalEnhanced OpenSSIDWPA3-LabOWE-LabKey managementSAEOWEPasswordRequiredNot requiredPairwise cipherCCMPCCMPPMF configurationRequiredRequired in our labConnection stateCOMPLETEDCOMPLETEDCryptographic group1919Wireshark evidenceSAE Commit / ConfirmOWE DH Parameter</p><p>The most interesting observation was that both connections used encrypted wireless communication, but their key establishment mechanisms were fundamentally different.</p><p>WPA3-Personal relied on SAE, a password-authenticated key agreement.</p><p>Enhanced Open relied on OWE, an unauthenticated Diffie-Hellman key exchange.</p><p>This demonstrates why <strong>encrypted communication should not automatically be interpreted as authenticated communication</strong>.</p><h3>14. Real-World Examples and Use Cases</h3><h3>Example 1: Home Wi-Fi</h3><p>For a home network where all devices support WPA3, WPA3-Personal is generally a suitable choice.</p><p>SAE strengthens authentication and improves resistance to passive offline password guessing.</p><p>A strong, unique Wi-Fi password and updated router firmware remain important.</p><h3>Example 2: Corporate Wireless Networks</h3><p>Organizations often require individual employee authentication and centralized access management.</p><p>WPA3-Enterprise can support these requirements through compatible enterprise authentication infrastructure.</p><p>It is especially useful where organizations need managed access policies rather than a shared wireless password.</p><h3>Example 3: Public Wi-Fi in Cafés and Hotels</h3><p>Public networks often prioritize convenient access.</p><p>Enhanced Open allows compatible devices to establish encrypted wireless connections without requiring users to enter a Wi-Fi password.</p><p>This provides better protection against passive wireless traffic observation than traditional open Wi-Fi.</p><p>However, users should still verify the network and rely on secure applications such as HTTPS-enabled websites.</p><h3>Example 4: Compatibility and Transition Modes</h3><p>Older devices may not support WPA3 or OWE.</p><p>WPA2/WPA3 transition mode allows different generations of devices to connect using their supported authentication mechanisms.</p><p>Similarly, OWE transition mode can provide encrypted access for compatible devices while allowing older devices to connect using traditional open Wi-Fi.</p><p>These modes improve compatibility but may introduce weaker security options.</p><p>For this reason, administrators should evaluate whether transition modes are actually necessary.</p><h3>15. Security Limitations and Best Practices</h3><p>WPA3 and Enhanced Open provide important improvements, but neither technology eliminates all wireless security risks.</p><p>Several considerations remain important.</p><p><strong>Use strong passwords for WPA3-Personal.</strong> SAE improves resistance to certain password attacks, but weak passwords and insecure implementations remain concerns.</p><p><strong>Prefer WPA3-only mode when practical.</strong> Legacy compatibility may expose devices to weaker security modes.</p><p><strong>Keep wireless equipment updated.</strong> Access points, drivers, and client devices should receive security patches.</p><p><strong>Understand the limitations of OWE.</strong> Enhanced Open provides encryption but does not authenticate the access point.</p><p><strong>Use secure application protocols.</strong> WPA3 and OWE protect wireless communication at the link layer. HTTPS and other end-to-end protections remain essential.</p><p><strong>Enable appropriate management frame protection.</strong> PMF helps protect robust management frames against certain spoofing attacks but does not prevent all forms of wireless disruption.</p><p><strong>Use enterprise authentication where appropriate.</strong> Organizations should consider centrally managed identity and access policies rather than shared passwords for sensitive networks.</p><p>No single wireless security mechanism provides complete protection against every threat.</p><h3>16. Limitations of the Laboratory</h3><p>The experiments were conducted using simulated wireless interfaces inside Kali Linux.</p><p>They demonstrated successful WPA3-Personal and OWE connections and allowed examination of their management frames.</p><p>However, the laboratory did not test real wireless radio interference, physical signal propagation, or commercial access point compatibility.</p><p>It also did not include password-cracking attempts, active man-in-the-middle attacks, or actual security exploitation.</p><p>WPA3-Enterprise and transition modes were discussed theoretically but were not configured or tested.</p><p>The findings should therefore be interpreted as practical demonstrations of authentication, association, and key exchange behavior rather than a complete wireless security assessment.</p><h3>17. Conclusion</h3><p>Wireless security is not only about encrypting traffic. It is also about establishing trust between devices and protecting the authentication process.</p><p>WPA3 and Wi-Fi Enhanced Open improve wireless security in different ways.</p><p>WPA3-Personal uses SAE to establish password-authenticated key material and provides stronger protection against passive offline password-guessing attacks than traditional WPA2-Personal authentication.</p><p>Wi-Fi Enhanced Open uses OWE to provide encrypted wireless communication without requiring a password.</p><p>Through practical experiments using Kali Linux, hostapd, wpa_supplicant, mac80211_hwsim, and Wireshark, I successfully configured and analyzed both technologies.</p><p>For WPA3-Personal, I observed a completed SAE connection and inspected Commit and Confirm authentication frames.</p><p>For Enhanced Open, I established a password-free encrypted connection and identified the Diffie-Hellman public key information in the association exchange.</p><p>These experiments helped me understand the relationship between authentication, encryption, and key agreement in wireless networking.</p><p><strong>The main conclusion is that WPA3 and Enhanced Open address different security needs: WPA3-Personal strengthens password-based authentication, while Enhanced Open improves privacy on password-free networks without providing access point authentication.</strong></p><p>Understanding these differences is important for both network administrators and everyday Wi-Fi users.</p><h3>References</h3><ol><li><a href="https://www.wi-fi.org/discover-wi-fi/security">Wi-Fi Alliance — Wi-Fi Security</a></li><li><a href="https://source.android.com/docs/core/connect/wifi-wpa3-owe">Android Open Source Project — WPA3 and Wi-Fi Enhanced Open</a></li><li><a href="https://www.rfc-editor.org/rfc/rfc8110">RFC 8110 — Opportunistic Wireless Encryption</a></li><li><a href="https://www.rfc-editor.org/rfc/rfc9672">RFC 9672 — Transferring OWE to the IEEE 802.11 Working Group</a></li><li><a href="https://www.wireshark.org/docs/">Wireshark Documentation</a></li><li><a href="https://wireless.docs.kernel.org/en/latest/en/users/drivers/mac80211_hwsim.html">Linux Wireless — mac80211_hwsim</a></li></ol><p><em>All experiments were conducted in an isolated, simulated wireless laboratory. The demonstration focused on legitimate protocol analysis and did not involve neighboring wireless networks or unauthorized access.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=395b7afd44bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Container Security: Understanding Docker Isolation, Security Risks, and Hardening Techniques]]></title>
            <link>https://medium.com/@yunusemreerten08/container-security-understanding-docker-isolation-security-risks-and-hardening-techniques-be9966a153ae?source=rss-7493fd34a983------2</link>
            <guid isPermaLink="false">https://medium.com/p/be9966a153ae</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[container-security]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Yunusemreerten]]></dc:creator>
            <pubDate>Mon, 02 Nov 2026 15:46:19 GMT</pubDate>
            <atom:updated>2026-11-02T15:46:19.217Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Exploring how containers work, why container security matters, and how Docker security mechanisms can reduce common risks through practical experiments.</em></p><h3>1. Introduction</h3><p>Containers have become an important part of modern software development.</p><p>From small applications to large cloud-based systems, container technologies allow developers to package and deploy software in consistent and portable environments.</p><p>Docker is one of the most widely used container platforms. It simplifies application deployment by packaging the application and its dependencies into a container image.</p><p>However, running an application inside a container does not automatically make it secure.</p><p>A container might run with unnecessary privileges, use vulnerable dependencies, expose sensitive files, or consume excessive system resources.</p><p>These issues can create security risks not only for the container itself but potentially for the underlying host system.</p><p>This is where <strong>container security</strong> becomes important.</p><p>In this article, I will explain why container security matters, how container isolation works, and which security mechanisms can reduce common risks.</p><p>I will also demonstrate several Docker security features using a hands-on laboratory environment built on Kali Linux.</p><p>The practical experiments will focus on three areas:</p><ul><li>Running containers as root and non-root users.</li><li>Restricting Linux capabilities and privilege escalation.</li><li>Protecting container filesystems and limiting resource usage.</li></ul><h3>2. What Is Containerization?</h3><p>Containerization is a technology that packages an application together with its required dependencies, libraries, and configuration into a portable environment.</p><p>A container can run consistently across different systems as long as a compatible container runtime and underlying platform are available.</p><p>For example, a developer might build a web application on their computer and package it into a Docker image.</p><p>The same image can then be used in a testing environment or deployed to a server without manually installing the application’s dependencies again.</p><h3>Containers vs. Virtual Machines</h3><p>Although containers and virtual machines provide forms of isolation, their architectures are different.</p><p>A traditional virtual machine includes its own guest operating system and kernel.</p><p>Containers, on the other hand, typically share the host operating system’s kernel while isolating individual processes and their execution environments.</p><p>This generally makes containers more lightweight than traditional virtual machines.</p><p>FeatureVirtual MachinesContainersOperating systemSeparate guest OSShared host kernelIsolationHypervisor-basedOS-level mechanismsResource overheadGenerally higherGenerally lowerStartup timeOften slowerUsually fasterMain use casesFull system virtualizationApplication packaging and deployment</p><p>However, the shared-kernel architecture introduces an important security consideration.</p><p><strong>A container is not a complete security boundary equivalent to a virtual machine.</strong></p><p>A vulnerability in the host kernel or an insecure container configuration can affect the isolation between containers and the host.</p><p>For this reason, container isolation should be combined with additional security controls.</p><h3>3. How Do Containers Work?</h3><p>To understand container security, we first need to understand some of the Linux technologies that make containers possible.</p><h3>Linux Namespaces</h3><p>Namespaces provide isolation for different system resources.</p><p>For example:</p><ul><li><strong>PID namespace:</strong> Isolates process identifiers and process visibility.</li><li><strong>Network namespace:</strong> Provides separate network interfaces, routing tables, and related network resources.</li><li><strong>Mount namespace:</strong> Isolates filesystem mount views.</li><li><strong>UTS namespace:</strong> Isolates hostname and domain-name information.</li><li><strong>IPC namespace:</strong> Isolates certain inter-process communication resources.</li><li><strong>User namespace:</strong> Allows user and group IDs to be mapped between different environments.</li></ul><p>These mechanisms help processes inside containers operate within separate views of the system.</p><p>For example, a process inside a container may see itself as PID 1 even though it has a different PID on the host.</p><p>However, namespaces do not automatically prevent every form of interaction with the host.</p><h3>Control Groups (cgroups)</h3><p>Control groups are Linux kernel mechanisms used to manage and limit resource consumption.</p><p>They can control resources such as:</p><ul><li>Memory</li><li>CPU</li><li>Processes and threads</li><li>Certain I/O resources</li></ul><p>For example, Docker can use cgroups to limit a container to a specific amount of memory.</p><p>This is useful when multiple containers share the same host because excessive resource usage by one application could affect other workloads.</p><h3>Container Images and Runtimes</h3><p>A Docker image contains the filesystem content and metadata needed to create a container.</p><p>When a container starts, the container runtime creates the execution environment and applies the configured isolation and resource restrictions.</p><p>In a typical Linux Docker Engine deployment, components such as Docker Engine, containerd, and runc participate in managing container execution.</p><p>These components provide the infrastructure for running containers, but their security depends on how they are configured and maintained.</p><h3>4. Why Is Container Security Important?</h3><p>Containers simplify deployment, but they also introduce risks that developers and system administrators need to understand.</p><h3>Excessive Privileges</h3><p>Some applications run as the root user even when they do not require administrative privileges.</p><p>If such an application is compromised, the attacker may gain access to more privileged operations inside the container.</p><h3>Vulnerable Container Images</h3><p>Container images can contain outdated software packages, vulnerable libraries, or insecure configurations.</p><p>Using an unknown or unmaintained image may introduce security weaknesses into an application environment.</p><h3>Insecure Runtime Configuration</h3><p>Containers can be configured with additional permissions, filesystem mounts, network access, and Linux capabilities.</p><p>If these settings provide more access than necessary, they may weaken isolation.</p><p>For example, mounting the Docker daemon socket into a container can expose powerful Docker management functionality.</p><h3>Resource Exhaustion</h3><p>A container without appropriate resource restrictions may consume excessive memory or create large numbers of processes.</p><p>This can affect the performance and availability of other applications running on the same host.</p><h3>Sensitive Data Exposure</h3><p>Credentials, API keys, and other secrets may be exposed if they are stored directly inside container images or insecure configuration files.</p><p>These risks demonstrate why container security must be considered throughout application development, image creation, deployment, and runtime operation.</p><h3>5. Container Security Mechanisms</h3><p>Docker and Linux provide several mechanisms that help reduce these risks.</p><h3>Least Privilege</h3><p>The principle of least privilege means that applications should receive only the permissions required to perform their intended tasks.</p><p>For containers, this may involve running applications as non-root users and restricting Linux capabilities.</p><h3>Linux Capabilities</h3><p>Linux capabilities divide many traditional root privileges into more specific permission categories.</p><p>Instead of granting unrestricted root capabilities, container administrators can remove unnecessary permissions.</p><h3>No New Privileges</h3><p>The no-new-privileges mechanism prevents a process from gaining additional privileges through operations such as executing setuid programs.</p><p>This helps reduce certain privilege escalation opportunities.</p><h3>Read-Only Filesystems</h3><p>A read-only root filesystem prevents processes from modifying files in the container’s root filesystem.</p><p>Applications that require writable directories can use carefully configured temporary filesystems or volumes.</p><h3>Resource Limits</h3><p>Memory, CPU, and PID limits can reduce the risk of a container consuming excessive host resources.</p><p>However, these mechanisms are not complete security solutions on their own.</p><p>They work best when applied together.</p><h3>6. Practical Lab: Setting Up Docker on Kali Linux</h3><p>To explore these security mechanisms, I created a laboratory using Kali Linux running inside VMware Workstation.</p><p>I installed Docker Engine and verified the installation by running the official hello-world container.</p><p>The command was:</p><pre>docker run --rm hello-world</pre><p>Docker returned:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*LBRg6I9RnhVI5E32i2yLOA.png" /></figure><pre>Hello from Docker!</pre><pre>This message shows that your installation appears to be working correctly.</pre><p>This confirmed that the Docker client could communicate with the Docker daemon, retrieve an image, and execute a container.</p><p>For the remaining experiments, I used the Ubuntu 24.04 container image.</p><p>All tests were performed locally and did not require deploying a vulnerable application or exposing container services to the internet.</p><h3>7. Lab 1: Root vs. Non-Root Containers</h3><p>The first experiment focused on user privileges.</p><p>By default, many container images start their processes using UID 0, which represents the root user inside the container.</p><p>Although container root does not always have unrestricted privileges on the host, unnecessary root access can increase security risks.</p><h3>Running a Container as Root</h3><p>First, I executed:</p><pre>docker run --rm ubuntu:24.04 id</pre><p>The output was:</p><pre>uid=0(root) gid=0(root) groups=0(root)</pre><p>This confirmed that the process was running as root inside the container.</p><h3>Running a Container as a Non-Root User</h3><p>Next, I used Docker’s --user option:</p><pre>docker run --rm --user 1000:1000 ubuntu:24.04 id</pre><p>The output was:</p><pre>uid=1000(ubuntu) gid=1000(ubuntu) groups=1000(ubuntu)</pre><p>The --user option allowed me to specify the user and group IDs used to run the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*YrKfy3lI8w5ZIuxQKT9ZsA.png" /><figcaption><strong>Figure 1 — Comparing root and non-root execution inside Ubuntu Docker containers using the Linux </strong><strong>id command.</strong></figcaption></figure><h3>Security Analysis</h3><p>The results showed that the same Docker image could execute processes using different user identities.</p><p>Running an application as a non-root user can reduce the privileges available to an attacker if the application becomes compromised.</p><p>However, it is important to distinguish running a container process as non-root from running Docker itself in rootless mode.</p><p>The --user option changes the process identity inside the container. It does not automatically make the Docker daemon rootless.</p><p>This experiment demonstrated a basic but important container security principle:</p><p><strong>Applications should not run with root privileges unless those privileges are necessary.</strong></p><h3>8. Lab 2: Linux Capabilities and Privilege Restrictions</h3><p>The second experiment focused on Linux capabilities and privilege restrictions.</p><p>Linux capabilities provide more granular control over operations traditionally associated with root privileges.</p><p>Docker normally provides containers with a restricted set of capabilities rather than granting every available capability.</p><h3>Examining Default Capabilities</h3><p>I started by checking the effective capabilities of a process inside a default Ubuntu container:</p><pre>docker run --rm ubuntu:24.04 sh -c &#39;grep CapEff /proc/self/status&#39;</pre><p>The output was:</p><pre>CapEff: 00000000a80425fb</pre><p>The hexadecimal value represents the process’s effective Linux capability set.</p><h3>Dropping All Capabilities</h3><p>Next, I repeated the command while removing all capabilities:</p><pre>docker run --rm --cap-drop ALL ubuntu:24.04 sh -c &#39;grep CapEff /proc/self/status&#39;</pre><p>This time, the output was:</p><pre>CapEff: 0000000000000000</pre><p>The all-zero value indicated that the process had no effective Linux capabilities.</p><p>This does not mean every possible Linux permission was removed, but it confirms that the effective capability set was empty.</p><h3>Enabling No New Privileges</h3><p>Finally, I tested Docker’s no-new-privileges option:</p><pre>docker run --rm --security-opt no-new-privileges:true ubuntu:24.04 sh -c &#39;grep NoNewPrivs /proc/self/status&#39;</pre><p>The result was:</p><pre>NoNewPrivs: 1</pre><p>This confirmed that the Linux no_new_privs flag was enabled for the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*J1cSh4Dsg91ggbwD6vqYJw.png" /><figcaption><strong>Figure 2 — Examining default Linux capabilities, dropped capabilities, and the no-new-privileges option in Docker containers.</strong></figcaption></figure><h3>Security Analysis</h3><p>These experiments demonstrated two different approaches to restricting privileges.</p><p>The --cap-drop ALL option removed the effective Linux capabilities available to the container process.</p><p>The no-new-privileges option restricted the process from gaining new privileges through certain execution mechanisms.</p><p>These mechanisms complement each other but do not perform the same function.</p><p>In a production environment, capabilities should be granted according to actual application requirements.</p><p>Rather than automatically adding broad permissions, administrators should begin with minimal privileges and add only what the application genuinely needs.</p><h3>9. Lab 3: Read-Only Filesystem and Resource Limits</h3><p>The third experiment focused on filesystem protection and resource restrictions.</p><p>These mechanisms are useful for reducing unauthorized filesystem modifications and limiting the resources a container can consume.</p><h3>Testing a Normal Writable Filesystem</h3><p>First, I created a file inside a container using the default filesystem configuration:</p><pre>docker run --rm ubuntu:24.04 sh -c &#39;touch /testfile &amp;&amp; echo &quot;File created successfully&quot;&#39;</pre><p>The output was:</p><pre>File created successfully</pre><p>This confirmed that the process could create a file at the specified location.</p><h3>Enabling a Read-Only Filesystem</h3><p>Next, I repeated the operation using Docker’s --read-only flag:</p><pre>docker run --rm --read-only ubuntu:24.04 sh -c &#39;touch /testfile&#39;</pre><p>The output was:</p><pre>touch: cannot touch &#39;/testfile&#39;: Read-only file system</pre><p>This demonstrated that the container’s root filesystem was mounted as read-only.</p><p><strong>An important distinction:</strong> Read-only mode protects the container’s root filesystem, but separately mounted writable volumes or temporary filesystems may still allow writes.</p><p>Therefore, filesystem protection also depends on mount configuration.</p><h3>Setting a Memory Limit</h3><p>I then configured a container with a memory limit of 128 MiB:</p><pre>docker run --rm --memory=128m ubuntu:24.04 sh -c &#39;cat /sys/fs/cgroup/memory.max&#39;</pre><p>The output was:</p><pre>134217728</pre><p>This value represents 128 MiB expressed in bytes.</p><p>The result confirmed that the configured memory limit was visible through the container’s cgroup interface.</p><h3>Limiting Processes</h3><p>Finally, I applied a PID limit:</p><pre>docker run --rm --pids-limit=20 ubuntu:24.04 sh -c &#39;cat /sys/fs/cgroup/pids.max&#39;</pre><p>The output was:</p><pre>20</pre><p>This confirmed that the container’s cgroup PID limit had been configured to 20 tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*BM7lm1nRSQLhtLIFGdtFQw.png" /><figcaption><strong>Figure 3 — Demonstrating Docker read-only filesystem protection, memory limits, and PID restrictions.</strong></figcaption></figure><h3>Security Analysis</h3><p>The read-only test demonstrated an actual blocked filesystem operation.</p><p>The memory and PID tests confirmed that the corresponding limits were configured correctly.</p><p>However, I did not perform a resource exhaustion experiment or intentionally exceed those limits.</p><p>These findings should therefore be interpreted as configuration verification rather than evidence of how the system behaves under a resource exhaustion attack.</p><p>When used appropriately, filesystem and resource restrictions can help reduce the impact of vulnerable or malfunctioning applications.</p><h3>10. Comparing the Security Controls</h3><p>The experiments demonstrated several Docker security mechanisms and the specific risks they are designed to reduce.</p><p>Security mechanismPurposeObserved resultNon-root userReduce process privilegesUID changed from 0 to 1000Capability restrictionLimit privileged operationsEffective capabilities became zeroNo New PrivilegesRestrict privilege gainsNoNewPrivs: 1Read-only filesystemPrevent root filesystem modificationsFile creation failedMemory limitRestrict memory consumption128 MiB limit confirmedPID limitRestrict process/thread creationLimit of 20 confirmed</p><p>The most important observation was that these mechanisms address different aspects of container security.</p><p>Running as non-root does not automatically create a read-only filesystem.</p><p>Dropping Linux capabilities does not automatically enforce memory limits.</p><p>Similarly, resource limits do not prevent insecure application configurations.</p><p>Container security requires multiple complementary controls rather than relying on a single setting.</p><h3>11. Container Security Best Practices</h3><p>Based on the concepts explored in this article and established container security guidance, several practices are particularly important.</p><h3>Run Applications as Non-Root</h3><p>Use an unprivileged user whenever possible.</p><p>This can be configured through Docker’s --user option or the USER instruction in a Dockerfile.</p><h3>Minimize Linux Capabilities</h3><p>Remove capabilities that applications do not need.</p><p>Avoid privileged containers unless there is a specific, justified requirement.</p><h3>Protect the Docker Daemon</h3><p>Do not expose the Docker daemon socket to untrusted applications or containers.</p><p>Access to the Docker API can provide extensive control over containers and host resources.</p><h3>Use Trusted and Maintained Images</h3><p>Prefer maintained image sources, use appropriately minimal base images, and regularly inspect dependencies for known vulnerabilities.</p><p>Container image scanning can help identify outdated or vulnerable packages before deployment.</p><h3>Restrict Filesystem Access</h3><p>Use read-only root filesystems where possible.</p><p>Provide only the writable directories required by the application, and carefully control volume mounts.</p><h3>Apply Resource Limits</h3><p>Configure suitable memory, CPU, and PID limits to reduce the risk of unexpected resource consumption.</p><h3>Keep the Host and Runtime Updated</h3><p>Since Linux containers share the host kernel, container security also depends on the security of the underlying operating system.</p><p>Keeping the kernel, Docker Engine, and container runtime updated is essential.</p><h3>Protect Secrets</h3><p>Avoid embedding passwords, API keys, and tokens directly into images or source code.</p><p>Use suitable secret-management mechanisms and restrict access to sensitive data.</p><h3>Consider Additional Isolation</h3><p>Depending on application requirements, additional protections may include seccomp profiles, AppArmor or SELinux policies, user namespaces, and rootless container execution.</p><p>These controls can provide additional layers of protection beyond basic Docker configuration.</p><h3>12. Limitations of the Laboratory</h3><p>Although the experiments demonstrated several important security mechanisms, the scope of the laboratory was limited.</p><p>First, the tests focused on Docker runtime configuration rather than actual exploitation of container vulnerabilities.</p><p>Second, the experiments used short-lived Ubuntu containers rather than a complete production application.</p><p>Third, rootless Docker mode, custom seccomp profiles, AppArmor policies, and container image vulnerability scanning were discussed but not tested.</p><p>Finally, the experiments did not measure the effectiveness of the security settings against real container escape attacks.</p><p>The results should therefore be understood as demonstrations of security configuration behavior, not as proof that a container is completely secure.</p><h3>13. Conclusion</h3><p>Container technologies have changed how applications are developed, packaged, and deployed.</p><p>They provide portability, consistent execution environments, and efficient resource usage.</p><p>However, containerization alone does not guarantee application security.</p><p>In this article, I examined how Linux namespaces, cgroups, container images, and runtimes contribute to container operation and isolation.</p><p>I then performed practical Docker experiments on Kali Linux to investigate different security mechanisms.</p><p>The first experiment demonstrated the difference between running container processes as root and non-root users.</p><p>The second experiment showed how Linux capabilities and the no-new-privileges option can restrict process privileges.</p><p>The third experiment demonstrated read-only filesystem protection and verified memory and PID limits.</p><p>These experiments highlighted an important lesson:</p><p><strong>Container security is not a single feature. It is the result of multiple security controls working together.</strong></p><p>Running applications with minimal privileges, restricting unnecessary capabilities, protecting filesystems, applying resource limits, and maintaining trusted images can all contribute to a more secure container environment.</p><p>Overall, this laboratory helped me better understand the relationship between container isolation, Linux security mechanisms, and practical Docker hardening.</p><h3>References</h3><ol><li><a href="https://docs.docker.com/engine/security/">Docker Documentation — Docker Engine Security</a></li><li><a href="https://docs.docker.com/reference/cli/docker/container/run/">Docker Documentation — Docker Run Reference</a></li><li><a href="https://docs.docker.com/engine/security/rootless/">Docker Documentation — Rootless Mode</a></li><li><a href="https://docs.docker.com/engine/containers/resource_constraints/">Docker Documentation — Resource Constraints</a></li><li><a href="https://cheatsheetseries.owasp.org/cheatsheets/Docker_Security_Cheat_Sheet.html">OWASP — Docker Security Cheat Sheet</a></li><li><a href="https://docs.docker.com/engine/security/seccomp/">Docker Documentation — Seccomp Security Profiles</a></li><li><a href="https://man7.org/linux/man-pages/man7/capabilities.7.html">Linux Manual Pages — Capabilities</a></li></ol><p><em>All experiments were performed in a controlled local laboratory environment using Docker containers on Kali Linux. The examples are intended for educational purposes and demonstrate security configuration mechanisms rather than real-world exploitation.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be9966a153ae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TACACS+ vs. RADIUS: Understanding AAA Protocols Through Practical Labs]]></title>
            <link>https://medium.com/@yunusemreerten08/tacacs-vs-radius-understanding-aaa-protocols-through-practical-labs-6db2ebdb5269?source=rss-7493fd34a983------2</link>
            <guid isPermaLink="false">https://medium.com/p/6db2ebdb5269</guid>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[radius]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[tacacs]]></category>
            <category><![CDATA[aaa]]></category>
            <dc:creator><![CDATA[Yunusemreerten]]></dc:creator>
            <pubDate>Mon, 26 Oct 2026 09:17:54 GMT</pubDate>
            <atom:updated>2026-10-26T09:17:54.296Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Exploring authentication, authorization, accounting, protocol security, and network traffic through hands-on experiments with Kali Linux.</em></p><h3>1. Introduction</h3><p>When managing a network, security is not only about protecting devices from external attacks. It is also about controlling who can access those devices and what they are allowed to do after logging in.</p><p>Imagine a company with dozens of routers, switches, wireless access points, and VPN connections. Managing separate user credentials on every device would quickly become difficult.</p><p>What happens when an employee leaves the company? How do administrators control which users can modify network configurations? How can organizations keep track of administrative activities?</p><p>These questions are closely related to three important security concepts: <strong>Authentication, Authorization, and Accounting (AAA).</strong></p><p>Two protocols commonly associated with AAA are <strong>RADIUS and TACACS+</strong>.</p><p>Although they serve similar purposes, they differ in their architecture, communication methods, authorization capabilities, and security characteristics.</p><p>In this article, I will compare TACACS+ and RADIUS, explain their advantages and disadvantages, and demonstrate how they work through practical experiments using Kali Linux, FreeRADIUS, TACACS+, and Wireshark.</p><h3>2. Understanding AAA: Authentication, Authorization, and Accounting</h3><p>Before comparing the protocols, it is important to understand AAA.</p><p>AAA is a security framework used to manage access to network resources.</p><p>It consists of three components.</p><h3>Authentication — Who are you?</h3><p>Authentication verifies the identity of a user or device requesting access.</p><p>For example, when a network administrator attempts to log in to a router, the system checks whether the provided credentials are valid.</p><p>If authentication succeeds, the user may proceed to the next stage.</p><h3>Authorization — What are you allowed to do?</h3><p>Authorization determines which resources or operations an authenticated user can access.</p><p>For example, a network administrator might be allowed to view router configurations but not modify them.</p><p>Successful authentication does not automatically mean that a user should have unrestricted access.</p><h3>Accounting — What did you do?</h3><p>Accounting collects information about user activity and sessions.</p><p>Depending on the implementation, it may record login times, session durations, resource usage, or administrative actions.</p><p>These records can support auditing, troubleshooting, and security investigations.</p><p>Together, these mechanisms help organizations implement centralized access control.</p><h3>3. What Is RADIUS?</h3><p>RADIUS stands for <strong>Remote Authentication Dial-In User Service</strong>.</p><p>It is a networking protocol used to provide centralized authentication, authorization, and accounting services.</p><p>Although RADIUS was originally developed for remote network access, it is now widely used in environments such as:</p><ul><li>Enterprise Wi-Fi authentication</li><li>VPN access</li><li>IEEE 802.1X network access control</li><li>Network access servers</li><li>Internet service provider infrastructure</li></ul><p>In a typical RADIUS environment, a network access device communicates with a centralized RADIUS server to determine whether a user should be granted network access.</p><p>For example, when an employee connects to an enterprise wireless network, the access infrastructure can communicate with a RADIUS server to authenticate the user.</p><h3>How RADIUS Works</h3><p>Traditional RADIUS commonly uses UDP.</p><p>Its standard ports are:</p><ul><li>UDP 1812 — Authentication and Authorization</li><li>UDP 1813 — Accounting</li></ul><p>The authentication exchange usually involves an Access-Request message followed by an Access-Accept, Access-Reject, or Access-Challenge response.</p><p>An important architectural characteristic of RADIUS is that authentication and authorization information are often handled within the same access exchange.</p><p>However, the exact behavior depends on the authentication method and network configuration.</p><h3>4. What Is TACACS+?</h3><p>TACACS+ stands for <strong>Terminal Access Controller Access-Control System Plus</strong>.</p><p>It is an AAA protocol commonly used to control administrative access to network devices.</p><p>TACACS+ is particularly useful in environments where administrators need different levels of access to routers, switches, firewalls, and other network infrastructure.</p><p>For example, an organization might want junior administrators to execute monitoring commands while preventing them from changing device configurations.</p><p>TACACS+ can support this type of granular authorization.</p><h3>How TACACS+ Works</h3><p>Traditional TACACS+ uses TCP port 49.</p><p>Unlike common RADIUS access workflows, TACACS+ provides distinct message types for:</p><ul><li>Authentication</li><li>Authorization</li><li>Accounting</li></ul><p>This separation is one of the protocol’s most important architectural features.</p><p>A user may successfully authenticate but still be denied permission to execute a particular command.</p><p>TACACS+ authorization requests can include information about the requested service, command, and command arguments.</p><p>This makes it particularly suitable for network device administration.</p><h3>5. TACACS+ vs. RADIUS: Key Differences</h3><p>Although both protocols support AAA, their technical characteristics differ.</p><p>FeatureRADIUSTACACS+TransportTraditionally UDPTCPStandard portsUDP 1812/1813TCP 49Common purposeNetwork access controlNetwork device administrationAuthentication and authorizationOften combined in access exchangesSeparate message typesCommand authorizationImplementation- and vendor-dependentGranular command authorizationLegacy credential protectionPassword attribute hidingPacket-body obfuscationCommon environmentsWi-Fi, VPN, 802.1XRouters, switches, firewalls</p><h3>Transport Protocol</h3><p>One of the most visible differences is the transport layer.</p><p>Traditional RADIUS uses UDP, while TACACS+ uses TCP.</p><p>UDP provides connectionless communication, meaning there is no TCP-style connection establishment before sending a RADIUS request.</p><p>TCP provides a connection-oriented transport mechanism with sequencing and retransmission.</p><p>However, using TCP does not automatically make a protocol more secure.</p><h3>Authorization Capabilities</h3><p>TACACS+ provides a flexible authorization architecture that is particularly useful for controlling administrative commands.</p><p>For example, a policy can allow an administrator to run show version while denying configure terminal.</p><p>RADIUS can also support authorization policies, including vendor-specific attributes, but granular device-command authorization is generally more closely associated with TACACS+.</p><h3>Security Considerations</h3><p>A commonly repeated statement is that RADIUS encrypts only passwords while TACACS+ encrypts entire packets.</p><p>This description is too simplistic.</p><p>Traditional RADIUS uses a password-hiding mechanism for the User-Password attribute, while other packet attributes may remain visible.</p><p>Traditional TACACS+ obfuscates the packet body, but its header remains visible.</p><p>Furthermore, TACACS+ legacy obfuscation should not be considered equivalent to modern cryptographic encryption.</p><p>Both protocols require appropriate security protections when deployed over untrusted networks.</p><h3>6. Advantages and Disadvantages</h3><h3>RADIUS Advantages</h3><p><strong>Wide Adoption</strong></p><p>RADIUS is extensively supported by wireless infrastructure, VPN solutions, and network access systems.</p><p><strong>Suitable for Network Access Control</strong></p><p>It works well in environments where the main objective is deciding whether a user or device can connect to a network.</p><p><strong>Centralized Authentication</strong></p><p>Administrators can manage authentication policies through centralized infrastructure instead of maintaining separate credentials on every device.</p><p><strong>Integration with Enterprise Technologies</strong></p><p>RADIUS can be integrated with identity systems and modern authentication frameworks, depending on the deployment.</p><h3>RADIUS Disadvantages</h3><p><strong>Legacy Security Limitations</strong></p><p>Classic RADIUS does not provide modern encryption for the entire packet.</p><p><strong>Less Direct Command-Level Authorization</strong></p><p>Although implementations may support advanced authorization attributes, TACACS+ is generally better suited to granular network device command control.</p><p><strong>Configuration Complexity</strong></p><p>Advanced RADIUS deployments involving EAP, certificates, and external identity systems can require careful configuration.</p><h3>TACACS+ Advantages</h3><p><strong>Granular Authorization</strong></p><p>TACACS+ can allow or deny specific administrative commands.</p><p><strong>Separate AAA Operations</strong></p><p>Authentication, authorization, and accounting are represented by distinct message types.</p><p><strong>Suitable for Device Administration</strong></p><p>It provides a flexible approach to controlling administrator permissions on network infrastructure.</p><p><strong>Centralized Administrative Policies</strong></p><p>Organizations can apply consistent management access policies across supported network devices.</p><h3>TACACS+ Disadvantages</h3><p><strong>Less Common in General Network Access</strong></p><p>TACACS+ is not as widely used as RADIUS for enterprise Wi-Fi or 802.1X authentication.</p><p><strong>Legacy Security Weaknesses</strong></p><p>Traditional TACACS+ obfuscation does not provide modern confidentiality and integrity guarantees.</p><p><strong>Compatibility Considerations</strong></p><p>Server and client support may differ depending on the vendor and implementation.</p><p><strong>Operational Complexity</strong></p><p>Granular authorization policies require careful configuration and maintenance.</p><h3>7. Practical Lab: Testing RADIUS Authentication</h3><p>To understand these differences in practice, I configured both protocols in a Kali Linux laboratory environment.</p><p>For the RADIUS experiment, I used FreeRADIUS 3.2.10.</p><p>For TACACS+, I used a locally compiled tac_plus server.</p><p>Both were tested on the same Kali Linux virtual machine using the loopback interface (127.0.0.1).</p><p>This setup allowed me to observe protocol behavior without exposing the services to external networks.</p><h3>Step 1: Installing FreeRADIUS</h3><p>I installed FreeRADIUS and its testing utilities:</p><pre>sudo apt install freeradius freeradius-utils</pre><p>After installation, I started the service:</p><pre>sudo systemctl start freeradius</pre><p>I confirmed that FreeRADIUS was running successfully.</p><h3>Step 2: Creating a Test User</h3><p>I configured a local test account in the FreeRADIUS authorization file:</p><pre>labuser Cleartext-Password := &quot;LabPass123!&quot;</pre><p>This was a laboratory-only account created to demonstrate authentication.</p><p>After validating the configuration, I restarted the FreeRADIUS service.</p><h3>Step 3: Testing Authentication</h3><p>I first sent an authentication request using the correct credentials:</p><pre>radtest labuser &#39;LabPass123!&#39; 127.0.0.1 0 testing123</pre><p>FreeRADIUS responded with:</p><pre>Received Access-Accept</pre><p>Next, I tested an incorrect password:</p><pre>radtest labuser &#39;WrongPass123!&#39; 127.0.0.1 0 testing123</pre><p>This time, the server returned:</p><pre>Received Access-Reject</pre><p>These results confirmed that FreeRADIUS correctly distinguished valid and invalid credentials.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*SnMyyUW-wFdO_M0RMUMZtA.png" /><figcaption><strong>[Figure 1 — FreeRADIUS authentication tests showing Access-Accept and Access-Reject responses.]</strong></figcaption></figure><h3>Step 4: Analyzing RADIUS Traffic with Wireshark</h3><p>Next, I opened Wireshark and selected the loopback interface.</p><p>Because the authentication requests were sent to 127.0.0.1, the traffic was visible on the local loopback interface rather than the virtual machine&#39;s Ethernet adapter.</p><p>I used the following display filter:</p><pre>radius</pre><p>After repeating the authentication tests, Wireshark captured four RADIUS messages:</p><p>PacketMessageIdentifier1Access-Request532Access-Accept533Access-Request2434Access-Reject243</p><p>The matching identifiers helped associate each response with its corresponding request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/969/1*4bu16q3IN3Fa46mCJPV6Bw.png" /><figcaption><strong>[Figure 2 — Wireshark capture showing RADIUS Access-Request, Access-Accept, and Access-Reject messages.]</strong></figcaption></figure><p>I then inspected the first Access-Request packet.</p><p>Wireshark displayed:</p><pre>Code: Access-Request (1)<br>Identifier: 53<br>User-Name: labuser<br>User-Password: Encrypted<br>Destination Port: 1812</pre><p>One interesting observation was that the username remained visible in the packet, while the password attribute was displayed as encrypted.</p><p>In classic RADIUS PAP, this password field is hidden using a shared-secret-based MD5 construction. It should not be confused with modern authenticated encryption.</p><p>The packet also included a Message-Authenticator attribute, which provides integrity protection for the corresponding message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/926/1*G12r4nr7dUSzlMGRAMIAUQ.png" /><figcaption><strong>[Figure 3 — RADIUS Access-Request packet showing username, password attribute, and authentication fields.]</strong></figcaption></figure><p>This experiment demonstrated how traditional RADIUS handles authentication messages and protects certain attributes.</p><h3>8. Practical Lab: Testing TACACS+ Authentication</h3><p>For the second part of the laboratory, I configured a TACACS+ server on Kali Linux.</p><p>The server was compiled from source and configured to listen locally on TCP port 49.</p><h3>Step 1: Configuring the TACACS+ Server</h3><p>I created a configuration file containing a shared secret and a local test account.</p><p>A simplified version of the initial configuration was:</p><pre>key = &quot;LabTacacsKey2026&quot;</pre><pre>user = labuser {<br>    login = cleartext &quot;LabPass123!&quot;</pre><pre>    service = exec {<br>        priv-lvl = 15<br>    }<br>}</pre><p>The shared secret was used for TACACS+ communication between the client and server.</p><p>The priv-lvl = 15 attribute represented an administrative privilege level that a compatible network device could interpret.</p><p>This did not grant root privileges on Kali Linux.</p><p>I started the TACACS+ service and verified that it was listening on 127.0.0.1:49.</p><h3>Step 2: Testing Authentication</h3><p>I used a Python TACACS+ client to send authentication requests.</p><p>With the correct password:</p><pre>tacacs_client -u labuser -H 127.0.0.1 \<br>-k &#39;LabTacacsKey2026&#39; -v authenticate \<br>-p &#39;LabPass123!&#39;</pre><p>The response was:</p><pre>status: PASS</pre><p>I repeated the test with an incorrect password:</p><pre>tacacs_client -u labuser -H 127.0.0.1 \<br>-k &#39;LabTacacsKey2026&#39; -v authenticate \<br>-p &#39;WrongPass123!&#39;</pre><p>The response was:</p><pre>status: FAIL</pre><p>Both tests behaved as expected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*ET4A8kdHDnj9gbh-aY4wOQ.png" /><figcaption><strong>[Figure 4 — TACACS+ authentication tests showing PASS and FAIL responses.]</strong></figcaption></figure><h3>Step 3: Analyzing TACACS+ Traffic</h3><p>Next, I captured the TACACS+ traffic using Wireshark.</p><p>I selected the loopback interface and applied:</p><pre>tcp.port == 49</pre><p>Unlike the RADIUS capture, the TACACS+ traffic included TCP connection establishment.</p><p>The capture showed the familiar three-way handshake:</p><pre>SYN → SYN/ACK → ACK</pre><p>Authentication messages were then exchanged over the established connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*srNyqR-2T7EFEDCCBAj13w.png" /><figcaption><strong>[Figure 5 — Wireshark capture of TACACS+ authentication messages over TCP port 49.]</strong></figcaption></figure><p>I also inspected the TACACS+ packet details.</p><p>Wireshark displayed information such as:</p><pre>Type: Authentication (1)<br>Sequence Number: 3<br>Flags: 0x00<br>Session ID: 3242594414<br>Encrypted Request</pre><p>The Sequence Number helps track message ordering within the TACACS+ session.</p><p>The Session ID identifies the corresponding protocol session.</p><p>The Flags field indicated that the packet body was obfuscated.</p><p>Importantly, Wireshark could identify the TACACS+ header even though the payload was not directly readable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NcXB6cKDl-af9Jx0SPbAuA.png" /><figcaption><strong>[Figure 6 — TACACS+ packet details showing authentication type, sequence number, session identifier, and obfuscated payload.]</strong></figcaption></figure><p>This provided a practical demonstration of the difference between the packet structures of traditional RADIUS and TACACS+.</p><h3>9. TACACS+ Command-Level Authorization</h3><p>One of the most interesting parts of this experiment was testing command authorization.</p><p>Unlike basic authentication, authorization determines what an authenticated user is permitted to do.</p><p>I wanted to demonstrate a scenario where an administrator could view device information but could not change its configuration.</p><h3>Step 1: Testing Shell Authorization</h3><p>I first sent a shell authorization request:</p><pre>tacacs_client -u labuser -H 127.0.0.1 \<br>-k &#39;LabTacacsKey2026&#39; -v authorize \<br>-c service=shell &#39;cmd=&#39;</pre><p>The server returned:</p><pre>status: PASS<br>priv-lvl=15</pre><p>This indicated that the configured shell authorization policy was applied successfully.</p><p>However, granting a shell session did not automatically mean that every command was permitted.</p><h3>Step 2: Configuring Command Authorization</h3><p>I updated the TACACS+ server configuration to define separate command rules.</p><p>The relevant policy was:</p><pre>cmd = show {<br>    permit .*<br>}</pre><pre>cmd = configure {<br>    deny .*<br>}</pre><p>The first rule permitted show commands.</p><p>The second rule denied configure commands.</p><h3>Step 3: Testing Allowed and Denied Commands</h3><p>After restarting the TACACS+ server, I tested two requests.</p><p><strong>Test 1: show version</strong></p><pre>tacacs_client -u labuser -H 127.0.0.1 \<br>-k &#39;LabTacacsKey2026&#39; -v authorize \<br>-c service=shell cmd=show cmdarg=version</pre><p>Result:</p><pre>status: PASS</pre><p><strong>Test 2: configure terminal</strong></p><pre>tacacs_client -u labuser -H 127.0.0.1 \<br>-k &#39;LabTacacsKey2026&#39; -v authorize \<br>-c service=shell cmd=configure cmdarg=terminal</pre><p>Result:</p><pre>status: FAIL</pre><p>The results demonstrated that TACACS+ could evaluate specific administrative commands against a configured authorization policy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*WoR80N5EIuAaMrXoam1lkw.png" /><figcaption><strong>[Figure 7 — TACACS+ command authorization allowing </strong><strong>show version while denying </strong><strong>configure terminal.]</strong></figcaption></figure><p>These tests simulated authorization requests. They did not execute commands on a physical network device.</p><p>Nevertheless, they demonstrated an important aspect of TACACS+: <strong>successful authentication does not automatically grant permission to execute every command.</strong></p><p>This is particularly valuable when organizations need to separate monitoring responsibilities from network configuration privileges.</p><h3>10. What About Accounting?</h3><p>Although AAA includes Accounting, this laboratory focused primarily on Authentication and Authorization.</p><p>RADIUS supports accounting exchanges, commonly using UDP port 1813, with messages such as Accounting-Request and Accounting-Response.</p><p>TACACS+ also supports accounting and can record administrative activities depending on the network device and server configuration.</p><p>In environments where command-level auditing is required, TACACS+ can provide detailed records associated with device administration.</p><p>However, accounting capabilities depend on the implementation and the information supplied by the client.</p><p>No separate accounting exchange was tested in this laboratory, so accounting behavior is discussed here at the protocol level rather than presented as an experimental result.</p><h3>11. Security Considerations: Legacy Protocols and Modern Protection</h3><p>One of the most important lessons from comparing these protocols is that packet protection should not be judged only by whether Wireshark displays a field as encrypted.</p><p>Traditional RADIUS hides the User-Password attribute, but other information may remain visible.</p><p>Legacy TACACS+ protects its body using an obfuscation mechanism rather than modern authenticated encryption.</p><p>According to RFC 8907, TACACS+ deployments should not rely solely on that obfuscation to provide confidentiality and integrity.</p><p>Modern deployments should use appropriately secured transport mechanisms and restrict which systems can communicate with AAA servers.</p><p>For RADIUS, TLS-based transport approaches are available.</p><p>For TACACS+, RFC 9887, published in December 2025, specifies TACACS+ over TLS 1.3.</p><p>This newer specification uses mutual authentication and strong transport protection, with TCP port 300 assigned for TACACS+ over TLS.</p><p>However, support depends on the actual client and server implementations.</p><p>The TACACS+ environment used in this article relied on traditional TCP port 49 and did not implement TACACS+ over TLS.</p><p>Therefore, the packet captures demonstrate legacy TACACS+ behavior rather than the newer TLS-protected protocol.</p><h3>12. When Should You Use RADIUS or TACACS+?</h3><p>The choice depends on the organization’s requirements.</p><h3>Choose RADIUS When:</h3><ul><li>Managing enterprise Wi-Fi authentication.</li><li>Implementing IEEE 802.1X network access control.</li><li>Centralizing VPN authentication.</li><li>Managing access to network connectivity.</li><li>Integrating with infrastructure built around RADIUS and EAP.</li></ul><h3>Choose TACACS+ When:</h3><ul><li>Managing administrative access to routers and switches.</li><li>Requiring granular command authorization.</li><li>Separating network administrator responsibilities.</li><li>Controlling configuration-changing commands.</li><li>Implementing device administration policies with compatible infrastructure.</li></ul><p>Many organizations use both protocols rather than choosing only one.</p><p>For example, RADIUS may manage employee Wi-Fi authentication while TACACS+ manages administrative access to network devices.</p><p>The protocols are therefore better understood as complementary technologies designed for different operational needs.</p><h3>13. Conclusion</h3><p>In this article, I compared RADIUS and TACACS+ from both theoretical and practical perspectives.</p><p>Using Kali Linux, I configured a FreeRADIUS server and tested successful and unsuccessful authentication requests.</p><p>I then examined the RADIUS packets using Wireshark, observing Access-Request, Access-Accept, and Access-Reject messages.</p><p>Next, I configured a TACACS+ server and performed similar authentication tests.</p><p>Wireshark helped demonstrate the transport and packet structure differences between the two protocols.</p><p>Finally, I implemented TACACS+ command authorization policies that allowed show version while denying configure terminal.</p><p>This was the most valuable part of the laboratory because it showed how authentication and authorization serve different purposes.</p><p><strong>RADIUS is particularly useful for centralized network access control, while TACACS+ provides flexible administrative authorization capabilities.</strong></p><p>Neither protocol should be considered universally superior. The correct choice depends on the environment, operational requirements, and available security protections.</p><p>Overall, this lab helped me better understand AAA architecture and how access control policies are applied in real network security environments.</p><h3>References</h3><ol><li><a href="https://www.rfc-editor.org/rfc/rfc2865">RFC 2865 — Remote Authentication Dial-In User Service (RADIUS)</a></li><li><a href="https://www.rfc-editor.org/rfc/rfc2866">RFC 2866 — RADIUS Accounting</a></li><li><a href="https://www.rfc-editor.org/rfc/rfc8907">RFC 8907 — The TACACS+ Protocol</a></li><li><a href="https://www.rfc-editor.org/rfc/rfc9887">RFC 9887 — TACACS+ over TLS 1.3</a></li><li><a href="https://www.freeradius.org/documentation/">FreeRADIUS Documentation</a></li><li><a href="https://www.wireshark.org/docs/">Wireshark Documentation</a></li><li><a href="https://www.rfc-editor.org/rfc/rfc6614">RFC 6614 — RADIUS over TCP/TLS</a></li></ol><p><em>All experiments were performed within an authorized, local laboratory environment. The credentials and shared secrets used in the examples were created solely for testing and should not be reused in production systems.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6db2ebdb5269" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vulnerability Assessment with Nessus: A Hands-On Security Analysis Using Kali Linux and…]]></title>
            <link>https://medium.com/@yunusemreerten08/vulnerability-assessment-with-nessus-a-hands-on-security-analysis-using-kali-linux-and-5bf4da369308?source=rss-7493fd34a983------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bf4da369308</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[nessus]]></category>
            <category><![CDATA[metasploit]]></category>
            <dc:creator><![CDATA[Yunusemreerten]]></dc:creator>
            <pubDate>Fri, 23 Oct 2026 13:44:32 GMT</pubDate>
            <atom:updated>2026-10-23T13:44:32.290Z</atom:updated>
            <content:encoded><![CDATA[<h3>Vulnerability Assessment with Nessus: A Hands-On Security Analysis Using Kali Linux and Metasploitable 2</h3><h3>Vulnerability Assessment with Nessus: A Hands-On Lab Using Kali Linux and Metasploitable 2</h3><p><em>Identifying security weaknesses, understanding vulnerability severity, and analyzing real scan results in a controlled laboratory environment.</em></p><h3>1. Introduction</h3><p>In cybersecurity, one of the most important questions is: <strong>How can we identify security weaknesses before an attacker takes advantage of them?</strong></p><p>Every system connected to a network can potentially contain vulnerabilities. These weaknesses may result from outdated software, insecure configurations, weak passwords, or unnecessary services running in the background.</p><p>For an organization managing hundreds of computers and servers, manually checking every system for vulnerabilities would be time-consuming and difficult.</p><p>This is where vulnerability assessment tools become useful.</p><p>In this article, I will explore <strong>Nessus</strong>, a vulnerability scanner developed by Tenable. I will explain its purpose, how it works, and its advantages and limitations.</p><p>I will also demonstrate a vulnerability assessment that I performed using Nessus Essentials on Kali Linux, targeting a deliberately vulnerable Metasploitable 2 virtual machine.</p><p>Rather than focusing only on vulnerability scores, I will examine three critical findings and explain the technical evidence provided by Nessus.</p><h3>2. What Is Nessus?</h3><p>Nessus is a vulnerability assessment tool. It is designed to identify known vulnerabilities, insecure configurations, outdated software, and other security weaknesses across systems and networks.</p><p>Security professionals use Nessus to evaluate the security posture of their infrastructure and determine which weaknesses require attention.</p><p>Nessus uses a <strong>plugin-based scanning architecture</strong>.</p><p>Plugins are individual security checks that allow Nessus to detect specific vulnerabilities or collect information about a target system.</p><p>For example, a plugin might check whether a server is running an outdated version of Apache Tomcat, whether a network service accepts weak credentials, or whether an insecure protocol is enabled.</p><p>Nessus findings may contain:</p><ul><li>Plugin ID and vulnerability description</li><li>CVE identifiers</li><li>CVSS severity scores</li><li>Technical evidence (Plugin Output)</li><li>Affected services and ports</li><li>Recommended remediation steps</li></ul><p>One important distinction is that <strong>vulnerability assessment is not the same as penetration testing</strong>.</p><p>A vulnerability scanner identifies potential security weaknesses and may actively validate some findings. A penetration test goes further by investigating whether vulnerabilities can be exploited and how they could affect the overall security of a system.</p><p>Nessus is therefore a valuable part of a security assessment, but it does not replace manual security analysis.</p><h3>3. Why Is Vulnerability Assessment Important?</h3><p>Imagine a company operating multiple web applications, databases, and internal servers.</p><p>Some servers may use outdated software. Others might expose services that are no longer needed. A few systems may still have default credentials configured.</p><p>Even if the organization uses firewalls and antivirus software, these weaknesses can create opportunities for attackers.</p><p>Vulnerability assessment helps organizations identify such problems before they lead to security incidents.</p><p>The main goals are to:</p><ul><li>Detect known security vulnerabilities.</li><li>Identify insecure services and configurations.</li><li>Discover systems running unsupported software.</li><li>Prioritize security issues based on their potential impact.</li><li>Provide information that supports remediation</li><li>Track security improvements through repeated assessments.</li></ul><p>However, vulnerability assessment is not simply about finding as many vulnerabilities as possible.</p><p><strong>The real value comes from understanding which vulnerabilities matter and determining how they should be addressed.</strong></p><h3>4. How Does Nessus Work?</h3><p>Nessus performs vulnerability assessments through several scanning and analysis operations.</p><h3>Host Discovery</h3><p>Nessus first attempts to identify reachable systems within the specified target scope.</p><h3>Port and Service Detection</h3><p>After discovering a target, Nessus examines accessible network ports and identifies the services running on them.</p><p>For example, SSH commonly uses port 22, HTTP uses port 80, and HTTPS uses port 443.</p><p>An open port does not automatically indicate a vulnerability. However, identifying services helps determine which security checks should be performed.</p><h3>Vulnerability Detection</h3><p>Nessus uses its plugin database to examine discovered services and configurations for known security weaknesses.</p><p>Some plugins rely on software versions or configuration information, while others perform active checks to validate vulnerabilities.</p><h3>Risk Assessment</h3><p>Nessus can use several metrics to help analysts understand and prioritize findings.</p><p><strong>CVSS (Common Vulnerability Scoring System)</strong> measures the technical severity of vulnerabilities.</p><p><strong>CVE (Common Vulnerabilities and Exposures)</strong> provides standardized identifiers for publicly documented vulnerabilities.</p><p><strong>EPSS (Exploit Prediction Scoring System)</strong> estimates the probability that a vulnerability will be exploited in the wild within the next 30 days.</p><p><strong>VPR (Vulnerability Priority Rating)</strong> is Tenable’s vulnerability prioritization score, which incorporates information about vulnerability characteristics and threats.</p><p>These metrics provide different perspectives. A critical CVSS score does not necessarily mean that a vulnerability is the most urgent issue in every environment.</p><h3>Results and Remediation</h3><p>Once a scan is completed, Nessus presents the findings along with technical descriptions, risk information, and possible solutions.</p><p>The analyst must then interpret the results and determine which actions are appropriate.</p><h3>5. Advantages and Disadvantages of Nessus</h3><p>Like any security tool, Nessus has both strengths and limitations.</p><h3>Advantages</h3><p><strong>Automated Vulnerability Detection</strong></p><p>Nessus reduces the manual effort required to identify known vulnerabilities across networked systems.</p><p><strong>Extensive Plugin Database</strong></p><p>Its plugin-based architecture supports vulnerability checks for many operating systems, applications, and network services.</p><p><strong>Detailed Technical Findings</strong></p><p>Nessus provides information such as vulnerability descriptions, severity scores, affected ports, and remediation recommendations.</p><p><strong>Easy-to-Use Interface</strong></p><p>Its web interface makes it relatively straightforward to configure scans, review findings, and investigate individual vulnerabilities.</p><p><strong>Active Vulnerability Validation</strong></p><p>Certain plugins can perform checks that go beyond software version detection. As demonstrated later in this article, Nessus can sometimes verify vulnerable behavior directly.</p><h3>Disadvantages</h3><p><strong>False Positives and False Negatives</strong></p><p>Not every reported vulnerability is necessarily exploitable, and automated scanners may fail to identify some weaknesses.</p><p><strong>Performance Impact</strong></p><p>Depending on scan configuration and target sensitivity, vulnerability scanning can place additional load on systems and network services.</p><p><strong>Limited Visibility Without Credentials</strong></p><p>Unauthenticated scanning cannot provide the same level of internal system information as properly configured credentialed assessments.</p><p><strong>Free Version Limitations</strong></p><p>Nessus Essentials includes restrictions compared with paid editions.</p><p>During my lab, I discovered that the free Essentials edition did not allow me to generate HTML or PDF scan reports.</p><p>Therefore, I documented the results using screenshots and the technical evidence displayed in the Nessus interface.</p><h3>6. Practical Demonstration: Setting Up the Lab</h3><p>To understand how Nessus works in practice, I created a virtual laboratory using VMware Workstation.</p><p>The environment consisted of two virtual machines.</p><p>ComponentConfigurationScannerNessus EssentialsScanner OSKali Linux 2026.1TargetMetasploitable 2VirtualizationVMware WorkstationNetworkHost-onlyTarget IP192.168.65.130Scan TemplateBasic Network Scan</p><p>Metasploitable 2 is an intentionally vulnerable Linux virtual machine developed for security testing and education.</p><p>Because the target contains deliberately insecure services, I configured it to use an isolated VMware Host-only network.</p><p>This allowed Kali Linux and Metasploitable 2 to communicate without directly exposing the vulnerable target to the external network.</p><h3>Step 1: Installing Nessus on Kali Linux</h3><p>First, I downloaded the appropriate Debian-compatible Nessus installation package from Tenable’s official website.</p><p>After downloading the .deb package, I installed it using:</p><pre>sudo dpkg -i Nessus*.deb</pre><p>I then started the Nessus service:</p><pre>sudo systemctl start nessusd</pre><p>To verify that the service was running, I used:</p><pre>sudo systemctl status nessusd</pre><p>After confirming the service status, I opened the Nessus web interface in Firefox:</p><pre>https://localhost:8834</pre><p>I completed the Nessus Essentials activation and waited for the plugins to finish compiling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZOI-00zcakExBURE4MNxrw.png" /><figcaption>Figure 1 — Nessus Essentials web interface after installation and initial configuration.</figcaption></figure><h3>Step 2: Preparing Metasploitable 2</h3><p>Next, I imported Metasploitable 2 into VMware Workstation.</p><p>I configured the target machine’s network adapter to use Host-only networking and connected Kali Linux to the same isolated virtual network.</p><p>After starting Metasploitable 2, I checked its assigned IP address using:</p><pre>ifconfig</pre><p>The target machine was assigned:</p><pre>192.168.65.130</pre><p>From Kali Linux, I verified connectivity using:</p><pre>ping -c 4 192.168.65.130</pre><p>The target responded successfully, confirming that the scanner could reach it.</p><h3>Step 3: Configuring the Nessus Scan</h3><p>After completing the network configuration, I returned to the Nessus web interface and selected:</p><p><strong>New Scan → Basic Network Scan</strong></p><p>I configured the following scan parameters:</p><pre>Name:<br>Metasploitable2-Vulnerability-Assessment</pre><pre>Description:<br>Vulnerability assessment of Metasploitable 2<br>in an isolated VMware lab.</pre><pre>Target:<br>192.168.65.130</pre><p>I used the default Basic Network Scan configuration without providing host credentials.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EEmRx7G6Zm36hqQQm7PeRQ.png" /><figcaption><strong>Figure 2 — Configuring a Basic Network Scan against Metasploitable 2</strong></figcaption></figure><p>After saving the configuration, I launched the scan.</p><h3>7. Analyzing the Scan Results</h3><p>The vulnerability assessment took approximately <strong>31 minutes</strong> to complete.</p><p>Nessus displayed 65 entries in the Vulnerabilities section for the single target system.</p><p>These entries included security findings, grouped issues, and informational results. Therefore, the number should not be interpreted as 65 independently confirmed exploitable vulnerabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OWxttC8nMYY94QqmEH4qUA.png" /><figcaption><strong>Figure 3 — Completed Nessus scan showing 65 vulnerability-list entries</strong></figcaption></figure><p>The scan identified several serious security weaknesses, including:</p><p>FindingReported severityUnsupported Ubuntu Linux 8.04CriticalVNC Server Weak PasswordCriticalApache Tomcat GhostcatCriticalSSLv2/SSLv3 Protocol DetectionCriticalBind Shell BackdoorCriticalSamba Badlock VulnerabilityHighWorld-Readable NFS SharesHigh</p><p>Instead of discussing every result, I selected three findings that demonstrated different types of security weaknesses.</p><p>These were Ghostcat, a weak VNC password, and an unauthenticated bind shell.</p><h3>Finding 1: Apache Tomcat Ghostcat (CVE-2020–1938)</h3><p>The first vulnerability I investigated was <strong>Apache Tomcat AJP Connector Request Injection</strong>, commonly known as Ghostcat.</p><p>Nessus identified this issue using Plugin ID 134862.</p><p>AttributeResultPlugin ID134862CVECVE-2020–1938CVSS v3.09.8SeverityCriticalVPR7.9EPSS0.9927</p><p>Ghostcat affects the Apache JServ Protocol (AJP), which is used for communication between web servers and Apache Tomcat.</p><p>When the AJP connector is improperly exposed, an attacker may be able to retrieve protected application files.</p><p>Under additional conditions, the vulnerability can also contribute to remote code execution.</p><p>What made this finding particularly interesting was the evidence provided by Nessus.</p><p>The Plugin Output showed that Nessus sent a crafted AJP request referencing:</p><pre>/WEB-INF/web.xml</pre><p>The server returned XML content associated with the protected application configuration file.</p><p>The response began with an XML declaration and Apache Software Foundation license information.</p><p>This demonstrated that the scanner could retrieve content from a file that should not normally be accessible through an unauthenticated remote request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*92XNFapQEq8h_HNZONcI8w.png" /><figcaption>Figure 4 — Plugin output from Nessus Plugin 134862 showing evidence of unauthorized file disclosure through the Apache Tomcat Ghostcat vulnerability.</figcaption></figure><p>The result provided evidence of unauthorized file disclosure.</p><p>Although Ghostcat can lead to more serious consequences under certain circumstances, this particular output did not demonstrate remote code execution.</p><p><strong>Remediation:</strong> Restrict or disable unnecessary AJP access, require appropriate connector protections, and upgrade Apache Tomcat to a supported, patched version.</p><h3>Finding 2: VNC Server Weak Password</h3><p>The second finding involved the VNC service running on TCP port 5900.</p><p>VNC (Virtual Network Computing) allows users to access and interact with a remote graphical desktop.</p><p>While useful for administration, weak authentication can expose remote desktop sessions to unauthorized access.</p><p>Nessus detected the weakness using Plugin ID 61708.</p><p>AttributeResultPlugin ID61708Port5900/TCPCVSS v210.0SeverityCriticalAuthenticationWeak password</p><p>The most important evidence appeared in the Plugin Output:</p><pre>Nessus logged in using a password of &quot;password&quot;.</pre><p>This confirmed that the scanner successfully authenticated to the VNC service using a weak password.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*51UG0z4T1Hq0O6n5eLSDeA.png" /><figcaption><strong>Figure 5 — Nessus Plugin 61708 confirming successful VNC authentication with a weak password</strong></figcaption></figure><p>Unlike a potential issue detected only from service version information, this result was supported by an actual authentication check.</p><p>An unauthorized user who successfully accesses a VNC session could potentially view sensitive information or interact with the remote desktop, depending on session permissions.</p><p><strong>Remediation:</strong> Use strong, unique passwords, restrict VNC access to trusted networks, and protect remote access through appropriate mechanisms such as VPNs or SSH tunnels.</p><p>This finding demonstrated that security risks are not always caused by complex software vulnerabilities. Sometimes, a simple configuration mistake creates a serious exposure.</p><h3>Finding 3: Bind Shell Backdoor Detection</h3><p>The third finding was particularly serious.</p><p>Nessus detected an unauthenticated bind shell listening on TCP port 1524.</p><p>A bind shell is a service that listens for incoming connections and provides command-line access to a system.</p><p>If such a service is accessible without authentication, a remote user may be able to execute operating system commands.</p><p>Nessus identified the issue using Plugin ID 51988.</p><p>AttributeResultPlugin ID51988Port1524/TCPCVSS v3.09.8SeverityCriticalAuthenticationNot requiredObserved privilegesroot</p><p>The Plugin Output stated that Nessus successfully executed the id command.</p><p>The server returned:</p><pre>uid=0(root) gid=0(root) groups=0(root)</pre><p>This output confirmed that the command executed with root privileges.</p><p>In Linux, the root account has the highest administrative privileges. Therefore, the ability to execute commands as root without authentication represents a critical security exposure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2D3dU5khIo3zQLzgdzsv3A.png" /><figcaption><strong>Figure 6 — Nessus Plugin 51988 confirming root-level command execution through TCP port 1524</strong></figcaption></figure><p>This was the strongest example of active vulnerability validation in my assessment.</p><p>The scanner did not merely identify a suspicious service. It demonstrated that an operating system command could be executed through the exposed shell.</p><p><strong>Remediation:</strong> In a production environment, such a finding should trigger immediate investigation and containment. Administrators should determine whether the system has been compromised and consider rebuilding it from a trusted source.</p><p>Because Metasploitable 2 is intentionally vulnerable, this service was expected in the laboratory environment.</p><h3>8. Comparing the Three Critical Findings</h3><p>The three findings demonstrated different security problems.</p><p>FindingWeaknessObserved evidenceGhostcatImproper AJP accessProtected XML file content retrievedVNC Weak PasswordWeak authenticationSuccessful login using passwordBind ShellUnauthenticated shell accessid executed with root privileges</p><p>What I found most useful was the difference between identifying a vulnerability and understanding its actual impact.</p><p>Ghostcat demonstrated file disclosure.</p><p>The VNC finding demonstrated successful authentication with a weak password.</p><p>The bind shell finding demonstrated remote command execution with root privileges.</p><p>These results show why security analysts should examine <strong>Plugin Output</strong>, rather than relying only on vulnerability names and severity scores.</p><h3>9. Limitations of the Assessment</h3><p>Although the scan identified several critical security weaknesses, there are some important limitations.</p><p>First, I performed an unauthenticated network scan. As a result, Nessus did not have the same internal visibility that credentialed scanning could provide.</p><p>Second, Metasploitable 2 is deliberately vulnerable and does not represent a normally maintained production system.</p><p>Third, automated vulnerability findings must be interpreted carefully. Some checks demonstrate vulnerable behavior directly, while others rely on version information or indirect evidence.</p><p>Finally, the free Nessus Essentials edition did not provide the HTML or PDF reporting functionality I initially expected.</p><p>For this reason, I used screenshots and individual plugin outputs to document the assessment.</p><p>These limitations are worth considering when using automated vulnerability scanners in real security operations.</p><h3>10. Conclusion</h3><p>In this lab, I installed Nessus Essentials on Kali Linux, configured an isolated VMware environment, and performed a vulnerability assessment against Metasploitable 2.</p><p>The scan completed in approximately 31 minutes and displayed 65 vulnerability-list entries, including critical security findings and informational results.</p><p>I investigated three significant weaknesses: Apache Tomcat Ghostcat, weak VNC authentication, and an unauthenticated bind shell.</p><p>The most important lesson from this experiment was that <strong>finding a vulnerability is only the first step</strong>.</p><p>Understanding the technical evidence, evaluating its impact, and identifying an appropriate remediation strategy are essential parts of vulnerability management.</p><p>Nessus proved useful for automated discovery, vulnerability identification, and technical validation. However, its findings still require careful analysis, and automated scanning should not be considered a replacement for comprehensive penetration testing.</p><p>Overall, this exercise helped me better understand how vulnerability assessment tools operate and how security findings can be translated into meaningful risk information.</p><h3>References</h3><ol><li><a href="https://docs.tenable.com/nessus/">Tenable — Nessus Documentation</a></li><li><a href="https://docs.tenable.com/nessus/Content/ScanAndPolicyTemplates.htm">Tenable — Basic Network Scan Templates</a></li><li><a href="https://docs.tenable.com/nessus/Content/Plugins.htm">Tenable — Nessus Plugins</a></li><li><a href="https://docs.rapid7.com/metasploit/metasploitable-2/">Rapid7 — Metasploitable 2 Documentation</a></li><li><a href="https://tomcat.apache.org/security-9">Apache Tomcat — Security Advisories</a></li><li><a href="https://nvd.nist.gov/">NIST — National Vulnerability Database</a></li><li><a href="https://www.first.org/cvss/">FIRST — Common Vulnerability Scoring System</a></li><li><a href="https://www.first.org/epss/">FIRST — Exploit Prediction Scoring System</a></li></ol><p><em>This assessment was performed exclusively in an isolated, authorized laboratory environment using a deliberately vulnerable virtual machine. All findings and examples are presented for educational purposes.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bf4da369308" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to Data and Database]]></title>
            <link>https://medium.com/@yunusemreerten08/introduction-to-data-and-database-a2825eb2b7eb?source=rss-7493fd34a983------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2825eb2b7eb</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[datatypes-in-sql]]></category>
            <category><![CDATA[structured-data]]></category>
            <category><![CDATA[postgresql]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[Yunusemreerten]]></dc:creator>
            <pubDate>Thu, 27 Feb 2025 19:29:21 GMT</pubDate>
            <atom:updated>2025-02-27T19:29:21.187Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is a Database?</h3><h4>Imagine It Like a Cabinet</h4><p>A database works just like a <em>cabinet.</em> Each drawer contains different files, and inside those files, data is organized in an accessible way. This data needs to be easy to reach and well-organized for users to access.</p><blockquote>Take, for example, the data centers of tech giants like Amazon, Google, or Microsoft. Here, user data is stored securely, regularly backed up, and maintained. A database essentially serves this function: it keeps data in a secure environment while allowing quick and easy access to it.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*mVLDuMSFAcDeSmUAChiy9w.png" /></figure><h4>Everything is Data</h4><p>Data is the digital footprint of everything around us. Every action we take on our phones, every second of a video recording, the details of a car, and even our banking transactions are all forms of data. Data starts as raw information, but when processed and organized, it becomes valuable knowledge.</p><p>This digital world is vast — every action we take leaves behind a trace of data. For example, the apps we use, the websites we visit, and the videos we watch are all pieces of data that make up the bigger picture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/945/1*af60nkosur20d7WhJnJACg.png" /></figure><h3>Structured Data vs Unstructured Data</h3><p>Data can generally be divided into two main categories: <strong>Structured Data</strong> and <strong>Unstructured Data</strong>.</p><p>◾ <strong>Structured Data</strong> is highly organized and typically found in rows and columns, like in an Excel spreadsheet. It can easily be stored and processed in relational databases.</p><p>◾ <strong>Unstructured Data</strong>, on the other hand, is more free-form and disorganized. This includes things like videos, images, or audio files. These types of data usually require special structures for storage and processing, as they don’t fit neatly into rows and columns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UdLOcj8d7fqpA1YAAfKbUQ.jpeg" /></figure><h3>Database Schema: It’s Like a Roadmap</h3><p>A <strong><em>database schema</em></strong> defines how everything in the database is organized. It outlines how data is related to each<em> </em>other, how tables are linked, and how information flows within the system. It’s essentially a roadmap for the entire database, helping you navigate through the data.</p><p>Think of a cabinet again — each drawer, each table, and each relationship is defined within the schema. A database schema is the plan that outlines how everything in the system fits together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*sa0ysesbBLUFSLWqsYJPXw.png" /></figure><h3>Relational Database Management Systems (RDBMS)</h3><p><strong>Relational Database Management Systems (RDBMS)</strong> store data in <strong>tables</strong>. Each row represents a <strong>record</strong>, and each column represents an <strong>attribute</strong> of that record.</p><p><em>For example</em>, in a customer table, each row would contain information about a single customer, while the columns would store details like name, phone number, and email.</p><p><strong>RDBMS</strong> define relationships between different sets of data. For instance, the relationship between customers and the orders they’ve placed. These relationships are often queried using SQL (Structured Query Language), a powerful language that allows us to interact with and manipulate data in the database.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/1*w6L0gkMD01LX6-92R5p9mA.png" /></figure><h3>Database Software: Querying with SQL</h3><p>Database software allows us to manage databases and retrieve specific data. With SQL queries, we can pull the information we need quickly and efficiently. Whether it’s retrieving customer details, updating records, or deleting unnecessary data, SQL is the tool that makes all of this possible.</p><p>SQL is especially useful when working with relational databases. You can search for specific data, modify records, or get information about transactions using simple SQL commands.</p><h3>Relational vs Non-Relational Databases</h3><p>Databases can be categorized into two main types: <strong>Relational Databases (RDBMS)</strong> and <strong>Non-Relational Databases (NoSQL)</strong>.</p><p>◾ <strong>Relational Databases</strong> store data in tables and define relationships between them. Examples include MySQL, PostgreSQL, and Oracle, which all use SQL to query and manipulate data.</p><p>◾ <strong>Non-Relational Databases</strong>, on the other hand, store data in different formats like documents, key-value pairs, or graphs. NoSQL databases like MongoDB, Redis, and Cassandra are examples of this type of database.</p><p>Each type of database has its use case. Relational databases are ideal for situations where data is tightly structured and relationships between different entities are well-defined. NoSQL, however, offers more flexibility and scalability, making it suitable for handling large amounts of data in real-time applications.</p><h3>Common Data Types in Databases</h3><p>Data types define the format in which data is stored. Here are some of the most common data types used in databases:</p><p>◾ <strong>Textual Data Types:</strong> CHAR, VARCHAR, TEXT are used to store text. CHAR is for fixed-length data, while VARCHAR is for variable-length text. TEXT is used for larger blocks of text.</p><p>◾ <strong>Numeric Data Types:</strong> INTEGER, SMALLINT, BIGINT, FLOAT, DECIMAL, and DOUBLE PRECISION are used for storing numerical data.</p><p>◾ <strong>Boolean Data Types:</strong> The BOOLEAN data type stores TRUE or FALSE values. For example, in a parking system, the status of a parking spot (occupied or vacant) could be stored as BOOLEAN.</p><p>◾ <strong>Date and Time Data Types:</strong> DATE, TIME, DATETIME, TIMESTAMP, and INTERVAL are used to store date and time information in a variety of formats.</p><h3>PostgreSQL: A Powerful and Flexible Database</h3><p>PostgreSQL is an open-source relational database that offers powerful features for managing and querying data. In PostgreSQL, databases are organized into schemas and tables, with clear distinctions between each. It helps in structuring your data efficiently and is widely used across a range of applications, from content management systems to e-commerce platforms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*ElfQbEj_dO3qTTOaKK0zSw.png" /></figure><blockquote>This article aimed to introduce databases in a way that’s both technical and approachable. Databases are fundamental tools for managing, accessing, and organizing the data that powers the digital world. I hope this post helps you better understand how databases work and their role in the modern tech landscape!</blockquote><p><strong>If you liked it, don’t forget to like it; if you didn’t, don’t forget to dislike it.:)</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2825eb2b7eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>