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

1. IP Addressing: IPv4, Subnets, Public and Private IPs

1.1 What Is an IP Address?

By Last updated:

In short: An IP (Internet Protocol) address is a logical number that identifies a device (host) on a network.

Mitrano, IP address mhanje network var pratyek device cha "postal address". Tumcha mobile, laptop, EC2 server, router – sagalyanna ek IP asto. Router tya address kade baghun packet pudhe pathavto.

An IP (Internet Protocol) address is a logical number that identifies a device (host) on a network. Every packet carries a source IP (who sent it) and a destination IP (where it must go).

  • IPv4 example: 192.168.1.10 (32 bits) – still the most common, and the focus of this chapter
  • IPv6 example: 2001:db8::10 (128 bits) – the newer version with a much larger address space

Analogy – aani khara mechanism

Pune madhe Shivaji Nagar chya ekhadya building cha address mhanje IP address, aani building madhla flat number mhanje port (pudhchya chapter madhe). Postman (router) building paryant pohochavto; watchman (operating system) patra yogya flat madhe (application) deto.

Lakshat theva – he fakt analogy aahe. Khara mechanism asa: every packet has a destination IP in its IP header; each router compares that IP with its routing table (longest matching prefix wins) and forwards the packet to the next hop.

Why this matters for security

Every log line, firewall rule and alert is written in terms of IP addresses. When a SOC analyst says "brute force from 198.51.100.7", the IP is the first clue. Attackers also hide behind other IPs (VPNs, proxies, compromised machines), so an IP identifies a network location, not a person.

Ravindra Bagale's Tip

Many students think an IP address is "a computer's permanent identity" and say "this IP means this person". That's wrong – many devices can share one IP (NAT), and a device's IP can change (DHCP). If you see an IP in a log, say "the request came from this IP", not straight away "this is the attacker".

Practice task

On your laptop run ipconfig (Windows) or ip addr (Linux/Mac). Note your IPv4 address and write down whether it looks like a home/office (private) address.

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.