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

26. Privilege Escalation

26.6 Defending Against Privilege Escalation

By Last updated:

He sagla shiklyacha khara faayda – system asalamat thevne:

Defence What it stops
Least privilege Give users/services only what they need; a foothold stays limited
Careful sudo rules Never give broad NOPASSWD or editors/shells via sudo
Remove unnecessary SUID bits Fewer SUID binaries = fewer escalation paths
Correct file/dir permissions No world-writable scripts that root runs
Patch the kernel and packages Closes local exploits (sudo yum update)
Separate service accounts A hacked web app runs as www-data, not root
Auditing and monitoring Detect enumeration and unexpected root shells (Part 11 SOC)

For your own reels app and servers: run the web server and PHP as a low-privilege user, keep the OS updated with sudo yum update, and never store passwords or AWS keys in world-readable files.

Why this matters for security

A single low-privilege foothold is limited; privilege escalation is what turns a small breach into a full compromise. Enforcing least privilege and patching removes most escalation paths, so even a successful intrusion causes far less damage.

Ravindra Bagale's Tip

The biggest mistake: running a web app as root "because it makes everything easier". Never do this – if that app is hacked, the attacker gets root directly. Always run services as a least-privilege user. This one rule stops a lot of breaches.

Lab

On your own EC2 server, list SUID binaries and confirm your web app runs as a non-root user (ps aux | grep -E 'apache|nginx|php'). Then run sudo yum update and, in your notes, write two least-privilege changes you made or would make.

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.