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

50. Glossary (Marathi column)

By Last updated:

Chala mitrano, Part 13 continue – aata glossary / shabdakosh. Book madhe hard words sobat Devanagari arth disla asel – ithe ek jaga var sabda-sangrah. Columns: Term | Meaning | मराठी अर्थ. Hard / abstract terms = Devanagari; rojche English shabd (file, folder, server, port, website, table, password, command, filter) = — (English madhech vapra). Ethics pehle: terms mahiti asne ≠ attack permission. OWN lab, host-only 192.168.56.x, written authorisation. Cafe / neighbour / client – never. Ghabru naka – patkan shodh, Blue control lakshat theva. He khup important aahe, lakshat theva!

What you will practise in this chapter

  • How to use the glossary columns (Term / Meaning / मराठी अर्थ)
  • Core security terms (CIA, threat, risk, malware, MFA, …)
  • Networking, Linux and AWS terms
  • Web, MySQL, OWASP and Kali lab terms
  • SOC, Indian cyber law, AD, malware, mobile/IoT terms
  • Red vs Blue glossary misuse, Build-Hack-Fix project, real incidents

Lab scope

Glossary madhe attack jargon asel – vocabulary, not a hunting licence. Every Red-looking term means: only systems you own (host-only VirtualBox Kali 192.168.56.10, Metasploitable 192.168.56.20, DVWA/Juice 192.168.56.30–.50, your Free Tier EC2) or written scope. Knowing “exploit” / “payload” English does not authorise scanning a cafe Wi-Fi. IT Act sections such as 43 and 66 apply without authority (verify current text). Terms = clear thinking. Lab = learn. Production = defend.

Concepts in this chapter

  1. 50.1How to use this glossary
  2. 50.2Core security terms
  3. 50.3Networking, Linux and AWS terms
  4. 50.4Web, MySQL, OWASP and Kali terms
  5. 50.5SOC, law, AD, malware, mobile/IoT terms
  6. 50.6Red vs Blue, Project and Real Incidents

The chapter recap is at the end of the last concept page.

Chapter 50: Glossary (English–Marathi) — practice tasks

Open chapter lessons · Full guided lab: glossary flashcards english marathi (not repeated here)

50.1 10 flashcards from the glossary

EasyIT

Why: Bilingual terms help interviews in Maharashtra.

What: Make 10 cards: English / Marathi / one example.

How:

  1. Use the course glossary.
  2. Include IP, firewall, phishing, encryption, malware.

Expected output: 10 cards.

Hint

See linked flashcards lab.

Answer / how to check
  1. You can say all 10 English terms from Marathi.

50.2 Explain phishing in Marathi

MediumRetail

Why: Family awareness reduces home risk.

What: Write a 1-minute Marathi script (or record audio).

How:

  1. Cover fake messages, don't click, call 1930 if money lost.

Expected output: 1-minute script/audio.

Hint

Keep words simple.

Answer / how to check
  1. A family member understands.

50.3 Fill glossary gaps

EasyHealthcare

Why: Write terms you still mix up.

What: Add 5 new rows you struggled with this course.

How:

  1. Term, simple English, Marathi if you know, chapter.
  2. Share with a study buddy.

Expected output: 5 new rows.

Hint

Revisit weekly.

Answer / how to check
  1. Each row has a chapter number.

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.