Dictionary WikiDictionary Wiki

Cybersecurity Vocabulary: Security and Hacking Terms

A close-up image of a hand using a pen to point at text in a book.
Photo by Tima Miroshnichenko

Every data breach that hits the news drags the same cloud of jargon with it: zero days, phishing kits, lateral movement, ransomware-as-a-service. You don't have to be a security engineer to want a translator. Whether you're an IT manager shopping for tools, a developer reading a pen-test report, or an ordinary user trying to figure out what your bank's security alert actually means, a working vocabulary goes a long way. This guide walks through the terms that matter across threats, attacks, encryption, networks, authentication, incident response, and compliance.

1. The Building Blocks of Cybersecurity

Before getting into specific threats or tools, it helps to pin down what cybersecurity actually covers and the handful of concepts every practitioner returns to.

Cybersecurity — The mix of technology, policy, and human habits used to keep computer systems, networks, software, and data safe from intrusion, disruption, or theft.
Information security — A wider umbrella than cybersecurity alone: the protection of information in any form, from paper files in a cabinet to encrypted records on a cloud server.
CIA triad — The three-letter mental model that anchors the field: Confidentiality, Integrity, and Availability—keep data private, keep it accurate, and keep it reachable for the people who are supposed to use it.
Vulnerability — Any weak spot—an unpatched bug, a misconfigured server, a careless setting—that an attacker could exploit to get where they shouldn't.
Threat — A realistic source of harm to your data or systems: a hacker with motive, a disgruntled employee, a storm that floods a data center, even a fat-fingered admin command.

Everything that follows in this guide is really a deeper look at where these five ideas meet in the real world.

2. Who and What Is Out There

The threat landscape stretches from opportunistic malware scanning the internet for low-hanging fruit to nation-state teams sitting quietly inside networks for years. Knowing the categories is the first step toward anticipating them.

Malware — A catch-all term for hostile software, covering viruses, worms, trojans, rootkits, ransomware, spyware, and anything else designed to damage or secretly control a device.
Ransomware — Malware that locks up files or entire systems with encryption and demands payment—typically in cryptocurrency—before the attacker releases the key (assuming they even do).
Phishing — A con played over email, text, or chat that impersonates a trusted sender to trick the victim into handing over credentials, clicking a malicious link, or installing something nasty.
Trojan horse — Malware that ships inside something that looks useful—a free utility, a cracked game, a fake browser extension—and quietly opens a door for the attacker once installed.
Spyware — Software that runs in the background gathering information about what a user types, visits, or stores, usually without any visible sign that it's there.

Pattern-match against this list and most consumer-level threats suddenly become recognizable rather than mysterious.

3. How Attackers Actually Break In

Threats describe the who and the what; attack methods describe the how. These techniques show up in breach reports again and again.

Social engineering — Manipulating a person instead of a computer—through flattery, urgency, authority, or plain old lying—to get them to hand over a password, click a link, or wire money.
Brute force attack — Grinding through every possible password or key with automated tools; slow against well-chosen passwords, devastating against weak or reused ones.
DDoS (Distributed Denial of Service) — Flooding a service with junk traffic from thousands of compromised devices at once, so real customers can't get through while the defender tries to filter the noise.
Man-in-the-middle attack — Quietly sitting between two parties who think they're talking directly, reading their conversation and sometimes changing messages on the fly.
SQL injection — Slipping crafted database commands into a web form or URL so they run against the application's database, often dumping or altering data that should be private.

Every one of these has a known countermeasure; the point of learning the vocabulary is to recognize which defense belongs to which attack.

4. Encryption, Keys, and Cryptography

Cryptography turns unreadable math into practical protection. The vocabulary below shows up in everything from HTTPS bars in your browser to the way your messaging app claims to keep chats private.

Encryption — Scrambling data with an algorithm and a key so that whoever intercepts it sees gibberish; only someone with the right key can reverse the scramble.
Decryption — The reverse of encryption: feeding ciphertext plus the correct key back through the algorithm to recover the original message.
Public key cryptography — A clever setup that uses two mathematically linked keys—a public one you can share, and a private one you guard—so strangers can send you secret messages without ever having met.
SSL/TLS — The protocol family that puts the "s" in HTTPS, wrapping web traffic in an encrypted, authenticated channel so your login doesn't sail across the network in plaintext.
End-to-end encryption — A design choice in which only the sender's and recipient's devices hold the keys, meaning the service routing the messages physically cannot read them.

You don't need to implement any of this from scratch to benefit from it—but you do need the words to evaluate whether a vendor is actually offering what they claim.

5. Protecting the Network

Most breaches travel across a wire at some point, so securing the network itself is a front line of defense. Here are the tools and concepts defenders lean on.

Firewall — A gatekeeper that inspects incoming and outgoing traffic against a set of rules and drops whatever doesn't fit; the classic example of a barrier between the wide-open internet and a trusted internal network.
VPN (Virtual Private Network) — A software tunnel that encrypts your traffic between your device and a remote server, shielding it from eavesdroppers and letting remote workers reach private resources safely.
Intrusion detection system (IDS) — A monitoring layer that watches packets or logs for signs of known attacks and suspicious patterns, then raises an alarm so humans can investigate.
Network segmentation — Chopping a big flat network into smaller zones so that a compromise in, say, the guest Wi-Fi can't automatically reach the payroll server on the other side of the building.
Zero trust — A modern philosophy that drops the idea of a trusted "inside": every request, from every user or device, has to reauthenticate and prove it should have access, no matter where it originates.

Zero trust in particular has reshaped enterprise network design over the past decade, mostly because too many breaches started with someone already "inside."

6. Proving Identity and Controlling Access

Authentication asks "Who are you?"; authorization asks "What are you allowed to do?" These terms are the nuts and bolts of answering both questions.

Authentication — The process of checking someone's identity—through a password, a fingerprint, a hardware token, or some combination—before letting them into a system.
Multi-factor authentication (MFA) — Requiring at least two independent proofs of identity, typically a mix of something you know, something you have, and something you are; the single biggest upgrade most people can make to their personal security.
Password manager — A vault application that remembers a unique strong password for every site you use, unlocked by one master password (plus ideally a second factor), so you don't reuse "Password123" everywhere.
Single sign-on (SSO) — A scheme that lets one authenticated session unlock many applications, cutting password fatigue but putting extra weight on the identity provider's own security.
Privilege escalation — An attack move where a user with limited access finds a way to promote themselves, often from a regular account to an administrator, typically by abusing a misconfiguration or bug.

Most serious breaches include a privilege-escalation step somewhere in the middle, which is why least-privilege access is a design principle in modern security.

7. Building a Layered Defense

No single tool stops every threat, so defenders stack controls in layers—technical on one side, human on the other.

Technical Layers

Antivirus and EDR (endpoint detection and response) software watch individual devices for malicious behavior and known bad files. Patch management keeps operating systems and applications up to date so known vulnerabilities don't stay exploitable for months. Penetration testing hires ethical hackers to try breaking in on purpose, surfacing weaknesses before the wrong people find them. SIEM (security information and event management) platforms pull logs from across the organization into one place and look for patterns that individual tools would miss.

Human Layers

Security awareness training teaches staff to spot suspicious emails and sketchy links before they click. Phishing simulations quietly test those lessons by sending harmless fakes and measuring who bites. Written security policies make expectations explicit—what data can live where, which devices are allowed, how to handle a lost laptop. Clear incident reporting channels mean that the moment something looks off, it reaches the team that can act on it instead of dying in a forwarded email thread.

8. What Happens When Something Goes Wrong

No defense is perfect, so mature organizations plan for the day something slips through. The incident response (IR) plan spells out exactly who does what when an alert fires, breaking the work into stages: detect, contain, eradicate, recover, and review. Digital forensics investigators comb through disk images, memory snapshots, and log trails to reconstruct how the attacker got in and what they touched. A security operations center (SOC) keeps eyes on the monitoring dashboards around the clock so alerts don't pile up overnight. Business continuity planning keeps the lights on during the disruption, and disaster recovery focuses on the narrower job of getting systems and data back to a known good state afterward.

9. Laws, Standards, and Governance

Beyond the technical work, security teams spend real time proving to auditors and regulators that they're doing the right things. GDPR sets strict privacy rules across the European Union and reaches any company that handles EU residents' data. HIPAA does similar work for U.S. healthcare information. PCI DSS is the payment card industry's own rulebook for anyone storing or processing credit card numbers. A SOC 2 report is the common evidence that a service provider has reasonable controls in place, while ISO 27001 is the international standard for running a formal information security management system. Regulated industries live and breathe this vocabulary; the rest of us run into it the moment we sign an enterprise deal or process someone else's personal data.

10. Everyday Habits That Keep You Secure

You don't need to memorize a textbook to protect yourself online—a handful of habits, repeated, does most of the work. Pick a password manager and let it generate long unique passwords for every account; turn on multi-factor authentication anywhere it's offered, ideally with an app or hardware key rather than SMS. Keep your phone, laptop, and router firmware patched. Assume unexpected messages are fake until proven otherwise, and when something does go sideways, have offline backups of anything you'd hate to lose. For readers aiming to take this into a career, certifications like CompTIA Security+, CISSP, and CEH line up well with the vocabulary above. Knowing these words is the first step; building the reflexes that go with them is the real defense.

Look Up Any Word Instantly on Dictionary Wiki

Get definitions, pronunciation, etymology, synonyms & examples for 1,200,000+ words.

Search the Dictionary