Ravindra BagaleCourses & study guides मराठी Track your progress

3. OSI Model, TCP/IP Model, TCP vs UDP and the 3-Way Handshake

3.2 Encapsulation and Decapsulation

By Last updated:

Mitrano, data khali jatana (sender side) pratyek layer swatahcha header laavto – jasa parcel var ek ek label chikatavla jato. Receiver side la ulta hota – pratyek layer aapla label kadhun data varchya layer la deto. Yala encapsulation (आवरण घालणे) aani decapsulation mhantat.

As data moves down, each layer adds its own header (Layer 2 also adds a trailer):

 L7-5   [                 HTTP data                   ]
 L4     [TCP hdr: ports ][        HTTP data           ]            = Segment
 L3     [IP hdr: IPs][TCP hdr][      HTTP data        ]            = Packet
 L2     [Eth hdr: MACs][IP][TCP][    HTTP data   ][FCS]            = Frame
 L1     0101100101110100101010010101001010101010101...            = Bits
Layer Header adds Example value
Transport (L4) Source and destination port 51544 → 443
Network (L3) Source and destination IP, TTL 192.​168.​1.​10 → 203.​0.​113.​10
Data Link (L2) Source and destination MAC, FCS trailer 0a:​1b:​2c:​3d:​4e:​5f → router MAC

Wireshark madhe ek packet open kela ki exactly hech layers khalun var distat – Frame, Ethernet II, Internet Protocol, TCP, HTTP. Mhanun encapsulation samjla tar Wireshark aapoaap samjel.

Why this matters for security

Every header is a field an attacker can forge or read: a spoofed source IP (L3), a fake MAC in ARP spoofing (L2), crafted TCP flags in stealth scans (L4). Packet filters read L3/L4 headers only; a WAF reads the L7 payload. Knowing which header a control inspects tells you what it can and cannot stop – and never trust a header just because it is present.

Ravindra Bagale's Tip

Many students mix up the PDU names and use "packet" for every layer. Be precise in interviews: L4 = segment (TCP) / datagram (UDP), L3 = packet, L2 = frame, L1 = bits. This small distinction shows that your concepts are clear.

Practice task

First, on paper, write the headers that are added to an HTTP request as it travels from L7 down to L2, and the address or number each header contains. Then open any capture in Wireshark (or the sample captures on the Wireshark wiki), click one HTTP packet and check your answer: note the source/destination MAC, IP and port from the three header sections.

Extended teaching notes

Why this lesson matters

Use this lesson to strengthen systems you own: understand the risk, practise safely in a lab, then write and apply the fix.

Apply the fix across stacks

Same class of bug, same idea in every language.

Java / Spring Boot

Parameterise queries, encode output, CSRF tokens, limited Actuator, dependency scanning.

ASP.NET Core

EF Core / parameterised SQL, Razor encoding, HTTPS, Data Protection.

Node.js / Express

helmet, parameterised SQL, npm audit, avoid eval and shell concat.

Python / Django / Flask / FastAPI

ORM, autoescape, pip-audit, Bandit; never shell=True with user input.

PHP / Laravel

PDO/Eloquent, Blade escaping, composer audit.

Go / Ruby

database/sql placeholders / ActiveRecord; html/template / ERB escaping; govulncheck / Brakeman.

nginx / Apache / Tomcat

Hide versions, TLS, security headers, least-open ports.

MySQL / PostgreSQL / MongoDB / Redis

Private networks, auth on, least-privilege users, no 0.0.0.0/0.

AWS / Azure / GCP

Roles not long-lived keys, private data stores, cloud audit logs on.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.