The CISSP is ISC2’s widely recognized certification for experienced security professionals, and it tests judgment as much as memory. Before you can reason through a scenario question, you need the vocabulary. This guide defines 100 essential CISSP terms in plain English, organized by the eight domains of the exam outline.
How to use this glossary
Watch the video above for a first pass, then work through the written terms one domain at a time. For each term, try to explain it in your own words before you read the definition. If you can also say when you would use it, you are studying the way the exam asks questions.
In this guide:
- Security and Risk Management (terms 1–16)
- Asset Security (terms 17–25)
- Security Architecture and Engineering (terms 26–40)
- Communication and Network Security (terms 41–52)
- Identity and Access Management (terms 53–64)
- Security Assessment and Testing (terms 65–73)
- Security Operations (terms 74–88)
- Software Development Security (terms 89–100)
Security and Risk Management
1. CIA Triad — The three core goals of security: confidentiality (only authorized people see data), integrity (data stays accurate and unaltered), and availability (systems and data are there when needed). Every control you study supports at least one of them.
2. Risk — The likelihood that a threat exploits a vulnerability, combined with the impact if it does. You can reduce risk, but you rarely eliminate it.
3. Threat — Any actor or event that could harm an asset, from a ransomware crew to a flood.
4. Vulnerability — A weakness a threat can exploit, such as unpatched software, a weak password policy or an unlocked server room.
5. Asset — Anything of value to the organization: data, systems, facilities, people and reputation. Protection starts with knowing what you have and what it is worth.
6. Risk Appetite — The amount and type of risk leadership is willing to accept to reach its goals. Security recommendations have to fit inside it.
7. Risk Treatment — The four ways to respond to a risk: mitigate it with controls, transfer it (for example, through insurance), avoid it by dropping the activity, or accept it knowingly.
8. Annualized Loss Expectancy (ALE) — A quantitative estimate of yearly loss from a risk: single loss expectancy (SLE) multiplied by the annualized rate of occurrence (ARO). It helps show whether a control costs less than the loss it prevents.
9. Due Care — Doing what a reasonable, prudent organization would do to protect its assets, such as applying patches and training staff. Due care is about acting.
10. Due Diligence — Investigating and understanding risk before you act, such as vetting a vendor or assessing a system. Due diligence is the research; due care is the follow-through.
11. Defense in Depth — Layering multiple, independent controls so that one failure does not expose the whole system.
12. Least Privilege — Giving people and systems only the access they need to do their jobs, and no more.
13. Separation of Duties — Splitting a sensitive task between two or more people so no single person can commit fraud or make a major error alone.
14. Security Governance — The policies, roles and oversight that keep security aligned with business goals and leadership accountable. Governance sets direction; management carries it out.
15. Business Continuity Plan (BCP) — The plan for keeping critical business functions running during and after a disruption. It covers the whole business, while disaster recovery focuses on restoring IT.
16. ISC2 Code of Professional Ethics — The code every CISSP agrees to follow. Its four canons start with protecting society, the common good, public trust and the infrastructure, and the order matters when they conflict.
Asset Security
17. Data Classification — Labeling data by sensitivity (for example public, internal, confidential and restricted) so handling rules and controls match its value.
18. Data Owner — The senior person accountable for a data set, who decides its classification and who may access it.
19. Data Custodian — The person or team that carries out the owner’s decisions day to day, including backups, access controls and storage.
20. Data Retention — The policy that defines how long data must be kept, driven by legal, regulatory and business needs, and when it must be destroyed.
21. Data Remanence — Residual data that remains on media after deletion or formatting and may still be recovered.
22. Media Sanitization — Making data unrecoverable before media is reused or discarded. NIST SP 800-88 describes three escalating levels: clear, purge and destroy.
23. Data Loss Prevention (DLP) — Tools and policies that detect and block sensitive data leaving the organization through email, uploads, removable media or cloud services.
24. Personally Identifiable Information (PII) — Information that can identify a specific person, alone or combined with other data, such as a name together with a Social Security number. Privacy laws set rules for protecting it.
25. Data Lifecycle — The stages data passes through: create, store, use, share, archive and destroy. Controls should follow the data through every stage.
Security Architecture and Engineering
26. Bell-LaPadula Model — A confidentiality model with “no read up” and “no write down,” built to stop classified data from flowing to lower levels.
27. Biba Model — An integrity model with “no read down” and “no write up,” built to stop low-integrity data from corrupting high-integrity data.
28. Trusted Computing Base (TCB) — The hardware, firmware and software that enforce a system’s security policy. If the TCB is compromised, the policy cannot be trusted.
29. Reference Monitor — The concept that every access between a subject and an object is mediated against policy. It must be tamper-proof, always invoked and small enough to verify.
30. Symmetric Encryption — Encryption that uses the same key to encrypt and decrypt. It is fast and suits bulk data (AES is the common example), but both sides must share the key securely.
31. Asymmetric Encryption — Encryption that uses a mathematically linked key pair: a public key to encrypt or verify, and a private key to decrypt or sign. It is slower, but it solves key distribution. RSA and elliptic curve cryptography are common.
32. Hashing — A one-way function that turns data into a fixed-length digest. It verifies integrity: change one bit and the hash changes. SHA-256 is a common example.
33. Digital Signature — A value created with the sender’s private key and checked with their public key. It provides integrity, authentication and non-repudiation.
34. Public Key Infrastructure (PKI) — The certificate authorities, registration authorities, policies and certificates that bind public keys to identities.
35. Key Management — Generating, distributing, storing, rotating, revoking and destroying cryptographic keys. Strong algorithms fail if the keys are handled badly.
36. Zero Trust — A model that trusts no user, device or network by default. Every request is verified explicitly against identity, device health and context.
37. Fail Secure — A design in which a failure leaves the system locked and protected, such as a door that stays locked when power is lost. Fail safe is the opposite priority: protecting human life, such as a door that unlocks.
38. Side-Channel Attack — An attack that infers secrets from physical effects such as timing, power use or electromagnetic emissions, instead of breaking the algorithm itself.
39. Hardware Security Module (HSM) — A tamper-resistant device that generates and stores cryptographic keys and performs cryptographic operations without exposing the keys.
40. Trusted Platform Module (TPM) — A chip on a device that stores keys and integrity measurements securely and supports features such as disk encryption and secure boot.
Communication and Network Security
41. OSI Model — A seven-layer reference model for network communication: physical, data link, network, transport, session, presentation and application. It helps you locate where an attack or a control operates.
42. TCP vs. UDP — TCP is connection-oriented and reliable, with a handshake and retransmission. UDP is connectionless and faster, with no delivery guarantee, which suits streaming and DNS queries.
43. Firewall — A control that allows or blocks traffic based on rules. Types include packet filtering, stateful inspection and next-generation firewalls that understand applications.
44. IDS vs. IPS — An intrusion detection system alerts on suspicious activity. An intrusion prevention system sits inline and can block it.
45. Virtual Private Network (VPN) — An encrypted tunnel across an untrusted network such as the internet, protecting traffic between a user or site and the organization.
46. Transport Layer Security (TLS) — The protocol that encrypts data in transit between clients and servers, and the foundation of HTTPS. It replaced SSL, which should no longer be used.
47. Network Segmentation — Dividing a network into zones to limit lateral movement and contain a breach.
48. Screened Subnet (DMZ) — A network segment between the internet and the internal network that hosts public-facing servers, so a compromise there does not give direct access inside.
49. VLAN — A virtual LAN: a logical segment created on switches so devices are separated at layer 2 regardless of physical location.
50. DNSSEC — Adds digital signatures to DNS records so resolvers can verify that answers were not forged or altered. It protects integrity, not confidentiality.
51. Network Address Translation (NAT) — Maps private internal addresses to public ones, conserving addresses and hiding internal addressing. It is not a substitute for a firewall.
52. WPA3 — The current Wi-Fi security standard. It strengthens the handshake and resists offline password guessing better than WPA2.
Identity and Access Management
53. Authentication — Proving you are who you claim to be, with something you know, have or are.
54. Authorization — Deciding what an authenticated identity is allowed to do. Authentication comes first; authorization follows.
55. Accountability — Being able to trace actions to an individual through unique IDs and audit logs. Without it you cannot investigate or enforce consequences.
56. Multifactor Authentication (MFA) — Requiring two or more different types of factor, such as a password plus an authenticator app. Two passwords are not MFA.
57. Single Sign-On (SSO) — One authentication that grants access to multiple applications. It reduces password sprawl but makes the identity provider a high-value target.
58. Federation — Trust between separate organizations or domains, so a user authenticated by one can reach resources in another without a new account.
59. SAML — Security Assertion Markup Language: an XML standard for exchanging authentication and authorization assertions between an identity provider and a service provider, common in enterprise SSO.
60. OAuth 2.0 — An authorization framework that lets an application obtain limited access to a user’s resources without receiving their password. OpenID Connect adds authentication on top.
61. Role-Based Access Control (RBAC) — Access is granted to roles based on job function, and users are assigned roles. It is straightforward to administer and audit.
62. Attribute-Based Access Control (ABAC) — Access decisions made from attributes of the user, the resource and the environment, such as department, data sensitivity and location. It allows fine-grained, dynamic policy.
63. Mandatory Access Control (MAC) — Access determined by labels and clearances set by a central authority, not by the data owner. It is used in high-security and government systems.
64. Privileged Access Management (PAM) — Controlling, monitoring and recording the use of administrator and other powerful accounts, often with vaulted credentials and just-in-time access.
Security Assessment and Testing
65. Vulnerability Assessment — A systematic scan and review that finds and ranks weaknesses. It identifies problems; it does not try to exploit them.
66. Penetration Test — An authorized, simulated attack that actively exploits weaknesses to show real-world impact, within agreed rules of engagement and scope.
67. Red Team — A group that emulates real adversaries over time to test an organization’s detection and response, not just its technical flaws.
68. Blue Team — The defenders who monitor, detect and respond to attacks. Purple teaming brings red and blue together to improve defenses.
69. Security Audit — A formal, independent examination of controls against a standard or policy, producing findings and evidence.
70. SOC 2 Report — An independent auditor’s report on a service organization’s controls for security, availability, processing integrity, confidentiality and privacy. Type I covers design at a point in time; Type II covers operating effectiveness over a period.
71. Log Review — Examining system and security logs for anomalies, policy violations and evidence of incidents. It only works if logs are protected and retained.
72. Fuzzing — Feeding malformed or random inputs to software to trigger crashes and expose bugs and vulnerabilities.
73. Key Risk Indicator (KRI) — A metric that signals rising risk before an incident occurs, such as the number of critical systems missing patches.
Security Operations
74. Incident Response — The organized approach to preparing for, detecting, containing, eradicating and recovering from security incidents, then learning from them.
75. Digital Forensics — Collecting, preserving and analyzing digital evidence in a way that holds up in an investigation or in court.
76. Chain of Custody — Documentation of who handled evidence, when and why, from collection to presentation. A gap can make evidence inadmissible.
77. Order of Volatility — The rule to collect the most perishable evidence first: CPU registers and cache, then memory, network state and running processes, then disk, then remote logs and backups.
78. SIEM — Security information and event management: collects and correlates logs from across the environment to detect threats and support investigations.
79. Patch Management — Identifying, testing, deploying and verifying software updates that fix vulnerabilities, prioritized by risk.
80. Change Management — A controlled process for requesting, reviewing, approving, testing and documenting changes so they do not cause outages or new vulnerabilities.
81. Configuration Management — Establishing and maintaining secure baselines for systems, and tracking any deviation from them.
82. Disaster Recovery Plan (DRP) — The plan to restore IT systems and data after a disruption. It is one part of business continuity.
83. Business Impact Analysis (BIA) — Identifies critical business functions and measures the effect of losing them over time. It drives recovery priorities and objectives.
84. Recovery Time Objective (RTO) — The target time within which a system must be restored after an outage.
85. Recovery Point Objective (RPO) — The maximum acceptable data loss, measured in time. It determines how often to back up or replicate.
86. Maximum Tolerable Downtime (MTD) — The longest a business function can be unavailable before the damage becomes unacceptable. The RTO should be shorter than the MTD.
87. Hot, Warm and Cold Sites — Alternate processing sites. A hot site is fully equipped and ready within minutes or hours, a warm site is partly equipped, and a cold site offers little more than space and power. Faster recovery costs more.
88. Backup Types — A full backup copies everything. An incremental backup copies changes since the last backup of any type. A differential backup copies changes since the last full backup. Storage and restore time differ for each.
Software Development Security
89. Software Development Life Cycle (SDLC) — The stages of building software: requirements, design, development, testing, deployment and maintenance. Security belongs in every stage, not only at the end.
90. DevSecOps — Building security into development and operations pipelines through automation, such as continuous scanning of code, dependencies and infrastructure.
91. Threat Modeling — A structured way to find what could go wrong in a design before it is built. STRIDE sorts threats into spoofing, tampering, repudiation, information disclosure, denial of service and elevation of privilege.
92. SQL Injection — Inserting malicious SQL through input fields to read or alter a database. Parameterized queries are the main defense.
93. Cross-Site Scripting (XSS) — Injecting script into a web page that other users view, so it runs in their browsers. Output encoding and a content security policy reduce the risk.
94. Cross-Site Request Forgery (CSRF) — Tricking a logged-in user’s browser into sending an unwanted request to a site that trusts them. Anti-CSRF tokens and same-site cookies help.
95. Buffer Overflow — Writing more data into a memory buffer than it can hold, overwriting adjacent memory and potentially hijacking execution. Bounds checking and memory-safe languages help.
96. Static Application Security Testing (SAST) — Analyzing source code or binaries for flaws without running the program. It finds issues early in development.
97. Dynamic Application Security Testing (DAST) — Testing a running application from the outside with crafted requests to find flaws such as injection.
98. Software Bill of Materials (SBOM) — An inventory of the components and dependencies inside a piece of software, so you can quickly find your exposure when a library turns out to be vulnerable.
99. Input Validation — Checking that data matches the expected type, length, format and range before it is processed. Validate on the server, and prefer allow-lists to block-lists.
100. OWASP Top 10 — A regularly updated awareness list of the most critical web application security risks, published by the Open Worldwide Application Security Project. It is a common starting point for secure coding training.
CISSP Terms: Frequently Asked Questions
What is the CISSP?
The Certified Information Systems Security Professional (CISSP) is a vendor-neutral certification from ISC2 for experienced security practitioners. It covers eight domains of security knowledge, from risk management to software development security.
How much experience do I need?
ISC2 requires candidates to have at least five years of cumulative, full-time work experience in two or more of the eight domains. A four-year degree or an approved credential can satisfy one year of that requirement, and candidates who pass the exam without the experience can become an Associate of ISC2 while they earn it. Requirements can change, so confirm the current details on isc2.org before you register.
Is memorizing terms enough to pass?
No. The CISSP is known for scenario questions that ask you to choose the best answer from a management perspective. Vocabulary is the starting point. Practice questions are where you build the judgment.
Ready to Practice?
These 100 terms are the foundation. At Cover6 Academy, we build courses and practice exams that teach the concepts behind the CISSP.
- Test yourself with the Cover6 CISSP practice exam
- Thinking about the leadership track? Read The vCISO Pathway: From Analyst to CISO
- Building your foundation first? Study the 100 Security+ terms
- Join The6 community: cover6solutions.com/the6
- Subscribe on YouTube: youtube.com/c/cover6solutions
