The definitions below are designed for teaching. Educators should adapt the wording to learner age while preserving the underlying idea.
| Term | Learner-friendly meaning | Educator note |
|---|---|---|
| Asset | Something people or organizations value and need to protect | Assets include people, services, data, reputation, equipment, and time |
| Authentication | The process of showing that an identity claim is credible | A password, security key, device, or biometric may be part of authentication |
| Authorization | The decision about what an authenticated identity is allowed to do | Authentication and authorization answer different questions |
| Availability | Information and services are accessible when authorized users need them | Availability includes resilience, capacity, recovery, and protection from disruption |
| Backup | A recoverable copy kept so information can be restored after loss or damage | A backup is useful only if it can be restored and is protected from the same failure |
| Cloud service | Computing capability delivered through remotely operated infrastructure or software | Teach shared responsibility rather than treating the cloud as automatically secure or insecure |
| Confidentiality | Information is disclosed only to authorized people, processes, or systems | Confidentiality can be affected by oversharing, weak access control, or interception |
| Control | A safeguard or practice used to change risk | Controls may be preventive, detective, responsive, corrective, physical, technical, or administrative |
| Credential | Information or an object used to support identity or access | Passwords, keys, tokens, certificates, and recovery codes are credentials |
| Cyberbullying | Repeated or harmful behavior carried out through digital communication | Follow safeguarding and reporting requirements rather than handling serious cases only as classroom conflict |
| Cybersecurity | The work of managing risks to systems, services, data, and people in digital environments | Cybersecurity is broader than hacking and includes governance, design, operations, recovery, and human behavior |
| Data | Recorded information that can be stored, processed, transmitted, or analyzed | Data sensitivity depends on content, context, combination, and use |
| Digital footprint | Information produced or collected through a person's digital activity | A footprint may be visible, inferred, copied, retained, or used in ways the person did not expect |
| Encryption | A cryptographic process that transforms readable data so it cannot be understood without authorized access to a key | Encryption protects data but does not by itself prove that a source is trustworthy |
| Firewall | A control that permits, blocks, or monitors network traffic according to rules | A firewall is one layer, not a complete security strategy |
| Hash | A one-way mathematical result used to represent data and detect change | Hashing is not the same as encryption because it is not intended to be reversed |
| Identity | A representation of a person, device, service, or other entity in a system | Identity lifecycle includes proofing, provisioning, use, review, change, and deprovisioning |
| Incident | An event or set of events that threatens or violates security objectives | Not every unusual event is an incident; analysis determines significance |
| Integrity | Information and systems remain accurate, complete, and protected from unauthorized change | Integrity includes trustworthy processes and records, not only file checks |
| Least privilege | Giving only the access needed for an authorized purpose and duration | Least privilege should be reviewed as roles and needs change |
| Log | A record of system, application, network, or user activity | Logs require context, time accuracy, protection, retention, and interpretation |
| Malware | Software or code intended to damage, disrupt, spy, extort, or gain unauthorized control | Avoid describing every unwanted program as a virus |
| Multi-factor authentication | Authentication that uses factors from more than one category | Two passwords are two steps but not two different factors |
| Network | Connected devices and services that exchange information | A network includes protocols, paths, trust relationships, and management decisions |
| Passkey | A phishing-resistant credential that uses public-key cryptography and is unlocked through an approved device or authenticator | Explain that recovery, device security, and service support still matter |
| Password manager | A tool that generates, stores, and fills unique credentials securely | The manager itself requires strong protection and a recovery plan |
| Phishing | Deceptive communication intended to influence a person to reveal information, approve an action, open content, or visit a destination | Verification should use a separate trusted channel, not the contact information in the suspicious message |
| Privacy | Appropriate control and protection of information about people and its collection, use, sharing, retention, and deletion | Privacy is related to but not identical with secrecy or security |
| Recovery | Restoring acceptable operations, information, access, or service after disruption | Recovery objectives, dependencies, backups, communication, and testing all matter |
| Resilience | The ability to prepare for, withstand, respond to, and recover from disruption | Resilience accepts that prevention can fail and designs for continued mission performance |
| Risk | The effect of uncertainty on objectives, often considered through likelihood and consequence | Risk is not simply a threat or vulnerability and cannot always be reduced to one number |
| Social engineering | Influencing people to take actions that benefit an attacker or violate expected safeguards | It exploits context and human behavior, not intelligence or character defects |
| Threat | A circumstance or actor that could cause harm | A threat needs a relevant path or condition to create risk |
| Threat model | A structured way to identify what could go wrong, why it matters, and how design can reduce the risk | Threat modeling should occur before and during design, not only after deployment |
| Update or patch | A change intended to fix defects, improve security, or maintain support | Updates require inventory, testing, deployment, verification, and exception handling |
| Vulnerability | A weakness or condition that could be used or triggered to cause harm | A vulnerability may be technical, procedural, physical, or human-centered |
| Zero trust | A security approach that continually evaluates access based on identity, context, policy, and least privilege rather than assuming trust from network location | Zero trust is an architecture and operating model, not a single product |
