Online Safety and Cybersecurity Glossary

This page covers the standardized terminology used across the online safety and cybersecurity service sectors in the United States. Definitions here draw from authoritative public sources including the National Institute of Standards and Technology (NIST), the Cybersecurity and Infrastructure Security Agency (CISA), and the Committee on National Security Systems (CNSS). Precise terminology is the foundation for regulatory compliance, incident response coordination, and professional licensing — imprecision in this vocabulary carries measurable operational and legal risk.


Definition and scope

Cybersecurity terminology operates within a structured definitional ecosystem maintained by federal standards bodies, not through informal consensus. NIST Special Publication 800-53, Revision 5 provides the canonical control catalog used across federal agencies and widely adopted in private-sector compliance frameworks. The CNSS Instruction 4009 maintains the national-level glossary for information assurance and cybersecurity terms used in classified and unclassified government contexts.

Core definitional distinctions:

The boundary between cybersecurity and online safety is codified differently across regulatory frameworks. The Children's Online Privacy Protection Act (COPPA), enforced by the Federal Trade Commission (FTC), addresses online safety for minors through a privacy and consent lens, not a technical security lens. This distinction shapes how service providers, attorneys, and compliance officers navigate sector-specific obligations. The Online Safety Listings on this domain reflect that regulatory bifurcation.


How it works

Standardized glossaries function as normative references — meaning compliance frameworks, contracts, and incident reports are interpreted against their definitions. A term like "breach" carries distinct legal weight under different statutory frameworks:

  1. HIPAA Breach — Defined under 45 CFR §164.402 as an impermissible acquisition, access, use, or disclosure of protected health information (PHI). Notification is required within 60 days of discovery for breaches affecting 500 or more individuals.
  2. State Law Data Breach — 50 U.S. states have enacted individual breach notification statutes, each with varying trigger definitions, timeframes, and covered data categories. California's notification standard, set under California Civil Code §1798.82, is among the most expansive.
  3. Federal Breach Reporting (CIRCIA) — The Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA) mandates that covered entities report significant cyber incidents to CISA within 72 hours and ransomware payments within 24 hours.

The operational impact of these distinctions means a single incident can trigger parallel obligations under federal and state frameworks simultaneously. Practitioners consult the NIST Cybersecurity Framework (CSF) 2.0 for a unified process architecture — organized across six functions: Govern, Identify, Protect, Detect, Respond, and Recover. The purpose and scope of this directory reflects this layered regulatory structure.


Common scenarios

Terminology confusion most frequently surfaces in four operational contexts:

Vulnerability vs. Threat vs. Risk
These three terms are frequently conflated in non-technical communications. Per NIST SP 800-30:
- Vulnerability — A weakness in an information system or its environment.
- Threat — Any circumstance or event with the potential to adversely impact operations through unauthorized access, destruction, or disclosure.
- Risk — The probability that a threat will exploit a vulnerability, combined with the resulting impact magnitude.

Authentication vs. Authorization
Authentication verifies identity; authorization determines access privileges. NIST SP 800-63 governs digital identity guidelines for federal systems, establishing assurance levels (IAL, AAL, FAL) that structure how identity proofing and authentication strength are calibrated.

Encryption vs. Hashing
Encryption is a reversible transformation requiring a key; hashing is a one-way function producing a fixed-length digest. Confusing the two creates compliance failures — for instance, storing passwords as encrypted values rather than salted hashes violates modern security baselines such as those described in NIST SP 800-63B.

Phishing vs. Spear Phishing vs. Whaling
All three are social engineering vectors, but differ in targeting scope. Generic phishing casts a wide net; spear phishing targets a defined individual or organization; whaling specifically targets senior executives. CISA's Phishing Guidance distinguishes these vectors for incident classification purposes.


Decision boundaries

Selecting applicable terminology depends on regulatory jurisdiction, incident type, and professional role. Key decision boundaries include:


References

📜 6 regulatory citations referenced  ·  🔍 Monitored by ANA Regulatory Watch  ·  View update log

Explore This Site