<?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 Assem on Medium]]></title>
        <description><![CDATA[Stories by Assem on Medium]]></description>
        <link>https://medium.com/@assem1272004?source=rss-bbbddf3dcc56------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*uLDZhaOEtTcM55H7</url>
            <title>Stories by Assem on Medium</title>
            <link>https://medium.com/@assem1272004?source=rss-bbbddf3dcc56------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:03:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@assem1272004/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[Understanding the OSI and TCP/IP Models: How Network Communication Works]]></title>
            <link>https://medium.com/@assem1272004/understanding-the-osi-and-tcp-ip-models-how-network-communication-works-3dc519375083?source=rss-bbbddf3dcc56------2</link>
            <guid isPermaLink="false">https://medium.com/p/3dc519375083</guid>
            <category><![CDATA[tcp-ip]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[osi-model]]></category>
            <dc:creator><![CDATA[Assem]]></dc:creator>
            <pubDate>Fri, 20 Nov 2026 13:42:29 GMT</pubDate>
            <atom:updated>2026-11-20T13:42:31.002Z</atom:updated>
            <content:encoded><![CDATA[<p>Understanding the OSI and TCP/IP Models: How Network Communication Works</p><p>My beginner&#39;s guide to understanding the layers behind network communication.</p><p>As I continue learning networking and cybersecurity, I realized that understanding how devices communicate is one of the most important things to start with.</p><p>When I first studied networking, I came across two important concepts: the OSI Model and the TCP/IP Model.</p><p>At first, understanding all the layers and their responsibilities was a little confusing. However, after spending some time studying them, I started to understand how they help explain what happens when data travels from one device to another.</p><p>In this article, I&#39;ll share what I learned about both models, their differences, and how they relate to real network communication.</p><p>1. What Is the OSI Model?</p><p>The OSI (Open Systems Interconnection) Model is a conceptual model that explains how network communication works by dividing it into seven layers.</p><p>Each layer has a specific responsibility and works with the layers above and below it.</p><p>The main idea is to break down a complex communication process into smaller parts, making it easier to understand, troubleshoot, and analyze network problems.</p><p>Here are the seven layers:</p><p>Layer 7 – Application</p><p>This is the layer closest to the user.</p><p>It provides network services that applications use to communicate.</p><p>Examples:</p><p>HTTP / HTTPS</p><p>DNS</p><p>FTP</p><p>SMTP</p><p>For example, when I open a website using a browser, application-layer protocols help make that communication possible.</p><p>Layer 6 – Presentation</p><p>This layer is responsible for how data is represented.</p><p>Its main functions include:</p><p>Data formatting</p><p>Encryption and decryption</p><p>Compression and decompression</p><p>For example, encryption helps protect data while it is being transmitted across a network.</p><p>Layer 5 – Session</p><p>The Session Layer manages communication sessions between applications.</p><p>It helps establish, maintain, and terminate sessions between communicating systems.</p><p>Layer 4 – Transport</p><p>This layer is responsible for end-to-end communication between devices.</p><p>Two important protocols here are:</p><p>TCP (Transmission Control Protocol)</p><p>Connection-oriented.</p><p>Provides reliable data delivery.</p><p>Uses acknowledgments and retransmissions.</p><p>UDP (User Datagram Protocol)</p><p>Connectionless.</p><p>Does not guarantee delivery.</p><p>Has less overhead than TCP.</p><p>This layer also uses port numbers to identify the applications involved in communication.</p><p>Layer 3 – Network</p><p>The Network Layer is responsible for logical addressing and routing packets between different networks.</p><p>One of its most important protocols is IP (Internet Protocol).</p><p>Routers mainly operate at this layer.</p><p>Layer 2 – Data Link</p><p>This layer handles communication between devices on the same local network.</p><p>It uses MAC addresses and organizes data into frames.</p><p>Switches commonly operate at this layer.</p><p>Layer 1 – Physical</p><p>This is the lowest layer of the OSI Model.</p><p>It is responsible for transmitting raw bits through physical media.</p><p>Examples include:</p><p>Ethernet cables</p><p>Fiber-optic cables</p><p>Wireless signals</p><p>2. What Is the TCP/IP Model?</p><p>The TCP/IP Model is another way to understand network communication.</p><p>Unlike the OSI Model, which has seven layers, the commonly used four-layer TCP/IP Model has four layers.</p><p>It is based on the protocols used in real-world networking and the Internet.</p><p>Layer 4 – Application</p><p>This layer combines the responsibilities of three OSI layers:</p><p>Application</p><p>Presentation</p><p>Session</p><p>It includes protocols such as HTTP, HTTPS, DNS, and SMTP.</p><p>Layer 3 – Transport</p><p>This layer is responsible for communication between applications on different devices.</p><p>Its main protocols are TCP and UDP.</p><p>Layer 2 – Internet</p><p>This layer handles logical addressing and routing packets between networks.</p><p>IP is one of its main protocols.</p><p>Layer 1 – Network Access</p><p>This layer handles how data is transmitted over the local network.</p><p>It combines the responsibilities of the OSI Data Link and Physical layers.</p><p>Examples include Ethernet and Wi-Fi.</p><p>3. OSI Model vs. TCP/IP Model</p><p>Both models help us understand network communication, but they organize the process differently.</p><p>Here is a simple comparison:</p><p>OSI ModelTCP/IP Model7. ApplicationApplication6. PresentationApplication5. SessionApplication4. TransportTransport3. NetworkInternet2. Data LinkNetwork Access1. PhysicalNetwork Access</p><p>The main difference is that the OSI Model has seven layers, while the commonly used TCP/IP Model has four.</p><p>The OSI Model is mainly used as a reference for understanding and troubleshooting networking concepts, while the TCP/IP Model describes the architecture behind real Internet communication.</p><p>4. How Does Data Travel Through These Layers?</p><p>Let&#39;s take a simple example.</p><p>Imagine that I open a website using my browser.</p><p>What happens behind the scenes?</p><p>The Application Layer handles the communication required by the application, such as an HTTP request.</p><p>The Transport Layer uses TCP in a typical HTTPS connection over TCP to manage the communication between the devices.</p><p>The Network Layer adds IP addressing information to help packets reach their destination.</p><p>The Data Link Layer prepares frames for transmission over the local network.</p><p>The Physical Layer transmits the data as bits through the network medium.</p><p>At the receiving device, the process happens in reverse.</p><p>This process is called encapsulation and decapsulation.</p><p>Each layer adds or processes information needed for communication.</p><p>5. Why Are These Models Important in Cybersecurity?</p><p>Understanding these models is not just about memorizing seven or four layers.</p><p>They are useful when analyzing network traffic and investigating security incidents.</p><p>For example:</p><p>A DNS problem can be investigated by looking at application-layer communication.</p><p>An unexpected connection to a specific port can be investigated at the Transport Layer.</p><p>Suspicious IP traffic can be analyzed at the Network Layer.</p><p>Problems involving MAC addresses or local network communication can be investigated at the Data Link Layer.</p><p>For someone interested in becoming a SOC Analyst, understanding these layers helps build a foundation for analyzing network activity and troubleshooting connectivity issues.</p><p>6. Practical Learning with Wireshark</p><p>After studying the two models, I wanted to connect the theory with something practical.</p><p>Wireshark is a useful tool for capturing and analyzing network traffic.</p><p>By capturing packets, we can examine information such as:</p><p>Source and Destination IP addresses.</p><p>Source and Destination Ports.</p><p>Network protocols.</p><p>TCP flags.</p><p>Ethernet information.</p><p>For example, when analyzing a TCP packet in Wireshark, we can expand the Ethernet, IP, and TCP sections to see information related to different layers of network communication.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hveQPETxeHbsEDczGnV7Xg.jpeg" /></figure><p>This helped me understand that the layers are not just theoretical concepts. They provide a way to organize and analyze the information carried by network packets.</p><p>7. What I Learned</p><p>Before studying these models, I knew that devices communicate using network protocols, but I didn&#39;t fully understand how this communication is organized.</p><p>Now I have a clearer understanding of the responsibilities of each layer and how the OSI and TCP/IP models relate to each other.</p><p>I also learned that understanding these fundamentals is important before moving to more advanced networking and cybersecurity topics.</p><p>I&#39;m still learning, and I plan to keep practicing these concepts using tools like Wireshark.</p><p>Learning networking step by step is helping me build a stronger foundation for my cybersecurity journey.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3dc519375083" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding TCP Three-Way Handshake Through Wireshark]]></title>
            <link>https://medium.com/@assem1272004/understanding-tcp-three-way-handshake-through-wireshark-30bec72c5ccd?source=rss-bbbddf3dcc56------2</link>
            <guid isPermaLink="false">https://medium.com/p/30bec72c5ccd</guid>
            <category><![CDATA[wireshark]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[tcp]]></category>
            <dc:creator><![CDATA[Assem]]></dc:creator>
            <pubDate>Fri, 20 Nov 2026 12:38:10 GMT</pubDate>
            <atom:updated>2026-11-20T12:38:10.996Z</atom:updated>
            <content:encoded><![CDATA[<p>Understanding TCP Three-Way Handshake Through Wireshark</p><p>As I continue learning networking and cybersecurity, I decided to start exploring how network connections actually work instead of just reading about protocols.</p><p>One of the things I studied recently was the TCP Three-Way Handshake. I used Wireshark to observe the packets exchanged when a TCP connection is established.</p><p>What is the TCP Three-Way Handshake?</p><p>TCP (Transmission Control Protocol) is a connection-oriented protocol. Before two devices start exchanging data, they need to establish a connection.</p><p>This process is called the Three-Way Handshake. It consists of three packets:</p><p>SYN</p><p>SYN-ACK</p><p>ACK</p><p>Each step has a specific role in establishing the connection.</p><p>1. SYN – Initiating the Connection</p><p>The first packet is sent by the client to the server with the SYN flag set.</p><p>SYN stands for Synchronization. It is used to initiate a connection and synchronize sequence numbers between the two devices.</p><p>At this point, the client is basically asking the server to establish a TCP connection.</p><p>2. SYN-ACK – The Server&#39;s Response</p><p>If the server is ready to accept the connection, it responds with a packet containing both SYN and ACK flags.</p><p>SYN: The server synchronizes its own sequence number.</p><p>ACK: The server acknowledges the client&#39;s initial SYN.</p><p>This means the server received the connection request and is responding to it.</p><p>3. ACK – Completing the Handshake</p><p>The client then sends the third packet with the ACK flag set.</p><p>This acknowledges the server&#39;s response and completes the Three-Way Handshake.</p><p>After this process, the TCP connection is established, and the devices can start exchanging data.</p><p>Capturing the Handshake Using Wireshark</p><p>I used Wireshark to capture network traffic and look for the TCP handshake.</p><p>By applying a TCP filter, I was able to focus on TCP packets and identify the packets involved in establishing a connection.</p><p>Wireshark filter:</p><p>tcp</p><p>To focus on SYN packets:</p><p>tcp.flags.syn == 1</p><p>The handshake can be identified by looking at the TCP flags in each packet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_il_qCVDkeSCHuQSCyQPKw.jpeg" /></figure><p>Analyzing the Packets</p><p>When analyzing a TCP packet, there are several important fields to look at:</p><p>Source IP: The IP address of the device sending the packet.</p><p>Destination IP: The IP address of the device receiving the packet.</p><p>Source Port: The port used by the sending device. For a client connection, it is usually an ephemeral port.</p><p>Destination Port: The port of the service the client is connecting to, such as port 443 for HTTPS.</p><p>TCP Flags: These show the state or purpose of the packet, such as SYN or ACK.</p><p>For example, when a client connects to a web server, the destination port may be 443, while the source port is randomly selected from the client&#39;s available ephemeral ports.</p><p>Why is the Three-Way Handshake Important?</p><p>The TCP Three-Way Handshake is important because it allows both devices to establish a connection and confirm that they are ready to communicate.</p><p>Understanding this process can also help when troubleshooting network issues or analyzing suspicious traffic.</p><p>For example, a large number of SYN packets without completed connections may be worth investigating, depending on the context and other evidence.</p><p>What I Learned</p><p>This lab helped me understand how a TCP connection starts and how the SYN, SYN-ACK, and ACK packets work together.</p><p>It was a small step, but it made the TCP connection process easier to understand by seeing the packets instead of just reading about them.</p><p>I&#39;m continuing to build my networking fundamentals and document what I learn along the way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30bec72c5ccd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>