Cybersecurity Glossary: Key Words Explained Simply

Cybersecurity · Plain English

Cybersecurity Glossary: Key Words Explained Simply

AK Ankit Kaushik · Lead Trainer, Data Engineering & AI | Updated 12 November 2026 | 14 min read Free · Glossary

The four pillars of any cybersecurity glossary — threats, defences, crypto, and compliance.

Quick summary — the cybersecurity glossary

Cybersecurity is full of jargon — but the underlying ideas are simple. This glossary covers 30+ essential terms in four categories: threats, defences, cryptography, and compliance — each with a plain definition and a real-world example.

In this guide you will learn:

Threat terms — malware, phishing, ransomware, DDoS.
Defence terms — firewall, IDS, MFA, zero-trust.
Cryptography terms — AES, RSA, hashing, TLS.
Compliance terms — GDPR, HIPAA, ISO 27001, DPDP.
Interview Q&A + quiz to test your understanding.

SECTION 01Threats — what attacks look like

These are the words you'll hear when someone is trying to break into a system. Knowing them precisely makes you sound like a pro in interviews:

Term	Plain English	Real-world example
Malware	Software designed to harm or steal	Trojan hidden in a free PDF reader
Virus	Malware that attaches to files and spreads	Word macro that infects shared docs
Worm	Malware that spreads without user action	WannaCry spreading over networks in 2017
Trojan	Malware disguised as legitimate software	Fake "Chrome update" installer
Ransomware	Malware that locks your files until you pay	Hospital systems locked, ₹ crores demanded
Phishing	Fake emails / messages asking for credentials	"Your bank account is frozen — click here"
Spear phishing	Targeted phishing using real details	Email referencing your manager by name
Social engineering	Manipulating people to break security	Caller pretending to be IT support
Zero-day	An attack on a bug with no patch yet	Chrome exploit used before Google fixes it
DDoS	Flooding a server until it crashes	Thousands of bots hitting a gaming server

Key insight: In interviews, always pair a term with an example. "Ransomware is malware that encrypts files and demands payment — like WannaCry in 2017" is 10× stronger than a textbook definition.

SECTION 02Defences — how we protect systems

Every defence is a wall. These are the walls most teams build — and the terms you must know to talk to them:

Term	Plain English	Example
Firewall	Filters network traffic like a security guard	Blocks port 22 from outside the office
IDS	Intrusion Detection System — alerts on suspicious activity	Warns you: "someone is port-scanning you"
IPS	Intrusion Prevention System — blocks, not just alerts	Auto-drops traffic from blacklisted IPs
MFA	Multi-factor auth — two or more proofs of identity	Password + OTP from phone
VPN	Encrypted tunnel for your traffic	Working from café without exposing data
Zero-trust	Trust nothing, verify everything	Every request re-authenticated, even inside office
SIEM	Central dashboard collecting security logs	Splunk showing a login attack across services
EDR	Endpoint Detection & Response — monitors laptops/servers	CrowdStrike catching a suspicious script
Patch management	Keeping software updated to fix known bugs	Windows update fixing a critical flaw
Least privilege	Every user gets the minimum access needed	Developer can't delete production DB

SECTION 03Cryptography — how encryption works

Cryptography terms sound scary — but the underlying ideas are intuitive. Here's what matters:

Term	Plain English	Example
Encryption	Scrambling data so only the right key can read it	WhatsApp message turning into unreadable text
Symmetric encryption	Same key to lock and unlock	AES — used in most disk encryption
Asymmetric encryption	Public key to lock, private key to unlock	RSA — used in HTTPS handshakes
Hashing	One-way fingerprint of data — can't be reversed	SHA-256 hash of a file to detect tampering
Salt	Random data added before hashing passwords	bcrypt + unique salt per user
Digital signature	Proves a file was made by you, unmodified	Signed software update from a vendor
TLS	The lock icon on websites — encrypted HTTP	Bank website over HTTPS
Certificate	Proof that a website is who it claims to be	issued by Let's Encrypt / DigiCert

import hashlib, os

# Password hashing with salt
password = b"MyStrongPassword123"
salt = os.urandom(16)

# Add salt, then hash
hashed = hashlib.pbkdf2_hmac('sha256', password, salt, 100_000)
print(hashed.hex())

# Store (salt + hash) — never store the raw password

from cryptography.fernet import Fernet

# Generate a symmetric key
key = Fernet.generate_key()
cipher = Fernet(key)

# Encrypt / decrypt
message = b"Top secret"
encrypted = cipher.encrypt(message)
print(encrypted)

decrypted = cipher.decrypt(encrypted)
print(decrypted.decode())

crypto-basics.py

Key insight: For passwords, always hash (never encrypt). For data in transit, encrypt. For file integrity, hash. These three use-cases cover 80% of interview crypto questions.

SECTION 04Compliance — the rules that matter

Compliance terms are the legal side of cybersecurity. Every serious organisation deals with at least one of these:

Term	Plain English	Applies to
GDPR	EU's data protection law	Anyone processing EU residents' data
HIPAA	US law protecting health data	Healthcare providers and their vendors
PCI-DSS	Rules for handling card data	Anyone storing/processing card payments
ISO 27001	Global standard for information security management	Any company wanting certified security practices
SOC 2	Audit report proving security controls	SaaS vendors
DPDP	India's data protection law	Indian companies handling personal data
NIST	US framework for security best practices	Reference for security programmes globally

Pro tip: Don't memorise every clause — instead, learn what kind of data each regulation protects. That's what interviewers actually check.

SECTION 05Common confusions to avoid

Virus vs worm vs trojan — viruses need a host file, worms spread on their own, trojans disguise as useful software.
Encryption vs hashing — encryption is reversible (with key), hashing isn't.
Authentication vs authorisation — authn is "who are you", authz is "what can you do".
IDS vs IPS — IDS detects, IPS prevents.
Vulnerability vs exploit vs threat — vulnerability is the flaw, exploit is the attack code, threat is the actor.
Zero-day vs malware — zero-day is a timeline, malware is a category. Different things.

SECTION 06Interview Q&A — cybersecurity glossary

Q1What's the difference between a virus and a worm?

A virus needs a host file (and usually a user to open it) to spread. A worm spreads on its own over the network without user action. Worms are generally more dangerous because they can spread faster.

Q2What's the difference between encryption and hashing?

Encryption is reversible: you can decrypt with the right key. Hashing is one-way: you can't get the original back. Use encryption for data in transit / at rest, hashing for passwords and file integrity checks.

Q3What does zero-trust mean?

Zero-trust means "never trust, always verify." Instead of trusting everything inside the office network, every request is re-authenticated and authorised based on context (device, user, location).

Q4What's a zero-day vulnerability?

A flaw in software that is being exploited before the vendor has released a patch. Developers have "zero days" to react — hence the name. These are the most dangerous flaws because standard defences can't detect the exploit yet.

Q5What does MFA protect against?

MFA protects against password theft. If an attacker gets your password, they still can't log in without the second factor (OTP, app push, hardware key). It's the single highest-impact security control you can enable.

SECTION 07Test yourself — cybersecurity glossary quiz

Five questions. No sign-up.

0 / 5

Pick an answer to see why it is right or wrong.

SECTION 08Frequently asked questions

Do I need to memorise all these terms?

No — but you need to understand them. Memorising definitions without examples is a red flag in interviews. Focus on plain meaning + one real example per term.

Which terms should a beginner learn first?

Start with: malware, phishing, ransomware, firewall, MFA, encryption, hashing, and CIA triad (confidentiality, integrity, availability). These cover 70% of beginner conversations.

What's the CIA triad?

Confidentiality (only authorised people can see data), Integrity (data can't be tampered with), and Availability (systems are up when needed). Every security control maps to at least one of these.

Do I need to learn cryptography deeply?

Only at a conceptual level for most cybersecurity roles. You need to know when to use encryption vs hashing, and how TLS works at a high level. The math behind AES or RSA is only necessary for cryptography-specialist roles.

Is GDPR relevant if I'm in India?

Yes — if you handle EU residents' data, GDPR applies to you regardless of where you are. Additionally, India's own DPDP Act governs personal data processing in India.

What I would do in the first 30 daysLayoff · 14 min Why sending 500 resumes won't workJob Search · 14 min Rebuild your resume for the AI job marketResume · 15 min Which skills to learn before applyingSkills · 14 min 90-day career recovery roadmapRecovery · 16 min How AI can help you prepare for interviewsAI · 11 min

Classroom & online · Noida

Learn cybersecurity from the ground up

Our Cybersecurity Training Programme covers every term in this glossary in real depth — with hands-on labs, real attacks, and interview prep.

₹15,500 · full programme ~~₹24,000~~

Explore the course Download the syllabus

Hands-on security labs
Real attack simulations
Interview prep
Weekday & weekend batches

Cybersecurity Glossary: Key Words Explained Simply