49.6 Quick Combined Revision Card
Ek dense card – situation bagha, tool recall, Blue control. Print kara. Samjla ka?
| Situation | Linux / MySQL / Nmap / MSF recall | Blue control |
|---|---|---|
| Need listening ports on OWN host | Linux: ss -tulpn | Close unexpected; firewalld/SG |
| Patch Amazon Linux | sudo yum update -y | Schedule; reboot if kernel needs |
| Restart httpd after config test | sudo apachectl configtest then sudo service httpd restart | Never reload blind |
| SSH harden | Keys; PasswordAuthentication no; sudo service sshd restart | fail2ban; restrict SG source |
| MySQL only local | bind-address=127.0.0.1; app user GRANT minimal | Deny 3306 from internet |
| Avoid wipe UPDATE | SET SQL_SAFE_UPDATES=1; + WHERE on key | Backups; change tickets |
| SQLi in PHP form | (App) prepared statements – ch29 | Least DB priv; input allow-lists |
| Map OWN lab host ports | sudo nmap -sS -T2 -p 22,80,443,3306 192.168.56.20 -oN … | Alert mindset for mass SYN |
| Version banners on OWN VM | nmap -sV -T2 … | Patch old banners first |
| Understand attacker module flow | MSF: search → use → set RHOSTS/LHOST → check → exploit (Metasploitable only) | Patch; disable service; re-scan |
| Lab evidence pack | nmap -oA; tar -czvf; note hashes | Keep under ~/labs/; no real org names |
| Disk full / logs gone | df -h; du -sh; rotate logs | Alert on disk; immutable log mindset ch31 |
| Red team (attacker) does | Blue team (defender) detects / stops |
|---|---|
| Revises only Red flags from this card | Revises situation + Blue column aloud weekly |
| Mixes cafe IP into Nmap/MSF lines | Hard-codes host-only examples in notebook |
Ravindra Bagale's Tip
Stick the combined card on the wall – but highlight the Blue column. In exams and interviews, “situation → control” is stronger than a “tool dump”. A blank Blue column = incomplete. This wins. Remember this.
Ravindra Bagale's Tip – मराठी
Combined card भिंतीवर चिकटवा – पण Blue column highlight करा. Exam / interview मध्ये “tool dump” पेक्षा “situation → control” strong. Blank Blue = incomplete. हे जिंकते. लक्षात ठेवा.
Ravindra Bagale's Tip – हिंदी
Combined card दीवार पर चिपकाओ – पर Blue column highlight करो. Exam / interview में “tool dump” से ज़्यादा “situation → control” strong है. Blank Blue = incomplete. यही जिताता है. याद रखो.
Lab
With Amir or Zoya: quiz ten random rows from the combined card. Answer format: (1) commands, (2) one Blue sentence, (3) which OWN IP you would type. Wrong IP range = restart the quiz.
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)
- Write the lesson title, date and the exact lab target you are allowed to use.
- List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
- Run one safe check from the lesson on a lab system only. Paste the command and output.
- Write a two-sentence fix you would give a teammate.
- 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.