<?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 Hassen Hannachi  on Medium]]></title>
        <description><![CDATA[Stories by Hassen Hannachi  on Medium]]></description>
        <link>https://medium.com/@hassen-hannachi?source=rss-bd4a1e5ed7c8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Hassen Hannachi  on Medium</title>
            <link>https://medium.com/@hassen-hannachi?source=rss-bd4a1e5ed7c8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:54:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hassen-hannachi/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[Day 6-Network+ N10–009 Network Topologies, Architectures & Types]]></title>
            <link>https://hassen-hannachi.medium.com/day-6-network-n10-009-network-topologies-architectures-types-d90952a965a6?source=rss-bd4a1e5ed7c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/d90952a965a6</guid>
            <category><![CDATA[network-topology]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[computer-networking]]></category>
            <category><![CDATA[comptia-certifications]]></category>
            <category><![CDATA[network-architecture]]></category>
            <dc:creator><![CDATA[Hassen Hannachi ]]></dc:creator>
            <pubDate>Wed, 20 May 2026 21:06:50 GMT</pubDate>
            <atom:updated>2026-05-20T21:06:50.233Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IWlKOE6-kWCU4vJ_WQth3w.png" /></figure><p>Chapter 6 of the Network+ N10–009 exam asks you to compare and contrast network <strong><em>topologies</em></strong>, <strong><em>architectures</em></strong>, and <strong><em>types</em></strong>. This means knowing not just what each one is, but when to use it, what its weaknesses are, and how to recognize it on the exam. This post covers all nine exam objectives in full.</p><h4><strong>1. Mesh Topology</strong></h4><p>In a mesh topology, every device connects to every other device — either fully or partially. There are two variants you must know:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/466/1*Ss1lAp1WPGtTTJDu7oQ1Hg.png" /><figcaption>Full mesh vs Partial mesh</figcaption></figure><p><strong><em>Full mesh</em></strong><br>• Every node connects to every other<br>• Maximum redundancy<br>• Expensive at scale<br>• Requires <strong><em>n(n−1)/2</em> </strong>links</p><p><strong><em>Partial mesh</em></strong><br>• Only critical nodes are fully interconnected<br>• Cost-effective compromise<br>• Common in <strong><em>WANs </em></strong>and <strong><em>ISP </em></strong>backbones</p><blockquote><strong>Exam tip</strong>: Mesh is used where <strong>fault tolerance</strong> is paramount — think WAN links, military networks, and the internet itself. A single link failure does not bring down the network.</blockquote><h4><strong>2. Star / Hub-and-Spoke Topology</strong></h4><p>The most common modern LAN topology. Every end device connects to a central switch or hub. All traffic passes through that central device.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*ORpunTJRh8Zg4E5Ufn-_vQ.png" /><figcaption>Star / Hub-and-Spoke</figcaption></figure><p><strong><em>Advantages</em></strong><br>• Easy to troubleshoot<br>• Single node failure doesn’t affect others<br>• Simple to add/remove devices</p><p><strong><em>Disadvantages</em></strong><br>• Central switch = single point of failure<br>• Performance limited by the central device</p><h4><strong>3. Token Ring Topology</strong></h4><p>A legacy topology (<strong><em>IEEE 802.5</em></strong>) where devices form a logical ring and pass a special frame called a token. Only the device holding the token may transmit — this eliminates collisions without needing <strong><em>CSMA/CD</em></strong>.<br>Devices are wired to a central Multistation Access Unit (<strong><em>MAU</em></strong>), making the physical layout look like a star, while the logical data flow is a ring.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/824/1*AqoHj5MCOUcEDkUliQDWJA.png" /><figcaption>Token Ring</figcaption></figure><blockquote><strong>Why it still appears on the exam</strong>: Network+ tests your understanding of how collision domains were historically managed. Token ring is essentially retired, but knowing how token passing avoids collisions is conceptually important.</blockquote><h4><strong>4. Hybrid Topology</strong></h4><p>A hybrid topology combines two or more different topology types into a single network. Real-world enterprise networks are almost always hybrid.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/557/1*Zg0PcPwxpdVgndAo0H2Qhg.png" /></figure><p>Common examples:<br>• <strong><em>Star-bus</em></strong>: Multiple star LANs connected via a backbone bus<br>• <strong><em>Star-mesh</em></strong>: Star LANs at branch offices, full-mesh WAN links between sites<br>•<strong><em> Star-ring</em></strong>: Star physical layout with token ring logical flow</p><blockquote><strong>Exam angle</strong>: If a question describes multiple topology characteristics in a single network, it’s describing a hybrid. Recognize the components — don’t get confused into thinking it’s a new topology.</blockquote><h4><strong>5. Spine-and-Leaf Architecture</strong></h4><p>A modern data center architecture designed for predictable, low-latency east-west traffic (server-to-server). It replaces the older three-tier model in hyperscale environments.<br>• <strong>Leaf switches</strong>: Connect directly to servers, storage, and firewalls<br>• <strong>Spine switches</strong>: Interconnect all leaf switches — no leaf-to-leaf direct link<br>• Every leaf connects to every spine (partial mesh between layers)<br>• Traffic between two servers crosses exactly two hops: leaf → spine → leaf</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/841/1*j1N584ZlwwB_eP2PXk4nxQ.png" /><figcaption>Spine-and-Leaf Architecture</figcaption></figure><p><strong><em>Strengths</em></strong><br>• Consistent, predictable latency<br>• Easy horizontal scaling<br>• No spanning tree needed</p><p><strong><em>Considerations</em></strong><br>• More cabling than three-tier<br>• All spine switches must be high-capacity</p><h4><strong>6. Point-to-Point Topology</strong></h4><p>The simplest possible topology: two nodes connected directly with a dedicated link. Think of a leased line between two offices, a <strong><em>serial WAN link</em></strong>, or a <strong><em>direct fiber</em></strong> run.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*5-o--TJcBSW3V_aYCoqEtg.png" /></figure><p><strong><em>Key characteristics</em></strong>:<br>• No shared medium — full bandwidth dedicated to the link<br>• No collision domain concerns<br>• Common for WAN uplinks, ISP handoffs, and backbone connections</p><blockquote><strong>Don’t confuse:</strong> Point-to-point with point-to-multipoint (like a hub broadcasting to many endpoints). P2P = exactly two endpoints, one dedicated path.</blockquote><h4>7. Three-Tier Hierarchical Model</h4><p>The classic Cisco enterprise campus architecture. Three distinct layers, each with a defined role:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/853/1*lmjkIKPqV17uLVCvmIghPg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/905/1*XACfRqCGN9JNkoPYsbZ0jg.png" /></figure><blockquote><strong>Mnemonic</strong>: Core, Distribution, Access → C-D-A → “Can’t Do Anything” — each layer has a specific job; policy lives in the middle.</blockquote><h4><strong>8. Collapsed Core</strong></h4><p>When a network is small enough that a separate core layer isn’t justified, the core and distribution layers are merged into a single layer. This is called collapsed core (or two-tier) architecture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/858/1*D_51DPxX_OQgNNw7vLfxrQ.png" /></figure><p><strong>When to use it</strong><br>• Small/medium enterprise<br>• Single-building campus<br>• Budget constraints</p><p><strong>Trade-offs</strong><br>• Less scalable<br>• Core devices must handle policy too<br>• Harder to upgrade without downtime</p><blockquote>Exam tip: A question describing a two-layer campus design (access + core/distribution combined) is describing a collapsed core. It’s a cost-justified simplification, not a flaw.</blockquote><p><strong>9. Traffic Flows</strong><br>Understanding where traffic goes is as important as understanding physical topology. Network+ N10–009 expects you to know these primary traffic patterns:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*CmARs8H-jBVlwyp-IbupIw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*6FNIlWbrxoVs4G229dt07A.png" /></figure><p><strong>North-south traffic</strong>: This refers to data flow that moves <strong><em>in and out</em></strong> of a data center or network, typically between <strong><em>users or external networks</em></strong> (such as the internet) and <strong><em>internal servers</em></strong>. with north-south traffic, security should be carefully considered, and control such as firewalls are often used even though they can slow down data.</p><p><strong>East-west traffic</strong>: This type of traffic refers to data flow that occurs <strong><em>within a data center or network</em></strong>, specifically between serves or devices inside the same environment. Managing east-west traffic efficiently is crucial for <strong><em>optimizing performance</em></strong> within a data center.</p><blockquote><strong>Why traffic flows matter for topology choice</strong>: A spine-and-leaf architecture exists because <strong>east-west</strong> traffic exploded with virtualization and microservices. Three-tier models optimized for <strong>north-south</strong>. Matching your architecture to your traffic flow is a design principle you will see tested.</blockquote><h4><strong>Chapter 6 — Exam Cheat Sheet</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/905/1*gLIbaD48-itNSUltx9htTA.png" /></figure><p>Topology questions on the Network+ exam often give you a scenario and ask you to identify the best fit. If you internalize why each topology exists, not just what it looks like, you’ll answer those scenario questions confidently. <strong>Good luck on your Network+ N10–009 exam! </strong><em>You’ve got this.</em></p><p><em>Part of the Network+ N10–009 Series, </em><strong>Next up</strong>: <strong>Approaite IPv4 Netwok Addrssing</strong>. Stay tuned! 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d90952a965a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Analyzing Tunnel Log Traffic Using Splunk SIEM]]></title>
            <link>https://hassen-hannachi.medium.com/analyzing-tunnel-log-traffic-using-splunk-siem-643ea9c9337c?source=rss-bd4a1e5ed7c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/643ea9c9337c</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[splunk]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <dc:creator><![CDATA[Hassen Hannachi ]]></dc:creator>
            <pubDate>Tue, 05 May 2026 20:17:44 GMT</pubDate>
            <atom:updated>2026-05-05T20:17:44.687Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cf0al0r_Wjc1ciZ3-5JILw.png" /></figure><p>Modern networks rely heavily on encrypted tunnels — <strong><em>VPNs</em></strong>, <strong><em>GRE</em></strong>, <strong><em>IPSec</em></strong> — to securely move data across untrusted environments. While these tunnels <strong><em>protect confidentiality</em></strong>, they can also obscure visibility, making them a prime channel for misuse or even <strong><em>data exfiltration</em></strong>. This is where Splunk SIEM becomes a powerful ally.</p><p>In this post, we’ll walk through how to analyze tunnel log traffic using Splunk, <strong><em>uncover suspicious behavior</em></strong>, and build actionable insights for security monitoring.</p><h4>Why Tunnel Traffic Matters</h4><p>Tunnel traffic often bypasses traditional inspection layers because it is encrypted or encapsulated. Attackers exploit this by:</p><ul><li>Exfiltrating sensitive data through VPN tunnels</li><li>Establishing covert command-and-control (C2) channels</li><li>Moving laterally across networks undetected</li></ul><p>Without proper monitoring, these activities can remain invisible.</p><blockquote><em>📦 The dataset used in this analysis comes from a publicly available cyber defense exercise. This dataset simulates enterprise network traffic under active attack conditions, making it ideal for threat hunting practice.</em></blockquote><h4>Prerequisites</h4><p>Before starting the project, ensure the following:</p><ul><li>Splunk instance is installed and configured.</li><li>Tunnel log data sources from Zeek IDS are configured to forward logs to Splunk.</li></ul><h4>Steps to Upload Sample Tunnel Log Traffic from Zeek IDS to Splunk SIEM</h4><h4>1. Prepare Sample Tunnel Log Files</h4><ul><li>Obtain sample <a href="https://www.secrepo.com/maccdc2012/tunnel.log.gz">tunnel log files</a> from Zeek IDS in a suitable format (e.g., text files).</li><li>Ensure the log files contain relevant tunneling events, including timestamps, source and destination IP addresses, tunneling protocols, etc.</li><li>Save the sample log files in a directory accessible by the Splunk instance.</li></ul><h4>2. Upload Log Files to Splunk</h4><ul><li>Log in to the Splunk web interface.</li><li>Navigate to <strong>Settings</strong> &gt; <strong>Add Data</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/389/0*C-LJ-i2ammjUQySv.png" /></figure><ul><li>Select <strong>Upload</strong> as the data input method.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/0*Mch0XhQbmhWVHRHj.png" /></figure><h4>3. Choose File</h4><ul><li>Click on <strong>Select File</strong> and choose the sample tunnel log file you prepared earlier. Click <strong>Next</strong> on the Top Right Corner</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*n2e99WBrjbSGTck0Nu6H7A.png" /></figure><h4>4. Set Source Type</h4><ul><li>In the <strong>Set Source Type</strong> section, Click on “<strong>Save As</strong>” and specify the source type for the uploaded log file.</li><li>Choose the appropriate source type for Zeek IDS tunnel logs (e.g., bro or a custom source type if applicable).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/569/1*6WX7T6Ap-c9-XxcpszXxtA.png" /></figure><ul><li>Click <strong>Save </strong>when all the settings are completed.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/557/1*qnrg41SuihJga5db5dQcvA.png" /></figure><h4>5. Input Settings</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*HiBv3c_VCURRW6-8.png" /></figure><ul><li>Once all settings are configured, click on the <strong>Review</strong> button.</li><li>Review the settings one final time to ensure accuracy.</li><li>Click <strong>Submit</strong> to upload the sample <strong><em>tunnel log file</em></strong> to Splunk.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/855/1*1FpxVIm0tlvYfRVwuqsAAw.png" /></figure><h4>6. Start Searching</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*eATKZNaGalH5ebch.png" /></figure><ul><li>After uploading, navigate to the search bar in the Splunk interface (or click on “<strong><em>Start Searching</em></strong>”).</li><li>Run a <strong><em>search query</em></strong> to verify that the uploaded tunnel events from Zeek IDS are visible.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/559/1*QS9k0-KO0xFNIf0eJ30p1g.png" /></figure><h4>7. Parsing Data</h4><ul><li>After uploading, navigate to the<strong> Extract New Fields</strong> in the Splunk interface.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/280/1*t0Qlxy_Cn89_uxm2o1-Cmg.png" /></figure><ul><li>Select any event and click Next.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rGxYcAkDaHOO0B6rHS21RA.png" /></figure><ul><li>Select <strong><em>Regular Expression</em></strong> (you can use Delimiters too), and click Next.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R_QKBCZh1LbG78bLe-uSHg.png" /></figure><ul><li>Select field <strong><em>192.168.202.102</em></strong> (Client machine address), and click<strong><em> Add Extraction.</em></strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/349/1*Htoypygia3hclKoOvVIN9g.png" /></figure><ul><li>Select field <strong><em>192.168.23.103</em></strong> (Destination machine address), click <strong><em>Add Extraction.</em></strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*6W4W03iKjZWFF0TtTrLfXA.png" /></figure><ul><li>Select filed 33771, give a name of <strong>src_port</strong> and click <strong>Add Extraction</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/316/1*8_phRMuzxkDwoKKBRRWs-g.png" /></figure><ul><li>Select filed 3544<strong>, </strong>give a name of <strong>dest_por</strong>t and click <strong>Add Extraction</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/394/1*vHOzpcEaUl9nnc6xmIq-2w.png" /></figure><ul><li>Select field Tunnel::TEREDO, give a name of <strong>protocol </strong>and Click <strong>Add Extraction</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/381/1*XICBoeoqfukdRIv_ZcZfQw.png" /></figure><ul><li>Select field Tunnel::DISCOVER, give a name of <strong>event </strong>and Click <strong>Add Extraction</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/329/1*LEe2NiVwJwjgIFVo2VqMqw.png" /></figure><blockquote><strong>Important</strong>: It is better to use “<strong>action”</strong> as name for this field. In my case I had to edit the <strong>regex extraction</strong> with the new name.</blockquote><ul><li>After the Select fields are <strong><em>validate </em></strong>and <strong><em>saved</em></strong>, last step is to check the new extract fields and Click<strong><em> Finish</em></strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/921/1*4CztbptM9zonyVgT-Ihf2g.png" /></figure><ul><li>Click on <strong>Explore the fields I Just create in Search</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/1*tp_0eglFl7elAxZsAygPeA.png" /></figure><ul><li>We have first to add those new fields Interesting Fields view. Click on <strong><em>All fields</em></strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/509/1*t5QqNS7TQFGNERz5Y9GKUA.png" /></figure><ul><li><strong><em>Check </em></strong>the<strong><em> box </em></strong>of<strong><em> all the new fields </em></strong>to be added to the Interesting Fields</li><li>Interesting Fields now contains the fields we extract <strong>dest_ip, dest_port, action, protocol, src_ip, src_port</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/281/1*YALRhgYfzZ_Xz0PJg8YcRA.png" /></figure><h4>Search for Tunnel Events</h4><ul><li>Open Splunk interface and navigate to the search bar.</li><li>Enter the following search query to retrieve tunnel events from Zeek IDS:</li></ul><h4>Key Use Cases for Analyze Tunnel Log Traffic</h4><p><strong>1. Total Tunnel Activity</strong></p><pre>sourcetype=tunnellogs<br>| stats count as total_events</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/506/1*VECyTmCXslqf3OrLa24UjQ.png" /></figure><p><strong>2. Tunnel Actions Breakdown</strong></p><pre>sourcetype=tunnellogs<br>| stats count as action</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/463/1*76KDnleiF8Hh817ihNBhvA.png" /></figure><p><strong>3. Top Source Hosts</strong></p><pre>sourcetype=tunnellogs<br>| stats count by src_ip<br>| sort - count<br>| head 10</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/490/1*dlQ_zEqhvfmpSZqi9lELiw.png" /></figure><p><strong>4. Top Destination Targets</strong></p><pre>sourcetype=tunnellogs<br>| stats count by dest_ip<br>| sort - count<br>| head 10</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/477/1*1NQ_Mo6Na8ImSOJZuZ1uGQ.png" /></figure><p>5. Unique Destinations per Source (Recon Detection)</p><pre>sourcetype=tunnellogs action=Tunnel::DISCOVER<br>| stats dc(dest_ip) as unique_targets by src_ip<br>| sort - unique_targets</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/497/1*Mzf11UFAAWJlDcCNASYzSA.png" /></figure><p>6. Tunnel Activity Over Time</p><pre>sourcetype=tunnellogs action=Tunnel::DISCOVER<br>| timechart span=5m count by action</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/501/1*d3iicAJx8C7-sxKB5FKSzw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/419/1*BLeaD6JrmsTSBjhFJRr53A.png" /></figure><p><strong>7. Session Duration Approximation</strong></p><pre>sourcetype=tunnellogs<br>| transaction src_ip dest_ip maxspan=5m<br>| eval duration=duration<br>| table src_ip dest_ip duration<br>| sort - duration</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/790/1*3DwzR_H-kKNzJAJtIZIWcg.png" /></figure><p><strong>8. High-Frequency Connections (Anomaly)</strong></p><pre>sourcetype=tunnellogs<br>| stats count by src_ip dest_ip<br>| where count &gt;= 4<br>| sort - count</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*Ze-fxNCygPb37OSsYJNLJw.png" /></figure><h4>Building Dashboards for Visibility (Coming Soon)</h4><p>Splunk dashboards can provide real-time insights into tunnel activity:</p><ul><li>Top talkers (by bandwidth usage)</li><li>Tunnel session counts over time</li><li>Geographic distribution of tunnel endpoints</li><li>Alerts for abnormal behavior</li></ul><p>Visualization helps analysts quickly identify anomalies without digging through raw logs.</p><h4>Correlation with Other Data Sources</h4><p>Tunnel logs alone are powerful — but combining them with other datasets makes them even more effective:</p><ul><li>Endpoint logs → detect compromised hosts initiating tunnels</li><li>DNS logs → correlate suspicious domains with tunnel traffic</li><li>Authentication logs → identify unusual login patterns</li></ul><p>Using Splunk ES correlation searches, you can tie these signals together into high-confidence alerts.</p><h4>Best Practices</h4><ul><li><strong>Enable detailed logging</strong> on all tunnel endpoints</li><li><strong>Baseline normal behavior</strong> before defining alerts</li><li><strong>Use threat intelligence feeds</strong> to enrich IP data</li><li><strong>Automate alerts</strong> for anomalies in traffic volume or destinations</li><li><strong>Regularly review dashboards</strong> for emerging patterns</li></ul><h3>Final Thoughts</h3><p>Encrypted tunnels are essential for secure communication — but they can also become blind spots if not monitored properly. With Splunk SIEM, you can turn these blind spots into visibility points, detecting threats that would otherwise go unnoticed.</p><p>By ingesting, analyzing, and correlating tunnel logs, security teams can proactively defend against data exfiltration, unauthorized access, and advanced persistent threats.</p><p>Feel free to customize these steps according to your specific use case and requirements.</p><p><strong>Happy analyzing!</strong> 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=643ea9c9337c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Analyzing SMTP Logs Using Splunk]]></title>
            <link>https://hassen-hannachi.medium.com/analyzing-smtp-logs-using-splunk-eb7d56c5f6fb?source=rss-bd4a1e5ed7c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb7d56c5f6fb</guid>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[splunk]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyber]]></category>
            <dc:creator><![CDATA[Hassen Hannachi ]]></dc:creator>
            <pubDate>Sat, 25 Apr 2026 03:27:25 GMT</pubDate>
            <atom:updated>2026-04-25T03:27:25.226Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G1NL8OD-ZS12TxAMs3blfA.png" /></figure><h3>Introduction</h3><p>Email remains one of the most exploited attack vectors in modern cybersecurity. From phishing campaigns to data exfiltration, attackers frequently abuse email infrastructure to achieve their goals.</p><p>But what if you had access to raw email traffic logs from a simulated enterprise under attack?</p><p>In this post, we’ll explore how to analyze SMTP logs using Splunk, leveraging a real-world dataset from the <strong><em>MACCDC 2012 cyber defense competition</em></strong>. Along the way, we’ll uncover patterns, detect anomalies, and demonstrate how security analysts can extract meaningful insights from seemingly chaotic log data.</p><blockquote>📦 The dataset used in this analysis comes from a publicly available cyber defense exercise. This dataset simulates enterprise network traffic under active attack conditions, making it ideal for threat hunting practice.</blockquote><h4>What’s inside the log?</h4><p>SMTP logs typically contain:</p><ul><li>Sender and recipient email addresses</li><li>Source IP addresses</li><li>Message IDs</li><li>Delivery status codes (e.g., sent, deferred, bounced)</li><li>Timestamps and routing details</li></ul><p>One important detail: <strong>a single email transaction often spans multiple log entries</strong>, which makes correlation essential.</p><h3>Prerequisites</h3><p>Before starting the project, ensure the following:</p><ul><li>Splunk instance is installed and configured.</li><li>FTP log data sources are configured to forward logs to Splunk.</li></ul><h3>Steps to Upload Sample SMTP Log Files to Splunk SIEM</h3><h4>1. Prepare Sample FTP Log Files</h4><ul><li>Obtain sample <a href="https://www.secrepo.com/maccdc2012/smtp.log.gz">SMTP log files</a> in a suitable format (e.g., text files).</li><li>Ensure the log files contain relevant SMTP events, including timestamps, source IP, username, commands, filenames, etc.</li><li>Save the sample log files in a directory accessible by the Splunk instance.</li></ul><h4>2. Upload Log Files to Splunk</h4><ul><li>Log in to the Splunk web interface.</li><li>Navigate to <strong>Settings</strong> &gt; <strong>Add Data</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/389/1*K4Kcj9SUBnWQgeNJpHXLsQ.png" /></figure><ul><li>Select <strong>Upload</strong> as the data input method.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*4yFYzeQHDVri9vTP1MXVng.png" /></figure><h4>3. Choose File</h4><ul><li>Click on <strong>Select File</strong> and choose the sample <strong><em>FTP log</em></strong> file you prepared earlier. Click <strong>Next</strong> on the Top Right Corner</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/890/1*yar4c5T_FG1Al9V9LVhrrQ.png" /></figure><h4>4. Set Source Type</h4><ul><li>In the <strong>Set Source Type</strong> section, Click on “<strong>Save As</strong>” and specify the source type for the uploaded log file.</li><li>Choose the appropriate source type for FTP logs (e.g., smtpor a custom source type if applicable).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/561/1*4649VvADJ0Z0ZP8mKjQYeg.png" /></figure><ul><li>Click <strong>Save </strong>when all the settings are completed.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*gKgHIbmunXMcspZR-IGecQ.png" /></figure><h4>5. Input Settings</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/866/1*k17dkda4NYIhCQkBn2bWaw.png" /></figure><ul><li>Once all settings are configured, click on the <strong>Review</strong> button.</li><li>Review the settings one final time to ensure accuracy.</li><li>Click <strong>Submit</strong> to upload the sample FTP log file to Splunk.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/857/1*nom4FvPDv6cXY5bq_zd6Wg.png" /></figure><h4>6. Start Searching</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/866/1*pt6uI73YekZShIi6PVfBjA.png" /></figure><ul><li>After uploading, navigate to the search bar in the Splunk interface.</li><li>Run a <strong>search query</strong> to verify that the uploaded FTP events are visible.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/545/1*19lnxlnOamoZQwz5Kls0_A.png" /></figure><h4>7. Parsing Data</h4><ul><li>After uploading, navigate to the <strong>Extract New Fields</strong> in the Splunk interface.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/281/1*5SDoaD9I4Xp0Ht7FpUUqGg.png" /></figure><ul><li>Select any event and click <strong>Next </strong>(I select an event that is suspicious).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cre6k-wP7qILKuPriUnU6g.png" /></figure><ul><li>Select <strong>Regular Expression</strong> (you can use Delimiters too), and click <strong>Next</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PObqdlKeAkAxJNHL-UesVQ.png" /></figure><ul><li>Select field <strong><em>192.168.202.138</em></strong> (source IP address), and click<strong><em> Add Extraction.</em></strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/504/1*yrX4WnR5u2HjGgHUYSuLAA.png" /></figure><ul><li>Select field <strong><em>192.168.23.103</em></strong> (Destination IP address -Mail server), click <strong><em>Add Extraction.</em></strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/384/1*xr8n4BcokSKQoK4Tydfe2A.png" /></figure><ul><li>Select filed 36048, give a name of <strong>src_port</strong> and click <strong>Add Extraction</strong></li><li>Select filed 25<strong>, </strong>give a name of <strong>dest_por</strong>t and click <strong>Add Extraction</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/656/1*2OOMmKp-CelE2rADYkIH8A.png" /></figure><ul><li>Select field<strong> &lt;root@[192.168.202.138]&gt;</strong> , give a name of <strong>Mail_from</strong> (Envelop sender) and Click <strong><em>Add Extraction</em></strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/370/1*M744wc1t2lTumUf5AUF59w.png" /></figure><ul><li>Select field <strong>root+:”|sleep 5 #”</strong> , give a name of <strong>RCPT_TO</strong> (Recipient ) and Click <strong><em>Add Extraction</em></strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*8DYmNxablCl12YSyjxahmA.png" /></figure><ul><li>Select field <strong>451</strong>, give a name of <strong>code_respone </strong>and Click <strong><em>Add Extraction</em></strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/364/1*woBQfzgUS_-WCoz5t-GQ_A.png" /></figure><ul><li>Select field <strong>4.3.0 &lt;root+:|sleep 5 #&gt;: Temporary lookup failure</strong> , give a name of <strong>SMTP_respone </strong>and Click <strong><em>Add Extraction</em></strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/763/1*QEWaSalGPv0rRhbVj8-_SQ.png" /></figure><ul><li>Select field <strong>empty </strong>, give a name of <strong>message_body </strong>and Click <strong><em>Add Extraction</em></strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/357/1*ZDvGNEEe6W9DmlexTJsSSw.png" /></figure><ul><li>Select field <strong>F</strong>, give a name of <strong>status (</strong>Final status) and Click <strong><em>Add Extraction</em></strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/352/1*i4DVW_B_Y6w6lUfIUROhfQ.png" /></figure><ul><li>After the Select fields are <strong><em>validate </em></strong>and <strong><em>saved</em></strong>, last step is to check the new extract fields and <strong><em>Click Finish</em></strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*XELU_B6gMKWdrrb27gW8nQ.png" /></figure><ul><li>Click on <strong>Explore the fields I Just create in Search</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/787/1*PoEoxROHIgLHP91QYrQ1gQ.png" /></figure><ul><li>First, we have to add those new fields Interesting Fields view. Click on <strong>9</strong> <strong><em>more fields (</em></strong>it suppose<strong><em> </em></strong>to<strong><em> show 10!!)</em></strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/281/1*GaMFBqYGBd7L6gI8CPocQA.png" /></figure><ul><li><strong><em>Check all the new fields </em></strong>to be added to the Interesting Fields</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*dkNcMp7KP1B-8m1F-l63Cw.png" /></figure><ul><li>Interesting Fields now contains the fields we extract c<strong>ode_response, dest_ip, dest_port, Mail_from, message_body, RCPT_TO, SMTP_response, src_ip, src_port, status</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/281/1*Q2iTz6ErULhMwZtqpvFNlw.png" /></figure><h3>Steps to Analyze SMTP Log Files in Splunk SIEM</h3><h4>1. Search for SMTP Events</h4><ul><li>Open Splunk interface and navigate to the search bar.</li><li>Enter the following search query to retrieve SMTP events</li></ul><pre>index=_* OR index=* sourcetype=smtplogs</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/731/1*v0hbXQyGxnxNurcKExW5Rw.png" /></figure><h4>2. Analyze Email Traffic Patterns</h4><ul><li>Determine the distribution of email senders</li></ul><pre>index=_* OR index=* sourcetype=smtplogs | top limit=10 src_ip</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UwEvPHODQuj5odJy1h9A8A.png" /></figure><ul><li>Identify top recipient addresses</li></ul><pre>index=_* OR index=* sourcetype=smtplogs | top limit=10 dest_ip</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d45Ye4Crq3iuydmjOG34IA.png" /></figure><h4>3. Find top attacking IPs</h4><pre>index=_* OR index=* sourcetype=smtplogs <br>| rex &quot;connect from (?&lt;src_ip&gt;\d+\.\d+\.\d+\.\d+)&quot;<br>| stats count by src_ip<br>| sort -count</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/691/1*nS6pPPTjCsvaXG4Y7mSNBA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/1*Pyr9TqhvotAbsL7mCd3jkg.png" /></figure><h4>Insight:</h4><ul><li>Top IPs = likely attackers</li><li>Very high counts = automation</li></ul><h4>4. Detect user enumeration attacks</h4><pre>index=_* OR index=* sourcetype=smtplogs <br>| rex &quot;connect from (?&lt;src_ip&gt;\d+\.\d+\.\d+\.\d+)&quot;<br>| rex &quot;RCPT TO:\&lt;(?&lt;recipient&gt;[^&gt;]+)\&gt;&quot;<br>| rex &quot;(?&lt;response_code&gt;5\d{2})&quot;<br>| stats count as failures by src_ip<br>| sort -failures</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/707/1*n_kd0sw0lzW0odvbhZZcgg.png" /></figure><h4>What to look for:</h4><ul><li>High failure counts per IP</li><li>Indicates <strong>username harvesting</strong></li></ul><h4>5. Detect suspicious sessions (no DATA phase)</h4><p>Normal email includes DATA. Attackers often skip it.</p><pre>index=_* OR index=* sourcetype=smtplogs <br>| rex &quot;connect from (?&lt;src_ip&gt;\d+\.\d+\.\d+\.\d+)&quot;<br>| stats values(_raw) as events by src_ip<br>| eval has_data=if(match(events,&quot;DATA&quot;),1,0)<br>| where has_data=0</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YdY0vBix5sB8H4gTFnap5A.png" /></figure><h4>Insight:</h4><ul><li>These are probing/enumeration sessions</li></ul><h4>6. Null sender detection (bounce abuse)</h4><pre>index=_* OR index=* sourcetype=smtplogs <br>| rex &quot;connect from (?&lt;src_ip&gt;\d+\.\d+\.\d+\.\d+)&quot;<br>| stats values(_raw) as events by src_ip<br>| eval has_data=if(match(events,&quot;DATA&quot;),1,0)<br>| where has_data=0</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*Bq_Pu0uGeT5PsYDiaILY3A.png" /></figure><h4>Interpretation:</h4><ul><li>Often spam/backscatter activity</li></ul><h4>7. Failure vs success ratio per IP</h4><pre>index=_* OR index=* sourcetype=smtplogs <br>| rex &quot;connect from (?&lt;src_ip&gt;\d+\.\d+\.\d+\.\d+)&quot;<br>| rex &quot;(?&lt;response_code&gt;[245]\d{2})&quot;<br>| eval status=if(response_code LIKE &quot;2%&quot;, &quot;success&quot;, &quot;fail&quot;)<br>| stats count by src_ip, status<br>| xyseries src_ip status count<br>| eval fail_ratio = fail / (fail + success)<br>| sort -fail_ratio</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/529/1*PFwCI5IjpzA2v9CZ4Kd2ow.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HU2cTSzpWKoYBZsNBesWfQ.png" /></figure><h4>Insight:</h4><ul><li>High fail ratio = attacker</li><li>Balanced ratio = legitimate sender</li></ul><h4>8. Reconstruct sessions (advanced)</h4><pre>index=_* OR index=* sourcetype=smtplogs <br>| rex &quot;connect from (?&lt;src_ip&gt;\d+\.\d+\.\d+\.\d+)&quot;<br>| transaction src_ip maxpause=30s</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/622/1*H1JFdE_rG24vpXZO9-u1jA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ri4x53GyyNg2wO0qrzCZ3A.png" /></figure><h4>This lets you:</h4><ul><li>See full SMTP conversations</li><li>Identify patterns like:</li><li>many RCPTs</li><li>no DATA</li><li>early disconnects</li></ul><h4>🧾 Case study: Exploit Attempt</h4><pre>index=_* OR index=* sourcetype=smtplogs code_response=451</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*RoJtlRLANlIe5jprrCUtGA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dhg-bcyBMzNyQytyUtYneg.png" /></figure><h4>🚨 What’s suspicious here</h4><p>The key red flag is this part:</p><p><strong>root+:”|sleep 5 #”</strong></p><p>This is <strong>not a normal email address</strong>. It looks like an attempt at <strong>command injection</strong>.</p><h4>Why?</h4><ul><li>The | (pipe) symbol is often used in Unix mail systems to <strong>pipe email into a shell command</strong></li><li>sleep 5 is a harmless command often used in testing exploits</li><li># is a shell comment character (used to ignore the rest)</li></ul><p>So this recipient is trying to exploit systems that:</p><ul><li>improperly pass email addresses to a shell</li><li>allow delivery to commands (e.g., via .forward files or aliases)</li></ul><p>This type of attack is commonly seen in:</p><ul><li>older or misconfigured MTAs</li><li>systems vulnerable to command injection via email routing</li></ul><h4>🧠 What the attacker is testing</h4><p>This payload:</p><p><strong>|sleep 5 #</strong></p><p>is likely probing for:</p><ul><li><strong>Command execution vulnerability</strong></li><li><strong>Timing-based confirmation</strong><br> (If the server delays by ~5 seconds, the attacker knows the command ran)</li></ul><p>This is a classic <strong>non-destructive test payload</strong> used in penetration testing.</p><h4>🛡️ Server response</h4><p><strong>451 4.3.0 … Temporary lookup failure</strong></p><p>This means:</p><ul><li>The server <strong>did NOT accept or process the recipient</strong></li><li>It failed during address handling / lookup</li><li>The attack likely <strong>did not succeed</strong></li></ul><p>Also:</p><ul><li>451 = temporary failure (not permanent rejection)</li><li>No delivery occurred (F = failure)</li></ul><h4>🧾 Overall interpretation</h4><p>This log shows:</p><ul><li>An internal host (192.168.202.138) connecting to a mail server</li><li>Attempting to send an email with a <strong>maliciously crafted recipient</strong></li><li>Likely probing for <strong>command execution via email delivery</strong></li><li>The server <strong>rejected it safely</strong></li></ul><h4>⚠️ Things to check on your system</h4><p>Even though this attempt failed, it’s worth verifying:</p><ul><li>Your MTA (e.g., Exim, Postfix, Sendmail) is up to date</li><li>No unsafe aliasing or .forward rules allow piping to shell</li><li>Recipient validation is strict (no shell interpretation)</li><li>Logs for repeated attempts from the same host</li></ul><h4>🧩 Bottom line</h4><p>This is <strong>very likely a probe or exploit attempt</strong>, not a legitimate email.<br> Good news: your server appears to have <strong>handled it correctly and rejected it</strong>.</p><h3>🔥 What you’ll uncover in this dataset</h3><p>Using these queries in <strong>Splunk</strong>, you’ll clearly see:</p><h4>🔴 Attack patterns</h4><ul><li>IPs with massive RCPT failures → <strong>user enumeration</strong></li><li>Bursty traffic → <strong>automation/bots</strong></li><li>Null senders → <strong>spam/backscatter</strong></li><li>No DATA phase → <strong>probing only</strong></li></ul><h4>🟢 Normal behavior</h4><ul><li>Low volume</li><li>Successful deliveries</li><li>Full SMTP flow</li></ul><h4>🧾 Bottom line</h4><p>With the right SPL queries, this dataset reveals:</p><ul><li><strong>Who the attackers are (IPs)</strong></li><li><strong>What they’re doing (enumeration, probing)</strong></li></ul><p><strong>Happy analyzing!</strong> 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb7d56c5f6fb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Essential Sandbox for SOC Analysts]]></title>
            <link>https://hassen-hannachi.medium.com/essential-sandbox-for-soc-analysts-4b96f4c5c7de?source=rss-bd4a1e5ed7c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b96f4c5c7de</guid>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[cybercrime]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Hassen Hannachi ]]></dc:creator>
            <pubDate>Sun, 19 Apr 2026 02:56:23 GMT</pubDate>
            <atom:updated>2026-04-19T02:56:23.564Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4D9lim_Xk8yMHynPtwCzAA.png" /></figure><p>Malware analysis sandboxes are isolated, controlled execution environments designed to safely detonate and observe malicious software. By executing suspicious files, URLs, or scripts within a contained virtual environment, analysts can observe the full behavioral lifecycle of malware without risk to production infrastructure.</p><p>These platforms have become an indispensable cornerstone of modern threat intelligence pipelines, SOC workflows, malware research, and incident response operations. This guide provides a comprehensive, technically rigorous overview of<strong><em> eighteen</em></strong> major sandbox platforms — ranging from <strong><em>cloud-based</em></strong> SaaS solutions to <strong><em>self-hosted</em></strong> open-source frameworks — enabling security teams to make informed tool-selection decisions.</p><h3>Core Sandbox Capabilities</h3><p>Regardless of vendor or deployment model, all mature sandbox platforms share a common set of analytical capabilities:</p><ul><li><strong><em>Dynamic analysis</em></strong> — executing samples in a live environment and recording runtime behavior</li><li><strong><em>Static analysis</em></strong> — inspecting file headers, imports, strings, and code without execution</li><li><strong><em>Network traffic capture</em></strong> — recording DNS queries, HTTP/S requests, TCP/UDP streams</li><li><strong><em>Process tree reconstruction</em></strong> — mapping parent-child process relationships</li><li><strong><em>Registry &amp; filesystem monitoring</em></strong> — tracking all CRUD operations on host artifacts</li><li><strong><em>Memory analysis</em></strong> — capturing injected code, unpacked shellcode, and heap artifacts</li><li>YARA &amp; Sigma rule matching — correlating behavior against known threat signatures</li><li><strong><em>MITRE ATT&amp;CK mapping</em></strong> — classifying behaviors to the ATT&amp;CK framework taxonomy</li></ul><h3>Evasion &amp; Anti-Analysis Techniques</h3><p>Modern malware employs a wide range of sandbox-evasion techniques. Understanding these is essential for evaluating sandbox robustness:</p><ul><li><strong><em>Timing attacks</em></strong> — sleeping for extended periods to outlast sandbox timeouts</li><li><strong><em>Human-interaction checks</em></strong> — detecting mouse movement, keystrokes, or screen resolution</li><li><strong><em>VM artifact detection</em></strong> — querying registry keys, files, or MAC prefixes specific to hypervisors</li><li><strong><em>Process enumeration</em></strong> — checking for analysis tools (Wireshark, Process Monitor, x64dbg)</li><li><strong><em>Parent process validation</em></strong> — expecting explorer.exe as parent rather than cmd.exe</li><li><strong><em>Anti-debugging</em></strong> via IsDebuggerPresent, NtQueryInformationProcess, or timing discrepancies</li><li>CPUID &amp; RDTSC-based <strong><em>VM detection</em></strong> — leveraging instruction timing differences</li><li><strong><em>Network connectivity checks</em></strong> — refusing to execute without live internet access</li></ul><p><strong>1.VirusTotal — </strong><em>Cloud SaaS</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/525/1*-7-aRljwZJtp013ZQmNQaw.png" /></figure><p><a href="https://www.virustotal.com/gui/home/upload">VirusTotal</a> is the world’s most widely used file and URL reputation service, scanning submissions against <strong><em>70+ antivirus engines</em></strong> and providing a crowdsourced threat intelligence corpus of billions of analyzed files. While often miscategorized as solely an AV scanner, VirusTotal incorporates <strong><em>behavioral sandbox analysis</em></strong>, YARA hunting, Sigma rule correlation, and a sophisticated graph analysis tool for threat actor infrastructure mapping.</p><p><strong>2. Any.Run — </strong><em>Cloud SaaS</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*7yjW6zPJ5A70D6hTnJ4oHg.png" /></figure><p><a href="https://any.run/">Any.Run</a> is a pioneering interactive malware sandbox that distinguishes itself from fully-automated platforms by allowing the analyst to interact with the running sample in <strong><em>real time</em></strong> through a <strong><em>browser-based remote</em></strong> desktop interface. This approach is particularly <strong><em>effective against evasion techniques</em></strong> that require user input to trigger malicious behavior — such as macros requiring a button click, or installers requiring license agreement.</p><p>Launched in 2016 and headquartered in Cyprus, Any.Run is one of the <strong><em>most-used shared threat intelligence resources</em></strong> in the security community.</p><p><strong>3. Hybrid Analysis -</strong><em>Cloud SaaS</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/451/1*Ich5l_Abxvi7weSW4nTQnA.png" /></figure><p><a href="https://hybrid-analysis.com/">Hybrid Analysis</a> is <strong><em>CrowdStrike</em></strong>’<strong><em>s public</em></strong>-facing <strong><em>malware analysis portal</em></strong>, powered by the Falcon Sandbox engine. It represents <strong><em>one of the largest publicly accessible</em></strong> repositories of malware analysis reports, with millions of samples analyzed and freely searchable. The platform derives its name from its hybrid approach: combining <strong><em>static analysis, full dynamic sandbox </em></strong>detonation, and <strong><em>network-level analysis</em></strong> in a unified workflow.</p><p><strong>4. Filescan.io — </strong><em>Cloud SaaS</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*czesOJFpIDmNKBDnHNnL4g.png" /></figure><p>Filescan.io is a <strong><em>cloud-based</em></strong> malware analysis platform operated by OPSWAT, emphasizing <strong><em>deep static analysis</em></strong> and lightweight emulation as complements to full dynamic execution. Its PolyUnpack engine attempts to defeat packing and obfuscation without requiring full sandbox detonation — enabling faster throughput and reducing evasion surface.</p><p>Filescan.io is particularly valued for <strong><em>high-volume triage workflows</em></strong> where full dynamic detonation of every sample is impractical, and for analyzing samples that are deliberately slow or environment-aware.</p><p><strong>5. Cuckoo Sandbox — </strong><em>Self-Hosted (orginal)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/289/1*U1hOE5aEAdCI83JHjoXtyQ.png" /></figure><p><a href="https://cuckoo.cert.ee/">Cuckoo</a> Sandbox is the <strong><em>foundational open-source malware analysis platform</em></strong> that defined the modern sandbox paradigm. Cuckoo became the de facto reference implementation for sandbox design — influencing virtually every subsequent platform, open-source or commercial.</p><p>While Cuckoo itself is <strong><em>no longer under active developmen</em></strong>t (the <a href="https://github.com/cuckoosandbox">main repository</a> has been archived), its architectural concepts, terminology, and module design live on in CAPEv2, Drakvuf Sandbox, and numerous commercial derivatives.</p><p><strong>6. CAPEv2 (Malware Configuration And Payload Extraction) -</strong><em>Self-Hosted</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/162/1*27ZJj7ulb6ObLAGeUR039Q.png" /></figure><p><a href="https://github.com/kevoreilly/CAPEv2">CAPEv2</a> is the <strong><em>most actively maintained fork</em></strong> of the <strong><em>original Cuckoo</em></strong> Sandbox, extensively redesigned to <strong><em>add payload extraction</em></strong> and <strong><em>malware configuration</em></strong> unpacking as first-class capabilities. The name stands for Configuration And Payload Extraction — reflecting its primary innovation over vanilla Cuckoo: the ability to automatically extract embedded payloads from packed or obfuscated malware and recover readable C2 configurations.</p><p>CAPEv2 is widely deployed in<strong><em> enterprise SOCs</em></strong>, <strong><em>national CERTs</em></strong>, and <strong><em>malware research institutions</em></strong>. It is considered the production-grade successor to Cuckoo for organizations requiring full on-premise deployment</p><p><strong>7. Joe Sandbox — </strong><em>Cloud + On-Prem</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/338/1*yB9h6cqIl9Dx_678_dIb6A.png" /></figure><p><a href="https://www.joesandbox.com/">Joe Sandbox</a> is a comprehensive <strong><em>commercial malware analysis</em></strong> platform notable for its breadth of supported operating systems (Windows, macOS, Linux, Android, iOS) and its <strong><em>deep analysis capabilities</em></strong>. Joe Security positions the platform at the intersection of automated behavioral analysis and forensic-grade reporting, making it a preferred choice for <strong><em>enterprise threat intelligence</em></strong> teams, MSSPs, and <strong><em>government agencies</em></strong>.</p><p><strong>8. Manalyzer -</strong><em>Cloud SaaS</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*kgd8TqZ91xBQXhOX4GuzrA.png" /></figure><p><a href="https://manalyzer.org/">Manalyzer</a> is a specialized <strong><em>static analysis</em></strong> service focused <strong><em>exclusively </em></strong>on <strong><em>Windows Portable Executable</em></strong> (PE) files. It performs deep structural analysis of PE binaries without execution, making it safe for analyzing potentially destructive samples and suitable for high-throughput triage environments where sandbox execution time is a bottleneck.</p><p>Manalyzer’s value proposition is <strong><em>depth of static analysis</em></strong>: rather than a shallow pass over PE headers, it applies a comprehensive plugin-based inspection framework including import analysis, resource inspection, certificate verification, and behavior prediction heuristics.</p><p><strong>9. MetaDefender (OPSWAT) — </strong><em>Cloud + On-Prem</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/1*1s2w_q-8Ms547duFMNhhgA.png" /></figure><p><a href="https://id.opswat.com/">MetaDefender</a> is OPSWAT’s <strong><em>enterprise-grade threat</em></strong> prevention platform combining <strong><em>multi-engine antivirus scanning</em></strong>, <strong><em>deep file analysis</em></strong>, and Content Disarm and Reconstruction (CDR) technology. CDR is MetaDefender’s flagship differentiator: rather than merely detecting malicious content, CDR proactively disarms files by stripping all active content, macros, and embedded objects — then reconstructing a sanitized, functionally equivalent document safe for delivery to end users.</p><p><strong>10. Triage (Hatching) — </strong><em>Cloud + On-Prem</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/307/1*Eb4Dx6yGXIpQo_06NC6K3A.png" /></figure><p><a href="https://tria.ge/">Triage</a> is a high-speed <strong><em>automated malware sandbox</em></strong> developed by Dutch security company Hatching, now part of Recorded Future’s threat intelligence ecosystem. Triage distinguishes itself through exceptional analysis speed — capable of completing a full behavioral analysis in under <strong><em>60 seconds</em></strong> for most samples — and its sophisticated malware configuration extraction capabilities covering <strong><em>400+ malware families</em></strong>.</p><p><strong>11. Valkyrie (Comodo) — </strong><em>Cloud SaaS</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/288/1*TOjRgmyFUqlksS414Actwg.png" /></figure><p><a href="https://valkyrie.comodo.com/">Valkyrie</a> is Comodo’s file verdict and analysis platform, built around the challenge of handling unknown files — those not yet classified as either safe or malicious by traditional AV signatures. Comodo’s Default Deny security model <strong><em>treats all unknown files as potentially malicious</em></strong> until Valkyrie classifies them, making high-throughput unknown file analysis a core business requirement that Valkyrie was built to address.</p><p><strong>12. DRAKVUF Sandbox — </strong><em>Self-Hosted</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/173/1*0_XKcaAlfnrJ-YtmKeYHig.png" /></figure><p><a href="https://github.com/CERT-Polska/drakvuf-sandbox">DRAKVUF</a> Sandbox is a technically distinctive platform built on the DRAKVUF binary analysis system, which leverages the Xen hypervisor’s Virtual Machine Introspection (VMI) interface to perform <strong><em>agentless behavioral monitoring</em></strong>. Unlike agent-based sandboxes (Cuckoo, CAPEv2), DRAKVUF <strong><em>requires no software</em></strong> to be installed inside the analyzed VM — making it inherently more resilient against agent-aware malware that detects injected DLLs or hooks.</p><p><strong>13. Malware Next-Gen (CISA) — </strong><em>Cloud (CISA)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/286/1*6cXfRjLjmurstwuWCZ2XKw.png" /></figure><p><a href="https://www.cisa.gov/resources-tools/services/malware-next-generation-analysis">Malware Next-Gen</a> is <strong><em>CISA’s government-operated malware analysis</em></strong> service, launched in 2023 to provide US government agencies and critical infrastructure partners with access to a no-cost, secure automated malware analysis capability. The platform accepts file and URL submissions and returns detailed behavioral analysis reports without requiring organizations to operate their own sandbox infrastructure.</p><p>Unlike commercial or community platforms, <strong><em>submissions</em></strong> to Malware Next-Gen are <strong><em>not publicly shared</em></strong> — maintaining <strong><em>confidentiality</em></strong> for sensitive government and critical infrastructure threat intelligence.</p><p><strong>14. Jotti’s Malware Scan — </strong><em>Cloud</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/1*MajcuvWw0TFC2SsGsTz_XA.png" /></figure><p><a href="https://virusscan.jotti.org/">Jotti’s Malware Scan</a> is a <strong><em>free multi-engine antivirus scanning</em></strong> service that allows users to submit files for analysis against approximately <strong><em>20</em></strong> commercial and open-source <strong><em>antivirus engines simultaneously</em></strong>. It is important to distinguish Jotti from behavioral sandbox platforms: Jotti performs <strong><em>purely static signature-based scanning</em></strong> and <strong><em>does not execute</em></strong> submitted samples <strong><em>or </em></strong><em>perform </em>any form of <strong><em>behavioral analysis</em></strong>.</p><p>Jotti is best positioned as a <strong><em>rapid triage</em></strong> tool for assessing whether a file is known-malicious according to AV vendors, rather than as a substitute for dynamic analysis. It is particularly useful for <strong><em>quick </em></strong>community <strong><em>corroboration </em></strong>during <strong><em>incident response triage</em></strong>.</p><p><strong>15. VMRay — </strong><em>Cloud + On-Prem</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/160/1*yzToGJYlCLRadnjZ9E99Kg.png" /></figure><p><a href="https://www.vmray.com/">VMRay</a> is a <strong><em>premium commercial</em></strong> sandbox platform distinguished by its hypervisor-based monitoring architecture — monitoring guest execution from outside the OS, making it <strong><em>highly resistant to in-guest evasion techniques</em></strong>. VMRay markets its platform on detection accuracy and minimal false positive rates, positioning it as an enterprise-grade solution for high-stakes environments including financial institutions, critical infrastructure operators, and government agencies.</p><p><strong>16. Malice — </strong><em>Self-Hosted</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/1*gq0-fLMFlIFEx-Ip8XzdTw.png" /></figure><p><a href="https://github.com/maliceio/malice">Malice</a> is an open-source malware analysis framework designed as a modular, <strong><em>Docker-native</em></strong> alternative to Cuckoo Sandbox. Rather than relying on traditional hypervisor-based VM guests, Malice orchestrates a collection of <strong><em>containerized analysis plugins </em></strong>— each implementing a specific scanning or analysis function — coordinated by a central Go-based engine. <strong><em>Results</em></strong> are <strong><em>stored </em></strong>in <strong><em>Elasticsearch </em></strong>and <strong><em>visualized </em></strong>via <strong><em>Kibana </em></strong>dashboards.</p><p>Malice was designed for cloud-native deployments and environments where Docker infrastructure already exists, reducing the overhead of hypervisor management.</p><p><strong>17. Viper — </strong><em>Self-Hosted</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*I_PxCXDe_a6TWF9XYOSolQ.png" /></figure><p><a href="https://github.com/viper-framework/viper">Viper</a> is an open-source binary analysis and management framework designed as a structured workspace for <strong><em>malware analysts and reverse engineers</em></strong>. Unlike automated detonation sandboxes, Viper functions as an interactive analysis environment where analysts manually drive investigation through a modular <strong><em>command-line interface</em></strong> — similar in philosophy to Metasploit’s msfconsole.</p><p>Viper excels at malware collection management: it maintains a structured repository of analyzed samples, preserving analysis context, notes, tags, and module results alongside each sample for team collaboration and longitudinal research.</p><p><strong>18. ViperMonkey — </strong><em>Self-Hosted (library)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/503/1*FHvJjyJ-lFsno-RKZTGGCQ.png" /></figure><p><a href="https://github.com/decalage2/ViperMonkey">ViperMonkey</a> is a specialized VBA (Visual Basic for Applications) macro emulation engine designed to <strong><em>analyze </em></strong>and <strong><em>deobfuscate malicious macros</em></strong> embedded in <strong><em>Microsoft Office documents</em></strong> (DOCX, XLSX, PPTX, DOC, XLS, PPT) without executing them in a live Microsoft Office environment. This makes it safe to analyze weaponized documents while extracting the malicious payload URLs, shellcode, or dropped file content.</p><p>ViperMonkey <strong><em>is not a full sandbox</em></strong> — it is a focused <strong><em>static-dynamic hybrid</em></strong> tool for the specific problem of <strong><em>Office macro analysis</em></strong>, an area where general-purpose sandboxes sometimes struggle with timing, font rendering, or DDE-based evasions.</p><h3><strong>Platform Comparison Matrix</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*4wD3YeEU7MMZYgQ8Il0alQ.png" /></figure><p>Organizations should select malware analysis platforms based on the following prioritized criteria:</p><h4>For High-Volume SOC Triage</h4><ul><li><strong><em>Primary</em></strong>: Triage (speed), Hybrid Analysis (free API), VirusTotal (known-file lookup)</li><li><strong><em>Supplement</em></strong>: Any.Run for interactive investigation of flagged samples</li><li><strong><em>Configuration extraction</em></strong>: Triage or CAPEv2 for automated C2 recovery</li></ul><h4>For Air-Gapped / High-Security Environments</h4><ul><li><strong><em>Primary</em></strong>: CAPEv2 or DRAKVUF (self-hosted, no external data leakage)</li><li><strong><em>Supplement</em></strong>: Viper for sample repository management and team collaboration</li><li><strong><em>Document analysis</em></strong>: ViperMonkey for Office macro deobfuscation without execution</li></ul><h4>For Malware Research &amp; Threat Intelligence</h4><p>• <strong><em>Primary</em></strong>: CAPEv2 (configuration extraction), VMRay (accuracy), Joe Sandbox (breadth)</p><p>• <strong><em>Hunting</em></strong>: VirusTotal Intelligence (corpus search), Triage (YARA hunting)</p><p>• <strong><em>Code analysis</em></strong>: Viper + ViperMonkey for deep static and macro investigation</p><h4>For Enterprise with Strict Privacy Requirements</h4><p>• <strong><em>Primary</em></strong>: VMRay on-premise or Joe Sandbox on-premise</p><p>• <strong><em>Supplement</em></strong>: MetaDefender for CDR-based file sanitization workflows</p><p>• <strong><em>Government entities </em></strong>(US): CISA Malware Next-Gen for no-cost secure analysis</p><h4>For Budget-Constrained / Resource-Limited Teams</h4><p>• <strong><em>Primary</em></strong>: CAPEv2 (self-hosted OSS) + Hybrid Analysis (free cloud)</p><p>• <strong><em>Triage</em></strong>: Filescan.io free tier + Jotti for rapid multi-AV confirmation</p><p>• <strong><em>Document analysis</em></strong>: ViperMonkey (free, no infrastructure required)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b96f4c5c7de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 5-Network+ N10–009 Compare and Contrast Transmission Media and Transceivers]]></title>
            <link>https://hassen-hannachi.medium.com/day-5-network-n10-009-compare-and-contrast-transmission-media-and-transceivers-67401540c90a?source=rss-bd4a1e5ed7c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/67401540c90a</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[computer-networking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[comptia-certifications]]></category>
            <dc:creator><![CDATA[Hassen Hannachi ]]></dc:creator>
            <pubDate>Sun, 12 Apr 2026 23:14:39 GMT</pubDate>
            <atom:updated>2026-04-12T23:14:39.456Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RFkmuLDkwWpcpr7efYpCqA.png" /></figure><p>Chapter 5 of CompTIA Network+ N10–009 focuses on the <strong><em>physical layer</em></strong> of networking — the cables, wireless standards, cellular technologies, connectors, and transceivers that carry data between devices. Understanding these topics is essential both for the exam and for day-to-day work in any network environment.</p><p>This chapter covers four major exam objective areas:</p><ul><li>Wireless — 802.11 standards and Wi-Fi generations</li><li>Cellular — LTE, NB-IoT, GSM, and satellite</li><li>Wired — Fibre, copper, coaxial, and cabling standards</li><li>Transceivers &amp; Connector Types — Form factors, protocols, and physical connectors</li></ul><h3>Wireless</h3><p>Wireless networking transmits data using <strong><em>radio frequency</em></strong> (<strong><em>RF</em></strong>) signals through the air rather than physical cables. The IEEE 802.11 family of standards defines how Wi-Fi networks operate, evolving over decades to deliver faster speeds and more reliable connections.</p><h4>802.11 Standards</h4><p>The <strong><em>IEEE</em></strong> (Institute of Electrical and Electronics Engineers) publishes all 802.11 wireless standards. Each generation improves on speed, frequency bands, range, and capacity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*BNZQzIRzR0R9YD1cTTldHw.png" /><figcaption>802.11 wireless standards</figcaption></figure><h4>Key 802.11 Concepts to Know</h4><ul><li><strong><em>MIMO </em></strong>(Multiple Input Multiple Output): Uses multiple antennas to send/receive simultaneously, boosting throughput — introduced in 802.11n.</li><li><strong><em>MU-MIMO</em></strong> (Multi-User MIMO): Allows the AP to communicate with multiple clients at once (802.11ac/ax).</li><li><strong><em>OFDMA</em></strong> (Orthogonal Frequency Division Multiple Access): Splits channels into sub-channels for more efficient delivery in dense environments — key feature of Wi-Fi 6.</li><li><strong><em>Beamforming</em></strong>: Focuses the wireless signal toward specific clients rather than broadcasting in all directions, improving range and speed.</li><li><strong><em>BSS Coloring</em></strong>: Reduces interference in dense deployments by tagging frames with a color identifier so devices can ignore signals from neighboring networks.</li><li><strong><em>Channels</em></strong>: 2.4 GHz has 11 channels (3 non-overlapping: 1, 6, 11); 5 GHz has many more non-overlapping channels — reducing co-channel interference.</li></ul><blockquote><strong>Exam Tip: </strong>Know the frequency bands for each standard. 802.11b and g are 2.4 GHz only; 802.11a is 5 GHz only; 802.11n, ac, and ax are dual or tri-band. 802.11ax (Wi-Fi 6E) adds the 6 GHz band.</blockquote><h3>Cellular</h3><p>Cellular networks use radio towers divided into geographic cells to provide wide-area wireless coverage. Unlike Wi-Fi, cellular can span cities, countries, and continents. The exam tests knowledge of four cellular technologies.</p><h4>Long Term Evolution (LTE)</h4><p>LTE — often marketed as 4G LTE — is the most widely deployed cellular standard globally. It represents a significant leap over previous 3G technologies and forms the backbone of modern mobile data networks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*uE-VrsqjKtYvgruAnSLLYw.png" /><figcaption>Long Term Evolution (LTE)</figcaption></figure><ul><li>Theoretical speeds: Up to 300 Mbps download / 75 Mbps upload (real-world is much less).</li><li>LTE-Advanced (<strong><em>LTE-A</em></strong>): Extends LTE with carrier aggregation, reaching speeds over 1 Gbps.</li><li><strong><em>LTE-M</em></strong> (LTE for Machines): A low-power variant designed for IoT devices; supports voice and mobility.</li><li>Uses licensed spectrum managed by mobile carriers (e.g., AT&amp;T, Verizon, T-Mobile).</li><li>Packet-switched: All data, including voice (VoLTE), is transmitted as IP packets.</li></ul><blockquote><strong>Real World: </strong>When you connect your phone to the internet away from Wi-Fi, you are almost certainly using LTE or 5G NR (New Radio). LTE is the global standard that 5G networks also rely on as a fallback.</blockquote><h4>Narrowband-IoT (NB-IoT)</h4><p>NB-IoT is a low-power wide-area (<strong><em>LPWA</em></strong>) technology standardized by 3GPP to connect IoT devices that send small amounts of data infrequently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/1*LhmoVHpDJOMs5XPcUiJoiw.png" /><figcaption>Narrow Band — Internet of Things (NB-IoT)</figcaption></figure><ul><li>Operates in licensed spectrum — reliable and interference-free compared to unlicensed alternatives.</li><li>Designed for deep indoor penetration (basements, underground meters).</li><li>Supports massive device density — thousands of devices per cell.</li><li>Very low power consumption — devices can run on small batteries for years.</li><li>Low data rates (up to ~250 kbps): suitable for sensors, smart meters, asset trackers.</li><li>Not designed for high mobility (phones moving at speed); suited for stationary or slow-moving devices.</li></ul><blockquote><strong>Exam Tip: </strong>NB-IoT competes with LoRaWAN and Sigfox for IoT connectivity. Know that NB-IoT uses licensed spectrum (more reliable) while LoRaWAN uses unlicensed spectrum (cheaper, less guaranteed).</blockquote><h4>Global System for Mobile Communication (GSM)</h4><p>GSM is the foundational 2G cellular standard, first deployed in 1991 and still in use as a fallback in many parts of the world. It introduced digital mobile communication and the SIM card.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/486/1*GQ0RYEgn76f6r5S7L6dclw.png" /></figure><p>• <strong><em>Frequency bands</em></strong>: 850 MHz, 900 MHz, 1800 MHz, 1900 MHz.</p><p>• <strong><em>TDMA</em></strong> (Time Division Multiple Access): Multiple users share a frequency channel by dividing it into time slots.</p><p>• Introduced the SIM (Subscriber Identity Module) card — a removable card identifying the subscriber.</p><p>• Data extensions: GPRS (2.5G) and EDGE (2.75G) added basic mobile data.</p><p>• Still relevant for IoT devices using GSM/GPRS modules in regions without LTE coverage.</p><blockquote><strong>Exam Tip: </strong>GSM is important context for the exam. Know that CDMA (used by Verizon historically) is the main alternative to GSM. Most modern networks have moved to LTE and 5G, but understanding GSM helps with troubleshooting legacy devices.</blockquote><h4>Satellite</h4><p>Satellite internet provides connectivity via communication satellites in Earth orbit. It is the go-to solution for remote areas without terrestrial infrastructure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*WEb3x7hpt-gWgmooUniGJg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/338/1*ibpm1YCFfwszOMsDFQTIQA.png" /></figure><ul><li><strong><em>GEO</em></strong> satellites orbit at a fixed point above the equator — the dish can be fixed but latency is very high.</li><li><strong><em>LEO </em></strong>satellites (like <strong><em>Starlink</em></strong>) orbit much closer, offering dramatically lower latency but require tracking antennas as satellites move across the sky.</li><li><strong><em>Use cases</em></strong>: remote locations, maritime, aviation, disaster recovery, military.</li></ul><blockquote><strong>Key Point: </strong>Satellite’s biggest challenge is latency. GEO latency (~600ms round trip) makes real-time applications (VoIP, gaming) difficult. LEO systems like Starlink aim to solve this with ~30–40ms latency.</blockquote><h3>Wired Media</h3><p>Wired transmission media remain the backbone of enterprise networking. Physical cables offer predictable performance, security, and high throughput compared to wireless alternatives.</p><h4>Fibre Ethernet and OM Standards</h4><p>Fibre optic cables transmit data as <strong><em>pulses of light</em></strong> through a glass or plastic core. They are immune to <strong><em>electromagnetic interference</em></strong> (<strong><em>EMI</em></strong>), support very long distances, and carry massive bandwidth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*pWHIhMg3aB0JzBuRXuvFoA.png" /><figcaption>Fibre optic cable</figcaption></figure><h4>Multimode Fibre (MMF) — OM Standards</h4><p>Multimode fibre has a larger core (50 or 62.5 microns) and allows multiple light modes to travel simultaneously. Used for <strong><em>shorter distances</em></strong>, typically within a <strong><em>data center</em></strong> or campus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*1y_TRhyDVDQYuoAmFsyFyg.png" /><figcaption>OM Standards</figcaption></figure><blockquote><strong>Memory Aid: </strong>OM1 and OM2 are legacy (orange). OM3 and OM4 are aqua — the modern standards. OM5 is lime green and designed for Wideband Multimode Fibre (WBMMF) using multiple wavelengths</blockquote><h4>Single-Mode vs Multimode Fibre</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*yLvsusWhq8Q6P4szVCtYKw.png" /><figcaption>Single-Mode vs Multimode Fibre</figcaption></figure><blockquote><strong>Exam Tip: Single<em>-</em>mode </strong>= long distance, laser, yellow jacket. <strong>Multimode </strong>= short distance, LED, color-coded by OM standard. The key differentiator is core size and distance.</blockquote><h4>Direct Attach Copper (DAC) Cables</h4><p>DAC cables are passive or active <strong><em>copper twinaxial</em></strong> cables with transceivers pre-attached at both ends. They are a cost-effective alternative to fibre for short-distance, high-speed connections within racks or between adjacent racks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*kGaTyb-9K4JdLQ3zfx6eaA.png" /><figcaption>Direct Attach Copper (DAC)</figcaption></figure><ul><li>Typical lengths: 1–7 meters (passive); up to 15 meters (active DAC).</li><li>Common speeds: 10G, 25G, 40G, 100G, 400G.</li><li>Used for <strong><em>server-to-switch</em></strong> and <strong><em>switch-to-switch</em></strong> connections inside <strong><em>data centers</em></strong>.</li><li>No optical conversion needed — reduces latency and cost vs. fibre + transceiver.</li><li>Form factors: SFP+, QSFP+, QSFP28 ends (pre-installed).</li></ul><blockquote><strong>Key Point: </strong>DAC cables are the cheapest and lowest-latency option for short data center runs. They cannot be used for long distances — that is where fibre takes over.</blockquote><h4>Coaxial Cable</h4><p>Coaxial (coax) cable consists of a central copper conductor, surrounded by insulation, a metallic shield, and an outer jacket. The shield protects against EMI and allows the cable to carry high-frequency signals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/230/1*HTkGwAwkf55Mi0IzPF0E9w.png" /></figure><ul><li><strong><em>RG-6</em></strong>: Standard for cable TV, satellite TV, and broadband internet to the home.</li><li><strong><em>RG-59</em></strong>: Older standard; lower quality, used for short CCTV runs and older cable TV.</li><li><strong><em>RG-11</em></strong>: Thicker, lower attenuation; used for longer cable runs.</li><li>Characteristic impedance: 75 ohms for video/broadband; 50 ohms for RF/networking.</li><li>Still widely used for cable internet (DOCSIS), CCTV cameras, and antenna connections.</li></ul><h4>Cable Speed</h4><p>Cable speed refers to the rated maximum data transfer rate of a cable type. Key factors affecting speed include:</p><p>• Category (Cat) rating for copper UTP: Cat5e supports 1 Gbps; Cat6 supports 10 Gbps (short runs); Cat6a supports 10 Gbps at 100m; Cat7/8 for higher speeds.</p><p>• Fibre type and OS/OM rating define supported speeds and distances.</p><p>• Coaxial speed depends on DOCSIS version — DOCSIS 3.1 supports multi-Gbps.</p><p>• DAC cable speed is defined by the transceiver standard (e.g., 25GBASE-CR for 25G DAC).</p><blockquote><strong>Exam Tip: </strong>For copper Ethernet: Cat5e = 1G, Cat6 = 10G (short distances), Cat6a = 10G (100m). These are commonly tested values.</blockquote><h4>Plenum vs Non-Plenum Cable</h4><p>Plenum is a type of jacket in Ethernet cables. The major difference between plenum cables and other cables are <strong><em>jacket material</em></strong>. In the plenum-rated cables use a <strong><em>fire-retardant</em></strong> material which burns slowly and emits <strong><em>less intoxicated</em></strong> fumes as compared to the non-plenum-rated cables.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*foFLviZ9Op7ATQHcSzcbdg.png" /><figcaption>Plenum-rated cable</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*Kv1uuqKbeH6JT8fKzV9t4g.png" /><figcaption>Plenum vs Non-Plenum</figcaption></figure><blockquote><strong>Important: </strong>Plenum spaces are the air-handling spaces in buildings (above drop ceilings, under raised floors) where HVAC air circulates. Fire codes (NEC) require plenum-rated cable in these spaces because toxic smoke from burning PVC could circulate throughout the building.</blockquote><h3>Transceivers</h3><p>A transceiver is a device that can both <strong><em>transmit and receive signal</em></strong>s. In networking, transceivers are modular components (often called pluggable optics) that convert <strong><em>electrical signals</em></strong> to <strong><em>optical (light)</em></strong> <strong><em>signals </em></strong>and <strong><em>vice versa</em></strong>, allowing network equipment to support different cable types and speeds.</p><h4>Transceiver Protocols</h4><p>The protocol defines the data rate and physical standard the transceiver implements:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*qD1t1lzQGpNP2rg9GOnoZQ.png" /><figcaption>Transceiver Protocols</figcaption></figure><blockquote><strong>Key Concept: SR</strong> = Short Range (multimode). <strong>LR</strong> = Long Range (single-mode). <strong>ER</strong> = Extended Range. <strong>ZR </strong>= Ultra-long range. These suffixes appear on transceivers and mean the same thing across speed tiers.</blockquote><h4>Transceiver Form Factors</h4><p>Form factors define the physical shape and interface of the transceiver module. Network equipment (switches, routers, NICs) has slots that accept specific form factors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/494/1*r2p6jnRShca9SpE0FGEw9A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*MY5Rcy_OgfbCJJbMcP_mUw.png" /></figure><blockquote><strong>Exam Tip: </strong>SFP = 1G; SFP+ = 10G; QSFP+ = 40G; QSFP28 = 100G. These are the four most tested transceiver form factors on the Network+ exam. Also remember that transceivers are hot-swappable — you can replace them without powering down the switch.</blockquote><h3>Connector Types</h3><p>Connectors are the physical interfaces at the end of cables. Knowing which connector goes with which cable type and use case is essential for the Network+ exam and for hands-on network work.</p><h4>Fibre Optic Connectors</h4><h4>SC (Subscriber Connector / Standard Connector)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/1*xHNAAWxaVBZhq4sH_WSSKQ.png" /><figcaption>SC (Subscriber Connector/ Standard Connector)</figcaption></figure><ul><li>Type: Fibre optic (single-mode and multimode)</li><li>Shape: Square, push-pull latching mechanism — click in, pull out.</li><li>Core size: 2.5mm ferrule.</li><li><strong><em>Use case</em></strong>: Older enterprise networking, broadband, cable TV (FTTX).</li><li>Duplex SC: Two SC connectors side by side for TX and RX.</li></ul><blockquote><strong>Memory Aid: </strong>SC = Square Connector. Its square shape and snap-in mechanism make it easy to identify.</blockquote><h4>LC (Lucent Connector / Little Connector)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/1*1DADui5M6czWLdsCUjE8yQ.png" /><figcaption>LC (Lucent Connector / Little Connector)</figcaption></figure><ul><li>Type: Fibre optic (single-mode and multimode)</li><li>Shape: Small form factor — half the size of SC; uses a 1.25mm ferrule.</li><li>Latching: Tab latch (similar to an RJ45 clip).</li><li><strong><em>Use case</em></strong>: Most common fibre connector in modern enterprise and data center environments.</li><li>Duplex LC: Two LC connectors in a single housing — the standard for SFP transceivers.</li></ul><blockquote><strong>Memory Aid: </strong>LC = Little Connector. It is the small, modern fibre connector you will see most often in data centers.</blockquote><h4>ST (Straight Tip)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/1*OWRMHdhqzr68QPe4GwvXHw.png" /><figcaption>ST (Straight Tip)</figcaption></figure><ul><li>Type: Fibre optic (multimode, occasionally single-mode)</li><li>Shape: Cylindrical with a bayonet-style twist-lock mechanism.</li><li>Core size: 2.5mm ferrule.</li><li><strong><em>Use case</em></strong>: Older fibre installations, campus networks, military applications.</li><li>Less common in new installations — SC and LC have largely replaced it.</li></ul><blockquote><strong>Memory Aid: </strong>ST = Stab and Twist. You insert and twist the bayonet lock to secure the connector.</blockquote><h4>Copper / Telephony Connectors</h4><h4>RJ11</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*DX2vKXK2t8lhlDIOgfduCQ.png" /><figcaption>RJ11</figcaption></figure><ul><li>Type: Copper telephone connector</li><li>Pins: 6 positions, 2 or 4 conductors (6P2C or 6P4C)</li><li><strong><em>Use case</em></strong>: Analog telephone lines (POTS), DSL modems, home phone wiring.</li><li>Smaller than RJ45; will not fit in an RJ45 jack correctly.</li></ul><blockquote><strong>Key Difference: </strong>RJ11 is for telephone/DSL (narrower, 6-position). RJ45 is for Ethernet (wider, 8-position). Knowing the difference is a basic but commonly tested Network+ question.</blockquote><h4>RJ45</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*Vn0ehwgLBrKMgRFsD-yLWg.png" /><figcaption>RJ45</figcaption></figure><ul><li>Type: Copper Ethernet connector</li><li>Pins: 8 positions, 8 conductors (8P8C)</li><li><strong><em>Use case</em></strong>: Ethernet cabling (Cat5e, Cat6, Cat6a) for LAN connections.</li><li>Wiring standards: T568A and T568B define which wire pair goes in which position.</li><li>Crossover cable: TX and RX pairs swapped — used for direct device-to-device connections (legacy; modern devices use Auto-MDIX).</li></ul><blockquote><strong>Exam Tip: </strong>RJ45 with T568B wiring is the most common Ethernet cabling standard in North America. Know the color order for both T568A and T568B for the exam.</blockquote><h4>Coaxial Connectors</h4><h4>F-Type Connector</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/253/1*ecb7Yf-twU3sKoUOY9Bedw.png" /><figcaption>F-Type Connector</figcaption></figure><ul><li>Type: Coaxial (RG-6, RG-59)</li><li>Mechanism: Threaded screw-on (male/female).</li><li><strong><em>Use case</em></strong>: Cable TV, satellite TV, broadband cable internet (DOCSIS modem connections), over-the-air antenna.</li><li>Impedance: 75 ohms.</li><li>The connector that screws onto the back of your cable modem or TV.</li></ul><blockquote><strong>Memory Aid: </strong>F-type = the connector on your cable TV or cable modem. It screws on.</blockquote><h4>BNC (Bayonet Neill-Concelman)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*21ednPKTodZ0u7LdpXykXg.png" /><figcaption>BNC (Bayonet Neill-Concelman)</figcaption></figure><ul><li>Type: Coaxial</li><li>Mechanism: Bayonet-style twist-lock (quarter-turn to lock/unlock).</li><li><strong><em>Use case</em></strong>: 10BASE2 (Thinnet) legacy Ethernet, professional video (SDI), test equipment, CCTV.</li><li>Impedance: 50 ohms (networking) or 75 ohms (video).</li><li>Largely legacy in networking but still common in broadcast video and security cameras.</li></ul><h4>BNC T-Connector</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*Du78pXta9JwPe9gCQSBd6A.png" /><figcaption>BNC T-Connector</figcaption></figure><ul><li>Type: Coaxial adapter</li><li>Shape: T-shaped; has one BNC female and two BNC male connectors.</li><li><strong><em>Use case</em></strong>: 10BASE2 (Thinnet) Ethernet bus topology — connected each network device to the coax backbone.</li><li>The device’s NIC connected to the middle of the T; the coax segments connected to each end.</li></ul><blockquote><strong>History Note: </strong>BNC T-connectors were essential in early Ethernet bus networks (10BASE2). If one T-connector or terminator failed, the entire segment went down — a key limitation of bus topology.</blockquote><h4>BNC Barrel Connector</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/225/1*Ug6UNZtGIPw4i0k0tdMs0g.png" /><figcaption>BNC Barrel Connector</figcaption></figure><ul><li>Type: Coaxial adapter</li><li>Shape: Cylindrical; joins two BNC male connectors end-to-end.</li><li><strong><em>Use case</em></strong>: Extending a coaxial cable run by joining two cable segments.</li><li>Used in 10BASE2 networks and CCTV/video installations.</li><li>Each barrel connector introduces signal loss (attenuation) — should be minimized.</li></ul><h4><strong>Connector Summary</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/1*h5B0HJ6jpb4-0bFlG6RPrw.png" /></figure><h3>Exam Tips &amp; Key Takeaways</h3><h4>Wireless</h4><ul><li>Know all 802.11 standards by frequency and max speed — especially 802.11n (dual-band, MIMO), 802.11ac (5 GHz, MU-MIMO), and 802.11ax (OFDMA, Wi-Fi 6, 6 GHz added).</li><li><strong><em>2.4 GHz</em></strong> = longer range, more interference (microwaves, Bluetooth). 5<strong><em> GHz</em></strong> = shorter range, less interference, more channels.</li></ul><h4>Cellular</h4><ul><li><strong><em>LTE</em></strong> = 4G mobile broadband. <strong><em>NB-IoT</em></strong> = low-power IoT in licensed spectrum. <strong><em>GSM</em></strong> = 2G foundation with SIM cards. <strong><em>Satellite </em></strong>= remote areas with GEO high latency vs. LEO low latency.</li></ul><h4>Wired</h4><ul><li><strong><em>Single-mode fibre</em></strong> = yellow jacket, laser, long distance. Multimode = colored (aqua/orange/green), LED, short distance.</li><li>OM1/OM2 are orange (legacy); OM3/OM4 are aqua; OM5 is lime green.</li><li><strong><em>Plenum cable</em></strong> is required where HVAC air circulates — it produces less toxic smoke when burning.</li><li><strong><em>DAC cables</em></strong>: cheap, low-latency, copper twinax for rack-to-rack runs in data centers.</li></ul><h4>Transceivers</h4><ul><li><strong><em>SFP</em></strong> = 1G, <strong><em>SFP+</em></strong> = 10G, <strong><em>QSFP+</em></strong> = 40G, <strong><em>QSFP28</em></strong> = 100G. These are hot-swappable.</li><li><strong><em>SR</em></strong> = short range (multimode), <strong><em>LR</em></strong> = long range (single-mode).</li></ul><h4>Connectors</h4><ul><li><strong><em>SC</em></strong> = square, push-pull fibre. LC = little/small, tab-latch fibre (modern standard). ST = stab and twist, bayonet lock (legacy).</li><li><strong><em>RJ11</em></strong> = phone (6 pins, narrow). RJ45 = Ethernet (8 pins, wider).</li><li><strong><em>F-type</em></strong> = cable TV/modem, threaded. BNC = legacy coax, bayonet. BNC T = bus topology. BNC Barrel = extends coax.</li></ul><blockquote><strong>Final Tip: </strong>For the Network+ exam, focus on what differentiates similar options: SC vs LC (size), single-mode vs multimode (core size, distance, color), RJ11 vs RJ45 (pins, use case), plenum vs non-plenum (fire rating, air space requirement). These contrasts are exactly what exam questions test.</blockquote><p><strong>Good luck on your Network+ N10–009 exam! </strong><em>You’ve got this.</em></p><p><em>Part of the Network+ N10–009 Series, </em><strong>Next up</strong>: <strong>Compare and Contrast Network Topologies, Architectures and Types</strong>. Stay tuned! 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67401540c90a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 4-Network+ N10–009 Common Networking Ports, Protocols, Services & Traffic Types]]></title>
            <link>https://hassen-hannachi.medium.com/day-4-network-n10-009-common-networking-ports-protocols-services-traffic-types-2c07f273b2c4?source=rss-bd4a1e5ed7c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c07f273b2c4</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[comptia-certifications]]></category>
            <category><![CDATA[computer-networking]]></category>
            <dc:creator><![CDATA[Hassen Hannachi ]]></dc:creator>
            <pubDate>Mon, 30 Mar 2026 03:20:33 GMT</pubDate>
            <atom:updated>2026-03-30T03:20:33.641Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*udOYttybxpDcEmh6cLfbbQ.png" /></figure><h3><strong>Introduction</strong></h3><p>Imagine a city full of apartment buildings. Every building has a street address — that’s your IP address. But inside each building are hundreds of individual apartments, each with its own number. Those apartment numbers are ports, and the rules the residents follow to communicate are protocols.</p><p>Chapter 4 dives into exactly this: how data finds its destination, what rules govern the conversation, and how traffic is classified across modern networks. This is foundational knowledge — mastering it makes the rest of networking click into place.</p><blockquote><strong>WHY THIS MATTERS</strong> Ports, protocols, and traffic types are tested directly on the Network+ exam and underpin firewall rules, network troubleshooting, and security analysis in real-world jobs.</blockquote><h3>Part 1 — Protocols and Ports</h3><h4>Ports — The Doors of Communication</h4><p>A port is a <strong><em>logical endpoint for communication</em></strong> on a device. When data arrives at your computer via its IP address, the operating system uses the port number to determine which application should handle it.<br>Port numbers range from <strong><em>0 to 65,535</em></strong> and are divided into three official categories defined by IANA (Internet Assigned Numbers Authority):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*LSK3D0N2_DpTNbNYuoHJqA.png" /></figure><p>When your browser opens a webpage, it contacts the server on port 80 (HTTP) or 443 (HTTPS). Your OS simultaneously assigns your browser a random ephemeral port (e.g., 51,423) so the server knows where to send the response back.</p><blockquote><strong>MENTAL MODEL</strong> Think of a port like a TV channel. The IP address is the cable box (the device), and the port is the channel number that routes incoming data to the right application (show).</blockquote><h4>Common Protocols &amp; Port Numbers</h4><p>A protocol is a standardized <strong><em>set of rules </em></strong>defining how data is <strong><em>formatted</em></strong>, <strong><em>transmitted</em></strong>, and <strong><em>received</em></strong>. The following are the protocols you must know for the exam, grouped by function.</p><p><strong><em>File Transfer &amp; Remote Access</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/724/1*rC5027ee6zNHr7KIe7vQLg.png" /></figure><p><strong><em>Email Protocols</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/726/1*gxT-lQszLOoqPYBrP2Cg2w.png" /></figure><p><strong><em>Web &amp; Name Resolution</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*DL6nLA9Ro36ivI2gu0FOhg.png" /></figure><p><strong><em>Network Management &amp; Infrastructure</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/726/1*Lnus2sWmU-5JHTjY9GPQ2A.png" /></figure><blockquote>📝 <strong>EXAM TIP</strong> DNS normally uses UDP port 53 for standard queries (fast, lightweight). It switches to TCP port 53 for zone transfers or when a UDP response exceeds 512 bytes. Expect a scenario question about this distinction on the exam.</blockquote><h3>Part 2 — Internet Protocol Types</h3><p>At <strong><em>Layer 3 (Network Layer)</em></strong> of the OSI model, several protocols handle how packets are addressed, routed, and delivered. The four IP-level protocols in this section each serve a distinct purpose — and each is tested on the exam.</p><h4>ICMP — Internet Control Message Protocol</h4><p>ICMP is not used to transfer user data. Instead, it carries error messages and diagnostic information between network devices. It operates at Layer 3 and is embedded directly in IP packets (protocol number 1).</p><p><strong>Common ICMP Message Types</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/724/1*7yOppoKtXV3O9VHd6hHF6w.png" /></figure><p><strong>Tools That Use ICMP</strong></p><ul><li><strong><em>ping</em></strong> — sends ICMP Echo Request (Type 8), awaits Echo Reply (Type 0)</li><li><strong><em>traceroute / tracert</em></strong> — uses incrementing TTL and ICMP Time Exceeded (Type 11) to map network hops</li><li><strong><em>pathping </em></strong>— Windows tool combining ping and traceroute with latency statistics</li></ul><blockquote><strong>SECURITY NOTE</strong> ICMP is often blocked by firewalls to prevent reconnaissance (e.g., ping sweeps). A lack of ping response does not always mean a host is down — ICMP packets may simply be filtered by a security policy.</blockquote><h4>TCP — Transmission Control Protocol</h4><p>TCP is a <strong><em>connection-oriented</em></strong> protocol at <strong><em>Layer 4 (Transport)</em></strong>. It guarantees that data arrives completely, in order, and without errors — at the cost of some overhead. TCP is identified by IP protocol number 6.</p><p><strong>The Three-Way Handshake</strong><br>Before any data is sent, TCP establishes a connection using a three-step process:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*CxAcycVbQoDOahYGdsQ1MQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/724/1*0uXre4DUjNB4UI4wJqnomQ.png" /></figure><p><strong>Key TCP Features</strong></p><ul><li><strong><em>Sequencing</em></strong> — packets are numbered; receiver reassembles in correct order</li><li><strong><em>Acknowledgements</em></strong> — receiver confirms receipt; sender retransmits on timeout</li><li><strong><em>Flow Control</em></strong> — sliding window mechanism prevents overwhelming the receiver</li><li><strong><em>Error Checking</em></strong> — checksum field detects corrupted packets in transit</li><li><strong><em>Connection Termination</em></strong> — four-way FIN/ACK handshake cleanly closes the session</li></ul><blockquote><strong>USE TCP WHEN…</strong> Data integrity matters more than speed: web browsing, email, file transfers, database queries, SSH sessions. If a packet is lost, you want it retransmitted automatically.</blockquote><h4>UDP — User Datagram Protocol</h4><p>UDP is a <strong><em>connectionless protocol</em></strong> — it sends packets with no handshake, no acknowledgement, and no delivery guarantee. What it lacks in reliability it makes up for in <strong><em>raw speed and low overhead</em></strong>. UDP is protocol number 17.</p><p><strong>TCP vs UDP — Head to Head</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*NKh-D5zu1PB4JMyxJYmFtg.png" /></figure><p><strong>USE UDP WHEN…</strong> Speed and low latency matter more than perfection: VoIP, live video streaming, online gaming, DNS lookups, TFTP, SNMP. A dropped frame in a call is better than freezing while waiting for retransmission.</p><blockquote>📝 <strong>EXAM TIP</strong> The exam often asks: ‘Which protocol would you use for real-time voice communication?’ The answer is always UDP. VoIP can tolerate an occasional lost packet, but cannot tolerate the delay caused by TCP retransmission. Know this distinction cold.</blockquote><h4>GRE — Generic Routing Encapsulation</h4><p>GRE is a tunneling protocol (IP protocol number 47) developed by Cisco. It wraps — encapsulates — one network protocol inside another, creating a virtual point-to-point link across an IP network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*Cu4l-dPvKu0zA1oj_AUsKw.png" /></figure><p><strong>How GRE Works</strong><br>GRE adds a new outer IP header and a GRE header to the original packet, allowing it to traverse networks that might not otherwise support the inner protocol:</p><p><strong>GRE Key Characteristics</strong></p><ul><li>Protocol-agnostic — can tunnel IPv4, IPv6, IPX, and other protocols inside an IP network</li><li><strong><em>No built-in encryption</em></strong> — GRE alone is not secure; pair with IPsec for secure tunnels</li><li>Common in VPNs — GRE + IPsec is a standard enterprise site-to-site VPN combination</li><li>Adds overhead — extra headers increase packet size; watch for MTU fragmentation issues</li></ul><blockquote><strong>GRE + IPSEC = SECURE VPN TUNNEL </strong>GRE provides the tunnel mechanism; IPsec provides encryption and authentication. Think of GRE as a pipe with no lock — IPsec is the padlock you add for security.</blockquote><h3>Part 3 — Traffic Types</h3><p>Not all network traffic is addressed the same way. The traffic type determines how many devices receive a given packet and how routers and switches handle it. There are four main types defined for the exam:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/727/1*w1prT6nJRy_IigQ9AWuYfg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/1*GUXuK_wjbdJDAUZprXrozg.png" /></figure><h4>Broadcast Domains vs Collision Domains</h4><p>A broadcast domain is the network segment where a broadcast frame will be forwarded. Understanding the boundaries of these domains is essential for network design, VLAN configuration, and troubleshooting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*PGLD4v9-xv-dyYSrN6pPzg.png" /></figure><blockquote><strong>📝 EXAM TIP</strong> Routers break up broadcast domains. Switches break up collision domains but NOT broadcast domains. Adding a VLAN to a switch creates a new broadcast domain without a physical router. This is a very common exam scenario — know the distinction between Layer 2 and Layer 3 boundaries.</blockquote><h3>Chapter Summary &amp; Key Takeaways</h3><p>Chapter 4 covers the fundamental language that networks speak. Lock down these concepts before exam day:</p><ul><li>Ports are logical endpoints (0–65,535). Know the <strong>three ranges</strong>: Well-Known (0–1023), Registered (1024–49151), Ephemeral (49152–65535).</li><li>Memorize <strong>critical port</strong> mappings: 22 (SSH), 25 (SMTP), 53 (DNS), 67/68 (DHCP), 80 (HTTP), 143 (IMAP), 443 (HTTPS), 3389 (RDP).</li><li><strong>ICMP </strong>is a <strong>diagnostic</strong>/error protocol — ping and traceroute use it, but it carries no user data.</li><li>TCP is connection-oriented: <strong>three-way handshake</strong>, ordered delivery, acknowledgements, retransmission.</li><li>UDP is connectionless: <strong>no handshake</strong>, no guarantees, low overhead, fast. Protocol number 17. Use for VoIP, video, DNS.</li><li>GRE (protocol 47) creates tunnels by <strong>encapsulating protocols</strong> inside IP. No encryption — always pair with IPsec for security.</li><li>Traffic types: <strong>Unicast</strong> (1→1), <strong>Broadcast </strong>(1→all in subnet), <strong>Multicast</strong> (1→group), <strong>Anycast </strong>(1→nearest). Routers break <strong>broadcast domains</strong>; switches do not.</li></ul><blockquote><strong>STUDY STRATEGY</strong> Create flashcards for every port/protocol pair in this guide. The N10–009 gives you scenario-based questions — map each protocol to a real-world failure. For example: ‘User can receive but not send email’ points to SMTP (port 25/587). Context is everything.</blockquote><p>That’s Chapter 4 complete. These building blocks — how data is addressed, what rules govern its journey, and how traffic is classified — are the foundation for every other networking concept ahead.</p><p><em>Part of the Network+ N10–009 Series, </em><strong>Next up</strong>: <strong>Compare and Contrast Transmission Media and Transceivers</strong>. Stay tuned! 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c07f273b2c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 3- Network+ N10–009 Cloud Concepts & Connectivity Options]]></title>
            <link>https://hassen-hannachi.medium.com/day-3-network-n10-009-cloud-concepts-connectivity-options-aa8785463e49?source=rss-bd4a1e5ed7c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa8785463e49</guid>
            <category><![CDATA[comptia]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[comptia-certifications]]></category>
            <dc:creator><![CDATA[Hassen Hannachi ]]></dc:creator>
            <pubDate>Sun, 22 Mar 2026 02:32:15 GMT</pubDate>
            <atom:updated>2026-03-22T02:32:15.622Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4IB19LN84W08ljfxbAb-Zg.png" /></figure><p>If you are working toward your CompTIA Network+ certification, Chapter 3 is one of the most important you will encounter. Cloud computing has fundamentally reshaped how networks are designed, deployed, and secured. Understanding cloud concepts is no longer optional — it is a core competency expected of every modern network professional.</p><p>In this post we will walk through every exam objective in Chapter 3, from Network Function Virtualization (NFV) all the way to elasticity and multitenancy. Grab a coffee, open your notes app, and let us get into it.</p><h3>Section 1: Network Function Virtualization (NFV)</h3><p>Network Function Virtualization is the practice of replacing dedicated, physical network hardware with software running on general-purpose servers. Instead of buying a separate physical firewall, load balancer, and router, NFV lets you run all of those as software on commodity hardware. This dramatically reduces cost, increases flexibility, and speeds up deployment.</p><h4>Virtual Machines (VMs)</h4><p>A Virtual Machine is a software emulation of a complete physical computer. A hypervisor — software such as VMware ESXi, Microsoft Hyper-V, or KVM — sits on top of the physical hardware and carves out isolated environments, each acting as its own independent machine.</p><blockquote><strong>Key Insight: </strong><em>Each VM has its own virtualized CPU, RAM, storage, and network interface. Multiple VMs can share a single physical host without knowing about each other, which is the foundation of multitenancy.</em></blockquote><p>For the exam, remember the two hypervisor types:</p><ul><li><strong><em>Type 1 (Bare-Metal)</em></strong>: runs<strong> directly on hardware.</strong> Examples:<strong> VMware ESXi, Microsoft Hyper-V, Xen. </strong><em>Used in enterprise data centers</em><strong>.</strong></li><li><strong><em>Type 2 (Hosted)</em></strong>: runs on<strong> top of an existing OS. </strong>Examples<strong>: VirtualBox, VMware Workstation. </strong><em>Used on personal machines for testing</em><strong>.</strong></li></ul><blockquote><strong>Why it matters: </strong><em>NFV + orchestration is what makes cloud networking programmable. Instead of flying a technician to a remote site to rack new hardware, you push a config and the orchestrator spins up a new VNF in seconds.</em></blockquote><h4>Containers</h4><p>Containers are a lighter-weight alternative to VMs. While a VM emulates an entire computer (including its own OS kernel), a container shares the host OS kernel and packages only the application and its dependencies.</p><p>The most widely used container platform is Docker. Container orchestration at scale is handled by Kubernetes (K8s). Containers are faster to start, use less memory, and are more portable than VMs — but they provide slightly less isolation.</p><blockquote><strong>Exam Tip: </strong><em>Think of VMs as separate apartments in a building (each with its own kitchen), and containers as rooms in a shared house (one kitchen for everyone). VMs offer stronger isolation; containers offer speed and efficiency.</em></blockquote><h4>Virtual Appliances</h4><p>A virtual appliance is a pre-packaged VM image that includes both an OS and a specific network application — essentially a physical appliance converted to software. Examples include virtual firewalls, virtual routers, virtual load balancers, and virtual WAN accelerators.</p><p>Virtual appliances can be spun up in minutes, snapshotted, backed up, and cloned — capabilities impossible with dedicated physical hardware.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*Beh4cfeHn4NTiiCu_ftMGg.png" /></figure><h4>VNF, NFVi, and Orchestration &amp; Automation</h4><p>These three concepts form the NFV framework defined by ETSI (the European Telecommunications Standards Institute):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/1*k9CkU1kGwE6_h_zPX29MKA.png" /></figure><blockquote><strong>Why it matters: </strong><em>NFV + orchestration is what makes cloud networking programmable. Instead of flying a technician to a remote site to rack new hardware, you push a config and the orchestrator spins up a new VNF in seconds.</em></blockquote><h3>Section 2: Virtual Private Cloud (VPC)</h3><p>A Virtual Private Cloud is a logically isolated section of a public cloud provider’s network. You get the scalability of the public cloud with control similar to what you would have in your own private data center. Think of a VPC as your own walled-off neighborhood inside a shared city.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Sefln3L5vNnXa0IPLQTO4w.png" /></figure><h4>VPN and Public vs. Private Subnets</h4><p>Within a VPC, you segment your network using subnets — just like you would on a physical network. The two fundamental subnet types are:</p><ul><li><strong><em>Public Subnet</em></strong>: resources in a public subnet<strong> </strong>can be<strong> reached directly from the internet. </strong>They are assigned<strong> public IP addresses </strong>and<strong> sit behind </strong>an<strong> Internet Gateway. Web servers, reverse proxies, </strong>and <strong>bastion hosts </strong>typically<strong> live here.</strong></li><li><strong><em>Private Subnet</em></strong>: resources here have<strong> no direct internet exposure. Database servers, application tiers, </strong>and <strong>internal services belong here. Outbound internet </strong>access<strong> (</strong>for updates, etc<strong>.) is handled </strong>via a<strong> NAT Gateway.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/617/1*CsoV1jxAnKyPlQmrNOnQiQ.png" /></figure><p>A VPN (Virtual Private Network) extends secure connectivity between on-premises networks and your VPC. A site-to-site VPN uses IPsec to encrypt traffic over the public internet, creating a private tunnel between your corporate network and your cloud environment.</p><blockquote><strong>Exam Tip: </strong><em>Public subnet = Internet Gateway (IGW) in route table. Private subnet = NAT Gateway (or NAT instance) in route table. Know the difference — it comes up often.</em></blockquote><h4>Network Security Groups (NSGs)</h4><p>Network Security Groups are <strong><em>stateful virtual firewalls</em></strong> that control inbound and outbound traffic at the resource level (typically at the VM/instance or NIC level). Rules are evaluated based on priority — lower numbers are evaluated first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/575/1*PW2tWzqqWX4Ac86o_-6rmg.png" /></figure><p>Key NSG characteristics:</p><ul><li><strong><em>Stateful</em></strong>: if you allow inbound traffic on port 443, the return traffic is automatically allowed regardless of outbound rules<strong>.</strong></li><li><strong><em>Applied to</em></strong>: individual VMs, network interfaces, or subnets (depending on the cloud provider)<strong>.</strong></li><li><strong><em>Rule components</em></strong>: source/destination IP or CIDR<strong>, </strong>port or port range<strong>, </strong>protocol (TCP/UDP/ICMP), and Allow/Deny action<strong>.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*1mZTYXDFljL-Jl6nSbE0AQ.png" /></figure><h4>Network Security Lists (NSLs)</h4><p>Network Security Lists (called Security Lists in Oracle Cloud Infrastructure’s (OCI), or Network ACLs in AWS) are <strong><em>stateless subnet-level</em></strong> <strong><em>firewall </em></strong>rules. Unlike NSGs, they apply to all traffic entering or leaving a subnet, and you must explicitly allow both inbound AND outbound traffic for a connection to work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/592/1*rOgq2xu9v7OJG4bnlxuiiA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/1*iawcjaa38Aamro5i9j6wBw.png" /></figure><blockquote><strong>Memory Aid: </strong><em>NSGs = smart (stateful, resource-level). NSLs = strict (stateless, subnet-level). Use both together for defense in depth.</em></blockquote><h4>Cloud Gateways</h4><p>Gateways are the on/off ramps for cloud network traffic. The two most important for the exam are:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/615/1*-ALPEAf9L0H_bPCq__Cg4g.png" /></figure><ul><li><strong><em>Internet Gateway (IGW): </em></strong>An Internet Gateway is a horizontally scaled, redundant, and highly available VPC component that enables communication between your VPC and the internet. Resources in a public subnet use it for both inbound and outbound internet traffic. One IGW per VPC.</li><li><strong><em>NAT Gateway (Network Address Translation Gateway): </em></strong>A NAT Gateway allows instances in a private subnet to initiate outbound connections to the internet (for software updates, API calls, etc.) while preventing the internet from initiating inbound connections to those instances. The NAT Gateway lives in a public subnet and translates private IPs to a public IP for outbound traffic.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/1*womE6adjmhtR2iCii6cmMA.png" /></figure><p>Other gateways you may encounter:</p><ul><li>Virtual Private Gateway (VGW): the <strong>VPC side </strong>of a<strong> VPN </strong>or<strong> Direct Connect connection.</strong></li><li>Transit Gateway: a hub that<strong> connects multiple VPCs </strong>and<strong> on-premises networks, </strong>simplifying<strong> large-scale </strong>architectures<strong>.</strong></li><li>Storage Gateway: <strong>connects on-premises </strong>environments<strong> to cloud storage services.</strong></li></ul><h4>Cloud Connectivity Options</h4><p>How do you connect your on-premises network to your cloud VPC? There are two primary options:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/1*9HX-e2M8C5kJvPe63RRz3A.png" /></figure><ul><li><strong><em>VPN (Virtual Private Network): </em></strong>A site-to-site VPN uses IPsec encryption to send traffic securely over the public internet. It is easy to set up and cost-effective, but performance varies with internet conditions. Best for: small workloads, disaster recovery, getting started quickly.</li><li><strong><em>Direct Connect / ExpressRoute / Cloud Interconnect: </em></strong><em>Direct Connect</em> (AWS), <em>ExpressRoute </em>(Azure), and <em>Cloud Interconnect</em> (GCP) are dedicated private network connections from your premises to the cloud provider’s network — bypassing the public internet entirely. They offer lower latency, more consistent bandwidth, and higher security.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/1*FkZXox6eEF5w2yUoJG1xVA.png" /></figure><blockquote><strong>Exam Tip: </strong><em>If a question describes a company needing guaranteed bandwidth and low latency to the cloud, the answer is Direct Connect (or its equivalent). If </em><strong>cost is the priority</strong><em> and performance variability is acceptable, VPN is the answer.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*5Ohw5cGy8LIDFHt6S24hJg.png" /></figure><h3>Section 3: Cloud Deployment Models</h3><p>Not all clouds are built the same way. The four deployment models describe who owns, manages, and has access to the cloud infrastructure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/633/1*md3E9hXLrWpEi_KCEvB0fg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/1*8g7DxKrPSrXwlds59Bu1MQ.png" /></figure><blockquote><strong>Exam Tip: </strong><em>Community cloud is the least common deployment model and often the answer people forget. Remember: it is shared, but only within a specific community with shared requirements — not open to the general public.</em></blockquote><h3>Section 4: Cloud Service Models</h3><p>Cloud service models define what the provider manages versus what you are responsible for. This is often illustrated with the “shared responsibility model.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*lcidYFDTkRGV0Nv9p-DlEA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/1*2rIBLrjWSQOvGSVFr_USLw.png" /></figure><blockquote><strong>Memory Aid: </strong><em>IaaS = you manage from the OS up. PaaS = you manage your app and data. SaaS = you manage nothing except your data and user settings.</em></blockquote><p>A helpful way to remember the responsibility layers:</p><ul><li>On-Premises: <strong>you manage everything — hardware to application.</strong></li><li>IaaS: <strong>provider manages hardware; you manage OS upward.</strong></li><li>PaaS: <strong>provider manages hardware + OS + platform; you manage app + data.</strong></li><li>SaaS: <strong>provider manages everything; you just use it.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*Uwp41PqWRg0lCgqMyyQYhw.png" /></figure><h3>Section 5: Scalability, Elasticity, and Multitenancy</h3><p>These three concepts are fundamental to understanding why cloud computing is so powerful — and they are guaranteed exam topics.</p><h4>Scalability</h4><p>Scalability is the ability of a system to handle increased load by adding resources. There are two types:</p><ul><li>Vertical Scaling (Scale Up): <strong>adding more resources (CPU, RAM, storage) to an existing machine. Limited by the maximum size of a single server.</strong></li><li>Horizontal Scaling (Scale Out): <strong>adding more machines to distribute the load. Theoretically unlimited, and the preferred model in cloud architectures.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*livmv7kG4auzIbdO6vxjtQ.png" /></figure><blockquote><strong>Key Distinction: </strong><em>Scalability is about the capability to scale. It does not mean it happens automatically. You can have a scalable architecture that still requires a human to trigger the scaling.</em></blockquote><h4>Elasticity</h4><p>Elasticity is the ability of a system to automatically scale resources up and down in response to demand — and then scale back when demand decreases, releasing unused resources to avoid waste.</p><p>Elasticity is what makes cloud computing cost-efficient. You pay for what you use. Traffic spike at midnight? The system adds servers. Spike ends? Servers are terminated automatically.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/652/1*-OE5tzpFL0Y3941vOUW3Qw.png" /></figure><blockquote><strong>Elasticity vs. Scalability: </strong><em>Scalability is the ability to grow. Elasticity is the ability to grow AND shrink automatically. Elasticity requires scalability, but scalability does not require elasticity.</em></blockquote><h4>Multitenancy</h4><p>Multitenancy means multiple customers (tenants) share the same physical infrastructure and software platform, but their data and environments are logically isolated from each other. This is the foundation of public cloud economics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*A-KzqnOh_S4sl6Nguia5bQ.png" /></figure><p>Providers implement multitenancy through:</p><ul><li>Hypervisor isolation: <strong>VMs on the same physical host are completely separated.</strong></li><li>Network segmentation: <strong>VPCs, VLANs, and security groups ensure traffic from one tenant never reaches another.</strong></li><li>Logical data isolation: <strong>databases and storage systems use tenant IDs to ensure data separation.</strong></li></ul><blockquote><strong>Security Note: </strong><em>Multitenancy introduces a risk called the “noisy neighbor” problem — one tenant consuming excessive resources can impact others. Cloud providers mitigate this with resource quotas, rate limiting, and dedicated instance options.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/619/1*Futtn6jWK0v3Ps-Mb6OTzA.png" /></figure><h3>Chapter 3 Quick-Reference Cheat Sheet</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*ESl4EyFo7vpJ1eTUfXzgLQ.png" /></figure><h3>Final Thoughts</h3><p>Chapter 3 covers a lot of ground, but the concepts are deeply interconnected. NFV gave us the ability to run network functions in software. The cloud gave us the infrastructure to run that software at scale. VPCs, subnets, NSGs, and gateways give us the control to do it securely. And deployment models, service models, scalability, elasticity, and multitenancy define the economic and operational model that makes it all worthwhile.</p><p>As you study, focus on the relationships between concepts — not just individual definitions. The Network+ exam loves scenario-based questions, so ask yourself: what would I choose in this situation, and why?</p><p>Good luck on your exam journey. If this post helped you, share it and leave a comment below with any questions. We are all learning together.</p><p><em>Part of the Network+ N10–009 Series, </em>Next up: <strong>Network Ports, Protocols and Services</strong>. Stay tuned! 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa8785463e49" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 2- Network+ N10–009 Networking Appliances, Applications, and Functions]]></title>
            <link>https://hassen-hannachi.medium.com/day-2-network-n10-009-networking-appliances-applications-and-functions-30d353db61b1?source=rss-bd4a1e5ed7c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/30d353db61b1</guid>
            <category><![CDATA[comptia-certifications]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[comptia]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Hassen Hannachi ]]></dc:creator>
            <pubDate>Wed, 18 Mar 2026 22:56:11 GMT</pubDate>
            <atom:updated>2026-03-18T22:56:11.348Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FLypbsybUHHdZOMMnasXhg.png" /></figure><h3>Introduction</h3><p>Welcome back to my Network+ study series! Chapter 2 of the N10–009 exam is one of the most hardware-heavy sections you will encounter. It covers the core devices and software constructs that make modern networks tick — from hubs and routers to firewalls, load balancers, CDNs, and quality-of-service mechanisms.</p><p>This post breaks down every exam objective in the chapter so you can read it, understand it, and walk into the exam with confidence. Let’s get into it.</p><h3>1. Physical &amp; Virtual Appliances</h3><p>Network appliances are dedicated hardware devices or software instances (virtual appliances) that perform specific networking functions. Understanding the difference between physical and virtual is key: a physical appliance is standalone hardware, while a virtual appliance runs as a software instance — often on a hypervisor — providing the same function with greater flexibility and scalability.</p><h3>Hub</h3><p>A hub connects multiple devices within a LAN and operates at <strong><em>Layer 1 (Physical Layer)</em></strong> of the OSI model. Unlike a switch, a hub has no intelligence — it simply receives a signal on one port and broadcasts it out to every other port, regardless of the intended destination.</p><ul><li><strong>Layer:</strong> Layer 1 — Physical Layer.</li><li><strong>Behavior:</strong> Broadcasts all incoming data to every connected device. Every device receives the frame and must decide whether to process it or discard it.</li><li><strong>Collision domain:</strong> All devices connected to a hub share a single collision domain. Only one device can transmit at a time without causing a collision.</li><li><strong>Half-duplex only:</strong> Hubs are inherently half-duplex devices.</li><li><strong>Status today:</strong> Hubs are largely obsolete, replaced by switches. They still appear on certification exams because they illustrate foundational networking concepts.</li></ul><p><strong>Real-world note: </strong>Because hubs broadcast to all ports, they are a security risk — any device on the hub can capture all traffic using a packet sniffer. This is one key reason switches replaced hubs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/579/1*n5PhFP9azgwHVb7lrHgDug.png" /></figure><p><strong><em>CSMA/CD</em></strong> is the reason hubs are inefficient at scale. As more devices are added to a hub, collisions increase and performance degrades. Switches eliminate this problem by giving each device its own dedicated collision domain.</p><blockquote><strong>Exam Tip: </strong>CSMA/CD is used in wired Ethernet with hubs. Wireless networks use CSMA/CA (Collision Avoidance) instead — because you cannot detect a collision mid-transmission over radio waves.</blockquote><h3>Switch</h3><p>A switch connects devices within the same network (LAN) and forwards frames based on MAC addresses. It operates primarily at <strong><em>Layer 2</em></strong> (<strong><em>Data Link Layer</em></strong>), though <strong><em>Layer 3 switches</em></strong> can also perform routing functions. Unlike a hub, each port on a switch is its own collision domain, enabling full-duplex communication and dramatically improving network performance.</p><h4>MAC Address Table</h4><p>The MAC address table (also called the <strong><em>CAM table</em></strong> — Content Addressable Memory) is the intelligence that makes a switch far more efficient than a hub.</p><p><strong>Security note: </strong>A MAC flooding attack overwhelms the MAC address table with fake entries, forcing the switch into hub-like behavior (flooding all traffic). This allows an attacker to capture traffic using a sniffer. Port security limits the number of MAC addresses per port to mitigate this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/742/1*TJaeKDx2Gkm-T5MGPgWF-w.png" /></figure><blockquote><strong>Exam Tip: </strong>Know the three actions a switch takes: Learn (record source MAC), Forward (send to known destination port), Flood (send to all ports when destination is unknown). Also know that the CAM table maps MAC addresses to port numbers.</blockquote><h4>Switch Types</h4><ul><li><strong>Managed switch:</strong> Configurable via CLI or web interface. Supports VLANs, QoS, port mirroring, spanning tree, and SNMP. Used in enterprise environments.</li><li><strong>Unmanaged switch:</strong> Plug-and-play, no configuration options. Suitable for small offices or home networks.</li><li><strong>Layer 3 switch:</strong> Combines switching and routing — can route between VLANs without a dedicated router. Used in large enterprise environments.</li><li><strong>Fixed-configuration switch:</strong> Has a set number of ports that cannot be changed. All ports are built into the device chassis. Examples: 24-port or 48-port access switches. Cost-effective and simple.</li><li><strong>Use case:</strong> Standard access layer deployments where the port count is predictable.</li><li><strong>Modular switch:</strong> The chassis has slots that accept interchangeable line cards, uplink modules, or power supplies. Port count and type can be customized and expanded.</li></ul><p><strong>Use case:</strong> Enterprise core and distribution layers where flexibility and scalability are required. You can add 10G, 40G, or 100G uplink modules as needs grow.</p><ul><li><strong>Examples:</strong> Cisco Catalyst 9400 series, Cisco Nexus 9500 series.</li></ul><blockquote><strong>Fixed vs Modular: </strong>Fixed switches are cheaper and simpler — great for the access layer. Modular switches are more expensive but allow you to swap line cards, add redundant power supplies, and scale without replacing the entire chassis.</blockquote><h4>PoE — Power over Ethernet</h4><p>Power over Ethernet (PoE) allows a switch to deliver electrical power to connected devices over standard Ethernet cabling, eliminating the need for separate power supplies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*qfq22B3TqEL5hwRf8gPsZw.png" /></figure><blockquote><strong>Exam Tip: </strong>Know the three PoE standards and their wattage. 802.3af = 15.4 W, 802.3at (PoE+) = 30 W, 802.3bt (PoE++) = 60/100 W. A device requiring PoE+ will not function correctly on a switch that only supports 802.3af.</blockquote><h3>Router</h3><p>A router is the device responsible for forwarding data packets between different networks. It operates at Layer 3 (Network Layer) of the OSI model and uses IP addresses to make forwarding decisions based on a routing table — a database that lists known networks, the next-hop address to reach them, and the metric (cost) of each path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*gP4y5LqHcpWsUFIN342yrQ.png" /></figure><p>• <strong>Key function:</strong> Connect separate networks (e.g., your LAN to the internet).</p><p>• <strong>Physical vs. virtual:</strong> Hardware routers are common in enterprises; virtual routers run in cloud environments such as AWS VPC routing.</p><blockquote><strong>Exam Tip: </strong>The exam may ask which OSI layer a router operates on. The answer is Layer 3 — Network Layer.</blockquote><h4>Static Routes</h4><p>A static route is a manually configured entry in the routing table. An administrator explicitly tells the router: to reach network X, send packets to next-hop Y.</p><p>Example<strong>: <em>ip route 192.168.10.0 255.255.255.0 10.0.0.1 </em></strong>— This tells the router: to reach the 192.168.10.0/24 network, forward packets to next-hop 10.0.0.1.</p><h4>Dynamic Routing</h4><p>Dynamic routing uses routing protocols that allow routers to automatically discover networks, share routing information with neighbors, and adapt to changes in the topology — such as link failures or new networks being added.</p><p>Dynamic routing protocols fall into two main categories:</p><ul><li><strong>Interior Gateway Protocols (IGPs):</strong> Used within a single organization’s network (an Autonomous System). Examples: OSPF, EIGRP, RIP.</li><li><strong>Exterior Gateway Protocols (EGPs):</strong> Used between different organizations or ISPs on the internet. BGP (Border Gateway Protocol) is the only EGP in widespread use today — it is the routing protocol that runs the internet.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*BbHGFkmwN9N6vlHyykyobA.png" /></figure><p><strong>Static vs Dynamic: </strong>Static routes give you full control and zero overhead but require manual updates. Dynamic routing protocols handle changes automatically and scale to large networks but add complexity. Most real-world networks use both — dynamic routing for internal paths, static default routes toward the internet.</p><blockquote><strong>Exam Tip: </strong>Know the four main routing protocols, their types, and metrics. Also understand Administrative Distance — if a router learns a route from both OSPF (AD 110) and RIP (AD 120), it will always prefer the OSPF route because lower AD wins.</blockquote><h3>Firewall</h3><p>A firewall monitors and controls incoming and outgoing network traffic based on predetermined security rules. It acts as a barrier between trusted internal networks and untrusted external ones. Firewalls come in many forms — the key differences are which OSI layer they inspect traffic at, and how much they understand about the content of that traffic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/745/1*tkl0-qTQ8C68sUPR0VoMvQ.png" /></figure><h4>Layer 4 Firewall — Transport Layer Firewall</h4><p>A Layer 4 firewall (also called a transport layer firewall or circuit-level gateway) makes filtering decisions based on TCP and UDP information — specifically source/destination IP addresses, source/destination port numbers, and TCP connection state</p><p><strong>Example: </strong>A Layer 4 firewall rule: permit TCP from any to 203.0.113.5 port 443. This allows HTTPS traffic to the web server but blocks all other ports. It does not care what is inside the HTTPS request.</p><blockquote><strong>Exam Tip: </strong>Layer 4 firewalls operate on IP + TCP/UDP headers. They understand connection state (stateful) but cannot inspect application-layer content. Fast but limited visibility.</blockquote><h4>Layer 7 Firewall — Application Layer Firewall</h4><p>A Layer 7 firewall (also called an application-layer firewall or next-generation firewall / NGFW) inspects traffic all the way up to the application layer. It can read, understand, and make decisions based on the actual content of network traffic — not just the port number it is using.</p><p><strong>Layer 4 vs Layer 7: </strong>A Layer 4 firewall sees a connection to port 80 and calls it HTTP — it allows or blocks based on port alone. A Layer 7 firewall reads the actual HTTP request and can block a specific URL, detect a SQL injection attempt in a POST body, or identify that the traffic is actually a tunneled VPN application despite using port 80.</p><blockquote><strong>Exam Tip: </strong>Layer 7 / NGFW firewalls use deep packet inspection to see inside application traffic. They can identify applications by behavior, not just port. SSL inspection allows them to see inside encrypted traffic. The trade-off is higher processing overhead.</blockquote><h4>Network Firewall</h4><p>A network firewall is a traditional perimeter security device deployed at the boundary between network segments — most commonly between the internal network (LAN) and the internet (WAN). It is the foundational firewall type that most people think of when they hear the word ‘firewall.’</p><p><strong>DMZ example: </strong>A company’s web server sits in the DMZ. The network firewall allows inbound HTTP/HTTPS from the internet to the DMZ web server, but blocks all direct traffic from the internet to the internal LAN. If the web server is compromised, the attacker is contained in the DMZ and cannot directly reach internal systems.</p><blockquote><strong>Exam Tip: </strong>Know the DMZ concept — it is a buffer zone for public-facing services. The network firewall enforces policy between the internet, DMZ, and internal LAN as separate zones with different trust levels.</blockquote><h4>WAF — Web Application Firewall</h4><p>A Web Application Firewall (WAF) is a specialized security appliance or service that sits in front of web applications and filters HTTP/HTTPS traffic specifically to protect against web application attacks. While a network firewall protects the network perimeter, a WAF protects the application itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/756/1*LLRSY12efkpGp4P6MyCUGg.png" /></figure><p><strong>WAF vs Network Firewall: </strong>A network firewall blocks traffic at the IP/port level — it would allow all HTTPS traffic to your web server on port 443 because the port is legitimate. A WAF inspects the content of those HTTPS requests and blocks the one containing ‘SELECT * FROM users WHERE 1=1’ — a SQL injection attempt. Both layers are needed for comprehensive security.</p><blockquote><strong>Exam Tip: </strong>A WAF operates at Layer 7 and is specifically designed to protect web applications from application-layer attacks like SQL injection and XSS. It is not a replacement for a network firewall — they complement each other. The exam may ask which device would detect and block a SQL injection attempt: the answer is a WAF.</blockquote><h3>UTM — Unified Threat Management</h3><p>A Unified Threat Management (UTM) appliance is an all-in-one security device that combines multiple security functions into a single platform. Instead of deploying separate boxes for firewall, IPS, antivirus, VPN, and web filtering, a UTM consolidates all of these into one appliance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*ITTdoldWY0Isp0apfl1aog.png" /></figure><p><strong>UTM vs NGFW: </strong>UTM and NGFW are often confused. UTM is a term more commonly used in the SMB space and emphasizes the all-in-one bundling of security services. NGFW is typically a higher-performance appliance with advanced application identification and threat intelligence, used in enterprise environments. In practice, the line between the two has blurred — many modern NGFWs include UTM-like features and many UTMs have evolved to include NGFW capabilities.</p><blockquote><strong>Exam Tip: </strong>UTM = one box, many security functions. The exam may present a scenario where a small business needs firewall, IPS, antivirus, and VPN without multiple devices — the answer is a UTM. Know that the trade-off is potential performance impact when all features are enabled simultaneously.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/834/1*BNLius15Jj5BA-YaEmAilQ.png" /></figure><h3>IDS / IPS</h3><p>Intrusion Detection Systems (IDS) and Intrusion Prevention Systems (IPS) are security appliances that monitor network traffic for malicious activity.</p><ul><li><strong>IDS (Intrusion Detection System):</strong> Passively monitors and alerts — it detects but does not block.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*gujSH79aubVB03yDNxyPWw.png" /></figure><ul><li><strong>IPS (Intrusion Prevention System):</strong> Actively monitors and blocks malicious traffic in real time.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/739/1*_ph5KKyd_g7qxbK2PwUJCw.png" /></figure><ul><li><strong>Placement:</strong> IDS can be out-of-band; IPS must be inline with traffic.</li><li><strong>Detection methods:</strong> Signature-based (known threats), anomaly-based (behavioral), and policy-based.</li></ul><blockquote><strong>Memory trick: </strong>Think of IDS as a burglar alarm and IPS as a security guard. The alarm tells you something happened; the guard stops it.</blockquote><h3>Load Balancer</h3><p>A load balancer distributes incoming network traffic across multiple servers to ensure no single server is overwhelmed, improving availability and reliability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/745/1*Z9K9y3oF0OZ2xsQgmy4mdA.png" /></figure><ul><li><strong>Hardware load balancer:</strong> Dedicated appliance, high performance.</li><li><strong>Software/virtual load balancer:</strong> Runs as software (e.g., HAProxy, NGINX, AWS ELB).</li><li><strong>Algorithms:</strong> Round-robin, least connections, IP hash, weighted distribution.</li><li><strong>Layer 4 vs Layer 7:</strong> L4 balances based on IP/port; L7 balances based on application content (HTTP headers, URLs).</li></ul><blockquote><strong>Exam Tip: </strong>Layer 7 load balancers can make smarter routing decisions because they understand application-level content.</blockquote><h3>Proxy</h3><p>A proxy server acts as an intermediary between a client and a destination server, forwarding requests on the client’s behalf.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*QMHxQtV6OtPurN1VJGrGyg.png" /></figure><ul><li><strong>Forward proxy:</strong> Client-side proxy. Hides the client’s identity from the internet. Used for content filtering and caching.</li><li><strong>Reverse proxy:</strong> Server-side proxy. Sits in front of web servers and hides backend infrastructure. Used for load balancing and SSL termination.</li><li><strong>Transparent proxy:</strong> Intercepts traffic without client configuration, often used by ISPs or corporate networks.</li></ul><blockquote><strong>Security use: </strong>Forward proxies are often used in corporate environments to filter web content and log employee browsing activity.</blockquote><p>A proxy server has three main function:</p><ul><li><strong>URL Filtering</strong>: is the process of inspecting the web address (URL) in a client’s HTTP/HTTPS request and deciding whether to allow or block it based on a defined policy.</li></ul><p><strong>Real-world example: </strong>A school deploys a proxy with URL filtering. Students attempting to visit gaming or adult content sites receive a block page. The proxy logs every request, giving administrators a full audit trail of browsing activity across the network.</p><blockquote><strong>Exam Tip: </strong>URL filtering checks the web address of requests — the WHERE. HTTPS traffic requires SSL inspection to filter beyond the domain name. The proxy is the enforcement point; all client traffic must route through it for filtering to be effective.</blockquote><ul><li>Content Filtering: goes deeper than URL filtering — instead of just checking the web address, it inspects the actual content of web pages, files, and data transfers to detect and block harmful or inappropriate material.</li></ul><p><strong>URL vs Content filtering: </strong>URL filtering decides whether to allow the connection based on the address. Content filtering decides whether to allow the data based on what is inside the response. A URL may be on an allowlist, but content filtering can still block a specific download from that site if it contains malware or prohibited file types.</p><blockquote><strong>Exam Tip: </strong>Content filtering inspects the payload — the WHAT inside the traffic, not just where it is going. This is a Layer 7 function. Combined with URL filtering it gives organizations comprehensive control over what enters and leaves the network through web traffic.</blockquote><ul><li>Web Page Caching: is the process of storing copies of frequently requested web content on the proxy server itself so that subsequent requests for the same content can be served locally — without going back out to the internet.</li></ul><p><strong>Real-world example: </strong>A company with 500 employees all visiting the same news site each morning. Without caching, the proxy makes 500 separate requests to the news server. With caching, the first request retrieves and stores the page; the remaining 499 are served from local cache — consuming no additional internet bandwidth.</p><blockquote><strong>Exam Tip: </strong>Web page caching reduces bandwidth and improves response times by serving content locally from the proxy. Know that HTTPS traffic cannot be cached without SSL inspection, and that cache freshness is governed by HTTP headers from the origin server.</blockquote><p><strong>Three Core Proxy Functions — Summary: </strong>URL Filtering = control <strong><em>WHERE</em></strong> users go (block by address or category). Content Filtering = control <strong><em>WHAT</em></strong> comes through (block by payload, file type, or keywords). Web Page Caching = <strong><em>save bandwidth</em></strong> and <strong><em>speed up</em></strong> browsing by storing content locally. All three work together to make the proxy a powerful network control and optimization point.</p><h3>NAS — Network Attached Storage</h3><p>NAS is a dedicated file storage device connected to a network that allows multiple clients to access data simultaneously over standard network protocols.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/657/1*3rSiEtlDQexncZZASEQvVg.png" /></figure><ul><li><strong>Protocols used:</strong> NFS (Unix/Linux), SMB/CIFS (Windows), AFP (Apple).</li><li><strong>Use case:</strong> Centralized file storage for homes, small businesses, and enterprises.</li><li><strong>Access:</strong> File-level access — clients access specific files and folders.</li></ul><h3>SAN — Storage Area Network</h3><p>A SAN is a high-speed network dedicated entirely to storage, connecting servers to storage devices at the block level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/684/1*fg3n5w_oiS9E-GyJUdiE8w.png" /></figure><ul><li><strong>Protocols:</strong> Fibre Channel (FC), iSCSI, FCoE (Fibre Channel over Ethernet).</li><li><strong>Use case:</strong> Databases, virtual machine storage, enterprise workloads requiring high IOPS.</li><li><strong>Access:</strong> Block-level access — the OS treats the storage as a local disk.</li></ul><p><strong>NAS vs SAN: </strong>NAS = file-level, easier to set up, cheaper. SAN = block-level, faster, more expensive, typically used in enterprise data centers.</p><blockquote><strong>Exam Tip: </strong>NAS uses file-level protocols (SMB, NFS); SAN uses block-level protocols (iSCSI, Fibre Channel).</blockquote><h3>Wireless — Access Points &amp; Controllers</h3><p>Wireless networking components include Access Points (APs) and Wireless LAN Controllers (WLCs).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*oJq_GS2pvROZRlnugQBTYw.png" /></figure><ul><li><strong>Wireless Access Point (WAP/AP):</strong> Connects wireless clients to the wired network. Operates at Layer 2.</li><li><strong>Autonomous AP:</strong> Self-contained, independently managed. Suitable for small deployments.</li><li><strong>Lightweight AP (LWAP):</strong> Managed centrally by a Wireless LAN Controller (WLC). Used in enterprise deployments.</li><li><strong>Wireless LAN Controller (WLC):</strong> Central management of multiple APs — handles roaming, channel assignment, load balancing, and security policies.</li></ul><p><strong>Enterprise insight: </strong>In large campuses or office buildings, WLCs enable seamless roaming as users move between APs without dropping their connection.</p><h3>2. Applications</h3><h4>Content Delivery Network (CDN)</h4><p>A Content Delivery Network (CDN) is a geographically distributed system of servers that delivers web content and media to users based on their geographic location, the origin of the content, and a content delivery server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*8wPclMafpeHWw1r_mAgI6A.png" /></figure><p>Instead of serving all requests from a single origin server, a CDN caches content at edge servers worldwide, dramatically reducing latency.</p><ul><li><strong>How it works:</strong> When a user requests content, the CDN routes the request to the nearest edge server. If the edge server has a cached copy, it serves it directly. If not, it fetches from the origin and caches it.</li><li><strong>Benefits:</strong> Reduced latency, improved load times, DDoS mitigation, and reduced bandwidth costs for origin servers.</li><li><strong>Examples:</strong> Cloudflare, Akamai, Amazon CloudFront, Fastly.</li></ul><blockquote><strong>Exam Tip: </strong>CDNs reduce latency by caching content closer to the end user. The exam may test your understanding of why CDNs improve performance for global users.</blockquote><h3>3. Functions</h3><h4>VPN — Virtual Private Network</h4><p>A VPN creates an encrypted tunnel over a public network (such as the internet) to securely connect remote users or sites to a private network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/756/1*FQWaeJ7_yUJItOGAul5oMQ.png" /></figure><ul><li><strong>Remote access VPN:</strong> Allows individual users to connect to the corporate network remotely.</li><li><strong>Site-to-site VPN:</strong> Connects two entire networks together (e.g., two office locations).</li><li><strong>Protocols:</strong> IPSec, SSL/TLS, OpenVPN, WireGuard, L2TP/IPSec.</li><li><strong>Split tunneling:</strong> Only traffic destined for the corporate network goes through the VPN.</li><li><strong>Full tunneling:</strong> All traffic is routed through the VPN for maximum security.</li></ul><p><strong>Security note: </strong>IPSec operates at Layer 3 and is commonly used for site-to-site VPNs. SSL VPNs operate at Layer 7 and are more commonly used for remote access because they work through standard HTTPS.</p><blockquote><strong>Exam Tip: </strong>Know the difference between remote access VPN and site-to-site VPN, and be familiar with IPSec vs SSL VPN.</blockquote><h4>QoS — Quality of Service</h4><p>QoS refers to the set of techniques used to manage network resources and ensure that critical applications receive the bandwidth, latency, and reliability they need — especially when the network is congested.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/1*xB33VGVHRieWipyX_ihtfg.png" /></figure><ul><li><strong>Traffic prioritization:</strong> High-priority traffic (VoIP, video conferencing) is given preference over less critical traffic.</li><li><strong>Traffic shaping:</strong> Limits bandwidth for certain applications or users to prevent congestion.</li><li><strong>Traffic policing:</strong> Drops packets that exceed a defined rate threshold.</li><li><strong>DSCP (Differentiated Services Code Point):</strong> Classifies and marks network traffic so routers and switches can apply appropriate QoS policies.</li><li><strong>CoS (Class of Service):</strong> Similar to DSCP but used at Layer 2 via 802.1p.</li></ul><p><strong>Real-world example: </strong>In a hospital network, VoIP calls and real-time patient monitoring data would be given the highest QoS priority, while streaming video on staff devices would be deprioritized.</p><blockquote><strong>Exam Tip: </strong>QoS is especially important for real-time applications like VoIP and video. The exam may ask which type of traffic benefits most — the answer is latency-sensitive, real-time traffic.</blockquote><h4>TTL — Time to Live</h4><p>TTL is a value in an IP packet header that specifies the maximum number of hops (routers) a packet can traverse before being discarded. Its purpose is to prevent packets from circulating indefinitely in routing loops.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/513/1*4KAWdRxjVMjQyBS3GISfKQ.png" /></figure><ul><li><strong>How it works:</strong> Each router decrements the TTL by 1. When it reaches 0, the router discards the packet and sends an ICMP Time Exceeded message back to the sender.</li><li><strong>Default values:</strong> Windows = TTL 128; Linux/Unix = TTL 64; Cisco routers = TTL 255.</li><li><strong>TTL in DNS:</strong> Specifies how long a resolver should cache a DNS record before requesting a fresh copy.</li><li><strong>TTL in traceroute:</strong> Traceroute deliberately exploits TTL — it sends packets with incrementally increasing TTL values to map each hop along the route.</li></ul><p><strong>Troubleshooting tip: </strong>When running ping, you can infer the OS of the remote host based on the TTL you receive. A response near 128 suggests Windows; near 64 suggests Linux.</p><blockquote><strong>Exam Tip: </strong>Understand TTL in both contexts: IP packets (preventing routing loops) and DNS (controlling cache duration).</blockquote><h3>Tunneling</h3><p>Tunneling is the process of encapsulating one network protocol inside another, creating a logical channel — the tunnel — that carries traffic across a network that might not natively support it. A tunneling protocol wraps the original packet (the payload) in a new packet with its own headers, which are used to route and deliver it across the transit network. When the packet reaches the other end of the tunnel, the outer wrapper is stripped and the original packet is delivered.</p><p>Tunneling is the foundational mechanism that makes VPNs possible. The two dominant tunneling protocol suites you must know for the Network+ exam are TLS and IPSec.</p><h4>TLS Tunneling — Transport Layer Security</h4><p>TLS (Transport Layer Security) is the successor to SSL and operates at Layer 5–7 of the OSI model. It provides encryption, authentication, and data integrity for application-layer traffic. When used as a VPN tunneling protocol, TLS wraps network traffic inside an encrypted HTTPS session, making it appear as ordinary web traffic to firewalls and NAT devices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/695/1*al5CuZ3m7FAnwkvdFI4kKA.png" /></figure><p><strong>TLS vs SSL: </strong>SSL (Secure Sockets Layer) is the older, deprecated predecessor to TLS. SSL 2.0 and 3.0 are considered broken and insecure. TLS 1.2 and TLS 1.3 are the current secure versions. The term ‘SSL VPN’ persists in the industry even though TLS is the actual protocol in use today. On the exam, treat SSL VPN and TLS VPN as the same concept.</p><blockquote><strong>Exam Tip: </strong>TLS tunneling = SSL VPN = runs over port 443 = firewall-friendly. Commonly used for remote access VPNs. The TLS handshake establishes a session key using asymmetric cryptography, then all data is encrypted with symmetric keys. Know TLS 1.2 and 1.3 are current; SSL is deprecated and insecure.</blockquote><h4>IPSec — IP Security</h4><p>IPSec is a suite of protocols that operates at Layer 3 (Network Layer) to provide authentication, integrity, and encryption for IP packets. Unlike TLS which protects a single application connection, IPSec protects all traffic between two endpoints at the IP layer — making it the standard protocol for site-to-site VPNs and many enterprise remote access deployments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/656/1*wfKx9SIDyIj7RF5M7FNCIA.png" /></figure><p>IPSec is not a single protocol — it is a framework composed of several components that work together. The three most important to know are AH, ESP, and IKE.</p><h4>AH — Authentication Header</h4><p>The Authentication Header (AH) is an IPSec protocol that provides data integrity and authentication for IP packets, but does NOT provide encryption. AH ensures that a packet has not been tampered with in transit and that it genuinely originated from the claimed sender, but the data itself remains readable.</p><p><strong>AH in practice: </strong>Because AH provides no encryption and is incompatible with NAT, it is rarely used alone in modern deployments. It is more commonly combined with ESP, or replaced entirely by ESP with authentication enabled. However, AH remains an exam topic because it tests your understanding of the distinction between integrity and confidentiality.</p><blockquote><strong>Exam Tip: </strong>AH = authentication and integrity only, NO encryption. Protocol 51. Incompatible with NAT because it hashes the IP header. If a question asks which IPSec protocol provides confidentiality, the answer is ESP, not AH.</blockquote><h4>ESP — Encapsulating Security Payload</h4><p>Encapsulating Security Payload (ESP) is the IPSec protocol that provides encryption (confidentiality), data integrity, authentication, and anti-replay protection. ESP is the workhorse of IPSec — it is what actually encrypts your VPN traffic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/1*AMGfWFnRMrvXCTm3VxNBhQ.png" /></figure><p><strong>AH vs ESP: </strong>AH authenticates but does not encrypt — think of it as a tamper-evident seal. ESP encrypts AND authenticates — it is the full security package. In modern IPSec deployments, ESP alone (with its built-in authentication) is almost always used instead of AH, or ESP+AH together for maximum security. The exam will test whether you know which protocol provides encryption: the answer is always ESP.</p><blockquote><strong>Exam Tip: </strong>ESP = encryption + integrity + authentication + anti-replay. Protocol 50. Works with NAT via NAT-T (UDP 4500). Tunnel mode encrypts the entire original packet and adds a new IP header — used for site-to-site VPNs. Transport mode encrypts only the payload — used for host-to-host.</blockquote><h4>IKE — Internet Key Exchange</h4><p>Internet Key Exchange (IKE) is the protocol IPSec uses to automatically negotiate and establish the security parameters and cryptographic keys needed to build an IPSec tunnel. Without IKE, you would have to manually configure every key on every device — which is impractical at scale. IKE automates the entire negotiation process.</p><p><strong>Diffie-Hellman: </strong>IKE uses the Diffie-Hellman (DH) key exchange algorithm to securely derive a shared secret over an untrusted network without ever transmitting the secret itself. The DH group number determines the key length and algorithm strength — higher group numbers provide stronger security. DH Group 14 (2048-bit) is a common minimum; Groups 19–21 use elliptic curve cryptography (ECDH) for stronger security at shorter key lengths.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*c0Q96DitHQOe_2oWcYE_QA.png" /></figure><blockquote><strong>Exam Tip: </strong>IKE Phase 1 = authenticate peers and build a secure management channel (ISAKMP SA). IKE Phase 2 = negotiate IPSec parameters and build the data tunnel (IPSec SA). IKE uses UDP 500; NAT-T uses UDP 4500. IKEv2 is the current version and supports mobile VPN via MOBIKE.</blockquote><h4>IPSec Security Associations (SA)</h4><p>A Security Association (SA) is a one-way logical connection between two IPSec peers that defines all the parameters for how traffic between them will be protected. Think of an SA as a contract that says: ‘traffic sent in this direction will be encrypted with AES-256, authenticated with HMAC-SHA-256, using this specific key, and this SA expires in 8 hours.’</p><blockquote><strong>Exam Tip: </strong>IPSec SA key facts: SAs are one-way (two SAs needed per tunnel). The SPI identifies which SA applies to a packet. IKE Phase 1 builds the management channel; Phase 2 builds the data tunnel SA. PFS ensures each session uses unique keys so past sessions cannot be decrypted if a current key is compromised.</blockquote><h3>Quick Reference Summary</h3><p>Use this table as a last-minute study aid before your exam:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/1*byxqbTEAQMdSNK6WWkfCRw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*uY5EhZy1SSVrJLtS7gQwsg.png" /></figure><h3>Wrapping Up</h3><p>Chapter 2 of the Network+ N10–009 covers a broad range of physical and virtual appliances, application services, and network functions. The key takeaways are:</p><ul><li><strong>Hub vs Switch:</strong> Hubs broadcast to all ports (half-duplex, CSMA/CD). Switches forward intelligently via MAC address table (full-duplex, no CSMA/CD).</li><li><strong>CSMA/CD:</strong> The collision management protocol for wired Ethernet — listen, transmit, detect collision, backoff, retransmit.</li><li><strong>Full vs half duplex:</strong> Full = simultaneous send/receive (switches). Half = one direction at a time (hubs).</li><li><strong>Static vs dynamic routing:</strong> Static routes are manually configured and predictable but do not adapt to failures. Dynamic protocols (OSPF, EIGRP, RIP, BGP) auto-discover routes and converge after changes. Administrative Distance decides which route wins when multiple sources exist.</li><li><strong>Firewall types:</strong> Layer 4 = IP/port/state filtering (fast, no content inspection). Layer 7 / NGFW = DPI, app-aware, SSL inspection. Network Firewall = perimeter zone-based device with DMZ. WAF = Layer 7 protection for web apps (SQLi, XSS). UTM = all-in-one security appliance for SMBs.</li><li><strong>ACL &amp; implicit deny:</strong> ACLs are processed top-down, first match wins. The implicit deny is the hidden last rule that silently drops all traffic not explicitly permitted — always plan for it.</li><li><strong>MAC address table:</strong> The CAM table that makes switches intelligent — learn, forward, flood.</li><li><strong>PoE standards:</strong> 802.3af (15.4 W), 802.3at (30 W), 802.3bt (60/100 W).</li><li><strong>Fixed vs modular:</strong> Fixed is simple and cheap; modular is scalable and flexible.</li><li><strong>802.1X + RADIUS:</strong> Enterprise authentication for both wired and wireless — supplicant, authenticator, RADIUS server.</li><li><strong>NAS vs SAN:</strong> File-level vs block-level storage.</li><li><strong>Proxy server:</strong> URL filtering (block by address/category), content filtering (block by payload/file type), and web page caching (serve local copies to save bandwidth and reduce latency).</li><li><strong>VPN, QoS, TTL:</strong> Core network functions for secure access, traffic prioritization, and packet lifecycle management.</li><li><strong>Tunneling &amp; IPSec:</strong> TLS tunneling = SSL VPN on port 443. IPSec uses AH (auth/integrity, no encryption, Protocol 51) and ESP (encryption + auth, Protocol 50). IKE Phase 1 builds the management channel; Phase 2 builds the data tunnel SA. Security Associations are one-way — two needed per tunnel. NAT-T wraps ESP in UDP 4500 for NAT traversal.</li></ul><p>If this post helped you, share it with your fellow Network+ candidates and follow along for the next chapter in the series. Happy studying, and good luck on the exam!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30d353db61b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 1- Network+ N10–009 OSI Module]]></title>
            <link>https://hassen-hannachi.medium.com/day-1-network-n10-009-osi-module-24c590f4415a?source=rss-bd4a1e5ed7c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/24c590f4415a</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[computer-networking]]></category>
            <category><![CDATA[comptia]]></category>
            <category><![CDATA[comptia-certifications]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Hassen Hannachi ]]></dc:creator>
            <pubDate>Mon, 16 Mar 2026 03:09:40 GMT</pubDate>
            <atom:updated>2026-03-16T03:09:40.383Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rDHQPu-T0rsPutN_5A8yEQ.png" /></figure><p>The OSI (Open Systems Interconnection) model is not just a textbook diagram — it is the universal language that network engineers, security analysts, and developers use to describe exactly where a problem is, where an attack is happening, or where a protocol lives. Mastering these 7 layers is foundational for CompTIA Network+ and for any career in IT or Cybersecurity.</p><p>Understanding these layers helps with:</p><ul><li>Troubleshooting network issues 🛠️</li><li>Identifying device functions</li><li>Understanding security boundaries 🔐</li><li>Passing exam scenario questions</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wA-cEWo7yp8H2O9Hcv4-eA.png" /></figure><p><strong>7 Application Layer</strong></p><p><em>// Human ↔ Network Interface</em></p><p>The layer closest to the end user. It provides network services directly to applications — not the apps themselves, but the protocols that allow them to communicate. When you open a browser and load a page, HTTP/HTTPS operates here. This layer handles things like user authentication, data representation requests, and access to network resources.</p><p><strong><em>PDU: Data </em></strong><em>HTTP / HTTPS FTP SMTP DNS SNMP</em></p><p><strong>6 Presentation Layer</strong></p><p><em>// Translation, Encryption, Compression</em></p><p>Often called the “translator” of the OSI model. It converts data from the application format into a format the network can understand — and vice versa on the receiving end. This layer handles data encoding (ASCII, EBCDIC), encryption/decryption (SSL/TLS lives here conceptually), and compression. Think of it as the interpreter between two parties speaking different dialects.</p><p><strong>PDU</strong>: <strong>Data</strong> <em>SSL / TLS JPEG / PNG ASCII MPEG</em></p><p><strong>5 Session Layer</strong></p><p><em>// Connection Establishment &amp; Control</em></p><p>Manages sessions — the logical connections between two devices. It is responsible for establishing, maintaining, and gracefully terminating communication sessions. If you are downloading a large file and the connection drops, the session layer handles checkpointing so the transfer can resume. It controls <em>full-duplex</em> vs <em>half-duplex</em> communication and session tokens.</p><p><strong>PDU: Data</strong> <em>NetBIOS RPC PPTP SAP</em></p><p><strong>4 Transport Layer</strong></p><p><em>// Reliable Delivery &amp; Flow Control</em></p><p>This is one of the most critical layers. It provides end-to-end communication between hosts, handling segmentation, reassembly, error recovery, and flow control. TCP (Transmission Control Protocol) guarantees delivery with acknowledgements and retransmissions. UDP (User Datagram Protocol) is connectionless and faster — used for streaming, DNS, and VoIP. Port numbers live here, which is why firewalls operate at Layer 4.</p><p><strong>PDU: Segment</strong> <em>(TCP) / Datagram (UDP) TCP UDP Port Numbers</em></p><p><strong>3 Network Layer</strong></p><p><em>// Logical Addressing &amp; Routing</em></p><p>Responsible for moving packets across different networks — this is where routing happens. IP addresses (logical addresses) live at Layer 3. Routers are the primary Layer 3 device; they read IP headers to determine the best path for each packet. Understanding this layer is critical for subnetting, CIDR, VLANs, and understanding attacks like IP spoofing or route poisoning.</p><p><strong>PDU: Packet</strong> <em>IPv4 / IPv6 ICMP OSPF BGP ARP</em></p><p><strong>2 Data Link Layer</strong></p><p><em>// Physical Addressing &amp; Node-to-Node Delivery</em></p><p>Handles communication between two directly connected nodes. MAC (Media Access Control) addresses live here — your network card’s hardware address. This layer packages data into frames and handles error detection (CRC). It is split into two sublayers: LLC (Logical Link Control) and MAC. Switches operate at Layer 2. From a security standpoint, ARP poisoning and MAC flooding attacks target this layer.</p><p><strong>PDU: Frame</strong> <em>Ethernet Wi-Fi (802.11) MAC Address PPP</em></p><p><strong>1 Physical Layer</strong></p><p><em>// Bits on the Wire</em></p><p>The foundation — converts data into raw bits (0s and 1s) and transmits them over a physical medium, whether copper cable, fiber optic, or radio waves. It defines voltage levels, cable specifications, connector types, data rates, and modulation. Hubs and repeaters work at this layer. Physical layer issues include cable breaks, signal interference, and hardware failures — the “is it plugged in?” of networking.</p><p><strong>PDU: Bit</strong> <em>Ethernet cables Fiber optic Wi-Fi signals RJ-45</em></p><h3>Practical Troubleshooting Using OSI</h3><p>A common Network+ strategy is <strong>layer-based troubleshooting</strong>:</p><h4>Example:</h4><ul><li>No network connectivity?<br> → Start at Layer 1 (cables, physical connection)</li><li>Can’t access websites but can ping IP?<br> → Likely Layer 7 (DNS issue)</li><li>Problems with routing between networks?<br> → Layer 3 issue</li></ul><p>Thinking in layers helps isolate problems faster and more logically.</p><h3>OSI vs TCP/IP Model</h3><p>The TCP/IP model is more commonly used in real-world networking, but the OSI model is more detailed and better for learning and troubleshooting.</p><p>Many Network+ questions may require you to:</p><ul><li>Compare both models</li><li>Map OSI layers to TCP/IP layers</li></ul><p>Understanding how they align is extremely helpful for exam success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/671/1*vm03wQ-BqSZ7iBypfN48_g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/1*XxqufD6NkL9Ke-wdIzKvyg.png" /></figure><h3>Network+ Exam Tips</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/1*fk_zgX7uvyqF5-9980hmHA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/689/1*yA8vMXikXjeWa250cgaCJg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/689/1*qJTnzUx5HXZpcflqlQw0nw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/687/1*IJLD7kQr7qiz685ioGH3-w.png" /></figure><h3>Found this helpful?</h3><p>Follow my Network+ study series on Medium as I work through each chapter of the N10–009 objectives. Next up: Networking Appliances, Applications, and Functions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24c590f4415a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making a Kali Bootable USB Drive on Windows]]></title>
            <link>https://hassen-hannachi.medium.com/making-a-kali-bootable-usb-drive-on-windows-6196a77e5578?source=rss-bd4a1e5ed7c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6196a77e5578</guid>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[kali-linux]]></category>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Hassen Hannachi ]]></dc:creator>
            <pubDate>Thu, 12 Mar 2026 21:31:29 GMT</pubDate>
            <atom:updated>2026-03-12T21:31:29.144Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V22mrKUg25VRd6YZleS7xw.png" /></figure><p>One of the fastest method, for getting up and running with Kali Linux is to run it “live” from a USB drive. This method has several advantages:</p><ul><li><strong>Non-destructive:</strong> It does not modify the host computer’s hard drive or installed operating system. To return to normal use, simply remove the USB drive and restart the computer.</li><li><strong>Portable:</strong> You can carry Kali Linux on a USB drive and run it on almost any compatible system within minutes.</li><li><strong>Customizable:</strong> You can <a href="https://www.kali.org/docs/development/live-build-a-custom-kali-iso/">roll your own custom Kali Linux ISO image</a> and load it onto a USB drive using the same process.</li><li><strong>Persistent</strong> (optional): With additional configuration, you can configure your Kali Linux “live” USB drive to have <a href="https://www.kali.org/docs/usb/usb-persistence/">persistent storage</a>, so that files and data are saved even after restarting the system.</li></ul><p>In order to do this, we first need to create a bootable USB drive which has been set up from an ISO image of Kali Linux.</p><p>The specifics of this procedure will vary depending on whether you’re doing it on a <a href="https://www.kali.org/docs/usb/live-usb-install-with-linux/">Linux</a>, <a href="https://www.kali.org/docs/usb/live-usb-install-with-mac/">macOS/OS X</a>, or <a href="https://www.kali.org/docs/usb/live-usb-install-with-windows/">Windows</a> system.</p><h4>Requirements</h4><p>Before starting, make sure you have the following:</p><ol><li>A <a href="https://www.kali.org/docs/introduction/download-official-kali-linux-images/"><em>verified</em></a> copy of the <a href="https://www.kali.org/docs/introduction/what-image-to-download/">appropriate ISO image</a> of the latest Kali build image for the system you’ll be running it on.</li><li>If you’re running under Windows, there is no one tool that is considered the overall best for imaging. We recommend <a href="https://www.balena.io/etcher/">Etcher</a> <em>(installer or portable)</em> as it is simpler to use, however <a href="https://rufus.ie/">Rufus</a> is another popular option with its advanced options. If one does not work for you, consider the other.</li><li>A USB drive, 8GB or larger <em>(Systems with a direct SD card slot can use an SD card with similar capacity. The procedure is identical.)</em></li></ol><blockquote>During this procedure, you might see some warnings telling you that Kali Linux contains malware, trojan, virus or whatever. This message usually comes from Windows Defender, USB Defender, or a third-party antivirus. Those warnings are expected: Kali Linux is packed with <strong>penetration testing tools</strong> that are likely to be flagged as malware. These warnings can safely be ignored.</blockquote><h4>Creating a Bootable Kali USB Drive on Windows (Etcher)</h4><ol><li>Plug your USB drive into an available USB port on your Windows PC, note which drive designator (e.g. “G:\”) it uses once it mounts, and launch <strong>Etcher</strong>.</li><li>Click <strong>Flash from file</strong>, and select the <strong>Kali Linux ISO file</strong></li><li>Click <strong>Select target</strong> and choose the USB drive you want to make bootable.</li><li>Click the <strong>Flash!</strong> button once ready.</li></ol><p><strong>Note</strong><em>: You may get a </em><strong>User Account Control (UAC)</strong> prompt<em> asking for administrator privileges that you will need to accept.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/1*P3GxrAVWUs4Ytup4SuiAug.png" /></figure><p>5. Once Etcher alerts you that the image has been flashed, you can safely remove the USB drive and proceed to boot into Kali with it.</p><p><em>At the time of writing, Etcher will use MBR. This is to allow for the most hardware compatibility.</em></p><h4>Creating a Bootable Kali USB Drive on Windows (Rufus)</h4><ol><li>Plug your USB drive into an available USB port on your Windows PC, note which drive designator (e.g. “G:\”) it uses once it mounts, and launch <strong>Rufus</strong>.</li><li>With <strong>Device</strong>, check the dropdown list of options for the USB drive (e.g. “G:\” and size).</li><li><strong>Boot selection</strong> needs to point to the Kali Linux ISO file, which can be done by clicking the <strong>SELECT</strong> button</li><li>Depending on your configuration, you can set the <strong>Partition scheme</strong>, as well as <strong>Target system</strong>. If you are not sure, leave it as the default values.</li><li>Click the <strong>START</strong> button once ready.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/411/1*GqAZV5fvDOtc4DxGK1R-PQ.png" /></figure><blockquote>While you can easily create a persistent live usb with the integrated options in Rufus by increasing the persistence slider, this is not the officially supported method (check <a href="https://www.kali.org/docs/usb/usb-persistence/">Adding Persistence to a Kali Linux Live USB Drive</a>), as it doesn’t work for all images, like the <strong>Kali Everything Live ISO</strong> introduced in <a href="https://www.kali.org/blog/kali-linux-2022-1-release/">release 2022.1</a>.</blockquote><p>6. You may get a prompt saying about <strong>ISOHybird image</strong>. Selecting ISO image, will allow you to edit the files from the Kali Linux ISO, but at the potential lose of hardware compatibility. As a result, we recommend selecting <strong>DD Image</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/1*dKrZllKBJ-EnJ4A6D2rNwg.png" /></figure><p><em>Note: If you select “DD Image” option, you can create another partition on the USB drive, allowing you to use the rest of the space.</em></p><ul><li>Press <strong>Windows + R</strong></li><li>Type diskmgmt.msc</li><li>Locate your USB drive</li><li>Right-click the <em>“Unallocated”</em></li><li>Select <em>New Simple Volume</em></li><li><em>Follow the rest of the wizard with next, next, next…</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/897/1*wjOdy886wKN0-1NHR7Q1iw.png" /></figure><h4>Booting A USB Drive In Windows</h4><p>Depending on the system <em>(such as BIOS or UEFI)</em>, as well as the version of Windows, and how they are each configured, you may need to re-image the USB drive.</p><ul><li><strong>M</strong>aster <strong>B</strong>oot <strong>R</strong>ecord (MBR) is often used on legacy systems that use BIOS as well as UEFI which has <strong>C</strong>ompatibility <strong>S</strong>upport <strong>M</strong>odule (CSM) enabled</li><li><strong>G</strong>UID <strong>P</strong>artition <strong>T</strong>able (GPT) is required where UEFI has CSM disabled, forcing to use the modern standard</li></ul><p>After writing the image to the USB drive, reboot Windows with the USB inserted. Depending on the motherboard manufacture, will also depend on the next stage.</p><p>Some motherboards support a “temporary” boot menu, allowing for a one off selection. Others you need to enter BIOS/UEFI to configure it to try and boot from USB first.</p><p>Entering either location, also depends on the motherboard. You can look up on the manufacture’s website and read the manual, try and read the screen when booting <em>(however the text may be shown too quick or full logos used)</em>, or try common key combinations (such as ESC, F1, F2, F3, F4, F8, F10, F11, F12 or DEL).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6196a77e5578" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>