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

41. Session Hijacking – Tokens, Cookies and Defence

41.10 Putting It Together – Purple Team Mindset

By Last updated:

Thodkyaat: session chapter = token identity + cookie flags + fixation/XSS/sniff/JWT pitfalls + detect + checklist + ethics + Build-Hack-Fix. Tools change; habit (regenerate, HTTPS, HttpOnly, own-lab only) rahate.

Interview model (clean English): "I treat session IDs as bearer credentials. In the lab I replay my own app's cookie, then enforce Secure, HttpOnly, SameSite, regenerate-on-login, and short TTLs. I do not capture sessions on networks I do not own."

Red team (attacker) does Blue team (defender) detects / stops
Full chain in lab: weak PHP → steal cookie → replay dashboard Purple Team: HTTPS + flags + regenerate + TTL proven
Shames SME after staff account takeover Helps SME kill sessions, force password reset, add MFA; documents lessons for Raja/Rani

Ravindra Bagale's Tip

Password hashing may be strong, but if the session is weak, the account is still gone. You need both hashing and session hygiene. Next up: IDS / firewall / honeypot evasion themes – Blue detection games!

Lab

Chapter project (41.9 box) complete kara. Mag 10 flashcards: session, cookie, Secure, HttpOnly, SameSite, fixation, regenerate, sidejacking, HSTS, JWT pitfall. Pair: ek Red "how identity moves", ek Blue "how we bind and kill sessions".

Thodkyaat sangaycha tar

  • HTTP is stateless – sessions / cookies / tokens carry identity after login.
  • Hijacking = use victim's valid session without their password – hits confidentiality + integrity of identity.
  • Cookie flags: Secure, HttpOnly, SameSite; pair with HTTPS + HSTS.
  • Fixation → regenerate session ID on login; avoid SID in URL; strong random IDs.
  • XSS can steal non-HttpOnly cookies and still abuse sessions – encode, CSP, fix XSS.
  • Sniffing lesson (Firesheep era): cleartext cookies on open Wi-Fi – lab demo on OWN HTTP only.
  • App layer: CSRF ≠ cookie theft but needs SameSite + CSRF tokens; JWT needs careful TTL/storage/validation.
  • Detect concurrent SID use, UA/IP anomalies; log session lifecycle; SIEM alerts.
  • Defence checklist + MFA + server-side logout invalidate + WAF support.
  • Lab ethics: own host-only PHP only; IT Act awareness; Project Build-Hack-Fix for Raja-Rani portal.

Samjla ka? Session hijacking shiklo – pan pratyek sobat bachav ani safe lab. Pudhchya chapter madhe **IDS, firewall and honeypot evasion** (defender detection games, still ethics-first) – CEH modules pudhe. Chala pudhe, mitrano!

Extended teaching notes

Why this lesson matters

Web flaws stay in the OWASP Top 10 because real apps still ship them. Your job is not to collect tool screenshots. It is to prevent and fix the class of bug on systems you own.

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.

Real examples

Global: injection and XSS still appear in breach reports and bug bounties every year. Indian company (sample): a Bengaluru SaaS team maps each OWASP item to a CI check or a code-review question so new code cannot silently reintroduce it.

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.