<?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 Khushi Sharma on Medium]]></title>
        <description><![CDATA[Stories by Khushi Sharma on Medium]]></description>
        <link>https://medium.com/@khushisharmadubai?source=rss-3a9366cdc931------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*A3_rU4rHa-UKp5RS</url>
            <title>Stories by Khushi Sharma on Medium</title>
            <link>https://medium.com/@khushisharmadubai?source=rss-3a9366cdc931------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 16:18:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@khushisharmadubai/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[Bridging the Gap Between PCI SSF Certification and Real-World Compliance]]></title>
            <link>https://blog.stackademic.com/bridging-the-gap-between-pci-ssf-certification-and-real-world-compliance-1852389ec010?source=rss-3a9366cdc931------2</link>
            <guid isPermaLink="false">https://medium.com/p/1852389ec010</guid>
            <category><![CDATA[pci-ssf]]></category>
            <category><![CDATA[sf]]></category>
            <dc:creator><![CDATA[Khushi Sharma]]></dc:creator>
            <pubDate>Sun, 30 Aug 2026 10:23:43 GMT</pubDate>
            <atom:updated>2026-08-30T10:23:43.363Z</atom:updated>
            <content:encoded><![CDATA[<p>Authors: <a href="https://www.linkedin.com/in/khushi-sharma-267108269">Khushi Sharma</a> and <a href="https://www.linkedin.com/in/kailashdagarwal/">Mr. Kailash D Agarwal</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*k7TnDx9P7V5qp2Dp-ouraQ.png" /></figure><p>EXECUTIVE SUMMARY</p><p>This article examines the misinterpretation of PCI SSF certification and identifies where organizations commonly go wrong in its adoption and implementation. While the PCI Security Software Framework is designed to ensure that payment software meets the security requirements at the time of assessment, a critical gap is seen between the certification and real-world implementation.</p><p>Many organizations, including the financial organizations, assume that deploying an SSF-validated product will automatically lead to compliance with PCI security standards. The organizations completely disregard the fact whether their implementation adheres to the required configuration and usage guidelines or not.</p><p>This disconnect leads to a false sense of security, where organizations believe they are compliant because they are using a certified product. This article aims to highlight the gaps, analyze their root cause, and emphasize the importance of correctly understanding the responsibilities associated with using SSF-validated software.</p><p>INTRODUCTION</p><p>The increasing reliance on software-based payment systems has made application security a critical component. In today’s ecosystem, organizations depend heavily on third-party software solutions to process and manage cardholder data. As a result, these solutions should meet an established security standard.</p><p>One of the primary benchmarks used to evaluate the security of such software is PCI SSF. Before exploring its implications, it is important to first understand PCI SSF.</p><p>PCI Software Security Framework (PCI SSF), developed by the PCI Security Standards Council, is designed to ensure that payment software is built with strong security controls from the ground up. It replaces the earlier PA-DSS and reflects modern application architectures and development practices.</p><p>At its core, SSF focuses on how software is designed, developed, and maintained. It follows an objective-based approach — defining what security outcomes must be achieved rather than prescribing exact methods. This allows vendors flexibility while still meeting defined security expectations.</p><p>The framework primarily applies to software vendors who choose to have their payment applications assessed and listed as validated. However, it is important to recognize that SSF validation applies only to specific versions of a product, under defined condition and environments.</p><p>For organizations using such software, SSF validation should be seen as a starting point — not a guarantee of secure or compliant deployment.</p><p>This article does not focus on the organizations that develop or maintain the payment software. Instead, it examines the organizations that deploy and use such software within their operational environments, with particular emphasis on how these entities interpret and implement PCI SSF-certified solutions.</p><p>KEY COMPONENTS OF THE PCI SOFTWARE SECURITY FRAMEWORK</p><p>The PCI Software Security Framework is the umbrella framework that includes:</p><p>1. PCI Secure Software Standard (PCI SSS)</p><p>The SSS standard focuses on securing individual payment software by evaluating its architecture, features, and overall resistance to cybersecurity threats. PCI SSS lists what the software must achieve, providing flexibility in how it is achieved.</p><p>2. PCI Secure Software Lifecycle (PCI SLC) Standard</p><p>The Secure SLC standard ensures that all stages of software development, deployment and maintenance follow established security practices. Implementing a structured and secure software development lifecycle.</p><p>PROBLEM STATEMENT</p><p>Organizations often rely on third-party provided software solutions assuming that SSF certification directly guarantees compliance with the PCI security standard. However, this assumption is flawed. A lot of organizations are not aware that, based on the interpretation of the PCI SSF guidelines, only specific versions of a product, assessed under defined condition, are considered compliant. Furthermore, the responsibility for the correct selection, implementation, and maintenance of the software lies with the organization using it.</p><p>Due to lack of awareness, the organizations fail to verify such scenarios. As a result, the organization may deploy software that is SSF-certified but operationally non-compliant, leading to a false sense of security.</p><p>This article highlights this gap between the certification and implementation in the real world.</p><p>IMPLEMENTATION GUIDE AND CUSTOMER RESPONSIBILITIES</p><p>An essential component of the framework is the requirement for vendors to provide an implementation guide. This guide outlines how the software should be securely installed, configured, and maintained, including aspects such as authentication, logging, updates and remote access. The purpose is to ensure that customers can deploy and use the software in a secure manner.</p><p>At the same time, PCI SSF places significant responsibility on the customers using the software. The customers are responsible for selecting validated software from the official listing, implement it according to the guide provided by the vendor, and maintain it securely within their environment.</p><p>SSF vs PCI DSS Responsibility Boundary</p><p>PCI SSF ensures that payment software is designed and built securely. It focuses on secure coding, vulnerability management, and software lifecycle practices. PCI DSS ensures that cardholder data is protected during storage, processing and transmission.</p><p>SSF focuses on creating a secure software, whereas PCI DSS focuses on operating a secure environment. Both are necessary, but one does not automatically satisfy the other. Importantly, SSF validation does not replace PCI DSS requirement 6 (Secure Software Development for custom code). Even if a software product is SSF validated, an organization still needs to demonstrate that its customization, deployment, and maintenance, of that software comply with PCI DSS.</p><p>CASE STUDY</p><p>In one of the assessments, it was observed that, an organization was using a payment switch that had been certified under SSF and listed as validated by the PCI SSC. However, the certification applied to only a specific platform and operating system, referred to here as Operating System 1.</p><p>In practice, the organization had deployed the payment switch on a different platform and operating system, referred to as Operating System 2, which was not included in the scope of the original assessment. As a result, the software validation status does not automatically extend to the new environment. Despite this, the organization assumed the product to be compliant, because of the SSF certification.</p><p>This case study highlights critical points :</p><ul><li>SSF certification is platform and version specific. It should only be used for the areas that have been assessed.</li><li>Using a validated product outside its testing environment may invalidate the assumptions of validation and requires additional assessment as per PCI DSS standard</li><li>Gaps in understanding the compliance due to insufficient organizational awareness.</li><li>Insufficient diligence on the part of organizations using SSF-certified software. Even when the guidance and implementation instructions are provided by the vendor, organizations tend to overlook these critical details.</li><li>Vendors do not always verify whether the software has been implemented correctly or not.</li><li>Organizations, vendors, third-party or system integrators insufficient diligence may expose data and systems to risk.</li></ul><p>VENDOR DELIVERABLES</p><p>1. Attestation of Validation: This is the vendor’s formal signed declaration that their payment software has been assessed and meets the PCI Secure Software Standard.</p><p>2. Implementation Guide/ Vendor Security Guidance: This document provides information for deployment, configuration and maintenance of the payment application.</p><p>3. Report on Validation: This document is produced by the assessor and captures everything that was tested during the formal security assessment. Customers can request this document under a NON-Disclosure Agreement.</p><p>4. Vulnerability Handling Procedures: This document describes the vendor’s internal process for dealing with security vulnerabilities once they are discovered.</p><p>5. Secure Software Update Documentation: Every time the vendor releases a patch or update, this document accompanies it.</p><p>6. Software Architecture and Data Flow Documentation: This document includes documents showing how the software is built and how cardholder data moves through it.</p><p>7. Annual Attestation and Validation listing: Ongoing public proof that validation is still active.</p><p>8. Vendor Release Agreement: The vendor’s contractual commitments to PCI SSC.</p><p>9. Change Notifications/Release Notes: What changed in each software version and why it matters.</p><p>10. Assessors Feedback Form: It is a quality control mechanism for the assessment process.</p><p>RECOMMENDATION</p><p>To address the observed issues, the following practices can be adopted:</p><ul><li>When organizations thoroughly understand their environment and select appropriate validated software that aligns with their needs and requirements.</li><li>Organizations should also monitor and apply updates regularly and ensure that internal teams are educated so they understand that certification does not mean compliance.</li><li>Organizations should clearly understand their rights regarding vendor responsibilities. Vendors should provide guidance and support to customers; however, PCI SSC separates vendor and customer responsibilities, and vendors are not responsible for misconfiguration caused by customer requested changes.</li><li>SSF-validated products typically come with vendor provided guidance, such as implementation guides, Attestation of Validation (AOV) and configuration instructions. System Integrators should also ensure that the software is implemented strictly according to these guides.</li></ul><p>CONCLUSION</p><p>The growing reliance on the third-party software solutions highlights the critical importance of understanding the scope and limitations of the SSF-certifications. While SSF-validation does provide the assurance that the product has been assessed against rigorous security standards but is not applicable for every platform or scenario. Misinterpretation has led to a false sense of security.</p><p>Organizations must take a proactive approach by selecting the correct validated software, adhering to the vendor provided guidance, monitoring updates and vulnerabilities, and educating the internal team about their responsibility. Vendors should also play a key role by provide the necessary guidance and support, although they should not be held accountable for misconfiguration caused by customer requested changes.</p><p>By bridging the gap between certification and real-world implementation, organizations can ensure that validated software not only meets PCI SSF standards on paper but also maintains security and compliance in practice. This approach strengthens the overall integrity of payment ecosystems.</p><p>REFERENCES</p><p><a href="https://docs-prv.pcisecuritystandards.org/Software%20Security/Standard/PCI-Secure-Software-Standard-v2.0.pdf">Payment Card Industry (PCI) Software Security Framework, Secure Software Standard Version: 2.0</a></p><p><a href="https://docs-prv.pcisecuritystandards.org/Software%20Security/Program%20Documents/PCI-Secure-Software-Program-Guide-v2.0.pdf">Payment Card Industry (PCI) Secure Software Program Guide Version 2.0</a></p><p><a href="https://listings.pcisecuritystandards.org/assessors_and_solutions/payment_software?agree=true">Validated Secure Software</a></p><p><a href="https://listings.pcisecuritystandards.org/documents/SSF_At-a-Glance.pdf">PCI Software Security Framework Provides a Modern Approach to Payment Software Security</a></p><p><a href="https://blog.rsisecurity.com/full-guide-to-pci-software-security-framework-pci-ssf/">Full Guide to PCI Software Security Framework</a></p><p><a href="https://www.ampcuscyber.com/knowledge-hub/guide-to-pci-ssf/">A Complete Guide to PCI Software Security Framework to Secure Modern Payment Applications</a></p><p><a href="https://www.nccgroup.com/introducing-the-software-security-framework-ssf/">Introducing the Software Security Framework (SSF)</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1852389ec010" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/bridging-the-gap-between-pci-ssf-certification-and-real-world-compliance-1852389ec010">Bridging the Gap Between PCI SSF Certification and Real-World Compliance</a> was originally published in <a href="https://blog.stackademic.com/">Stackademic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RANDOM DIGITS OR FINANCIAL IDENTITY: THE SCIENCE BEHIND PAN VALIDATION]]></title>
            <link>https://meetcyber.net/random-digits-or-financial-identity-the-science-behind-pan-validation-e7c404b3aa52?source=rss-3a9366cdc931------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7c404b3aa52</guid>
            <category><![CDATA[pci-dss]]></category>
            <category><![CDATA[luhn-algorithm]]></category>
            <category><![CDATA[pan]]></category>
            <category><![CDATA[check-digit]]></category>
            <dc:creator><![CDATA[Khushi Sharma]]></dc:creator>
            <pubDate>Fri, 19 Jun 2026 12:54:52 GMT</pubDate>
            <atom:updated>2026-06-19T12:54:52.826Z</atom:updated>
            <content:encoded><![CDATA[<p>Authors: <a href="https://www.linkedin.com/in/khushi-sharma-267108269">Khushi Sharma</a> and <a href="https://www.linkedin.com/in/kailashdagarwal/">Mr. Kailash D Agarwal</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/774/1*mw30Qbgofh35O-Y60dZpMg.png" /></figure><p><strong>THE DECEPTION OF RANDOM DIGITS</strong></p><p>Imagine typing sixteen random digits into an online payment page. Could those numbers accidentally become someone’s financial identity?</p><p>At first glance, a 16-digit number may seem meaningless, just another random sequence among a billion of others. But what if those randomly typed digits accidentally qualify as Primary Account Number? Is it merely a coincidence, or is there an invisible system silently deciding which numbers are trusted and which are rejected?</p><p>Behind every valid PAN lies more than just randomness. Hidden beneath the surface are mathematical validations, issuer identification systems, and security mechanisms that separate ordinary numbers from globally recognized financial identities.</p><p>With this intriguing question in mind, let’s dive deeper into what qualifies a number to be called a Primary Account Number.</p><p><strong>DECODING THE PAN</strong></p><p>The starting point of this exploration is understanding what a Primary Account Number actually represents. A PAN is a unique number found on debit and credit cards that identifies a cardholder’s account within a payment system. In most cases, it appears as a 16-digit number printed on the front of the card, although depending on the card network, it can range from 13–19 digits.</p><p>At first glance, it may appear to be just a random sequence of numbers. However, a PAN is not random at all. It is part of a structured global system designed to ensure that every card issued is uniquely identifiable, verifiable, and secure within a financial network.</p><p>These digits are not only used for identification but also play a key role in enabling secure electronic transactions across banking systems, point-of-sale terminals, and online payment gateways. What seems like a simple number is actually the entry point into a highly regulated financial structure.</p><p><strong>ANATOMY OF A PAN</strong></p><p>Next important step is dissecting the PAN and understanding what exactly the structure of the PAN is. The PAN in most cases has 16-digits of number.</p><p>1. The first 6–8 digits are the BIN. The BIN consists of two distinct parts:</p><ul><li>MII (Major Industry Identification number) which signifies the category of business of the card issuer.</li><li>IIN (Issuer Identification number) which consists of 6 to 8 digits including the MII. BINs are crucial for transaction routing, identifying the card brand and card type.</li></ul><p>2. The Personal Account Identity: The digits between the BIN and the check digit are called Account Identifier. These are also sometimes referred to as individual account identifier, although there is no strict universal public name for this part. These digits are assigned by the issuing bank and are used to uniquely identify each card within the bank’s system. However, it does not map to a bank account number since multiple cards can sometimes be linked to the same underlying account depending on how the bank structures their systems.</p><p>3. The Silent Auditor: The final digit is the check digit and is calculated using Luhn algorithm. So if someone mistypes even one digit, the check digit instantly knows that it is not valid card number.</p><p><strong>CAN RANDOMNESS BE TRUSTED?</strong></p><p>This is an extremely valid question especially when dealing with something as sensitive and as important as PAN. At first glance, it might seem like such a long number can be generated randomly. However, with financial systems, such randomness cannot be trusted. If numbers were truly generated randomly it would create havoc, global systems would collapse under fraud, transaction errors, and identity misuse within minutes.</p><p>A PAN cannot be chosen randomly. Every digit has a purpose. Some identify the issuer. Others identify the customer. The final digit acts like a validation marker, silently verifying whether the number itself is mathematically trustworthy or not.</p><p><strong>THE INVISIBLE MATHEMATICS BEHIND FINANCIAL IDENTITY</strong></p><p>This is the most interesting part but after reading this, the “magic” behind PAN numbers disappears completely.</p><p>A PAN is carefully structured. One of the most important components is the check digit, which helps verify whether the card number is valid or not. The moment you write your full PAN, the page tells you, even before submission, that the card number is invalid. All this is possible because of the check digit.</p><p>A check digit does not make the number secure. It does not encrypt anything or protect against hacking. Instead, it ensures that the numbers follow a mathematical pattern.</p><p>To understand how this works, let’s explore the algorithm behind it called the Luhn algorithm, also known as the modulus 10 or mod 10 algorithm. It is a checksum formula method used to validate the authenticity of card numbers.</p><p><strong>STEP-BY-STEP LUHN ALGORITHM:</strong></p><p>1. Start from the right: The Luhn algorithm always begins from the rightmost digit, moving leftwards to process the number systematically.</p><p>2. Apply the doubling rule: Starting from the right, every second digit is doubled. Doubling the digit is important to detect swapped digits and increases accuracy.</p><p>3. Reduce double-digit numbers: Any result above 9 is broken into digits and then added. For example, 14 will be broken down to 1+4=3</p><p>4. Add all digits: Now all the digits are added</p><p>5. Validate using divisibility rule: A PAN is only valid if: Sum%10 = 0.</p><p><strong>How the PAN check digit is created?</strong></p><p>Instead of only verifying numbers, banks also use Luhn Algorithm in reverse to generate valid PANs.</p><p>The bank generates the first 15 digits, then applies the Luhn algorithm to these digits. It then calculates what the final digit must be so it becomes divisible by 10. That final digit is added as the check digit.</p><p>So, the structure becomes: (First 15 digits + check digit) must satisfy divisibility by 10.</p><p><strong>CAN MATHEMATICAL RULES DETERMINE TRUST?</strong></p><p>One of the most fascinating aspects of a PAN is that trust within payment system begins with mathematics. Before a transaction is approved, payment systems first determine whether the PAN is valid or not and so the Luhn algorithm comes into the picture. But does Luhn algorithm truly represent the epitome of trust.</p><p>The Luhn algorithm is checksum validation system, that works silently in the background detecting typing errors, invalid combinations, and incorrectly generated numbers. However, an important distinction must be made between mathematical validity and actual legitimacy.</p><p>The Luhn Algorithm does not determine whether the card belongs to a real person. It does not check whether the account has balance. It does not determine whether the card has been stolen or used fraudulently and whether the transaction is safe or not. Even if a number passes Luhn, it can still be fake, stolen or inactive. This raises a crucial perspective on digital trust itself. The mathematical rules act as the first checkpoints, but trust is built through layers of verifications.</p><p><strong>INSIDE THE ARCHITECTURE OF TRUST?</strong></p><p>If mathematical validation alone cannot establish trust, then what truly does?</p><p>Behind every successful transaction lies a vast and carefully engineered architecture of trust. A PAN is not trusted simply because it passes the Luhn algorithm. Multiple layers of security and interconnected systems play a key role in establishing the trust.</p><p>The moment a PAN enters a payment gateway, a chain reaction silently begins. The payment network identifies the card issuer. Banking systems verify whether the card exists, whether sufficient funds are available. Fraud detection system analyzes transaction pattern. Authentication mechanisms evaluate whether the transaction is genuine or suspicious. All of this occurs within seconds, without the user realizing all everything that happens in the background.</p><p>The security of PAN is further strengthened by security standards such as PCI DSS. PCI DSS enhances the security of cardholder data by defining how sensitive account data must be stored, processed, or transmitted. Without such systems, financial networks would become highly vulnerable to fraud, identity misuse, and cyberattacks.</p><p><strong>BEYOND SIXTEEN DIGITS</strong></p><p>At the beginning, the question seemed simple: can any random 16-digit number qualify as a PAN?</p><p>Technically, the answer appears straightforward, no. But the deeper exploration behind PANs reveals something far more interesting. A valid PAN is not created by numerical length alone. Hidden beneath those digits exists an entire system of issuer identification, mathematical validation, authentication mechanisms, fraud detection systems, and security protocols working together to establish trust.</p><p>What makes this fascinating is that most people never notice this invisible infrastructure. A card transaction lasting only a few seconds depends on countless silent verifications taking place in the background. Every layer exists for one purpose: distinguishing legitimacy from randomness.</p><p>The existence of PAN validation systems also reveals an important reality about the modern digital world. Trust today is rarely based on human recognition. Instead, it is engineered through algorithms, verification systems, and interconnected security architectures capable of operating at a global scale.</p><p>In the end, a PAN is not merely sixteen digits printed on a card. It is proof that within digital systems, trust itself must be desig</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7c404b3aa52" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/random-digits-or-financial-identity-the-science-behind-pan-validation-e7c404b3aa52">RANDOM DIGITS OR FINANCIAL IDENTITY: THE SCIENCE BEHIND PAN VALIDATION</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Always-On Defense: The Role of WAFs in Meeting PCI DSS v4.0.1 Requirements]]></title>
            <link>https://cybersecuritywriteups.com/always-on-defense-the-role-of-wafs-in-meeting-pci-dss-v4-0-1-requirements-0f90441cf610?source=rss-3a9366cdc931------2</link>
            <guid isPermaLink="false">https://medium.com/p/0f90441cf610</guid>
            <category><![CDATA[waf]]></category>
            <category><![CDATA[pci-dss]]></category>
            <dc:creator><![CDATA[Khushi Sharma]]></dc:creator>
            <pubDate>Sun, 14 Jun 2026 12:16:31 GMT</pubDate>
            <atom:updated>2026-06-14T12:16:31.451Z</atom:updated>
            <content:encoded><![CDATA[<p>Authors: <a href="https://www.linkedin.com/in/ACoAAEGwk28BZKsHw2wQl0EOis3cHVvWXMCqhrE?miniProfileUrn=urn%3Ali%3Afs_miniProfile%3AACoAAEGwk28BZKsHw2wQl0EOis3cHVvWXMCqhrE">Khushi Sharma</a> &amp; <a href="https://www.linkedin.com/in/kailashdagarwal/">Kailash D Agarwal</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TdxILnJl0DDnYw7fOUm8-w.png" /></figure><p>ABSTRACT</p><p>This article examines the shift from periodic testing to continuous protection in context of evolving cybersecurity threats. As attackers constantly discover new ways to exploit vulnerabilities, the frequency and sophistication of attacks have increased significantly. This has made it essential for organizations to strengthen their security posture. This article analyzes the limitation of traditional periodic testing approaches and discusses how the adoption of continuous protection mechanisms, such as web application firewalls (WAF), enhances overall security and resilience.</p><p>INTRODUCTION</p><p>The rapid growth of digital applications has significantly increased the importance of securing web environments, especially for organizations handling sensitive payment data. The Payment Card Industry Data Security Standard (PCI DSS) provides a comprehensive framework to ensure the protection of cardholder information and to maintain a secure application infrastructure.</p><p>Traditionally, under PCI DSS v3.2.1 Requirement 6.6, organizations were given an option to protect public-facing web applications either by conducting periodic application-layer penetration testing (or using automated vulnerability assessment tools) or by implementing a web application firewall. It is important to note that network-level penetration testing remained mandatory regardless, under Requirement 11.3. While both approaches contributed to improving security, many organizations relied on periodic testing for application security, which only provided a snapshot of an application’s security posture at a specific point in time.</p><p>However, the modern threat landscape has evolved significantly. Cyber attackers now use automated tools and continuous scan for vulnerabilities, making web applications more susceptible to real time attacks. This has exposed the limitation of periodic testing, as new vulnerabilities may arise after testing is completed, leaving systems unprotected.</p><p>In response to these challenges, PCI DSS v4.0 (and the current minor revision, v4.0.1) has introduced a shift in focus towards continuous protection mechanisms. Specifically, Requirement 6.4.2 mandates the deployment of an automated technical solution that continually detects and prevents web-based attacks against public-facing applications. While the standard is technology-agnostic, Web Application Firewalls (WAFs) are the most widely adopted solution for meeting this requirement. This article aims to analyze this shift, highlighting the limitations of traditional approaches and demonstrating how continuous protection enhances the overall security posture of organizations.</p><p>TRADITIONAL WEB APPLICATION SECURITY: PT or WAF?</p><p>Traditionally, under PCI DSS v3.2.1 Requirement 6.6, organizations were given an option to protect public-facing web applications either by conducting periodic application-layer penetration testing (or automated vulnerability scanning) or by implementing a web application firewall. It is important to note, however, that network-level penetration testing remained mandatory under Requirement 11.3, regardless of which option was chosen for application-layer security. But whether this is truly an option or not is discussed further.</p><p>Penetration testing is a controlled and authorized simulation of a cyberattack on a system, application or a network to identify security vulnerabilities before real attackers can exploit them. It involves ethical security professionals breaking into a system using the same techniques as hackers, but in a safe and structured manner. The goal is not to exploit vulnerabilities but to identify them, assess their impact and help fix them.</p><p>Penetration testing has one downside: it is a point-in-time assessment, and it happens periodically rather than continuously. As a result, any vulnerabilities that arise after a test is completed, or before the next testing cycle, may go undetected and unanalyzed. This exposes a potential security gap that can be exploited by the attacker. To address this limitation, a Web Application Firewall (WAF) is used to provide continuous monitoring and real time protection against ongoing threats.</p><p>ALWAYS ON SECURITY: THE ROLE OF WAF</p><p>Web application firewall (WAF) helps protect web applications, mobile applications, and APIs by monitoring, filtering and blocking malicious HTTP/S traffic. It identifies and helps block malicious requests before they can reach the application. In addition to blocking attacks, it also provides continuous monitoring of web traffic which helps in detecting suspicious patterns and unusual behavior.</p><p>Another important advantage of WAF is virtual patching, that is it blocks exploitation attempts against known vulnerabilities, and acts as a temporary shield without modifying application code. It intercepts malicious traffic at the entry point, providing protection while developers work on implementing permanent fixes.</p><p>HOW WAF OPERATES</p><p>A web application firewall (WAF) operates by examining and monitoring HTTP/HTTPS requests and applying a set of predefined rules to detect and prevent malicious activities. It can be deployed in different forms, such as a hardware appliance, software solution, or a cloud-based service depending on the organization’s requirements.</p><p>WAF acts as a specialized reverse-proxy as clients pass through the WAF before reaching the server. The WAF closely inspects various components of web traffic. It analyzes:</p><p>· GET Requests: Retrieve data from the server</p><p>· POST Requests: Sends data to the server and modifies the state</p><p>· PUT Requests: Update or create resources</p><p>· DELETE Requests: Removes data</p><p>In addition to request methods, WAF examines other critical parts of the HTTP communication, including headers, query parameters, and the request body. By analyzing these parameters WAF can detect suspicious behavior. When a request matches known attack patterns or violates defined security rules, WAF can take immediate action by blocking the request. It may also generate alerts or logs to inform the security team, allowing them to investigate and respond effectively. This ability to monitor and act in real time makes WAF a key component in protecting web applications.</p><p>WAF SECURITY MODELS AND DEPLOYMENT TYPES</p><p>A web application firewall can operate using different security approaches, primarily known as blocklist (negative security model) and allowlist (positive security model).</p><ul><li>Blocklist-based WAF : Operates by identifying and blocking traffic that matches known attack patterns or signatures.</li><li>Allowlist based WAF : Only permits traffic that has been explicitly approved. Any request that does not meet predefined rules is automatically blocked.</li></ul><p>To balance security and usability many modern WAFs use a hybrid model, combining both blocklist and allowlist techniques. This allows them to block known threats while also restricting access to only approved traffic.</p><p>In addition to security models, WAFs can also be deployed in different ways.</p><ul><li>Network based WAF — Installed locally and is generally hardware based</li><li>Host based WAF — Completely integrated into an application’s software</li><li>Cloud based WAF — They are easy to deploy and rely on third party providers</li></ul><p>IMPORTANCE OF WAF IN MODERN SECURITY</p><p>In today’s threat landscape, web applications are constantly exposed to automated and sophisticated attacks. Attacks such as SQL injection, cross-site scripting (XSS), command injection, file inclusion, DDoS, and zero-day attacks. WAF plays a critical role by providing continuous, real-time protection, unlike traditional security methods that operate periodically. It helps reduce the window of exposure, enhance the security posture of an organization, and ensure better resilience against evolving threats.</p><p>LIMITATIONS OF WAF</p><p>While WAFs are highly effective, they cannot address underlying vulnerabilities in application code and should not be considered a replacement for secure development practices or penetration testing. Additionally, they are not a complete security solution. Their effectiveness depends on proper configuration and continuous tuning. Poorly configured rules may lead to false positives, blocking legitimate traffic. Therefore, correct implementation of WAF is crucial as well.</p><p>EFFECTIVE WAF IMPLEMENTATION</p><p>The effectiveness of a web application firewall depends not just on its deployment, but on how well it is configured, tested and maintained. A properly implemented WAF ensures accurate threat detection while minimizing disruptions to legitimate users.</p><ul><li>Start in monitoring mode: Initially deploy the WAF in passive mode to observe and log traffic without blocking, this helps in understanding the normal behavior.</li><li>Define security rules: Configure allowlist, blocklist, rate-limiting, and geo-blocking policies to control traffic effectively.</li><li>Test in a staging environment: Validate configurations in a non-production state to avoid disruptions. Two common methods are:<br>1. Full stack replication that is to duplicate the entire application infrastructure and then integrate the WAF into the replicated stack.<br>2. Staging via new endpoint: Introducing a new endpoint within your existing production setup.</li><li>Gradual deployment: Begin with less critical applications and move to production once stable.</li><li>Continuously tune rules: Adjust rules to reduce false positives and ensure legitimate traffic is not blocked.</li><li>Integrate with security systems: Connect WAF logs with SIEM tools for better monitoring.</li></ul><p>Proper implementation is important because it ensures the WAF can accurately distinguish between legitimate and malicious traffic, provide effective protection, and minimize disruptions to normal application usage.</p><p>RECOMMENDATIONS</p><p>Based on the analysis presented in the article, organizations should move beyond relying solely on periodic security assessments and adopt continuous protection mechanisms to strengthen web application security. The following recommendations can help improve overall resilience against modern threats:</p><ul><li>Adopt a layered security approach: Penetration testing and WAF should be used together. While penetration testing identifies underlying vulnerabilities, WAF provides continuous, real-time protection.</li><li>Properly configure WAF solutions: WAFs must be correctly configured, regularly tuned, and continuously monitored to reduce false positives and improve detection accuracy.</li><li>Integrate WAF with security monitoring systems: WAF logs and alerts should be connected to SIEM tools for centralized visibility, faster detection, and improved incident response.</li><li>Conduct regular penetration testing and vulnerability assessments: Despite WAF protection, periodic testing and secure code reviews remain essential to identify and fix root vulnerabilities.</li><li>Adopt secure development practices: Security should be embedded in the SDLC through secure coding standards, code reviews, and vulnerability management.</li><li>Continuously update security controls: WAF rules, security policies, and system patches must be updated regularly to address evolving threats and zero-day attacks.</li><li>Provide security awareness and training: Developers and security teams should be trained on secure coding, WAF usage, and modern attack techniques.</li></ul><p>CONCLUSION</p><p>This article highlights the clear shift in web application security from periodic testing approaches toward continuous protection mechanisms. Traditional penetration testing, while still valuable, provides only a snapshot of an application’s security state at a specific point in time. In contrast, modern attack patterns are continuous, automated, and capable of exploiting newly discovered vulnerabilities almost immediately.</p><p>The increased emphasis on continuous protection in PCI DSS v4.0 (and v4.0.1) — particularly through Requirement 6.4.2, which mandates an automated solution that continually detects and prevents web-based attacks — reflects the industry’s recognition of the need for always-on protection. WAFs are the most widely adopted means of meeting this requirement. They help bridge the gap between vulnerability discovery and remediation by filtering malicious traffic in real time and offering capabilities such as traffic inspection, rule-based blocking, and virtual patching. This significantly reduces the exposure window for potential attacks.</p><p>However, WAFs should not be viewed as a standalone security solution. Their effectiveness depends heavily on correct configuration, continuous maintenance, and integration with broader security practices such as penetration testing, secure development, and monitoring systems. Overall, the most effective security posture is achieved through a combined approach. Continuous protection mechanisms like WAFs provide immediate defense, while periodic assessments ensure deeper vulnerabilities are identified and resolved. Together, these strategies enable organizations to build stronger, more resilient web application environments capable of withstanding evolving cyber threats.</p><p><strong>REFERENCES</strong></p><p><a href="https://www.geeksforgeeks.org/computer-networks/what-is-a-web-application-firewall/">https://www.geeksforgeeks.org/computer-networks/what-is-a-web-application-firewall/</a></p><p><a href="https://owasp.org/www-community/Virtual_Patching_Best_Practices">https://owasp.org/www-community/Virtual_Patching_Best_Practices</a></p><p><a href="https://www.cisco.com/site/us/en/learn/topics/security/what-is-web-application-firewall-waf.html">https://www.cisco.com/site/us/en/learn/topics/security/what-is-web-application-firewall-waf.html</a></p><p><a href="https://www.cloudflare.com/en-gb/learning/ddos/glossary/web-application-firewall-waf/">https://www.cloudflare.com/en-gb/learning/ddos/glossary/web-application-firewall-waf/</a></p><p><a href="https://www.checkpoint.com/cyber-hub/cloud-security/what-is-web-application-firewall/web-application-firewalls-implementation/">https://www.checkpoint.com/cyber-hub/cloud-security/what-is-web-application-firewall/web-application-firewalls-implementation/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0f90441cf610" width="1" height="1" alt=""><hr><p><a href="https://cybersecuritywriteups.com/always-on-defense-the-role-of-wafs-in-meeting-pci-dss-v4-0-1-requirements-0f90441cf610">Always-On Defense: The Role of WAFs in Meeting PCI DSS v4.0.1 Requirements</a> was originally published in <a href="https://cybersecuritywriteups.com/">Cyber Security Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DELAY, LOSS AND THROUGHPUT IN PACKET SWITCH NETWORKS]]></title>
            <link>https://meetcyber.net/delay-loss-and-throughput-in-packet-switch-networks-23867e69839a?source=rss-3a9366cdc931------2</link>
            <guid isPermaLink="false">https://medium.com/p/23867e69839a</guid>
            <category><![CDATA[packet-loss]]></category>
            <category><![CDATA[throughput]]></category>
            <category><![CDATA[delay]]></category>
            <dc:creator><![CDATA[Khushi Sharma]]></dc:creator>
            <pubDate>Sat, 25 Apr 2026 18:18:02 GMT</pubDate>
            <atom:updated>2026-04-25T18:18:02.182Z</atom:updated>
            <content:encoded><![CDATA[<p>Series: Computer Networking from Absolute Basics — Part 5</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Hj58DnjRA8IKEV7A" /><figcaption>Photo by <a href="https://unsplash.com/@realmenwearpants?utm_source=medium&amp;utm_medium=referral">Ankit Shetty</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Hello Readers,</p><p>If you’ve been following this series, you already know how packet switching works and how data moves across networks.</p><p>But here’s the real question:</p><p>Why does the internet sometimes feel slow, laggy, or unreliable?</p><ul><li>Why does a video buffer?</li><li>Why does a call break?</li><li>Why does downloading a file sometimes take forever?</li></ul><p>The answer lies in three core concepts:</p><p><strong>Delay, Packet Loss, and Throughput</strong></p><p>These aren’t just theoretical ideas, they define your actual internet experience.</p><p>Let’s break them down in a way that actually makes sense.</p><h4><strong>Understanding Delay (Why Things Feel Slow)</strong></h4><p>Ever clicked something and felt that tiny pause before it loads? That’s delay in action.</p><p>Whenever you send data, it doesn’t instantly reach the destination. It travels through multiple routers, and at each step, it experiences delays.</p><p>Think of it like this:</p><p>Your data is moving through a series of checkpoints and each one adds a small delay.</p><p><strong>There are four main types of delay:</strong></p><ol><li><strong>Processing Delay (Decision Time)</strong></li></ol><p>This is the time a router takes to:</p><ul><li>check the packet</li><li>understand where it needs to go</li><li>verify it’s not corrupted</li></ul><p>Real-world analogy: Like a security guard quickly checking your ID.<br>It’s usually very small, but it happens at every router.</p><p><strong>2.</strong> <strong>Queuing Delay (Waiting Time)</strong></p><p>This is where things get interesting. Packets don’t always move immediately, sometimes they have to wait.</p><p>If many packets arrive at a router at the same time, they form a queue.</p><p>Example:</p><ul><li>No traffic -&gt; instant forwarding</li><li>Heavy traffic -&gt; waiting in line</li></ul><p>This delay is unpredictable and depends on network congestion.</p><p><strong>3.</strong> <strong>Transmission Delay (Sending Time)</strong></p><p>This is the time required to push all bits of a packet onto the link.</p><ul><li>A larger packet takes more time</li></ul><p>Think of it like: Uploading a file, larger files take longer to send.</p><p><strong>4. Propagation Delay (Travel Time)</strong></p><p>Once the packet is sent, it still needs to physically travel.</p><p>This depends on distance<strong>,</strong> not size.</p><p>Example:</p><ul><li>Sending data within a city -&gt; fast</li><li>Sending across continents -&gt; slower</li></ul><p>Even at near light speed, distance still matters.</p><p>Now you might be a little confused between transmission and propagation delay, but don’t worry I’ve got you.</p><p><strong>Transmission vs Propagation</strong></p><p>This confuses almost everyone at first.</p><ul><li><strong>Transmission Delay</strong> -&gt; time to send data</li><li><strong>Propagation Delay</strong> -&gt; time for data to travel</li></ul><p>Simple analogy:</p><ul><li>Transmission = loading a truck</li><li>Propagation = truck driving to destination</li></ul><p>Both happen, and both matter.</p><h4><strong>The Real Problem: Queuing Delay &amp; Packet Loss</strong></h4><p>Now let’s talk about what actually breaks things.</p><p>Routers don’t have unlimited space; they have <strong>buffers (queues)</strong>.</p><p>When traffic is high: packets start waiting, queues get longer, eventually… the buffer fills up</p><p>And when that happens?<br><strong>Packets are dropped. </strong>This is called <strong>Packet Loss.</strong></p><p><strong>Why Packet Loss Happens?</strong></p><ul><li>Network congestion</li><li>Too many users at once</li><li>Limited buffer capacity</li></ul><p><strong>What It Looks Like to You?</strong></p><ul><li>Video buffering</li><li>Voice cracking on calls</li><li>Lag in games</li><li>Failed downloads</li></ul><p>From your perspective, it feels like:</p><p>“The data just disappeared”</p><h4><strong>End-to-End Delay (The Full Journey)</strong></h4><p>So far, we looked at delays at one router called the nodal delay. But in reality, your data goes through multiple routers.</p><p>So the total delay becomes:</p><p><strong>End-to-End Delay = Sum of all delays across the entire path</strong></p><p>This includes: processing delays, queuing delays, transmission delays, and propagation delays. Even small delays add up.</p><p>Up until now, we’ve been looking at how long it takes for data to travel across a network. But speed alone doesn’t tell the full story.</p><p>Imagine a network where packets arrive quickly, but only a small amount of data is being delivered at a time. Would that feel fast to the user? Probably not.</p><p>This brings us to another equally important question:</p><p>How much data is actually being delivered over time?</p><h4><strong>Throughput (How Fast Data Actually Moves)</strong></h4><p>Now let’s talk about performance.</p><p><strong>Throughput = how much data successfully reaches the destination per second</strong></p><p><strong>Throughput vs What You’re Promised</strong></p><ul><li>Internet plan: 100 Mbps</li><li>Actual speed: maybe 40–70 Mbps</li></ul><p>This happens because throughput isn’t fixed, it depends on several real-world factors. Network congestion can slow things down when too many packets are competing for the same path, packet loss can force data to be retransmitted, reducing effective speed, and the actual route your data takes across the network can introduce limitations. On top of that, bandwidth is often shared with other users, so the more people using the network at the same time, the lower the throughput you may experience.</p><p><strong>The Bottleneck Rule</strong></p><p>Your speed is limited by the <strong>slowest link in the path</strong>.</p><p>Example: Server -&gt;100 Mbps, Your connection -&gt; 10 Mbps</p><p>Final throughput = <strong>10 Mbps</strong></p><p><strong>Shared Networks Make It Worse</strong></p><p>If multiple users share a link:</p><ul><li>bandwidth gets divided</li><li>throughput drops</li></ul><p>Example: 10 users sharing the same network -&gt; Each gets less speed.</p><p><strong>6. Why This Matters (Beyond Theory)</strong></p><p>This isn’t just networking theory, it has a direct impact on real-world usage. Slow websites are often a result of high delay, buffering happens when throughput is low, and call issues are usually caused by packet loss.</p><p>These concepts are also crucial in system and network design, where engineers use them to optimise performance, reduce congestion, and improve the overall user experience.</p><p><strong>Cybersecurity (Where This Becomes Powerful)</strong></p><p>This is where it connects to your field:</p><ul><li><strong>DDoS attacks</strong>: overwhelm network -&gt; high delay &amp; packet loss</li><li><strong>Traffic analysis: </strong>understanding throughput patterns</li><li><strong>Anomaly detection: </strong>unusual delays can signal attacks</li></ul><p>These metrics are not just performance indicators, they are <strong>security signals</strong></p><h4><strong>Final Thoughts</strong></h4><p>The internet is not perfect, and that’s exactly what makes it interesting. Every packet you send experiences some delay, carries the risk of being lost, and competes for available bandwidth. Understanding these factors helps you move from simply wondering.</p><p>“Why is my internet slow?”<br> to<br> “I know exactly what’s happening inside the network.”</p><p>And that’s a big step forward.</p><p>If you’ve followed this series so far, you’re not just learning networking, you’re building the foundation to understand real-world systems and cybersecurity behaviour.</p><p>In the next part, we’ll take this a step further by exploring <strong>protocol layers</strong> and their <strong>service models</strong>, and how they structure communication across networks.</p><h3>References</h3><ul><li>James F. Kurose &amp; Keith W. Ross, <em>Computer Networking: A Top-Down Approach</em>, 8th Edition, Pearson.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23867e69839a" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/delay-loss-and-throughput-in-packet-switch-networks-23867e69839a">DELAY, LOSS AND THROUGHPUT IN PACKET SWITCH NETWORKS</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deep Dive into Access Networks]]></title>
            <link>https://infosecwriteups.com/deep-dive-into-access-networks-22cda971ce1d?source=rss-3a9366cdc931------2</link>
            <guid isPermaLink="false">https://medium.com/p/22cda971ce1d</guid>
            <category><![CDATA[wifi]]></category>
            <category><![CDATA[access-networks]]></category>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[networking]]></category>
            <dc:creator><![CDATA[Khushi Sharma]]></dc:creator>
            <pubDate>Sat, 10 Jan 2026 08:02:09 GMT</pubDate>
            <atom:updated>2026-01-10T08:02:09.262Z</atom:updated>
            <content:encoded><![CDATA[<p>Series: Computer Networking from Absolute Basics — Part 2</p><p>This is the part 2 of my series “Computer Networking from Absolute Basics”. If you haven’t read part 1 yet, I’d really appreciate it if you check that out first. It mainly covers what the internet is, how we access it, how data travels from one end system to the other end system, and more.</p><p>Part 1 was published in MeetCyber and can be read here: <a href="https://medium.com/meetcyber/the-internet-explained-from-absolute-basics-ff02f26d8900">Click Here</a></p><p>That said, if you’re already familiar with these basics and want to jump straight into <strong>access networks</strong>, feel free to continue reading.</p><h3><strong>Access Networks</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zFh24hOCK5W32mh1" /><figcaption>Photo by <a href="https://unsplash.com/@choys_?utm_source=medium&amp;utm_medium=referral">Conny Schneider</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Access network is the part of the network that connects end devices to the ISP’s first router, also called <strong>edge router</strong>.</p><p>An ISP (Internet service provider) is a company that provides access to the internet.</p><p>Everything from your home router or modem up to the ISP’s first router falls under the access network. This includes all the network equipments and physical links between your home router or modem and the ISP’s first router.</p><p>The access network doesn’t include the end device itself.</p><p>Now that we understand what an access network is, the next question is: how do we actually connect our homes to the ISP?</p><p>The answer isn’t the same for everyone. Depending on where you live and the infrastructure available, your internet connection may use telephone lines, cable TV lines, or optical fibre. These different way of connecting end users to the ISP are called <strong>access technologies</strong>.</p><p>In the next sections, we’ll look at common access technologies used today.</p><h3><strong>ACCESS TECHNOLOGIES</strong></h3><h3><strong>Home Access:</strong></h3><ol><li><strong>DSL ( Digital Subscriber Line ):</strong></li></ol><p>It is a technology that allows you to get a high speed internet over your existing telephone lines.</p><p>How does DSL work?</p><p>A telephone line can carry signals at different frequencies. <br>Low frequencies are used for voice calls while, high frequencies are used to carry internet data.<br>Because of this frequency separation, a telephone call and an internet connection can <strong>share the same DSL line at the same time</strong> without interfering with each other.</p><p>Now, let’s take a look at a diagram to make everything crystal clear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PFMgkqsvWgYe6WPdtxhzfQ.png" /><figcaption>DSL internet access technology</figcaption></figure><p>Types of DSL:</p><ul><li>ADSL ( Asymmetric Digital Subscriber Line ) : Downstream (download) speeds are higher than upstream (upload) speeds.</li><li>SDSL ( Symmetric Digital Subscriber Line ) : Downstream (download) speeds are equal to upstream (upload) speeds.</li></ul><p>2.<strong> Cable Internet access :</strong></p><p><strong>Cable Internet</strong> uses the cable TV wires that are already installed in many homes. A residence usually gets cable internet access from the same company that provides its cable television service.</p><p>From the ISP’s side, fiber optic cables are used because they are very fast. The fiber reaches a junction point in your neighbourhood and from there, coaxial cable runs to individual houses or apartments.</p><p>Since both fiber and coaxial cables are used in this setup, it is referred to as hybrid fiber coax (HFC).</p><p>Cable internet access requires a cable modem, a cable modem is usually connected to a home router through an Ethernet port, and the router then connects to computing devices such as laptops and smartphones. We’ll discuss Ethernet later in the series.</p><p>At ISP’s central location, called the head end. <strong>CMTS</strong> manages communication between multiple cable modems and the ISP’s network. The CMTS receives data from cable modems on the upstream channel and sends data back to them on the downstream channel. In simple terms, it acts as the <strong>central control point</strong> for cable internet, performing a role similar to what a DSLAM does in DSL networks.</p><p>Cable modems divide the HFC network into two channels, a downstream and an upstream channel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*bAtl_2M9SbQ9zRQmDGC_nA.png" /><figcaption>Hybrid fiber-coaxial cable</figcaption></figure><p>One important point to note is that <strong>cable internet access is a shared broadcast medium</strong>. This means that data sent by the ISP is broadcast to everyone in the neighbourhood, and <strong>each cable modem picks only the data meant for it</strong>.</p><p>Because the medium is shared, if several users in the same neighbourhood download large files or stream videos at the same time, they all use the <strong>same downstream channel</strong>. As a result, the <strong>actual data rate received by each user becomes lower</strong> than the total (aggregate) downstream capacity of the cable network.</p><p>The same idea applies to the <strong>upstream channel</strong> as well. When multiple users upload data simultaneously, such as sending files, joining video calls, or backing up data to the cloud, they must <strong>share the available upstream bandwidth</strong>, which can reduce individual upload speeds.</p><p>A simple way to understand this is through an analogy. Imagine a <strong>single large water pipe</strong> supplying water to many houses in a neighbourhood. When only a few houses are using water, everyone gets good water pressure. But when many houses turn on their taps at the same time, the <strong>water pressure at each house drops</strong>.</p><p>In the same way, cable internet users share a common communication channel, and heavy usage by many users at the same time can reduce the speed experienced by each individual user.</p><p>3. FTTH ( Fiber to the home ) :</p><p><strong>FTTH (Fiber to the Home)</strong> is an access technology in which <strong>optical fiber cables run from the ISP to the user’s home</strong>. Unlike DSL or cable internet, FTTH does not rely on copper or coaxial cables for the last part of the connection. <strong>Instead, it uses optical fiber cables that carry data as light signals directly to the home.</strong></p><p>At the ISP’s central office, a device called the <strong>Optical Line Terminal (OLT)</strong> is responsible for managing communication with many homes. Think of the <strong>OLT as a traffic controller</strong>:</p><p><strong>Downstream</strong>: sends data to everyone<br><strong>Upstream</strong>: tells each home <strong>when to speak and for how long</strong></p><p><strong>A single optical fiber leaves the OLT</strong> and travels toward a neighbourhood. When this fiber reaches <strong>very close to homes</strong>, it is <strong>split using a passive optical splitter</strong>, and individual fiber strands then go to each house or apartment.</p><p><strong>Downstream communication</strong></p><p>When the OLT sends data downstream, the <strong>optical splitter simply copies the same light signal</strong> and forwards it to <strong>every connected home</strong>. As a result, <strong>every ONT receives all downstream data</strong>. Now you might wonder what an ONT is. <strong>ONT</strong> <strong>( Optical Network Terminator )</strong> acts like a fiber modem by converting light signals to electric signals and vice-versa.</p><p>However, this does not mean users can see each other’s data. <strong>Each packet is encrypted</strong>, and an ONT at the user’s home can <strong>only decrypt the packets meant for that specific user</strong>. All other packets are discarded.</p><p><strong>Upstream communication</strong></p><p>Upstream communication works differently. Since multiple homes share the same fiber toward the OLT, transmissions must be <strong>carefully coordinated</strong>. Each home is assigned <strong>specific time slots</strong> during which it is allowed to transmit data. This prevents signals from different homes from colliding on the shared fiber.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/784/1*xS5HJwCeh6ikvWGxiLLYdw.png" /><figcaption>Simplified FTTH (PON-based)</figcaption></figure><p>4. 5G fixed wireless</p><p><strong>5G Fixed Wireless Access (FWA)</strong> is an access network technology that delivers high-speed broadband connectivity using 5G wireless signals instead of traditional wired connections like fiber or DSL. It provides homes and businesses with low-latency, high-capacity internet through radio links, often serving as a cost-effective alternative to laying physical cables. Essentially, it brings 5G mobility performance to fixed locations, enabling ultra-fast internet without extensive infrastructure deployment.</p><h3><strong>Access in the Enterprise and the Home:</strong></h3><ol><li>Ethernet</li></ol><p>Ethernet is a wired access technology widely used to connect end devices like computers and routers to a local area network (LAN). It provides reliable, high-speed, and low-latency connectivity, typically using twisted-pair or fiber-optic cables, and is the backbone for enterprise and home networking.</p><p>2. WiFi</p><p>Wi-Fi is a wireless access technology that allows devices to connect to a network over radio waves. It offers flexibility and mobility within homes, offices, and public areas, supporting high-speed internet without physical cables, though speeds and reliability can vary depending on distance, interference, and network congestion.</p><p><strong>How the Internet Reaches Your Home (Summary):</strong><br>Imagine the Internet as a stream of information flowing from your ISP to your home. It travels over an <strong>access network</strong> like DSL (telephone lines), cable (TV cables), or FTTH (optical fiber) until it reaches your router. Inside the router is a built-in <strong>access point (AP)</strong>, which acts like a translator — turning this digital stream into <strong>Wi-Fi radio signals</strong> that your phones, laptops, and smart devices can understand. Devices that prefer a wired connection can still tap into the Internet through <strong>Ethernet cables</strong>. In essence, the access point is the bridge that brings the wired Internet to life wirelessly inside your home.</p><h3><strong>Wide Area Wireless Access and Base Station:</strong></h3><p>Wide Area Wireless Access (WWA) delivers Internet connectivity over large geographic areas using cellular or radio networks, enabling devices to stay connected across cities, towns, or even remote locations. Technologies like <strong>4G, 5G, and LTE</strong> provide broad coverage far beyond what Wi-Fi can reach. At the heart of this network are <strong>base stations</strong> (cell towers), which act as communication hubs. Each base station transmits and receives radio signals within a specific area, manages multiple device connections, and links users to the core network, effectively bridging mobile devices to the Internet while on the move.</p><p>That’s it for Part 2! We’ll continue exploring more in the next part of this series. I’m still learning, so if you notice any mistakes or have suggestions, I’d love to hear them. This series is based on what I’m reading in the book <em>Computer Networking: A Top-Down Approach </em>by James F. Kurose and Keith W. Ross, and I’m sharing it here as I understand it.</p><p>Next up: the <strong>network core</strong> — let’s explore it together in the next post!”</p><h3>References</h3><ul><li>James F. Kurose &amp; Keith W. Ross, <em>Computer Networking: A Top-Down Approach</em>, 8th Edition, Pearson.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22cda971ce1d" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/deep-dive-into-access-networks-22cda971ce1d">Deep Dive into Access Networks</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Internet As A Network of Networks]]></title>
            <link>https://meetcyber.net/the-internet-as-a-network-of-networks-8473773e8fed?source=rss-3a9366cdc931------2</link>
            <guid isPermaLink="false">https://medium.com/p/8473773e8fed</guid>
            <category><![CDATA[multihome]]></category>
            <category><![CDATA[network]]></category>
            <category><![CDATA[network-structures]]></category>
            <category><![CDATA[ixp]]></category>
            <dc:creator><![CDATA[Khushi Sharma]]></dc:creator>
            <pubDate>Thu, 08 Jan 2026 12:08:49 GMT</pubDate>
            <atom:updated>2026-01-08T12:08:49.691Z</atom:updated>
            <content:encoded><![CDATA[<p>Series: Computer Networking from Absolute Basics — Part 4</p><p>Hello readers<strong>, </strong>If you’re following this series, welcome back to part 4! Part 3 of this series has already been published on <a href="https://infosecwriteups.com/how-data-travels-packet-switching-vs-circuit-switching-f097ca6e2d9b"><strong>InfoSec Write-ups</strong></a><strong>. </strong>so if you haven’t checked it out yet,I highly recommend doing so. But if you’re here to dive straight into the fascinating world of networks of networks, let’s not waste any time — let’s jump right in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SiNsFR4noONRpf8K" /><figcaption>Photo by <a href="https://unsplash.com/@dulhiier?utm_source=medium&amp;utm_medium=referral">Nastya Dulhiier</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Network Of Networks</h3><p>The Internet is not a single network; rather, it is composed of many smaller networks, known as Internet Service Providers (ISPs), that are interconnected.</p><p>Access ISPs provide internet connectivity to end users, whereas transit ISPs connect access ISPs to other ISPs and to the broader Internet.</p><p>If you have any doubts about access ISPs or what exactly an ISP is, I highly recommend reading Part 1 and Part 2 of this series.</p><p>Now, access ISPs themselves need to be interconnected. This interconnection is achieved by creating a <strong>network of networks</strong>. In fact, understanding the concept of a network of networks is key to understanding how the Internet works.</p><p>Since access ISPs must be connected to one another, a naive approach would be to use a full mesh design, where each access ISP connects to every other access ISP. However, this approach is extremely expensive and inefficient. Therefore, let’s focus on other network structures that are more practical and cost-effective.</p><h4>Network Structure 1</h4><p>The simplest possible network structure is one in which all access ISPs are interconnected through a single global transit ISP. In this model, there exists one extremely large ISP that spans the entire world, and every access ISP connects only to this central transit provider.</p><p>This global transit ISP is not a single device but a vast network of routers and communication links. It spans the globe and maintains at least one router geographically close to each access ISP, ensuring efficient connectivity. However, building and maintaining such an extensive infrastructure would be extremely expensive. As a result, the global transit ISP would naturally charge access ISPs based on the volume of traffic exchanged between them.</p><p>In this structure, the access ISP acts as the customer, while the global transit ISP functions as the service provider.</p><p>The major limitation of this model is economic rather than technical. If one company were able to build such a global transit network, other companies would likely attempt to do the same to compete in the market. This competition would lead to the emergence of multiple global transit ISPs, giving rise to a more complex interconnection model — commonly referred to as <strong>network structure 2</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7cVZDTtbj2CjEW0-x_5-tg.png" /></figure><h4>Network Structure 2</h4><p>Network Structure 2 improves on Network Structure 1 by introducing <strong>multiple global transit ISPs</strong> instead of just one.</p><ul><li>There are <strong>hundreds of thousands of access ISPs</strong> at the bottom.</li><li>There are <strong>multiple global transit ISPs</strong> at the top.</li><li>Access ISPs can now <strong>choose</strong> which global transit ISP to connect to based on: pricing, performance, reliability and services offered</li></ul><p>This competition makes Network Structure 2 more attractive for access ISPs.</p><p>However, there’s a critical requirement: <strong>All global transit ISPs must interconnect with each other.</strong><br>Otherwise, users connected to different transit ISPs wouldn’t be able to communicate.</p><p>This creates a <strong>two-tier architecture</strong>:</p><ul><li><strong>Top tier:</strong> Global transit ISPs</li><li><strong>Bottom tier:</strong> Access ISPs</li></ul><p>The assumption here is that global transit ISPs can reach every access ISP and that it makes economic sense to do so, but this assumption doesn’t fully hold in the real world.</p><p><strong>Path of a Packet in Network Structure 2</strong></p><p>Let’s say:</p><ul><li><strong>User A</strong> is connected to <strong>Access ISP A</strong></li><li><strong>User B</strong> is connected to <strong>Access ISP B</strong></li><li>They are connected to <strong>different global transit ISPs</strong></li></ul><p><strong>Packet Path:</strong></p><ol><li>User A sends data → <strong>Access ISP A</strong></li><li>Access ISP A forwards data → <strong>Global Transit ISP 1</strong></li><li>Global Transit ISP 1 forwards data → <strong>Global Transit ISP 2</strong> (interconnection between transit ISPs)</li><li>Global Transit ISP 2 forwards data → <strong>Access ISP B</strong></li><li>Access ISP B delivers data → <strong>User B</strong></li></ol><p>Without interconnection between global transit ISPs, this communication would fail.</p><p><strong>Why Is This Model Unrealistic in Practice?</strong></p><p>Network Structure 2 assumes that global transit ISPs are capable of reaching every access ISP and that doing so is economically feasible. In theory, this sounds reasonable — after all, global transit ISPs are designed to provide large-scale connectivity. However, in practice, this assumption does not hold.</p><p>No single ISP has infrastructure in every city or region around the world. Building and maintaining such extensive coverage would require massive investment, making it both costly and inefficient. In many cases, deploying infrastructure in smaller or less profitable regions is simply not economically justified. As a result, access ISPs usually do not connect directly to global transit ISPs.</p><h4>Transition: From Network Structure 2 to Network Structure 3</h4><p>The limitations of Network Structure 2 lead to the introduction of <strong>intermediate layers</strong> in the Internet hierarchy.</p><p>Once this happens, the Internet can no longer be described as a simple two-tier model.</p><p>This transition brings us to <strong>Network Structure 3</strong>.</p><h4><strong>Network Structure 3</strong></h4><h4><strong>The Role of Regional ISPs</strong></h4><p>To address this limitation, regional ISPs come into play. Regional ISPs operate within specific geographic areas and act as intermediaries between access ISPs and global transit (tier-1) ISPs. Instead of each access ISP connecting directly to a global provider, multiple access ISPs in a region connect to a regional ISP.</p><p>The typical connectivity flow therefore becomes: access ISPs connect to regional ISPs, and regional ISPs then connect to tier-1 ISPs. Tier-1 ISPs are conceptually similar to the global transit ISPs discussed earlier, but even they do not maintain infrastructure in every part of the world. Only a small number of such tier-1 ISPs exist, and interestingly, there is no official authority that assigns this status. Instead, tier-1 recognition is informally established within the networking industry.</p><p><strong>How Does Payment Work in This Hierarchy?</strong></p><p>This hierarchical structure also defines clear business relationships. At each level, ISPs pay the provider above them in the hierarchy. Access ISPs pay the regional ISPs they connect to, and regional ISPs pay the tier-1 ISPs. Tier-1 ISPs, being at the top of the hierarchy, do not pay any upstream providers.</p><p>In certain cases, an access ISP may bypass regional ISPs and connect directly to a tier-1 ISP, paying it directly. These payment-based relationships are often referred to as customer–provider relationships and form the economic backbone of the Internet.</p><p>Once regional ISPs and multiple layers of connectivity are introduced, the Internet can no longer be accurately described as a simple two-tier architecture. Instead, it evolves into a more realistic, multi-level hierarchy. This refined model, which better reflects how the modern Internet operates, is known as <strong>Network Structure 3</strong>.</p><p>However, while Structure 3 is more realistic, it still doesn’t fully capture the redundancy, efficiency, and flexibility of the modern Internet. That’s where Network Structure 4 comes in.</p><h4>Network Structure 4</h4><p>Network Structure 4 expands upon Structure 3 by incorporating features that make it closely resemble the Internet as it exists today. These features improve redundancy, efficiency, and connectivity.</p><p><strong>1. Points of Presence (POPs)</strong></p><ul><li>POPs exist at all levels of the hierarchy <strong>except the access ISP level</strong>.</li><li>A POP is a <strong>physical location with one or more routers</strong> where customer ISPs can connect.</li><li>Customer networks connect to a POP using <strong>high-speed links</strong>, allowing scalable and reliable communication.</li></ul><p><strong>2. Multihoming</strong></p><p>Most ISPs (except Tier-1) can connect to <strong>two or more upstream providers</strong>, a setup called <strong>multihoming</strong>.</p><p><strong>Examples:</strong></p><ul><li>An access ISP might connect to <strong>two regional ISPs</strong>, or to <strong>several regional ISPs plus a Tier-1 ISP</strong>.</li><li>A regional ISP can connect to <strong>multiple Tier-1 ISPs</strong>.</li></ul><p><strong>Benefits:</strong></p><ul><li>Provides <strong>redundancy</strong>: if one provider fails, traffic can still flow through others</li><li>Improves <strong>reliability and availability</strong> of the Internet</li><li>Allows traffic to take <strong>alternate paths</strong> for efficiency and performance</li></ul><p><strong>3. Peering</strong></p><ul><li>ISPs that are on the <strong>same level in the hierarchy</strong> can connect directly to each other to exchange traffic. This direct connection is called <strong>peering</strong>.</li><li><strong>Key points:</strong></li><li>Traffic between peering ISPs does <strong>not need to go through higher-level providers</strong>, which saves cost and reduces delays.</li><li>Peering is usually <strong>settlement-free</strong>, meaning neither ISP pays the other for this traffic exchange.</li><li><strong>Tier-1 ISPs</strong> also peer with each other without payment, forming the <strong>backbone of the global Internet</strong>.</li><li><strong>In short:</strong> Peering allows ISPs to exchange data directly, improving efficiency, reducing costs, and increasing network resilience.</li></ul><p><strong>4. Internet Exchange Points (IXPs)</strong></p><ul><li>An <strong>Internet Exchange Point (IXP)</strong> is a physical location where multiple ISPs meet to directly exchange Internet traffic.</li><li><strong>How it works:</strong></li><li>Instead of sending traffic through multiple higher-level providers, ISPs can <strong>connect at an IXP</strong> and exchange data directly.</li><li>IXPs usually have <strong>dedicated switches and routers</strong> to handle traffic between all connected networks efficiently.</li></ul><p><strong>Example:</strong></p><ul><li>Suppose <strong>ISP A</strong> and <strong>ISP B</strong> serve different neighbourhoods in the same city.</li><li>Without an IXP, traffic from a customer on ISP A to a customer on ISP B might travel <strong>up the hierarchy</strong>: ISP A → regional ISP → Tier-1 ISP → regional ISP → ISP B.</li><li>With an IXP in the city, ISP A can send traffic <strong>directly to ISP B</strong> through the IXP.</li><li>This makes the connection <strong>faster, cheaper, and more reliable</strong>, because it avoids multiple intermediate providers.</li><li><strong>In short:</strong> IXPs act as <strong>local traffic hubs</strong>, allowing networks to exchange data directly, which reduces latency, cuts costs, and improves efficiency.</li></ul><p>Note : <br>Peering = a <strong>direct traffic exchange</strong> agreement between two ISPs.<br>IXP = a <strong>facility</strong> that allows many ISPs to peer in one place efficiently.</p><p>Peering is the agreement/connection, IXPs are the infrastructure that makes multiple peerings easier.</p><p><strong>Summary</strong></p><p>Network Structure 4 = Structure 3 + advanced features (POPs, multihoming, peering, IXPs). It ensures robustness, efficiency, and flexibility, accurately representing the modern Internet while building on the hierarchical model of Structure 3.</p><h4><strong>Network Structure 5</strong></h4><p><strong>Network Structure 5</strong> represents <strong>today’s Internet</strong>, extending Structure 4 by incorporating <strong>content provider networks (CPNs)</strong>.</p><p>While Structure 4 focuses on hierarchical ISPs, POPs, multihoming, peering, and IXPs, Structure 5 recognises that <strong>major content providers like Google, Netflix, and Facebook operate their own global networks</strong> to deliver content more efficiently to end users.</p><p><strong>1. Content Provider Networks (CPNs)</strong></p><ul><li>Large content providers build <strong>private networks</strong> connecting their data centers around the world.</li><li>Example: Google has:</li><li><strong>19 major data centers</strong> across North America, Europe, Asia, South America, and Australia, each with <strong>tens of thousands of servers</strong>.</li><li><strong>Smaller data centers</strong> at IXPs, with a few hundred servers each.</li><li>These private networks <strong>only carry traffic to and from the provider’s servers</strong>, bypassing parts of the public Internet for better control and performance.</li></ul><p><strong>2. How Content Providers Connect to the Internet</strong></p><ul><li>CPNs try to <strong>connect directly to access ISPs</strong> wherever possible, including via IXPs, to reduce dependence on tier-1 ISPs.</li><li>For access ISPs that cannot be reached directly, the content provider connects to <strong>tier-1 ISPs</strong> and pays for the traffic it exchanges.</li><li>This approach reduces costs, improves reliability, and gives content providers <strong>greater control over how their services reach users</strong>.</li></ul><p>Network Structure 5 is <strong>today’s Internet</strong>: a network of networks with hierarchical ISPs <strong>plus major content providers’ private networks</strong>. This allows faster, more reliable delivery of content while reducing dependence on tier-1 ISPs and improving overall network control.</p><p><strong>Conclusion</strong></p><p>The Internet is far more than a single network — it is a <strong>complex network of networks</strong>, built from hierarchical ISPs, POPs, multihoming, peering agreements, IXPs, and now the private networks of major content providers.</p><p>From the simplest structure with a single global transit ISP (Structure 1) to today’s Internet with advanced redundancy, efficiency, and content provider integration (Structure 5), we can see how the Internet has evolved to meet the demands of scale, reliability, and performance.</p><p>Understanding these network structures gives us insight into how data flows across the globe, how ISPs interact economically, and how content reaches end-users efficiently.</p><p>In the next article, we will dive deeper into <strong>packet-switched networks</strong>, exploring concepts like <strong>delay, loss, and throughput</strong>, which determine how quickly and reliably data moves through these networks. Stay tuned to see how these factors shape Internet performance in practice.</p><h3>References</h3><ul><li>This article heavily references James F. Kurose &amp; Keith W. Ross, <em>Computer Networking: A Top-Down Approach</em>, 8th Edition, Pearson for network structure explanations.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8473773e8fed" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/the-internet-as-a-network-of-networks-8473773e8fed">The Internet As A Network of Networks</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Data Travels: Packet Switching vs Circuit Switching]]></title>
            <link>https://infosecwriteups.com/how-data-travels-packet-switching-vs-circuit-switching-f097ca6e2d9b?source=rss-3a9366cdc931------2</link>
            <guid isPermaLink="false">https://medium.com/p/f097ca6e2d9b</guid>
            <category><![CDATA[circuit-switching]]></category>
            <category><![CDATA[core-network]]></category>
            <category><![CDATA[packet-switching]]></category>
            <dc:creator><![CDATA[Khushi Sharma]]></dc:creator>
            <pubDate>Sat, 27 Dec 2025 04:36:53 GMT</pubDate>
            <atom:updated>2026-01-10T08:08:16.262Z</atom:updated>
            <content:encoded><![CDATA[<p>Series: Computer Networking from Absolute Basics — Part 3</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JyZzryJQ8JsvgV1Z" /><figcaption>Photo by <a href="https://unsplash.com/@theshubhamdhage?utm_source=medium&amp;utm_medium=referral">Shubham Dhage</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Note: This is Part 3 of a series. If you haven’t read Part 2, I strongly recommend starting there to understand the context: <a href="https://medium.com/bugbountywriteup/deep-dive-into-access-networks-22cda971ce1d">Access Networks</a></p><p>In the earlier parts of this series, we laid the foundation of computer networking by exploring what the Internet is, how end systems communicate, and how access networks such as DSL, cable, FTTH, and mobile networks connect our devices to the larger network. While access networks explain how we get connected, an important question still remains once data enters the network:</p><p><strong>How is that data actually carried from one device to another?</strong></p><p>Networks need a systematic way to move information across links, routers, and switches. Over time, two fundamental techniques have been developed for this purpose:</p><ul><li><strong>Circuit Switching</strong></li><li><strong>Packet Switching</strong></li></ul><p>Although both aim to transfer data from a source to a destination, they operate in very different ways. Circuit switching was the backbone of traditional telephone networks, while packet switching is the core technology behind the modern Internet.</p><p>In this part of the series, we’ll start from absolute basics and explore how both techniques work, why packet switching became dominant, and what trade-offs exist between the two approaches.</p><h3>Packet Switching</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TZ5H4pI1JJxuNqXYeYT6sg.png" /><figcaption>Packet Switching</figcaption></figure><p>When we use the internet, whether to send a message, stream a video, or open a website, data does not travel as one large continuous block. Instead, it follows a method known as <strong>packet switching</strong>, which forms the backbone of modern computer networks.</p><p>Packet switching is connectionless, meaning no dedicated path is established before transmission begins. Packets are sent independently without reserving network resources, and packets belonging to the same message may take different routes depending on current traffic conditions, often arriving out of order.</p><p>To handle this, packets carry sequence numbers, which allow the destination system to reassemble the packets in the correct order before delivering the data to the application. This flexibility makes packet switching efficient and resilient, especially in large and dynamic networks like the Internet.</p><p>Let’s break this concept down step by step.</p><h4><strong>Messages and End Systems</strong></h4><p>In a network application, end systems such as laptops, smartphones, and servers exchange messages designed by application developers. These messages may contain user data or control information. However, sending an entire message as a single large unit would be inefficient and unreliable, which is why packet switching is used.</p><h4><strong>Breaking Messages into Packets</strong></h4><p>Instead of sending a complete message at once, the source system divides it into smaller chunks called <strong>packets</strong>. Each packet travels independently through the network toward the destination.</p><p>Between the source and destination, packets move across:</p><ul><li><strong>Communication links</strong>, and</li><li><strong>Packet switches</strong>, primarily <strong>routers</strong> and <strong>link-layer switches</strong>.</li></ul><p>At the destination, packets are reassembled to reconstruct the original message.</p><h4><strong>Transmission Rate and Packet Delay</strong></h4><p>Every communication link has a <strong>transmission rate</strong>, usually denoted as <strong>R bits per second</strong>. If a packet contains <strong>L bits</strong>, then the time required to push that packet onto the link is:</p><p>Transmission Delay = L/R</p><p>This delay represents the time needed to push all the bits of a packet onto the link, not the time taken to travel through the cable, which is known as <strong>propagation delay</strong> and depends on distance and signal speed.</p><p>As I was reading about this, one question stood out.</p><p>When you hit “send” on a message, do all the bits of your packet instantly appear at the router? If not, how long does it really take for the first and last bits to arrive, and what roles do <strong>transmission delay</strong> and <strong>propagation delay</strong> play in this journey?</p><p><strong>Transmission delay</strong> is the time needed to <strong>push all the bits of a packet onto the link</strong>, calculated as:</p><p>Transmission delay = L/R</p><p><strong>Propagation delay</strong> is the time it takes for the bits to <strong>physically travel across the link</strong>, calculated as:</p><p>Propagation delay = d/s, where d = distance and s = signal speed</p><p><strong>Timeline for a packet from source to router:</strong></p><ol><li><strong>0 sec:</strong> The first bit leaves the source immediately.</li><li><strong>After d/s seconds:</strong> The first bit reaches the router (<strong>propagation delay</strong>).</li><li><strong>After L/R seconds:</strong> The last bit leaves the source (<strong>transmission delay</strong>).</li><li><strong>Total time for last bit to arrive:</strong></li></ol><p>Total time = Transmission delay + Propagation delay = L/R + d/s</p><p>But in this article we will ignore the propagation delay</p><h4><strong>Store-and-Forward Transmission</strong></h4><p>Most packet switches use a technique called <strong>store-and-forward transmission</strong>. This means a router must:</p><ol><li>Receive the <strong>entire packet</strong></li><li>Store it in memory</li><li>Then forward it onto the next link</li></ol><p>The router cannot transmit even the first bit of a packet until it has received the last bit.</p><h4><strong>Sending Multiple Packets</strong></h4><p>Now suppose the source wants to send <strong>three packets</strong>, each of size <strong>L bits</strong>, to the destination.</p><p>Because of <strong>pipelining</strong>, the source and router can work at the same time:</p><ul><li>While the <strong>router is forwarding the first packet</strong>, the <strong>source can start sending the second packet</strong>.</li><li>This overlapping of sending and forwarding makes the process more efficient.</li></ul><p>Here’s what happens over time (ignoring propagation delay for simplicity):</p><ol><li><strong>Time 0 → L/R:</strong></li></ol><ul><li>Source transmits <strong>packet 1</strong> onto the first link.</li><li>Router receives <strong>packet 1</strong> and <strong>starts forwarding</strong> it immediately after receiving the entire packet.</li></ul><p>2.<strong> Time L/R → 2L/R:</strong></p><ul><li>Router is forwarding <strong>packet 1</strong> to the destination.</li><li>Source starts transmitting <strong>packet 2</strong> onto the link.</li></ul><p>3.<strong> Time 2L/R → 3L/R:</strong></p><ul><li>Destination receives <strong>packet 1</strong>.</li><li>Router receives <strong>packet 2</strong> and begins forwarding it.</li><li>Source starts transmitting <strong>packet 3</strong>.</li></ul><p>4.<strong> Time 3L/R → 4L/R:</strong></p><ul><li>Destination receives <strong>packet 2</strong>.</li><li>Router forwards <strong>packet 3</strong>.</li></ul><p>5.<strong> Time 4L/R:</strong></p><ul><li>Destination receives <strong>packet 3</strong>.</li></ul><h4><strong>Generalising the Delay</strong></h4><p>For a path consisting of:<br><strong>n links<br>n − 1 routers</strong></p><p>The end-to-end delay for <strong>one packet</strong> is:</p><p><strong>d = N(L/R)</strong></p><h4><strong>Queuing Delays and Packet Loss</strong></h4><p>So far, we’ve seen how packets are transmitted and forwarded through routers. But in real networks, things aren’t always perfectly smooth. Each router has <strong>multiple links</strong>, and for every link, it keeps a <strong>small memory space called an output buffer</strong> (or output queue). This buffer temporarily holds packets that are waiting to be sent on that link.</p><p>Here’s the catch:</p><ul><li>If a packet arrives at a router but the outgoing link is <strong>already busy transmitting another packet</strong>, the new packet must <strong>wait in the buffer</strong>.</li><li>The time a packet spends waiting is called <strong>queuing delay</strong>.</li><li>Queuing delay is <strong>variable</strong>, depending on how busy the network is at that moment.</li></ul><p>And if the buffer becomes completely full? Some packets might have to be <strong>dropped</strong>, resulting in <strong>packet loss</strong>.</p><h4><strong>Forwarding Tables and Routing Protocols</strong></h4><p>Once a packet reaches a router, the router needs to figure out <strong>where to send it next</strong>. This is where <strong>forwarding tables</strong> and <strong>routing protocols</strong> come in.</p><p>Here’s how it works in the Internet:</p><ol><li>Every device has a unique <strong>IP address</strong>.</li><li>When a source wants to send a packet, it includes the <strong>destination IP address</strong> in the packet.</li><li>When the packet arrives at a router:</li></ol><ul><li>The router checks the <strong>destination address</strong></li><li>Looks up its <strong>forwarding table</strong> to find the appropriate outgoing link</li><li>Forwards the packet onto that link toward the next router</li></ul><p>Forwarding tables are built and updated using <strong>routing protocols</strong>, which help routers learn the network layout and select the <strong>most efficient paths</strong> for packets.</p><p>And that wraps up our deep dive into packet switching, from how packets are transmitted, pipelined, and queued, to how routers use forwarding tables and routing protocols to deliver them efficiently.</p><p>With this understanding, let’s turn our attention to the other major technique: circuit switching, the approach that powered traditional telephone networks and works very differently from packet switching.</p><h3>Circuit Switching</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KEk3JXaYAPLPvDSP4cvXaQ.png" /><figcaption>Circuit Switching</figcaption></figure><p>Circuit switching is a communication technique in which a dedicated, end-to-end communication path is established before any data is transmitted. Once this path is set up, all data flows through the same fixed route for the entire duration of the communication.</p><p>This approach was famously used in traditional telephone networks, where a physical or logical circuit was reserved for a call from start to finish.</p><p>Before any information is sent:</p><ul><li>The network first <strong>sets up a connection</strong></li><li>Resources along the path are <strong>reserved</strong></li><li>Only after this setup is complete does data transmission begin</li></ul><p>Once the circuit is established:</p><ul><li>Data arrives <strong>in order</strong></li><li>Bandwidth is <strong>guaranteed</strong></li><li>No other communication can use that circuit until it is released</li></ul><p>Now that we understand the basic idea behind circuit switching, let’s look at <strong>how it actually works in more detail.</strong></p><h4><strong>Resource Reservation in Circuit Switching</strong></h4><p>In a <strong>circuit-switched network</strong>, the resources required for communication such as link bandwidth and switching capacity are <strong>reserved in advance</strong> for the entire duration of the communication session. Once this reservation is made, those resources are <strong>exclusively used</strong> by the two communicating end systems until the session ends.</p><p><strong>But what exactly is a <em>circuit</em>?</strong></p><p>In networking terms, a <strong>circuit</strong> is a <strong>dedicated logical path</strong> established between the sender and the receiver. This path may pass through multiple switches and links, but from the moment it is set up, all data follows the <strong>same fixed route</strong>, using <strong>pre-allocated resources</strong> at each step.</p><h4><strong>Guaranteed Transmission Rate</strong></h4><p>When a network establishes a circuit, it doesn’t just choose a path it also <strong>reserves a constant transmission rate</strong> along that path. In other words, a fixed portion of each link’s total capacity is set aside exclusively for the connection.</p><p>Because this transmission rate is guaranteed:</p><ul><li>The sender can transmit data at a <strong>steady, predictable speed</strong></li><li>Data arrives <strong>in order</strong></li><li>Delays remain <strong>consistent and bounded</strong></li></ul><p>This is especially useful for applications like traditional voice calls, where a continuous and reliable flow of data is more important than maximizing overall network efficiency.</p><h4><strong>Multiplexing in Circuit-Switched Networks</strong></h4><p>By now, we know one key thing about <strong>circuit switching</strong>:<br>once a connection is set up, the network <strong>reserves resources</strong> for it until the communication ends.</p><p>But here’s the obvious question:</p><p><strong>If one physical link exists, how can multiple calls or connections use it at the same time?</strong></p><p>The answer is <strong>multiplexing</strong>.</p><p>Multiplexing is simply the technique that allows <strong>many circuits to share one physical link</strong>, without interfering with each other.</p><p>In circuit-switched networks, this is done in <strong>two main ways</strong>:</p><ul><li>by dividing <strong>frequency</strong> (FDM)</li><li>or by dividing <strong>time</strong> (TDM)</li></ul><h4><strong>Frequency-Division Multiplexing (FDM)</strong></h4><p>In <strong>FDM</strong>, the link is shared by splitting its <strong>frequency range</strong> into smaller pieces.</p><p>Think of it like this:</p><ul><li>The link has a large frequency spectrum</li><li>Each connection is given <strong>its own frequency band</strong></li><li>That band stays <strong>exclusively reserved</strong> for that connection until it ends</li></ul><p>So even if the user is silent, their frequency band:</p><ul><li>is still reserved</li><li>cannot be used by anyone else</li></ul><p>A very intuitive example is <strong>FM radio</strong>:</p><ul><li>The radio spectrum is shared</li><li>Each station broadcasts on a specific frequency</li><li>Stations don’t take turns, they transmit <strong>at the same time</strong>, but on <strong>different frequencies</strong></li></ul><p>That’s exactly how FDM works in circuit switching.</p><h4><strong>Time-Division Multiplexing (TDM)</strong></h4><p>In <strong>TDM</strong>, instead of splitting frequency, the network splits <strong>time</strong>.</p><p>Here’s the intuition:</p><ul><li>Time is divided into repeating cycles called <strong>frames</strong></li><li>Each frame is divided into small <strong>time slots</strong></li><li>When a circuit is created, <strong>one specific time slot in every frame</strong> is reserved for it</li></ul><p>So the connection:</p><ul><li>gets to send data <strong>at regular intervals</strong></li><li>always in the same slot</li><li>and no other connection can use that slot</li></ul><p>Even if the user sends nothing for a moment, their slot:</p><ul><li>still appears in every frame</li><li>still goes unused</li><li>but remains reserved</li></ul><p>Because these frames repeat extremely fast, communication feels continuous.</p><p>So far, we’ve discussed circuit switching conceptually. But what does this actually mean in practice?</p><p>Let’s walk through a small numerical example to see how data flows in a circuit-switched network and why, once a circuit is established, the transmission time does <strong>not</strong> depend on how many links the data crosses.</p><p><strong>A Numerical Example</strong></p><p>Let’s now consider a concrete example.</p><p><strong>Given</strong></p><p>Suppose:</p><ul><li>A file of <strong>900,000 bits</strong> needs to be sent from <strong>Host A</strong> to <strong>Host B</strong></li><li>The network uses <strong>Time-Division Multiplexing (TDM)</strong></li><li>Each link supports <strong>30 time slots</strong></li><li>The total link transmission rate is <strong>3 Mbps</strong></li><li>It takes <strong>0.4 seconds</strong> to establish an end-to-end circuit</li></ul><p><strong>Step 1: Transmission Rate per Circuit</strong></p><p>In a TDM-based circuit-switched network:</p><ul><li>The total link capacity is shared equally among all time slots</li><li>Each circuit gets <strong>one fixed time slot in every frame</strong></li></ul><p>So the transmission rate available to one circuit is: (3Mbps/30) = 0.1 Mbps=100 kbps</p><p>This rate is <strong>reserved exclusively</strong> for the entire duration of the connection.</p><p><strong>Step 2: Time to Transmit the File</strong></p><p>Now that the circuit exists, data flows at a <strong>constant rate of 100 kbps</strong>.</p><p>The time required to transmit the file is: (900,000 bits) / (100,000 bits/sec) = 9 seconds</p><p><strong>Step 3: Add Circuit Setup Time</strong></p><p>Before any data is sent, the network must establish the circuit.<br>So the total time becomes: 9 seconds+0.4 seconds=9.4 seconds</p><p><strong>Packet Switching vs Circuit Switching: The Key Difference</strong></p><p>Circuit switching and packet switching solve the same problem in very different ways.</p><p>Circuit switching reserves bandwidth in advance, giving predictable delays and guaranteed performance. This works well for traditional voice calls, but it wastes resources when users are idle.</p><p>Packet switching does not reserve resources. Instead, packets share the network dynamically. Although this can lead to variable delays, it uses network capacity far more efficiently by taking advantage of the fact that users send data in bursts rather than continuously.</p><p>This efficiency and scalability are the main reasons packet switching became the foundation of the Internet.</p><p><strong>Conclusion</strong></p><p>In this part of the series, we explored how data moves through a network using <strong>packet switching</strong> and <strong>circuit switching</strong>, and why the Internet ultimately adopted packet switching.</p><p>In <strong>Part 4</strong>, we’ll zoom out and look at the Internet as a <strong>network of networks</strong>, and see how different networks connect to form the global Internet.</p><h3>References</h3><ul><li>James F. Kurose &amp; Keith W. Ross, <em>Computer Networking: A Top-Down Approach</em>, 8th Edition, Pearson.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f097ca6e2d9b" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/how-data-travels-packet-switching-vs-circuit-switching-f097ca6e2d9b">How Data Travels: Packet Switching vs Circuit Switching</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Internet Explained From Absolute Basics]]></title>
            <link>https://meetcyber.net/the-internet-explained-from-absolute-basics-ff02f26d8900?source=rss-3a9366cdc931------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff02f26d8900</guid>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[internet-service-provider]]></category>
            <category><![CDATA[protocol]]></category>
            <dc:creator><![CDATA[Khushi Sharma]]></dc:creator>
            <pubDate>Fri, 19 Dec 2025 14:42:48 GMT</pubDate>
            <atom:updated>2025-12-19T14:42:48.649Z</atom:updated>
            <content:encoded><![CDATA[<p>Series: Computer Networking from Absolute Basics — Part 1</p><p>I’ve been reading a book called <strong><em>Computer Networking: A Top-Down Approach </em></strong>by James F. Kurose and Keith W. Ross<strong><em>. </em></strong>In this blog, I’ll explain the topics that I learned today, starting from the absolute basics.</p><p>I’ll begin with what the Internet actually is. Everybody uses it, but theoretically, many people don’t really know how to define it and that’s completely okay. Even I didn’t know earlier. But instead of overthinking that, let’s not waste time and just dive in.</p><h3>INTERNET</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1bOfnusWbkfzDXUS" /><figcaption>Photo by <a href="https://unsplash.com/@alinnnaaaa?utm_source=medium&amp;utm_medium=referral">Alina Grubnyak</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The<strong> Internet</strong> is a computer network that connects billions of computing devices all over the world. If you’re a complete beginner, don’t stress — I’ll explain everything step by step.</p><p>A<strong> computer network</strong> is a system where two or more computing devices are connected so they can share data, resources, and communicate with each other.</p><p>You might now wonder: what exactly is a computing device?</p><p>A <strong>computing device</strong> can be anything—desktop computers, servers, smartphones, tablets, and more. All of these devices are called hosts or end systems. End systems are called hosts cause they host various application programs.</p><h3><strong>How are these end systems connected?</strong></h3><p>End systems are connected together by a network of communication links and packet switches.</p><ul><li><strong>Communication links</strong> include fiber-optic cables, copper wires, and wireless links</li><li><strong>Packet switches</strong> are devices that forward data through the network</li></ul><p>Together, these components form the backbone of the Internet.</p><p>Let’s dive into another interesting question…</p><h3><strong>How does data travel on the Internet?</strong></h3><p>When data is sent from one end system to another, it does not move as a single large unit. Instead, the data is divided into smaller, organised pieces called packets.</p><p>Each packet travels independently through the network, possibly taking different paths. Once all packets reach the destination, they are reassembled to recreate the original data.</p><p>The next obvious question is:</p><h3><strong>Where does the Internet come from?</strong></h3><p>We get Internet access from ISPs (Internet Service Providers). Just like we get electricity from an electric company, we get Internet access from an ISP.</p><p>An ISP connects your device to the global internet, owns routers, cables, and towers, and charges you a monthly fee for the service.</p><p>So far, we’ve talked about:</p><ul><li>What the internet is</li><li>What end systems are</li><li>How they are connected</li><li>How data is sent in the form of packets</li><li>where does the internet access come from</li></ul><p>But knowing all this brings up an important question.</p><p>If billions of devices are connected and packets are constantly moving across the network, how do all these devices know what to do with the data they receive? How does one device know when to send data, how to send it, or how to understand the data coming from another device. This is where<strong> protocols</strong> come into picture.</p><p>Think of protocols like rules in a conversation. When two people talk, they unconsciously follow certain rules: when one speaks, the other listens, both understand the same language, and they know when the conversation starts and ends.</p><p>In the same way, a protocol is a set of rules that devices follow to communicate with each other over the internet. These rules decide:</p><ul><li>How data is formatted</li><li>How it is transmitted</li><li>How errors are handled</li><li>What actions are taken when communication doesn’t go as expected</li></ul><p>Without protocols, devices could be connected to the same network and still fail to communicate properly, because there would be no common agreement on how communication should happen.</p><p>For now, this blog was just about building comfort with the basics. I’m still learning myself, so if you notice any mistakes or have suggestions, I’d love to hear them. I know you’ll probably have many more questions, just like I did , but don’t worry. We’ll explore everything in detail later.</p><h3><strong>References</strong></h3><ul><li>James F. Kurose &amp; Keith W. Ross, <em>Computer Networking: A Top-Down Approach</em>, 8th Edition, Pearson.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff02f26d8900" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/the-internet-explained-from-absolute-basics-ff02f26d8900">The Internet Explained From Absolute Basics</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ABOUT ME]]></title>
            <link>https://medium.com/@khushisharmadubai/about-me-27c66d2bd8eb?source=rss-3a9366cdc931------2</link>
            <guid isPermaLink="false">https://medium.com/p/27c66d2bd8eb</guid>
            <category><![CDATA[students]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Khushi Sharma]]></dc:creator>
            <pubDate>Thu, 18 Dec 2025 11:10:16 GMT</pubDate>
            <atom:updated>2025-12-18T11:10:16.268Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello Everyone,</p><p>I’m Khushi Sharma, a Computer Science Engineering student with a strong interest in cybersecurity.</p><p>Over the past year, I found myself constantly thinking about whether I should seriously pursue cybersecurity or not. Most of the conversations around me, especially during campus placements, were focused on software development and software engineering roles. Because of that, I was skeptical and honestly procrastinated for quite some time.</p><p>But eventually, I realised something important: this is the field I’m genuinely passionate about and want to grow in. I’ve already completed an internship in cybersecurity, and that experience further confirmed that this is the path I want to follow.</p><p>I’ve started writing on Medium to share my learning journey. I’ll be writing about everything I learn, starting with the basics and foundational topics, because I truly believe that without strong basics, nothing meaningful can be built.</p><p>The idea here is simple:</p><ul><li>I share what I learn, in an easy and practical way.</li><li>If I’m wrong somewhere, I genuinely welcome corrections.</li><li>This becomes a two-way learning process</li></ul><p>I wouldn’t call myself a writer. I’m more comfortable making notes and I make pretty good ones. Writing about my thoughts and experiences is new to me, but I want to start. This is as much for my own growth as it is for anyone who finds value in reading along.</p><p>If you’re someone who’s learning, confused, or just curious about cybersecurity, you’re welcome here. Let’s learn together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27c66d2bd8eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>