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

50. Glossary (Marathi column)

50.1 How to use this glossary

By Last updated:

Pehle columns, mag tables. Glossary = pocket dictionary for what you already practised. Samjla ka?

Three columns (classroom rules):

  1. Term – exact English you use in tickets, labs and interviews.
  2. Meaning – one short English sentence (no story dump).
  3. मराठी अर्थ – Devanagari for hard / abstract ideas; for everyday tech English write — (English madhech vapra) and keep saying the English word in class.

How to revise:

  1. Hard word visarla → ithe bagha → chapter number notebook madhe note (e.g. Encryption → ch33).
  2. Interview / SOC ticket → prefer precise English; Marathi column is for classroom clarity, not for mixing scripts in a ticket.
  3. Red jargon rattlo ≠ Blue skill – every term needs one defender sentence.
  4. Ethics line every session – “Do I own this / have paper?” before you practise a tool named in a definition.
Red team (attacker) does Blue team (defender) detects / stops
Collects jargon to brag / scan random IPs Uses precise terms in tickets, IR notes and scope docs
Mixes Devanagari into production logs “for fun” Keeps tickets in clean English; uses Marathi only in class notes
Treats glossary as exploit cookbook Maps each term to OWN-lab practice + one Blue control

Ravindra Bagale's Tip

Students print the glossary and try “recon” on cafe Wi-Fi – knowing a word ≠ having permission. In column 3, don't force Devanagari onto everyday words (file, password, port stay in English). In interviews, no Marathi dump – clean English + control language. Remember this.

Lab

Open this chapter and pick five hard terms you already saw in the book. Write: (1) Meaning in your own words, (2) one Blue control sentence, (3) which OWN lab chapter you practised it in. No cafe targets. No inventing numbers.

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.