reference

Glossary

857 terms, in plain language.

3

  • 3-2-1 backup rule ops

    Keep three copies of data, on two different types of media, with one copy offsite.

8

  • 802.1X controls

    A standard for port-based network access control, requiring devices to authenticate before connecting.

A

  • Acceptable use policy (AUP) grc

    A policy that explains how employees may and may not use company systems and data.

  • Access control list (ACL) controls

    A list of rules saying who or what can access a resource, or which traffic is allowed.

  • Access review controls

    A periodic check by owners that users’ access is still needed, used to remove excess permissions. Also called recertification.

  • Access token controls

    A credential issued after login that a client presents to prove what it is allowed to do.

  • Account lockout controls

    Temporarily blocking an account after too many failed login attempts to slow guessing.

  • Account takeover (ATO) threats

    When an attacker gains control of someone’s legitimate account, often through stolen or reused credentials.

  • Accountability foundations

    Being able to trace actions to the person or system that performed them, which relies on authentication and logging.

  • Active Directory controls

    Microsoft’s directory service for Windows networks, storing users, computers and policies. A frequent attacker target.

  • Advance-fee fraud threats

    A scam that promises a large reward in return for a smaller upfront payment, which is then never repaid.

  • Advanced persistent threat (APT) threats

    A skilled, well-resourced adversary, often linked to a nation-state or organized group, that gains access and stays hidden for a long time to pursue specific goals.

  • Adversarial example threats

    An input subtly altered to make a machine-learning model give a wrong answer.

  • Adversary emulation ops

    Imitating a specific attacker’s techniques to test defences.

  • Adversary-in-the-middle (AiTM) threats

    A phishing technique where a proxy site relays the real login page and steals the session cookie after the victim completes MFA, which is why phishing-resistant MFA matters.

  • Adware threats

    Software that displays unwanted advertising, sometimes while tracking user behaviour.

  • AES foundations

    Advanced Encryption Standard: a symmetric block cipher standardized by NIST and used almost everywhere. It supports 128-, 192- and 256-bit keys.

  • Air gap ops

    Physically isolating a system from other networks. It reduces exposure but is not absolute, since removable media and maintenance connections can bridge it.

  • Alert ops

    A notification that something may need attention, generated by a security tool.

  • Alert fatigue ops

    Analysts becoming desensitized and missing real threats because of too many alerts, many of them false positives.

  • Alert tuning ops

    Adjusting detection rules to reduce false positives while still catching real threats.

  • Allow list controls

    A list of things explicitly permitted, with everything else blocked. Also called a whitelist.

  • Amplification attack threats

    A DDoS technique in which a small request to a third-party server triggers a much larger response sent to the victim.

  • Angler phishing threats

    Phishing in which attackers pose as a company’s customer-support account on social media to reach people who are complaining.

  • Annualized loss expectancy (ALE) grc

    The expected yearly financial loss from a risk, calculated as single loss expectancy times annual rate of occurrence.

  • Anomaly detection ops

    Finding behaviour that departs from normal patterns.

  • Antivirus controls

    Software that detects and removes known malware, mostly through signatures and behavior checks. Useful, but not enough alone.

  • API foundations

    Application programming interface: a defined way for one piece of software to request data or actions from another.

  • API gateway controls

    A front door for APIs that handles authentication, rate limiting, routing and logging in one place.

  • API key controls

    A secret string that identifies the calling application to an API. It is not strong user authentication and must be kept out of public code.

  • Application allowlisting controls

    Permitting only approved programs to run and blocking everything else.

  • Arbitrary code execution vulnerabilities

    The ability to run any code of the attacker’s choosing on a system.

  • ARP spoofing threats

    Sending forged ARP messages on a local network to link the attacker’s MAC address to another host’s IP address, enabling interception.

  • ASLR vulnerabilities

    Address space layout randomization: randomizing where code and data are placed in memory so exploits cannot rely on fixed addresses.

  • Asset inventory controls

    A maintained list of an organization’s hardware, software and data. You cannot protect what you do not know you have.

  • Asymmetric encryption foundations

    Encryption that uses a pair of mathematically linked keys: a public key that can be shared and a private key that stays secret. It underpins key exchange, certificates and digital signatures.

  • Attack chain threats

    The sequence of steps an attacker takes from first access to final goal.

  • Attack complexity vulnerabilities

    In CVSS, how many special conditions an attacker needs in order to exploit a flaw.

  • Attack surface threats

    Every point where an outsider could try to get in. Smaller is safer.

  • Attack vector threats

    The route or method an attacker uses to reach a target, such as email, an exposed service or a USB drive.

  • Attestation grc

    A formal statement by an independent party, or by management, that something meets stated criteria, as in a SOC 2 report.

  • Attribute-based access control (ABAC) controls

    Deciding access from attributes of the user, resource and context, such as department, data sensitivity and time, rather than fixed roles.

  • Attribution ops

    Identifying who is behind an attack. It is difficult and often uncertain.

  • Audit grc

    A systematic, independent examination of evidence to determine whether controls or processes meet defined criteria.

  • Audit evidence grc

    Information collected to support an audit conclusion, such as logs, screenshots, configurations, records and interviews.

  • Audit finding grc

    A documented observation where evidence shows a gap between what is required and what is happening.

  • Audit observation grc

    An audit note on something that is not a failure but could be improved.

  • Audit plan grc

    A document outlining what will be audited, when, how and by whom.

  • Audit report grc

    The written outcome of an audit, setting out findings, conclusions and recommendations.

  • Audit sampling grc

    Examining a selected portion of items to reach conclusions about the whole.

  • Audit scope grc

    The systems, processes and period covered by an audit.

  • Audit trail grc

    A chronological record of events showing who did what and when, used for accountability and investigation.

  • Authentication controls

    Proving you are who you say you are — a password, a fingerprint, a hardware key.

  • Authenticator app controls

    An app on your phone that generates time-based codes (TOTP) for logging in.

  • Authorization controls

    Deciding what someone who's already proven their identity is actually allowed to do.

  • Availability foundations

    One leg of the CIA triad — making sure systems and data are there when needed.

    Read the full topic →

B

  • Backdoor threats

    A hidden way to bypass normal authentication and access a system.

  • Backup testing controls

    Regularly restoring from backups to prove they actually work.

  • Baiting threats

    Luring a victim with something tempting, such as a USB drive left in a public place, to get them to run malware.

  • Banking trojan threats

    Malware designed to steal online banking credentials or manipulate transactions.

  • Base64 foundations

    An encoding that represents binary data as text. It is not encryption and gives no secrecy.

  • Baseline behaviour ops

    What normal looks like for a user or system, so unusual activity stands out.

  • Baseline configuration controls

    An agreed, documented secure configuration for a type of system, used as the standard to build and check against. CIS Benchmarks are an example.

  • Bash foundations

    A common Unix/Linux command shell and scripting language.

  • Bastion host controls

    A hardened, tightly monitored server used as the single entry point to administer systems in a private network. Also called a jump host.

  • Bearer token controls

    An access token that grants access to whoever holds it, so it must be sent over HTTPS, kept short-lived and protected.

  • BGP hijacking threats

    Falsely announcing internet routes so that traffic is redirected through the attacker’s network.

  • Biometrics controls

    Authentication based on physical traits such as a fingerprint or face. They are convenient but cannot be changed if compromised.

  • Black hat foundations

    A hacker who breaks into systems without permission for personal gain, disruption or malice. Their actions are illegal.

  • Black-box, white-box and grey-box testing threats

    Black-box testers start with no inside knowledge; white-box testers get full details such as source code and architecture; grey-box testing sits in between.

  • Blind SQL injection vulnerabilities

    SQL injection in which the application does not show query results, so the attacker infers data from true/false behaviour or timing.

  • Blue team threats

    The defenders: the people who monitor, detect and respond to attacks and harden systems.

  • Bluejacking threats

    Sending unsolicited messages to nearby Bluetooth devices.

  • Bluesnarfing threats

    Unauthorized access to data on a Bluetooth device.

  • BOLA vulnerabilities

    Broken object level authorization: an API fails to check that the caller may access the specific object requested, so changing an ID reveals other people’s data. It tops the OWASP API Security Top 10.

  • Bootkit threats

    A rootkit that infects the boot process, so it runs before the operating system loads.

  • Botnet threats

    A network of compromised devices controlled remotely by an attacker, often used for DDoS attacks, spam or credential attacks.

  • Breach and attack simulation (BAS) ops

    Tools that automatically run attack techniques to test whether security controls detect them.

  • Breach notification grc

    The legal duty to tell regulators and sometimes affected people when personal data is breached.

  • Break-glass account controls

    An emergency account with high privilege kept sealed and closely monitored, used only when normal access fails.

  • Bring your own key (BYOK) controls

    A model where the customer generates or controls the encryption keys used by a cloud service, rather than relying only on provider-managed keys.

  • Broken access control vulnerabilities

    Failures to enforce what users are allowed to do, such as viewing other people’s data or reaching admin functions. It is a leading category in the OWASP Top 10.

  • Broken authentication vulnerabilities

    Flaws in login and session handling that let attackers assume other users’ identities, such as weak passwords or predictable session IDs.

  • Broken function level authorization vulnerabilities

    An API that fails to restrict sensitive functions, such as admin actions, to the right roles.

  • Broken object level authorization vulnerabilities

    See BOLA: an API failing to check that the caller may access the specific object requested.

  • Browser hijacker threats

    Malware that changes browser settings, such as the home page or search engine, to redirect users.

  • Brute force (offline) threats

    Guessing passwords against a stolen hash file on the attacker’s own hardware, where there are no lockouts or rate limits.

  • Brute-force attack threats

    Trying many possible passwords or keys until one works. Rate limiting, lockouts and long passwords make it impractical.

  • Buffer overflow vulnerabilities

    Writing more data into memory than it can hold, overwriting adjacent memory and potentially letting an attacker run code.

  • Bug bounty threats

    A program where an organization pays independent researchers for responsibly reporting vulnerabilities.

  • Bug bounty programme ops

    A scheme that rewards people for responsibly reporting security flaws.

  • Burp Suite threats

    A web security testing tool from PortSwigger that works as a proxy between browser and site so testers can inspect and modify requests.

  • Business continuity ops

    Keeping critical operations running (or getting them back up fast) during a disruption.

  • Business continuity plan (BCP) grc

    A plan for keeping essential business functions running during a disruption.

  • Business email compromise (BEC) threats

    Fraud where an attacker impersonates or takes over a trusted business email account to trick staff into sending money or sensitive data.

  • Business impact analysis (BIA) grc

    Identifying critical business functions and the impact of losing them over time, to set recovery priorities.

C

  • CAPTCHA vulnerabilities

    A test meant to tell humans from bots, used to slow automated abuse.

  • CASB controls

    Cloud access security broker: a control point between users and cloud services that enforces policies such as visibility, data protection and threat detection.

  • Catfishing threats

    Creating a fake online identity to deceive someone, often in romance scams.

  • CCPA grc

    California Consumer Privacy Act: a US state law giving California residents rights over their personal data.

  • CDN foundations

    Content delivery network: a distributed set of servers that serve content from locations close to users, which also helps absorb attack traffic.

  • CEO fraud threats

    Impersonating a senior executive, usually by email, to trick staff into sending money or data.

  • CERT-In ops

    India’s national agency for responding to cybersecurity incidents, under the Ministry of Electronics and Information Technology.

  • Certificate authority (CA) foundations

    A trusted organization that verifies identities and signs digital certificates. Browsers and operating systems ship with a list of CAs they trust.

  • Certificate pinning foundations

    Configuring an application to accept only a specific certificate or key for a service, even if another certificate is otherwise valid.

  • Certificate signing request (CSR) foundations

    A message sent to a certificate authority asking for a certificate, containing the public key and details to be certified.

  • Certification audit grc

    An independent audit that decides whether an organization may be certified to a standard.

  • Chain of custody ops

    A documented record of who handled evidence, when and why, showing it has not been altered.

  • Change management controls

    A controlled process for requesting, approving and recording changes to systems.

  • Checksum foundations

    A small value calculated from data and used to detect accidental corruption. Unlike a cryptographic hash, it does not defend against deliberate tampering.

  • CIA Triad foundations

    Confidentiality, Integrity, Availability — the three things security is actually trying to protect.

    Read the full topic →
  • Cipher foundations

    An algorithm that performs encryption and decryption.

  • Ciphertext foundations

    Data after encryption, unreadable without the key. The readable original is called plaintext.

  • CIS Benchmarks grc

    Consensus-based secure configuration guides for specific technologies, published by the Center for Internet Security.

  • CIS Controls grc

    A prioritized set of safeguards from the Center for Internet Security for defending against common attacks.

  • CISO grc

    Chief information security officer: the executive responsible for an organization’s security programme.

  • Clickjacking vulnerabilities

    Tricking a user into clicking something different from what they see by hiding a page under a decoy. Frame-blocking headers help.

  • Clone phishing threats

    Copying a genuine email that was already delivered and resending it with a malicious link or attachment, from a spoofed sender.

  • Cloud computing foundations

    Renting computing resources such as servers, storage and software over the internet instead of owning the hardware.

  • Cloud security posture management (CSPM) controls

    Tools that continuously check cloud configurations against best practices and standards and flag misconfigurations.

  • Cloud workload protection platform (CWPP) controls

    Security tools that protect workloads such as virtual machines, containers and serverless functions across cloud environments.

  • COBIT grc

    A governance and management framework from ISACA for enterprise IT.

  • Code injection vulnerabilities

    Making an application execute attacker-supplied code in the language it is written in.

  • Code review controls

    Having another person examine source code to find bugs and security flaws before release.

  • Cold boot attack threats

    Recovering encryption keys from a computer’s memory shortly after it is powered off.

  • Cold site grc

    An alternate facility with space and basic utilities but no ready equipment.

  • Command and control (C2) threats

    The channel an attacker uses to send instructions to, and receive data from, compromised systems.

  • Command injection vulnerabilities

    Getting an application to run attacker-supplied operating system commands, usually through unsanitized input.

  • Command line foundations

    A text interface where you control a computer by typing commands, such as Bash or PowerShell.

  • Compensating control grc

    An alternative control that meets the intent of a requirement when the original control cannot be applied.

  • Compliance grc

    Meeting the requirements of laws, regulations, standards or contracts, and being able to show it.

  • Conditional access controls

    Policies that decide whether to allow, block or challenge a sign-in based on signals such as user, device health, location and risk.

  • Confidentiality foundations

    One leg of the CIA triad — keeping information away from people who shouldn't see it.

    Read the full topic →
  • Configuration management controls

    Tracking and controlling system settings so they stay consistent and secure.

  • Consent grc

    A person’s freely given, informed and specific agreement to the use of their personal data.

  • Container foundations

    A lightweight, isolated package that bundles an application with its dependencies and shares the host operating system kernel. Docker is a well-known tool.

  • Container scanning controls

    Checking container images for known vulnerabilities and bad configuration.

  • Containment ops

    Actions that stop an incident spreading or causing more damage, such as isolating a host.

  • Content Security Policy (CSP) controls

    A browser security header that restricts where a page may load scripts and other resources from, limiting the damage of XSS.

  • Continuous monitoring grc

    Ongoing, ideally automated, assessment of controls and risks rather than only periodic checks.

  • Control framework grc

    A structured set of controls an organization can adopt and be assessed against, such as ISO 27001 or the CIS Controls.

  • Control mapping grc

    Showing how controls in one framework correspond to those in another, to avoid duplicate work.

  • Control objective grc

    What a control is meant to achieve, used by auditors to judge whether the control is adequate.

  • Control testing grc

    Checking whether a control is designed properly and working in practice.

  • Cookie foundations

    A small piece of data a website stores in your browser, often to keep you logged in or remember settings.

  • Cookie theft threats

    Stealing a session cookie to impersonate a logged-in user without knowing their password.

  • Coordinated vulnerability disclosure vulnerabilities

    Reporting a vulnerability privately to the vendor and agreeing a timeline before details are made public, so a fix can be ready.

  • Corrective action grc

    A step taken to remove the cause of a problem or nonconformity so it does not recur.

  • Corrective control grc

    A control that limits impact or restores things after an event, such as restoring from backup or applying a patch.

  • CORS controls

    Cross-origin resource sharing: a browser mechanism that lets a server say which other origins may read its responses. Misconfigured, it can expose data.

  • COSO grc

    A framework for internal control and enterprise risk management.

  • Credential harvesting threats

    Collecting usernames and passwords, usually through fake login pages or malware.

  • Credential hygiene controls

    Practices such as unique passwords per site, a password manager and MFA.

  • Credential stuffing threats

    Trying username and password pairs leaked from one breach against other sites, relying on people reusing passwords.

  • Crisis communication ops

    Informing staff, customers, regulators and the media accurately and quickly during an incident.

  • Cross-border data transfer grc

    Moving personal data from one country to another, which many laws restrict or condition.

  • Cross-site scripting (XSS) vulnerabilities

    Injecting script into a web page that other users’ browsers then run. Output encoding and a Content Security Policy reduce the risk.

  • Cryptanalysis foundations

    The study of breaking or weakening cryptographic systems, for example by finding weaknesses in an algorithm.

  • Cryptographic failures vulnerabilities

    OWASP’s category for weak, missing or misused cryptography, such as outdated algorithms or hardcoded keys.

  • Cryptography foundations

    The science of protecting information using mathematical techniques such as encryption, hashing and digital signatures.

  • Cryptojacking threats

    Secretly using someone else’s computing power to mine cryptocurrency.

  • CSIRT ops

    Computer security incident response team: a group responsible for handling security incidents.

  • CSRF vulnerabilities

    Cross-site request forgery: tricking a logged-in user’s browser into sending an unwanted request to a site that trusts them. Anti-CSRF tokens and SameSite cookies help.

  • CVE vulnerabilities

    Common Vulnerabilities and Exposures: a standard identifier (such as CVE-2021-44228) for a publicly disclosed vulnerability.

  • CVE ID vulnerabilities

    The unique identifier of a publicly known vulnerability, such as CVE-2021-44228.

  • CVSS vulnerabilities

    Common Vulnerability Scoring System — a standardized 0–10 severity score for a vulnerability.

    Read the full topic →
  • CWE vulnerabilities

    Common Weakness Enumeration: a community-developed catalog of types of software and hardware weakness, such as CWE-79 for cross-site scripting.

  • Cyber espionage threats

    Using attacks to secretly obtain confidential information from governments or organizations.

  • Cyber hygiene foundations

    Routine good habits that keep systems and accounts healthy: patching, strong unique passwords, MFA, backups and caution with unknown links.

  • Cyber insurance grc

    Insurance that covers some costs of cyber incidents, such as response and recovery.

  • Cyber kill chain ops

    A model from Lockheed Martin that describes an intrusion in stages, from reconnaissance to actions on objectives, to help defenders break the chain.

  • Cyber warfare foundations

    The use of attacks on computer systems by or on behalf of states to damage or disrupt an adversary.

  • Cybercrime foundations

    Crime carried out using computers or networks, such as fraud, ransomware or identity theft.

  • Cybersecurity foundations

    The practice of protecting computers, networks, applications and data from attack, damage and unauthorized access.

D

  • Daemon foundations

    A background program on Unix-like systems that runs without direct user interaction, such as a web server.

  • DAST vulnerabilities

    Dynamic application security testing: testing a running application from the outside by sending it crafted requests.

  • Data backup controls

    A copy of data kept separately so it can be restored after loss or attack.

  • Data breach foundations

    An incident in which data is accessed, disclosed or stolen by someone who should not have it.

  • Data classification controls

    Labeling data by sensitivity, such as public, internal or confidential, so appropriate protection can be applied.

  • Data controller grc

    The party that decides why and how personal data is processed.

  • Data exfiltration threats

    Unauthorized transfer of data out of an organization.

  • Data leak foundations

    Exposure of data, often by accident or misconfiguration, without necessarily involving an active attacker.

  • Data loss prevention (DLP) controls

    Tools and policies that detect and block sensitive data from leaving an organization through email, uploads, devices and other channels.

  • Data masking controls

    Hiding or altering parts of sensitive data, for example showing only the last four digits, so it can be used without exposing the real value.

  • Data minimization grc

    Collecting and keeping only the personal data that is needed for a stated purpose.

  • Data poisoning threats

    Corrupting the data used to train a machine-learning model so that it learns wrong or harmful behaviour.

  • Data processing agreement (DPA) grc

    A contract between a data controller and processor describing how personal data will be handled.

  • Data processor grc

    A party that processes personal data on behalf of a data controller.

  • Data protection grc

    Safeguarding personal and sensitive data so it is used lawfully and kept secure.

  • Data protection impact assessment (DPIA) grc

    An assessment of the privacy risks of a planned activity that processes personal data.

  • Data protection officer (DPO) grc

    A person responsible for overseeing an organization’s data protection compliance.

  • Data residency controls

    The physical or legal location where data is stored and processed, which can be restricted by law or contract.

  • Data retention grc

    Rules for how long data is kept and when it must be deleted.

  • Data sanitization controls

    Permanently removing data from storage media so it cannot be recovered.

  • Data subject grc

    The person whose personal data is being collected or processed.

  • DCS ops

    Distributed control system: a control system for a process plant or factory with controllers distributed across the site.

  • DCSync threats

    An attack technique that imitates a domain controller to ask for password data from Active Directory.

  • DDoS threats

    Distributed denial of service: a DoS attack launched from many systems at once, often a botnet, which makes it harder to block.

  • Deauthentication attack threats

    Sending forged Wi-Fi frames that force devices off a network, often to capture a handshake or force reconnection to a fake access point.

  • Deception technology controls

    Decoys such as honeypots and fake credentials that lure attackers and raise an alert.

  • Deepfake threats

    Synthetic audio, image or video generated or altered by AI to impersonate someone, increasingly used in fraud and social engineering.

  • Defacement threats

    Changing the visible content of a website without authorization.

  • Default credentials vulnerabilities

    Factory-set usernames and passwords that attackers know and that must be changed at deployment.

  • Defense in depth controls

    Layering multiple independent controls so no single failure exposes everything.

    Read the full topic →
  • Denial of service (DoS) threats

    An attack that makes a system or service unavailable to legitimate users, typically by overwhelming it with traffic or requests.

  • Denial-of-service vulnerability vulnerabilities

    A flaw that lets an attacker crash or exhaust a service with little effort.

  • Deny list controls

    A list of things explicitly blocked, with everything else allowed. Also called a blocklist or blacklist.

  • DEP vulnerabilities

    Data execution prevention: a protection that marks memory regions as non-executable so injected data cannot run as code.

  • Dependency confusion threats

    A supply chain attack that tricks a build system into downloading a malicious public package instead of a private internal one with the same name.

  • Design effectiveness grc

    Whether a control, as designed, would meet its objective if it operated as intended.

  • Detection engineering ops

    Designing, testing and tuning the rules and analytics that detect threats.

  • Detection rule ops

    Logic that matches events to suspicious behaviour and raises an alert.

  • Detective control grc

    A control that identifies an event as or after it happens, such as log monitoring or an intrusion alert.

  • DevSecOps vulnerabilities

    Integrating security into DevOps practices so that checks happen automatically and early in the delivery pipeline.

  • DHCP foundations

    Dynamic Host Configuration Protocol: automatically gives devices an IP address and other network settings when they join a network.

  • Diamond model ops

    A model for analyzing intrusions by relating adversary, capability, infrastructure and victim.

  • Dictionary attack threats

    Guessing passwords using a list of common words and known passwords instead of trying every combination.

  • Diffie-Hellman foundations

    A key exchange method that lets two parties create a shared secret over a public channel without sending the secret itself.

  • Digital certificate foundations

    An electronic document, usually in X.509 format, that binds a public key to an identity such as a website. It is signed by a certificate authority.

  • Digital forensics ops

    Collecting, preserving and analyzing digital evidence to understand what happened, in a way that can stand up to scrutiny.

  • Digital signature foundations

    A value created with a private key that lets anyone holding the matching public key check who signed the data and that it has not changed since.

  • Directory listing vulnerabilities

    A web server setting that shows a folder’s contents when there is no index page, potentially exposing files.

  • Directory service controls

    A central database of users, devices and permissions, such as Active Directory.

  • Disassembler ops

    A tool that turns machine code into readable assembly instructions.

  • Disaster recovery ops

    Plans and capabilities for restoring IT systems and data after a major disruption.

  • Discretionary access control (DAC) controls

    An access model where the owner of a resource decides who can access it.

  • Disk image ops

    An exact bit-by-bit copy of a storage device used in forensic analysis.

  • DKIM controls

    DomainKeys Identified Mail: signs outgoing email so that receivers can verify it came from the domain and was not altered.

  • DMARC controls

    A DNS policy that tells receivers what to do with email that fails SPF or DKIM alignment checks and where to send reports, helping stop spoofing of a domain.

  • DMZ controls

    Demilitarized zone: a network segment that hosts public-facing services, separated from the internal network by firewalls.

  • DNP3 ops

    Distributed Network Protocol: a communications protocol used mainly in electric and water utilities.

  • DNS foundations

    The system that translates human-readable names into the numeric addresses machines use.

    Read the full topic →
  • DNS cache poisoning threats

    Inserting forged records into a DNS resolver’s cache so users are redirected to the wrong address.

  • DNS filtering controls

    Blocking domains known to be malicious by controlling DNS responses.

  • DNS hijacking threats

    Changing DNS settings or records so that users are sent to a malicious server.

  • DNS spoofing threats

    Feeding false DNS answers to a victim so that a real domain name leads to an attacker’s address. Also called DNS cache poisoning.

  • DNS tunnelling threats

    Hiding data inside DNS queries and responses to sneak it past defences or control malware.

  • DOM-based XSS vulnerabilities

    Cross-site scripting that occurs entirely in the browser, when client-side code writes untrusted data into the page unsafely.

  • Domain name foundations

    A human-readable name, such as example.com, that DNS translates to an IP address.

  • DORA grc

    Digital Operational Resilience Act: an EU regulation on ICT risk management for financial entities.

  • Double extortion threats

    A ransomware tactic where attackers both encrypt data and steal it, threatening to publish it unless paid.

  • Doxxing threats

    Publishing someone’s private personal information online to harass or endanger them.

  • DPDP Act grc

    India’s Digital Personal Data Protection Act, 2023, which governs the processing of digital personal data and sets duties for organizations and rights for individuals.

  • Drive-by download threats

    Malware downloaded automatically when a user visits a compromised or malicious page, without clicking to install anything.

  • Dropper threats

    Malware whose job is to install or download other malware onto a system.

  • Due care grc

    Taking the reasonable steps a prudent organization would take to protect assets once risks are known.

  • Due diligence grc

    Investigating a vendor or partner before engaging them, to understand their security and risk posture.

  • Dumpster diving threats

    Searching discarded material such as paper or old hardware for sensitive information.

  • Dwell time ops

    How long an attacker remains in an environment before being detected.

  • Dynamic analysis ops

    Examining software by running it and observing its behaviour.

E

  • Eavesdropping threats

    Secretly listening to or capturing communications, such as sniffing network traffic.

  • EDR ops

    Endpoint detection and response: software on endpoints that records activity, detects suspicious behavior and lets analysts investigate and contain threats.

  • Egress filtering controls

    Controlling outbound traffic to stop data leaving or malware calling home.

  • Elevation of privilege threats

    Gaining more access rights than intended.

  • Elliptic curve cryptography (ECC) foundations

    Public-key cryptography based on the mathematics of elliptic curves. It gives similar security to RSA with much smaller keys.

  • Email security gateway controls

    A service that scans incoming and outgoing email for spam, phishing and malware.

  • Email spoofing threats

    Forging the sender address of an email so it appears to come from someone else. SPF, DKIM and DMARC help detect it.

  • Embedded system ops

    A computer built into a device to perform a dedicated function.

  • Encryption controls

    Scrambling data so only someone with the right key can read it.

  • Encryption at rest controls

    Encrypting stored data, such as on disks and in databases, so that it is unreadable if the storage is stolen.

  • Encryption in transit controls

    Encrypting data as it moves across a network, for example with TLS.

  • End of life (EOL) vulnerabilities

    The point when a vendor stops providing updates, including security patches, making the product a growing risk.

  • End-to-end encryption (E2EE) foundations

    Encryption where only the communicating users hold the keys, so even the service carrying the messages cannot read them.

  • Endpoint foundations

    Any device that connects to a network, such as a laptop, phone or server. Endpoints are common targets and need their own protection.

  • Endpoint protection platform (EPP) controls

    Software that prevents threats on endpoints, combining antivirus with other protections.

  • Engineering workstation ops

    A computer used to programme and configure industrial controllers, which makes it a high-value target.

  • Entropy foundations

    A measure of unpredictability. Cryptographic keys and tokens need high entropy so that they cannot be guessed.

  • Enumeration threats

    Actively extracting details such as usernames, shares or services from a target after discovery.

  • EPSS vulnerabilities

    Exploit Prediction Scoring System: a score from FIRST estimating the probability that a vulnerability will be exploited in the wild soon, used alongside CVSS to prioritize fixes.

  • Eradication ops

    Removing the cause of an incident: malware, attacker access or the vulnerable configuration.

  • Escalation ops

    Passing an issue to more senior or specialized staff when it exceeds the first responder’s scope or severity.

  • EternalBlue vulnerabilities

    An exploit for a Windows SMB flaw, used by the WannaCry and NotPetya attacks in 2017.

  • Event ID ops

    A number that identifies the type of an event in a log, such as Windows event 4625 for a failed logon.

  • Evidence collection grc

    Gathering documents, logs and screenshots that show a control is operating, for audit.

  • Evidence preservation ops

    Protecting data and logs from change or loss so they can be analyzed or used legally.

  • Evil maid attack threats

    An attack requiring brief physical access to an unattended device to tamper with it, such as changing its boot software.

  • Evil twin threats

    A rogue Wi-Fi access point set up to look like a legitimate one so that users connect and can be spied on.

  • Excessive data exposure vulnerabilities

    An API returning more fields than the client needs, relying on the client to hide them.

  • Exfiltration channel threats

    The route used to move stolen data out of an environment, such as HTTPS, DNS or cloud storage.

  • Exploit threats

    Code or a technique that takes advantage of a specific vulnerability.

  • Exploit chain threats

    Several vulnerabilities used one after another to achieve what none could alone.

  • Exploit kit threats

    A toolkit that automatically probes a victim’s browser or system for known vulnerabilities and delivers malware.

  • Exploitability vulnerabilities

    How easy it is to take advantage of a vulnerability in practice.

  • Exploitation ops

    The phase of a test or attack in which a weakness is actually used to gain access.

  • Exposed service vulnerabilities

    A service reachable from the internet that does not need to be, such as a database or remote desktop.

  • External audit grc

    An audit by an independent outside party, often for certification, regulation or customer assurance.

F

  • Fail secure controls

    A design choice in which a failure leaves a system locked or denied, not open.

  • Failover controls

    Automatically switching to a standby system when the primary one fails.

  • False negative ops

    A real problem or attack that a tool fails to detect.

  • False positive ops

    An alert or scan result that flags harmless activity or a problem that does not exist.

  • Faraday bag controls

    A shielded pouch that blocks wireless signals to a device.

  • Federation controls

    Trust between separate organizations or systems so that an identity from one can be accepted by another without a new account.

  • FedRAMP grc

    A US government programme that standardizes security assessment of cloud services used by federal agencies.

  • FIDO2 and WebAuthn controls

    Open standards for phishing-resistant authentication using public-key cryptography, where a security key or device proves possession and the credential is tied to the real site.

  • Fieldbus ops

    A family of industrial networks that connect sensors, actuators and controllers.

  • Fileless malware threats

    Malware that runs in memory or through built-in tools instead of writing a traditional file to disk, making it harder for some antivirus products to spot.

  • Firewall controls

    A control that filters network traffic based on rules — the first fence around a network.

  • Firmware foundations

    Low-level software stored on a hardware device that controls how it starts and operates. Outdated firmware is a common weak point.

  • FISMA grc

    US law requiring federal agencies to build information security programs.

  • Flow data (NetFlow) ops

    Summary records of network conversations (who talked to whom, and how much), used for monitoring without storing full packets.

  • Forced browsing vulnerabilities

    Guessing URLs for pages or files that are not linked but are not protected either, such as /admin or /backup.zip.

  • Format string vulnerability vulnerabilities

    A flaw where user input is used as a format string in functions such as printf, allowing memory to be read or written.

  • Full-disk encryption controls

    Encrypting an entire drive so data is unreadable if the device is lost or stolen. Examples are BitLocker and FileVault.

  • Fuzzing threats

    Feeding a program large amounts of unexpected or random input to trigger crashes and find bugs.

G

  • Gap analysis grc

    Comparing the current state with a target standard or requirement to find what is missing.

  • Gateway foundations

    A node that connects one network to another and is the exit point for traffic leaving a network.

  • GDPR grc

    The EU General Data Protection Regulation, governing how personal data of people in the EU is processed, with rights for individuals and penalties for breaches.

  • GLBA grc

    Gramm-Leach-Bliley Act: US law requiring financial institutions to protect customer information.

  • Golden image controls

    A pre-approved, hardened system image used to build new machines consistently.

  • Golden ticket threats

    A forged Kerberos ticket-granting ticket made after stealing a key from a domain, giving long-lasting, wide access.

  • Governance grc

    The structure of roles, decisions and accountability by which an organization directs and oversees security and risk.

  • Governance, risk and compliance (GRC) grc

    The combined practice of directing an organization (governance), managing uncertainty (risk) and meeting rules and standards (compliance).

  • GraphQL introspection vulnerabilities

    A GraphQL feature that lets clients discover the whole schema. Leaving it on in production can help attackers.

  • Grey hat foundations

    A hacker who falls between white and black: they may probe systems without permission, but usually without malicious intent, and often disclose what they find. Acting without authorization is still illegal in most places.

  • Group Policy controls

    A Windows feature for centrally managing settings and security on computers in a domain.

  • Guideline grc

    Recommended, non-mandatory advice on good practice.

H

  • Hacker foundations

    Someone who explores how systems work and finds ways to make them do things their designers did not intend. The word covers both people who help (security researchers) and people who cause harm, which is why the hat colours below exist.

  • Hacktivist foundations

    Someone who uses hacking to promote a political or social cause, for example by defacing websites or leaking data.

  • Hardcoded credentials vulnerabilities

    Passwords or keys written into source code or configuration, where anyone with access to it can find them.

  • Hardware security module (HSM) controls

    A tamper-resistant device that generates and stores cryptographic keys and performs cryptographic operations without exposing the keys.

  • Hash collision foundations

    Two different inputs that produce the same hash value. A secure hash function makes finding one practically impossible.

  • Hash verification ops

    Comparing hash values to confirm that a file or image has not changed.

  • Hashcat ops

    A fast password-recovery tool that uses GPUs to test password guesses against hashes.

  • Hashing foundations

    A one-way function that turns data into a fixed-length fingerprint. Can't be reversed.

  • Header injection vulnerabilities

    Inserting line breaks into HTTP headers to add or alter headers or responses.

  • Heap overflow vulnerabilities

    A buffer overflow on the heap, where data overwrites neighbouring dynamically allocated memory.

  • Heartbleed vulnerabilities

    A 2014 flaw in OpenSSL that let attackers read chunks of server memory, potentially exposing keys and passwords.

  • Hidden form field tampering vulnerabilities

    Editing values in hidden form fields, which only appear hidden, because anything sent from the browser can be changed.

  • High availability controls

    Designing systems to stay operational with minimal downtime.

  • HIPAA grc

    The US Health Insurance Portability and Accountability Act, whose Security Rule sets safeguards for electronic protected health information.

  • Historian ops

    A database in industrial systems that stores time-series process data.

  • HMAC foundations

    Hash-based message authentication code: a MAC built from a hash function and a secret key, widely used to sign API requests and tokens.

  • HMI ops

    Human-machine interface: the screen or panel operators use to view and control an industrial process.

  • Honeypot controls

    A decoy system designed to attract attackers so that their methods can be observed and early warning raised.

  • Honeytoken controls

    A fake credential, file or record that alerts defenders when someone touches it.

  • Hot site grc

    A fully equipped alternate facility ready to take over almost immediately.

  • HSTS controls

    HTTP Strict Transport Security: a header that tells browsers to use only HTTPS for a site.

  • HTTP foundations

    Hypertext Transfer Protocol: the protocol browsers use to talk to web servers. Plain HTTP is not encrypted; HTTPS adds TLS.

  • HTTP parameter pollution vulnerabilities

    Sending the same parameter several times in a request so different parts of a system interpret it differently, sometimes bypassing checks.

  • HTTPS foundations

    HTTP carried over TLS. It protects web traffic from eavesdropping and tampering and lets the browser check it is talking to the real site.

  • Hypervisor foundations

    Software that creates and runs virtual machines, keeping them isolated from each other while they share the physical hardware.

I

  • IaaS, PaaS and SaaS foundations

    The three main cloud service models: infrastructure (virtual machines), platform (an environment to run your code) and software (a finished application). The more the provider manages, the less you secure yourself.

  • IAM role controls

    A cloud identity with a set of permissions that users or services can assume temporarily, avoiding long-lived credentials.

  • ICMP foundations

    Internet Control Message Protocol: used for network diagnostics such as ping, and sometimes abused for scanning or tunnelling.

  • Identity and access management (IAM) controls

    The policies and tools that make sure the right people and systems have the right access to the right resources at the right time.

  • Identity governance and administration (IGA) controls

    Tools and processes that manage identity lifecycles, access requests, approvals and reviews, to show who has access to what and why.

  • Identity provider (IdP) controls

    A service that creates and manages identities and authenticates users, then vouches for them to other applications.

  • Identity theft foundations

    Using someone else’s personal information, such as their name or ID numbers, to impersonate them, usually for fraud.

  • IDOR vulnerabilities

    Insecure direct object reference: changing an identifier, such as an ID in a URL, to reach another user’s data because the server does not check ownership.

  • IEC 62443 ops

    A series of international standards for securing industrial automation and control systems.

  • Image signing controls

    Digitally signing software or container images so users can check they are genuine and unmodified.

  • Immutable backup ops

    A backup that cannot be changed or deleted for a set period, which protects it from ransomware.

  • Impact grc

    The damage that would result if a risk event happened.

  • Impersonation threats

    Pretending to be a trusted person or organization, whether by phone, email or in person, to deceive a target.

  • Incident ops

    A security event that actually or potentially harms confidentiality, integrity or availability.

  • Incident commander ops

    The person who leads the response to a major incident and coordinates the team.

  • Incident response ops

    The structured process of detecting, containing, and recovering from a security incident.

    Read the full topic →
  • Incident response lifecycle ops

    The phases of handling an incident: preparation, detection and analysis, containment, eradication, recovery and post-incident review. NIST and SANS describe slightly different versions.

  • Incident response policy grc

    A policy that defines how security incidents are reported, handled and escalated.

  • Incident ticket ops

    A record that tracks an incident’s details, actions and status.

  • Indicator ops

    A sign, such as a file hash or IP address, that may point to malicious activity.

  • Indicator of attack (IOA) ops

    A sign of attacker behavior or intent in progress, such as unusual credential use, rather than a known-bad artifact.

  • Indicator of compromise (IOC) ops

    Evidence that a system may have been compromised, such as a malicious file hash, IP address or domain.

  • Industrial control system (ICS) ops

    A general term for systems that control industrial processes, including SCADA and DCS.

  • Industrial DMZ ops

    A buffer zone between the corporate IT network and the OT network where data is exchanged under tight control.

  • Industroyer ops

    Malware used in the 2016 attack on Ukraine’s power grid, designed to speak industrial protocols.

  • Information disclosure threats

    Exposing data to people who should not see it.

  • Information security foundations

    Protecting information, in any form, from unauthorized access, change or loss. Cybersecurity is the part focused on digital systems.

  • Infostealer threats

    Malware that steals saved passwords, browser cookies, crypto wallets and other data from an infected device.

  • Infrastructure as code (IaC) controls

    Defining and managing infrastructure through version-controlled code, which makes it repeatable and lets security checks run before deployment.

  • Inherent risk grc

    The level of risk before any controls are applied.

  • Initial access broker threats

    A criminal who gains access to organizations and sells that access to others, such as ransomware groups.

  • Initialization vector (IV) foundations

    A random or unique value used with a key so that encrypting the same data twice gives different results.

  • Injection vulnerabilities

    A class of flaw in which untrusted input is interpreted as code or commands by an interpreter, such as SQL, the OS shell or LDAP.

  • Input validation controls

    Checking that data from users or other systems is of the expected type, length and format before the application uses it.

  • Insecure deserialization vulnerabilities

    Unsafely rebuilding objects from untrusted data, which can let attackers run code or tamper with application logic.

  • Insecure design vulnerabilities

    Weaknesses that come from missing or flawed security thinking in the design itself, which cannot be fixed by coding perfectly.

  • Insecure direct object reference vulnerabilities

    See IDOR: exposing internal identifiers so that changing them gives access to other users’ data.

  • Insider threat threats

    Risk from people with legitimate access, such as employees or contractors, who misuse it deliberately or by mistake.

  • Integer overflow vulnerabilities

    A bug where a number exceeds the maximum its type can hold and wraps around, which can lead to memory errors.

  • Integrity foundations

    One leg of the CIA triad — making sure data hasn't been tampered with.

    Read the full topic →
  • Interactive application security testing (IAST) controls

    Testing that monitors a running application from inside to find vulnerabilities as it is exercised.

  • Internal audit grc

    An audit carried out by an independent function inside the organization to give management assurance about risk and controls.

  • Internet of Things (IoT) ops

    Everyday devices, such as cameras, sensors and appliances, connected to the internet, often with weak security.

  • Intrusion detection system (IDS) controls

    A system that monitors traffic or hosts for suspicious activity and raises alerts.

  • Intrusion prevention system (IPS) controls

    Like an IDS, but placed in the traffic path so it can also block malicious activity automatically.

  • IP address foundations

    A numeric label that identifies a device on a network, in IPv4 (such as 192.0.2.1) or IPv6 form.

  • IP spoofing threats

    Sending network packets with a forged source IP address, often used in denial-of-service attacks.

  • IPv4 foundations

    The widely used version of the Internet Protocol, with 32-bit addresses such as 192.168.1.1.

  • IPv6 foundations

    The newer Internet Protocol with 128-bit addresses, created because IPv4 addresses are running out.

  • ISAC ops

    Information sharing and analysis centre: an industry group where members share threat information.

  • Island hopping threats

    Breaking into a smaller partner or supplier to reach a bigger target.

  • ISMS grc

    Information security management system: the policies, processes and controls an organization uses to manage information security systematically.

  • ISO 22301 grc

    The international standard for business continuity management systems.

  • ISO 31000 grc

    An international standard giving guidelines for risk management.

  • ISO/IEC 27001 grc

    An international standard for an information security management system (ISMS), against which organizations can be certified.

  • ISO/IEC 27002 grc

    A guidance document listing information security controls and how to implement them, used alongside ISO/IEC 27001.

  • ISO/IEC 27701 grc

    An extension to ISO 27001 for managing privacy information.

  • IT Act 2000 grc

    India’s primary law on electronic records, digital signatures and cybercrime.

  • IT/OT convergence ops

    The increasing connection of industrial systems to corporate IT networks, which brings efficiency but exposes OT to IT-style threats.

  • ITIL grc

    A set of practices for IT service management.

J

  • Jailbreak (AI) threats

    A prompt designed to make an AI model bypass its safety rules.

  • John the Ripper ops

    A well-known open-source password-cracking tool.

  • Joiner-mover-leaver controls

    The lifecycle process for granting access when someone joins, changing it when their role changes, and removing it when they leave.

  • JSON Web Token (JWT) controls

    A compact, signed token format used to carry claims such as who the user is. Services must verify the signature, expiry and audience.

  • Juice jacking threats

    The idea of stealing data or installing malware through a public USB charging port. Real-world cases are rare, but using your own charger is a simple precaution.

  • Just-in-time access controls

    Granting elevated access only when needed and only for a short, approved time, rather than leaving standing privileges in place.

K

  • Kali Linux ops

    A Linux distribution packed with security testing tools.

  • Kerberoasting threats

    Requesting Kerberos service tickets for service accounts and cracking them offline to recover the accounts’ passwords.

  • Kerberos controls

    A network authentication protocol that uses tickets issued by a trusted server so that passwords are not sent over the network. Used by Active Directory.

  • Kernel foundations

    The central part of an operating system that controls hardware and enforces process and memory isolation.

  • KEV catalog vulnerabilities

    CISA’s Known Exploited Vulnerabilities catalog: a list of vulnerabilities with evidence of active exploitation, used by US federal agencies and many others to prioritize fixes.

  • Key exchange foundations

    A method for two parties to agree on a shared secret over an insecure channel, such as Diffie-Hellman.

  • Key management foundations

    Generating, storing, distributing, rotating and retiring cryptographic keys. Strong encryption is only as safe as the way its keys are handled.

  • Key management service (KMS) controls

    A managed service for creating, storing and controlling the use of encryption keys.

  • Key performance indicator (KPI) grc

    A measure of how well something is achieving its goals.

  • Key risk indicator (KRI) grc

    A metric that signals rising risk exposure, giving early warning before a loss occurs.

  • Key stretching foundations

    Making password hashing deliberately slow, by repeating or tuning the computation, so guessing is expensive.

  • Keylogger threats

    Software or hardware that records keystrokes to capture passwords and other typed data.

  • Kubernetes controls

    An open-source system for deploying and managing containerized applications at scale. Its configuration, access control and network policies need careful security.

L

  • Lack of rate limiting vulnerabilities

    Failing to restrict how often a client can call a service, which enables brute force and scraping.

  • LAN foundations

    Local area network: a network covering a small area such as a home or office.

  • Lateral movement threats

    Moving from one compromised system to others inside a network to reach valuable targets.

  • LDAP controls

    Lightweight Directory Access Protocol: a protocol for querying and managing directory services that store users, groups and devices.

  • LDAP injection vulnerabilities

    Injecting input that changes an LDAP query, which can bypass authentication or leak directory data.

  • Least privilege controls

    Give people and systems only the access they need, nothing more.

  • Legacy system vulnerabilities

    An older system still in use, often unsupported and hard to patch, and a frequent source of risk, especially in industrial environments.

  • Likelihood grc

    How probable it is that a risk event will occur.

  • Living off the land threats

    Attackers using tools already present on a system, such as PowerShell, to avoid dropping obvious malware and to blend in with normal activity.

  • Load balancer foundations

    A system that spreads incoming traffic across several servers to improve reliability and performance.

  • Loader threats

    A small malware component whose job is to download and run other malware.

  • Local file inclusion (LFI) vulnerabilities

    A flaw that lets an attacker make an application load files from the server, such as configuration files.

  • Log correlation ops

    Linking events from different sources to spot patterns that individual events would not show.

  • Log management ops

    Collecting, storing, protecting and analyzing log data from systems and applications.

  • Log retention ops

    How long logs are kept, which affects both investigations and compliance.

  • Log source ops

    Any system that produces logs sent to a monitoring tool.

  • Log4Shell vulnerabilities

    A critical 2021 vulnerability (CVE-2021-44228) in the Apache Log4j library that allowed remote code execution through crafted log messages.

  • Logic bomb threats

    Malicious code that stays hidden until a condition is met, such as a date or a user account being deleted.

M

  • MAC address foundations

    A hardware address assigned to a network interface and used to deliver frames on the local network (OSI layer 2). It can be spoofed, so it is not proof of identity.

  • Major nonconformity grc

    A significant failure to meet a requirement of a standard, which can prevent certification.

  • Malvertising threats

    Delivering malware or scams through online adverts.

  • Malware threats

    Software designed to do something harmful — viruses, worms, trojans, ransomware, and more.

    Read the full topic →
  • Malware analysis ops

    Studying malicious software to learn what it does, how it spreads and how to detect it, using static methods (without running it) and dynamic methods (in a safe environment).

  • Malware-as-a-service threats

    A criminal business model in which malware and its infrastructure are rented to other attackers.

  • Man-in-the-middle (MitM) attack threats

    An attacker secretly sits between two parties, reading or altering their communication. TLS with proper certificate checks defends against it.

  • Management response grc

    An organization’s written reply to an audit finding, stating what it will do and by when.

  • Mandatory access control (MAC) controls

    An access model where a central policy, not the owner, decides access based on labels such as classification levels.

  • Mantrap controls

    A small space with two interlocking doors that admits one person at a time to prevent tailgating.

  • Masquerading threats

    An attack in which someone pretends to be a legitimate user, device or service, for example by using stolen credentials or forging an identity, to gain access or trust.

  • Mass assignment vulnerabilities

    An API automatically binds client-supplied fields to internal object properties, letting an attacker set fields they should not, such as an admin flag.

  • Maturity assessment grc

    Judging how developed and repeatable an organization’s security practices are.

  • Maximum tolerable downtime (MTD) grc

    The longest an organization can be without a function before the damage becomes unacceptable.

  • MDR ops

    Managed detection and response: a service where an external team monitors and responds to threats for you.

  • Mean time to contain (MTTC) ops

    The average time taken to contain an incident after detection.

  • Memory forensics ops

    Analyzing a computer’s RAM to find running processes, network connections and malware.

  • Memory safety vulnerabilities

    Protection against bugs such as buffer overflows and use after free. Languages such as Rust and Go are memory-safe by design.

  • Message authentication code (MAC) foundations

    A short tag calculated from a message and a shared secret key that lets the receiver verify both the message’s integrity and its origin.

  • Metadata foundations

    Data about data, such as who created a file and when. It can reveal more than people expect.

  • Metasploit threats

    An open-source framework for developing and running exploits, widely used in penetration testing.

  • MFA controls

    Multi-factor authentication — combining two or more independent proofs of identity.

    Read the full topic →
  • MFA fatigue threats

    Flooding a user with push approval requests until they approve one by mistake or just to make it stop. Number matching and phishing-resistant MFA reduce the risk.

  • Microsegmentation controls

    Very fine-grained segmentation, often down to individual workloads, with policies that restrict which systems can talk to each other.

  • Mimikatz threats

    A well-known tool that extracts credentials from Windows memory, used by both testers and attackers.

  • Minor nonconformity grc

    A smaller failure to meet a requirement that does not by itself undermine the whole system.

  • Mirai ops

    A botnet that took over insecure IoT devices using default passwords and launched huge DDoS attacks in 2016.

  • Misconfigured cloud storage vulnerabilities

    Cloud storage such as a bucket set to public access by mistake, exposing data to the internet.

  • Missing patch vulnerabilities

    A known fix that has not been installed, leaving a vulnerability open.

  • Mitigation vulnerabilities

    Reducing the likelihood or impact of a vulnerability when it cannot be fixed immediately, for example with a firewall rule.

  • MITRE ATT&CK ops

    A public knowledge base of adversary tactics and techniques based on real-world observations, used to describe attacks and plan detections.

  • Mobile device management (MDM) controls

    Tools for managing and securing smartphones and tablets used for work.

  • Modbus ops

    A long-standing industrial communication protocol. The original has no built-in authentication or encryption, so it must be protected by network design.

  • Model theft threats

    Copying or extracting a machine-learning model, for example by querying it many times.

  • MTTD ops

    Mean time to detect: the average time between a compromise starting and the organization detecting it.

  • MTTR ops

    Mean time to respond (or recover, or resolve, depending on the organization): the average time to act on or fix an incident. Always check which meaning is used.

  • Multi-factor authentication (MFA) controls

    Requiring two or more kinds of proof to log in, such as a password plus a code or a security key.

  • Multi-tenancy controls

    Multiple customers sharing the same underlying infrastructure with logical separation between them.

  • Mutual TLS (mTLS) controls

    TLS where both client and server present certificates, so each side authenticates the other. Common between services.

N

  • N-day vulnerability vulnerabilities

    A vulnerability that is publicly known and has a patch, but remains exploitable on unpatched systems.

  • NAT foundations

    Network Address Translation: rewriting the addresses in packets as they cross a router, which lets many devices with private addresses share one public address.

  • Nation-state actor foundations

    A threat actor backed by a government, usually well funded and patient, pursuing espionage, disruption or strategic goals.

  • NDR ops

    Network detection and response: analyses network traffic to spot threats that other tools miss.

  • Need to know controls

    Giving people access only to the information required for their specific job.

  • NERC CIP ops

    Mandatory cybersecurity standards for the bulk electric system in North America.

  • Nessus ops

    A widely used commercial vulnerability scanner.

  • Network access control (NAC) controls

    Technology that checks devices and users before allowing them on a network.

  • Network forensics ops

    Capturing and analyzing network traffic to investigate incidents.

  • Network monitoring ops

    Continuously watching network performance and activity to spot problems and threats.

  • Network segmentation controls

    Dividing a network into separate zones with controlled paths between them so that a breach in one area is contained.

  • Next-generation firewall (NGFW) controls

    A firewall that also inspects applications, users and threats, not just ports and addresses.

  • Nikto ops

    An open-source web server scanner that checks for dangerous files and outdated software.

  • NIS2 grc

    The European Union directive that sets cybersecurity obligations for operators of essential and important services.

  • NIST Cybersecurity Framework (CSF) grc

    A voluntary framework from NIST that organizes cybersecurity outcomes into functions. Version 2.0 has Govern, Identify, Protect, Detect, Respond and Recover.

  • NIST privacy framework grc

    A NIST framework that helps organizations manage privacy risk.

  • NIST Risk Management Framework (RMF) grc

    A NIST process for managing security and privacy risk across a system’s lifecycle: prepare, categorize, select, implement, assess, authorize and monitor.

  • NIST SP 800-30 grc

    NIST’s guide for conducting risk assessments.

  • NIST SP 800-53 grc

    A NIST catalog of security and privacy controls, widely used for US federal systems and as a reference elsewhere.

  • NIST SP 800-61 grc

    NIST’s guide to computer security incident handling.

  • Nmap threats

    A widely used open-source network scanner for discovering hosts, open ports and services.

  • Non-repudiation grc

    Proof that an action or message genuinely came from a specific party — they can't credibly deny it.

  • Nonce foundations

    A number used once: a value that must not repeat in a given context, used to stop replay and to make encryption safe.

  • Nonconformity grc

    A failure to meet a requirement, a term used in ISO management system audits and often graded major or minor.

  • NoSQL injection vulnerabilities

    Injection against NoSQL databases through crafted input that alters the query.

  • NVD vulnerabilities

    National Vulnerability Database: the US government repository, run by NIST, that enriches CVE records with severity scores and other data.

O

  • OAuth 2.0 controls

    A framework for delegated authorization: it lets an application get limited access to a resource on a user’s behalf without seeing their password.

  • OCSP foundations

    Online Certificate Status Protocol: a way to check whether a certificate has been revoked.

  • One-time password (OTP) controls

    A password valid for a single login or a short time.

  • OPC UA ops

    A secure, platform-independent industrial communication standard that supports authentication and encryption.

  • Open port vulnerabilities

    A network port that accepts connections. Each unnecessary open port widens the attack surface.

  • Open redirect vulnerabilities

    A flaw where a site can be made to send users to an attacker-chosen address, often used to make phishing links look trustworthy.

  • Open source foundations

    Software whose source code is published and can be inspected, modified and shared under a licence.

  • Open-source intelligence (OSINT) foundations

    Collecting information from public sources such as websites, social media and records, used for investigations and reconnaissance.

  • OpenID Connect (OIDC) controls

    An identity layer on top of OAuth 2.0 that lets applications verify who a user is and get basic profile information.

  • OpenVAS ops

    An open-source vulnerability scanner.

  • Operating effectiveness grc

    Whether a control actually worked consistently over a period.

  • Operating system (OS) foundations

    The core software, such as Windows, Linux or macOS, that manages hardware and runs other programs.

  • Operational technology (OT) ops

    Hardware and software that monitors or controls physical equipment and processes, such as in factories, power and water systems.

  • Order of volatility ops

    The principle of collecting the most short-lived evidence first, such as memory, before more persistent data such as disks.

  • OT priorities (safety and availability) ops

    In OT, safety and availability usually come before confidentiality, the reverse of the typical IT ordering, so patching and scanning must be done carefully.

  • Output encoding controls

    Converting special characters in data to a safe form before showing it in a page, so that it is displayed as text and not run as code.

  • OWASP API Security Top 10 vulnerabilities

    OWASP’s list of the most critical API-specific risks, such as broken object level authorization and broken authentication.

  • OWASP Top 10 vulnerabilities

    A regularly updated awareness list, from the Open Worldwide Application Security Project, of the most critical web application security risks.

  • OWASP ZAP ops

    A free open-source web application security scanner and proxy.

P

  • Packet foundations

    A small chunk of data sent across a network, made of a header (addressing and control information) and a payload.

  • Packet analyzer ops

    A tool that captures and displays network traffic, such as Wireshark.

  • Packet capture (PCAP) ops

    A recording of network traffic, used for analysis and investigation.

  • Packet sniffing threats

    Capturing and reading network traffic as it passes by. Unencrypted traffic can be read easily.

  • Parameter tampering vulnerabilities

    Changing values in a URL, form field, cookie or API request, such as a price or user ID, to make an application behave in a way the designer did not intend. Servers must validate everything the client sends.

  • Pass-the-hash threats

    Using a stolen password hash, rather than the password itself, to authenticate to other systems on a Windows network.

  • Pass-the-ticket threats

    Reusing a stolen Kerberos ticket to access resources as another user without knowing their password.

  • Passkey controls

    A phishing-resistant sign-in credential based on FIDO standards, stored on a device or synced by a password manager, that replaces a password.

  • Passphrase controls

    A long password made of several words, which is easier to remember and harder to guess than short complex ones.

  • Password cracking threats

    Recovering passwords from stored hashes or protected files by guessing.

  • Password hashing foundations

    Storing a slow, salted one-way hash of a password instead of the password itself. Algorithms built for this include Argon2, bcrypt and scrypt.

  • Password manager controls

    An application that generates and stores unique strong passwords so that people do not reuse them.

  • Password policy controls

    Rules for how passwords must be created and managed. Current guidance favours length and screening against breached passwords over forced complexity and frequent changes.

  • Password spraying threats

    Trying a few common passwords against many accounts, so no single account is locked out. Often seen against cloud and VPN logins.

  • Password vault controls

    A secure tool for storing and managing privileged credentials, often with automatic rotation and session recording.

  • Passwordless authentication controls

    Signing in without a typed password, for example with a passkey, security key or biometric on a trusted device.

  • Patch cycle controls

    The regular process of testing and applying software updates.

  • Patch management vulnerabilities

    Tracking, testing and applying software updates to fix vulnerabilities in a timely way.

  • Patch Tuesday vulnerabilities

    Microsoft’s regular monthly release of security updates, on the second Tuesday of each month.

  • Path traversal vulnerabilities

    Using sequences such as ../ to reach files outside the intended directory.

  • Payload threats

    The part of an attack that performs the harmful action, such as running code or encrypting files.

  • PCI DSS grc

    Payment Card Industry Data Security Standard: requirements for organizations that store, process or transmit payment card data.

  • Penetration test report ops

    The document giving a tester’s findings, evidence, risk ratings and fix advice.

  • Penetration testing threats

    An authorized, scoped attempt to exploit weaknesses in a system to show what an attacker could achieve, followed by a report with fixes.

  • Pepper foundations

    A secret value added to passwords before hashing and stored separately from the database, so a stolen database alone is less useful.

  • Perfect forward secrecy foundations

    A property of some TLS setups where each session uses temporary keys, so stealing a server’s long-term key later does not reveal past traffic.

  • Persistence threats

    Techniques an attacker uses to keep access to a system across restarts or password changes.

  • Personal data grc

    Any information relating to an identified or identifiable person, such as a name, email address or ID number.

  • Pharming threats

    Redirecting users to a fake website even when they type the correct address, for example by tampering with DNS.

  • Phishing threats

    Tricking someone into giving up information or access, usually through a fake message or site.

    Read the full topic →
  • Phishing simulation controls

    A controlled test email sent to staff to measure and train their response to phishing.

  • Physical security controls

    Protecting buildings, equipment and people with measures such as locks, badges, cameras and guards.

  • Pig butchering threats

    A long-con investment scam in which fraudsters build trust with a victim over weeks, then steer them into fake investment platforms.

  • Piggybacking threats

    Gaining physical entry by following an authorized person through a door, with their knowledge or consent. Tailgating is the unnoticed version.

  • PII grc

    Personally identifiable information: data that can identify a specific person, such as a name, ID number or contact details.

  • Pivoting threats

    Using a compromised system as a stepping stone to reach other parts of a network.

  • Plaintext foundations

    Readable, unencrypted data. Encryption turns plaintext into ciphertext.

  • Playbook ops

    A documented set of steps for handling a specific type of incident or alert.

  • PLC ops

    Programmable logic controller: a rugged industrial computer that controls machinery by reading sensors and driving actuators.

  • Policy grc

    A high-level, management-approved statement of what must be done and why.

  • Polymorphic malware threats

    Malware that changes its own code each time it spreads so signature-based detection is harder.

  • Port foundations

    A number from 0 to 65535 that identifies a service on a host at the transport layer. For example, HTTPS normally uses TCP port 443.

  • Port scanning threats

    Probing a host or network to find which ports are open and what services respond. Nmap is a common tool.

  • Post-exploitation ops

    Activities after gaining access, such as escalating privileges or moving laterally.

  • Post-incident review ops

    A structured look back after an incident to learn what happened, what worked and what to improve. Also called lessons learned.

  • Post-quantum cryptography foundations

    Algorithms designed to stay secure even against quantum computers.

  • PowerShell foundations

    Microsoft’s command-line shell and scripting language, powerful for administration and also frequently abused by attackers.

  • Pretexting threats

    Social engineering that uses an invented scenario, such as posing as IT support, to gain trust and information.

  • Preventive control grc

    A control that stops an event happening, such as MFA or a firewall rule.

  • Principle of least functionality controls

    Enabling only the features and services that are actually needed.

  • Privacy by design grc

    Building privacy protections into systems and processes from the start.

  • Privacy policy grc

    A public statement explaining what personal data an organization collects, why and how it is used.

  • Privilege abuse threats

    Misusing legitimate access rights, for example an administrator reading data they have no business reason to see.

  • Privilege escalation threats

    Gaining higher access than originally obtained, for example from a normal user to an administrator.

  • Privileged access management (PAM) controls

    Controls and tools that protect, monitor and limit the use of powerful accounts such as administrators, often with vaulted passwords and session recording.

  • Privileged account controls

    An account with elevated rights, such as an administrator, which needs extra protection.

  • Procedure grc

    Step-by-step instructions for carrying out a task consistently.

  • Process foundations

    A running instance of a program.

  • Programmable automation controller (PAC) ops

    A more capable industrial controller that combines PLC-style control with computing features.

  • Prompt injection threats

    An attack on AI systems in which hidden or crafted text in the input makes the model ignore its instructions or take unintended actions.

  • Proof of concept (PoC) threats

    A demonstration that a vulnerability can be exploited, usually minimal and meant to prove the issue exists rather than to cause harm.

  • Protocol foundations

    An agreed set of rules for how systems communicate, such as HTTP, DNS or TLS.

  • Proxy server foundations

    A server that sits between a client and the internet, forwarding requests on the client’s behalf. It can filter, cache or anonymize traffic.

  • Pseudonymization grc

    Replacing identifying details with a code so that data cannot be tied to a person without additional information that is kept separately.

  • Public key infrastructure (PKI) foundations

    The people, policies and technology used to issue, manage and revoke digital certificates and the public keys they carry.

  • Purdue model ops

    A reference model that arranges industrial network components into levels, from field devices up to enterprise IT, used to plan segmentation.

  • Purple team threats

    Red and blue teams working together and sharing findings so that detections improve faster.

  • Purpose limitation grc

    Using personal data only for the purposes it was collected for.

  • Pyramid of Pain ops

    A model showing that denying attackers things like their tools and behaviour hurts them more than blocking hashes or IP addresses.

Q

  • Qualitative risk assessment grc

    Rating risk with descriptive scales such as low, medium and high.

  • Quantitative risk assessment grc

    Rating risk with numbers, usually money, such as expected annual loss.

  • Quantum computing foundations

    Computing that uses quantum effects. A large enough quantum computer could break RSA and ECC, which is why new algorithms are being standardized.

  • Quishing threats

    Phishing that uses QR codes to send victims to malicious sites.

R

  • Race condition vulnerabilities

    A flaw where behavior depends on the timing of events, which an attacker can exploit by forcing an unexpected order.

  • Rainbow table foundations

    A precomputed table of hashes for many possible passwords, used to reverse unsalted hashes quickly. Salting defeats it.

  • Ransom negotiation ops

    Communicating with extortionists during a ransomware incident. It is a specialist, high-stakes decision that should involve legal and law-enforcement advice.

  • Ransomware threats

    Malware that encrypts a victim's data and demands payment for the key to unlock it.

  • Ransomware-as-a-service (RaaS) threats

    A model in which ransomware developers lease their tools to affiliates who carry out attacks and share the profit.

  • Rate limiting controls

    Restricting how many requests a client can make in a period, to slow abuse, brute force and denial of service.

  • Reconnaissance threats

    Gathering information about a target before attacking, either passively (from public sources) or actively (by probing systems).

  • Recovery strategy grc

    The chosen approach to restoring systems, such as a hot site, cold site or cloud failover.

  • Red team threats

    A group that simulates a real adversary, using stealth and varied tactics, to test an organization’s detection and response.

  • Redundancy controls

    Having backup components so a failure does not cause an outage.

  • Reflected XSS vulnerabilities

    Cross-site scripting where the script comes from the request, such as a crafted link, and is echoed back in the response.

  • Refresh token controls

    A long-lived token used to get new short-lived access tokens without logging in again.

  • Registry (Windows) foundations

    A database in Windows that stores system and application settings. Malware often uses it for persistence.

  • Remediation vulnerabilities

    Fixing a vulnerability, for example by patching, reconfiguring or removing the affected component.

  • Remote access trojan (RAT) threats

    Malware that gives an attacker remote control over a victim’s computer.

  • Remote code execution (RCE) vulnerabilities

    A vulnerability that lets an attacker run commands or code on a target system from afar. It is usually rated critical.

  • Remote file inclusion (RFI) vulnerabilities

    A flaw that lets an attacker make an application load and run a file from a remote location.

  • Replay attack threats

    Capturing valid data, such as an authentication message, and sending it again later to gain access.

  • Reproducible build controls

    A build process that produces identical output from the same source, helping to verify nothing was tampered with.

  • Repudiation threats

    Denying having performed an action. Logging and digital signatures support non-repudiation.

  • Residual risk grc

    The risk that remains after controls have been applied.

  • Resilience ops

    An organization’s ability to withstand, adapt to and recover from attacks and disruption.

  • Responsible disclosure vulnerabilities

    Reporting a vulnerability privately to the vendor and allowing time to fix it before publishing details.

  • Return-oriented programming (ROP) vulnerabilities

    An exploitation technique that chains small existing code snippets in a program to run an attacker’s logic when injected code is blocked.

  • Reverse engineering ops

    Taking apart software to understand how it works, often without the source code.

  • Reverse proxy controls

    A server in front of applications that receives client requests and forwards them, often adding TLS, caching and filtering.

  • Reverse shell threats

    A connection where the compromised machine connects back to the attacker, giving them a command line and often getting past firewalls that block inbound connections.

  • Right to audit grc

    A contract clause allowing a customer to audit a supplier’s controls.

  • Right to erasure grc

    A person’s right, under laws such as the GDPR, to ask for their personal data to be deleted in certain cases.

  • Risk vulnerabilities

    The likelihood of a threat exploiting a vulnerability, multiplied by the impact if it does.

    Read the full topic →
  • Risk acceptance grc

    Knowingly choosing to live with a risk, usually when it is within appetite or too costly to reduce.

  • Risk appetite grc

    The amount and type of risk an organization is willing to pursue to meet its goals.

  • Risk assessment grc

    Identifying risks, estimating their likelihood and impact, and ranking them so they can be treated.

  • Risk avoidance grc

    Choosing not to do the activity that creates the risk.

  • Risk exception grc

    A formal, time-limited approval to operate outside a policy, with a documented reason and owner.

  • Risk matrix grc

    A grid that rates risks by likelihood and impact, usually colour-coded.

  • Risk mitigation grc

    Reducing a risk’s likelihood or impact with controls.

  • Risk owner grc

    The person accountable for managing a particular risk and deciding how to treat it.

  • Risk register grc

    A record of identified risks with their ratings, owners and planned treatments.

  • Risk tolerance grc

    The acceptable variation around risk appetite: the limit beyond which action is required.

  • Risk transfer grc

    Shifting risk to another party, for example through insurance or outsourcing.

  • Risk treatment grc

    The choices for dealing with a risk: mitigate, transfer, avoid or accept.

  • Risk-based prioritization vulnerabilities

    Ranking vulnerabilities by real risk, using exploit likelihood and business impact, instead of severity alone.

  • Rogue access point threats

    An unauthorized wireless access point connected to a network, which can bypass security controls.

  • Rogue security software threats

    Fake antivirus or cleaning tools that pretend to remove threats but are themselves malicious or useless.

  • Role-based access control (RBAC) controls

    Granting permissions to roles, such as “auditor”, and then assigning people to roles instead of giving each person individual rights.

  • Romance scam threats

    Fraud in which the attacker builds a fake relationship to get money from the victim.

  • Root cause analysis ops

    Investigating an incident to find the underlying cause so it can be fixed, not just its symptoms.

  • Rootkit threats

    Malware designed to hide its presence and keep privileged access, often by modifying the operating system.

  • Router foundations

    A device that forwards traffic between networks, for example between your home network and the internet.

  • RPO grc

    Recovery point objective: the maximum acceptable amount of data loss, measured as time back to the last good backup.

  • RSA foundations

    A public-key algorithm whose security rests on the difficulty of factoring very large numbers. Used for encryption, key exchange and digital signatures.

  • RTO grc

    Recovery time objective: the maximum acceptable time to restore a service after a disruption.

  • RTU ops

    Remote terminal unit: a field device that collects data and sends it to a central control system.

  • Rubber Ducky threats

    A USB device that pretends to be a keyboard and types malicious commands very fast when plugged in.

  • Rules of engagement threats

    The agreed written limits of a penetration test: what may be tested, when, how, and who to contact.

  • Runbook ops

    A detailed operational procedure for a routine or technical task.

  • Runtime application self-protection (RASP) controls

    Security built into an application that detects and blocks attacks while it runs.

S

  • Safety instrumented system (SIS) ops

    An independent system that automatically brings a process to a safe state if dangerous conditions arise. Protecting it from cyber tampering is critical.

  • Salt foundations

    A random value added to a password before hashing so that identical passwords produce different hashes and precomputed lookup tables stop working.

  • Same-origin policy vulnerabilities

    A browser rule that stops a page from one origin reading data from another origin.

  • SAML controls

    Security Assertion Markup Language: an XML-based standard that lets an identity provider pass sign-in and attribute information to applications, common for enterprise SSO.

  • Sandbox controls

    An isolated environment for running untrusted code or files safely so that they cannot affect the real system.

  • Sandbox analysis ops

    Running a suspicious file in an isolated environment to watch what it does.

  • SASE controls

    Secure access service edge: combines network and cloud-delivered security functions, such as a secure web gateway and ZTNA, into one service.

  • SAST vulnerabilities

    Static application security testing: analyzing source code or binaries for flaws without running the application.

  • SBOM vulnerabilities

    Software bill of materials: a list of the components and dependencies in a piece of software, used to find out quickly whether a vulnerable component is affected.

  • SCADA ops

    Supervisory control and data acquisition: systems that gather data from remote equipment and let operators monitor and control it, common in utilities and pipelines.

  • Scareware threats

    Software or pop-ups that frighten users with fake warnings, such as a fake virus alert, to make them buy something or install malware.

  • Scope threats

    In a penetration test or audit, the systems, locations and activities that are agreed to be in or out of bounds.

  • Script kiddie foundations

    A derogatory term for an unskilled attacker who runs tools or scripts written by others without understanding how they work.

  • Secrets management controls

    Securely storing, distributing, rotating and auditing credentials such as passwords, API keys and certificates, instead of embedding them in code.

  • Secure boot controls

    A feature that checks that the software loaded at start-up is trusted.

  • Secure by default controls

    Shipping products with safe settings enabled out of the box.

  • Secure by design controls

    Building security into a product from the start rather than adding it later.

  • Secure coding controls

    Writing software in ways that avoid common vulnerabilities.

  • Secure disposal controls

    Destroying or wiping devices and media safely at end of life.

  • Secure SDLC vulnerabilities

    Building security activities, such as design review, testing and code review, into every stage of software development.

  • Secure, HttpOnly and SameSite cookies controls

    Cookie attributes: Secure sends the cookie only over HTTPS, HttpOnly hides it from page scripts, and SameSite limits when it is sent on cross-site requests.

  • Security advisory vulnerabilities

    A notice from a vendor or organization describing a vulnerability, its impact and how to fix it.

  • Security awareness grc

    People’s understanding of security risks and their role in preventing them.

  • Security awareness training controls

    Teaching staff to recognize and report threats such as phishing and to follow secure practices.

  • Security baseline controls

    A minimum set of security settings every system must meet.

  • Security by obscurity foundations

    Relying on keeping a design secret as the main protection. It is weak on its own; good security should still hold if the design is known.

  • Security champion controls

    A team member who promotes security practices within their group and acts as a link to the security team.

  • Security control grc

    A safeguard or countermeasure that reduces risk. It can be technical, administrative or physical.

  • Security event ops

    An observable occurrence in a system or network, such as a failed login. Most events are harmless; some become incidents.

  • Security group controls

    A virtual firewall for cloud resources that allows or blocks traffic according to rules.

  • Security headers vulnerabilities

    HTTP response headers, such as CSP, HSTS and X-Content-Type-Options, that tell browsers to apply extra protections.

  • Security key controls

    A physical device used for strong authentication, often based on FIDO2, that resists phishing.

  • Security logging and monitoring failures vulnerabilities

    Not logging or watching for suspicious activity, so attacks go unnoticed.

  • Security maturity model grc

    A scale describing how developed an organization’s security capabilities are, from ad hoc to optimized.

  • Security metrics grc

    Measurements, such as patch time or phishing click rate, used to judge how well security is working.

  • Security misconfiguration vulnerabilities

    Insecure settings, defaults or unnecessary features, such as open cloud storage or default passwords.

  • Security operations ops

    The day-to-day work of monitoring, detecting, investigating and responding to security events.

  • Security operations center (SOC) analyst ops

    A person who monitors alerts, investigates suspicious activity and escalates incidents. Often organized in tiers.

  • Security orchestration ops

    Connecting security tools so they work together and share data.

  • Security policy grc

    A high-level document that states management’s rules and expectations for protecting information.

  • Security questionnaire grc

    A set of questions a supplier or customer uses to assess another organization’s security.

  • Security steering committee grc

    A senior group that sets direction and priorities for security.

  • Security.txt ops

    A standard file at /.well-known/security.txt that tells researchers how to report vulnerabilities.

  • Segregation of duties grc

    Splitting critical tasks between people so that no one person can complete and conceal a fraud or error alone.

  • Self-signed certificate foundations

    A certificate signed by its own key rather than a trusted authority. Browsers do not trust it by default.

  • Sensitive data exposure vulnerabilities

    Failing to adequately protect sensitive data in storage or transit, for example by not encrypting it.

  • Sensitive personal data grc

    Categories of personal data that deserve extra protection, such as health, biometric or financial information. Definitions vary by law.

  • Separation of duties controls

    Dividing a critical task between several people so no single person can complete or hide fraud. Also called segregation of duties.

  • Server-side template injection (SSTI) vulnerabilities

    Injecting template syntax into a server-side template engine so the server evaluates attacker-controlled code.

  • Serverless controls

    A cloud model where the provider runs and scales your code on demand, so you manage no servers but still secure the code, permissions and data.

  • Service account controls

    A non-human account used by an application or system to access resources. They are often over-privileged and poorly monitored.

  • Service level agreement (SLA) grc

    A contract term that sets expected service levels, such as uptime or response time.

  • Session foundations

    A period of interaction between a user and a system, usually tracked with a session ID or token after login.

  • Session fixation threats

    An attack in which the attacker makes a victim use a session ID the attacker already knows, then takes over the session after login.

  • Session hijacking threats

    Taking over a user’s authenticated session, for example by stealing a session cookie.

  • Session management controls

    How an application creates, tracks, protects and ends user sessions, including timeouts, token handling and logout.

  • Severity ops

    A rating of how serious an alert or incident is.

  • Sextortion threats

    Blackmail threatening to release intimate images or messages unless the victim pays or complies.

  • Shadow API vulnerabilities

    An API running in production that the security team does not know about or track, so it is not tested or protected.

  • Shadow IT grc

    Technology used in an organization without the approval or knowledge of IT or security.

  • Shared responsibility model controls

    The division of security duties between a cloud provider and its customer. The provider secures the underlying infrastructure; the customer secures what they put in it and how they configure it, with the split varying by service type.

  • Shellcode threats

    Small code used as the payload of an exploit, often to give the attacker a command shell on the target.

  • Shellshock vulnerabilities

    A 2014 vulnerability in the Bash shell that let attackers run commands through environment variables.

  • Shift left controls

    Moving security activities earlier in the development process, where fixes are cheaper.

  • Shoulder surfing threats

    Watching someone enter a password or read their screen.

  • Side-channel attack threats

    Learning secrets by observing physical effects such as timing, power use or sound instead of attacking the algorithm itself.

  • SIEM ops

    Security information and event management: a platform that collects and correlates logs from many sources to detect threats and support investigations.

  • Sigma rules ops

    An open, generic rule format for describing log-based detections so they can be converted to many SIEM products.

  • SIM swapping threats

    Taking over a victim’s phone number by convincing a carrier to move it to a SIM the attacker controls, in order to intercept SMS codes.

  • Single point of failure controls

    A component whose failure takes the whole system down.

  • Single sign-on (SSO) controls

    Signing in once to reach several applications, using an identity provider to vouch for you. It reduces password sprawl and centralizes control.

  • Skimming threats

    Capturing card data with a hidden device placed on a payment terminal or ATM.

  • Slowloris threats

    A denial-of-service attack that holds many connections to a web server open by sending requests very slowly.

  • Smart grid ops

    An electricity network that uses digital communication to monitor and manage supply and demand.

  • Smishing threats

    SMS phishing: fraudulent text messages that try to get victims to click links or share data.

  • Snort ops

    An open-source network intrusion detection and prevention system.

  • SOAR ops

    Security orchestration, automation and response: tools that automate repetitive response tasks and coordinate workflows through playbooks.

  • SOC ops

    Security Operations Center — the team (and room) that monitors for and responds to threats.

    Read the full topic →
  • SOC 1 grc

    A report on controls at a service organization that are relevant to its customers’ financial reporting.

  • SOC 2 grc

    An audit report on how well a company's controls protect customer data, common in SaaS.

    Read the full topic →
  • SOC 2 Type II grc

    A SOC 2 report that tests whether controls were designed well and operated effectively over a period of time, unlike Type I, which looks at a single point in time.

  • Social engineering threats

    Manipulating a person, rather than a system, into doing something insecure.

  • Social-engineer toolkit (SET) ops

    An open-source framework used by testers to simulate social engineering attacks.

  • Software bill of materials controls

    See SBOM: a list of the components that make up a piece of software.

  • Software composition analysis (SCA) vulnerabilities

    Tools that find open-source components in a codebase and flag known vulnerabilities and license issues.

  • Software supply chain attack threats

    Compromising software or its build process so that many users receive the malicious code through a trusted update.

  • SOX grc

    The US Sarbanes-Oxley Act, requiring reliable financial reporting by public companies. IT general controls are often tested as part of it.

  • Spear phishing threats

    Phishing aimed at a specific person or organization, using personal details to appear convincing.

  • Spectre and Meltdown threats

    A family of processor flaws disclosed in 2018 that let programs read memory they should not, by exploiting speculative execution.

  • SPF controls

    Sender Policy Framework: a DNS record listing the servers allowed to send email for a domain.

  • Spoofing threats

    Faking an identity or source, such as a sender address, IP address or website, so that a victim trusts something they should not.

  • Spyware threats

    Malware that secretly gathers information about a user or system and sends it to an attacker.

  • SQL injection vulnerabilities

    Inserting attacker-controlled SQL into a query because input is not handled safely, letting the attacker read or change data. Parameterized queries prevent it.

  • SSH foundations

    Secure Shell: a protocol for secure remote login and file transfer over an untrusted network.

  • SSL foundations

    Secure Sockets Layer: the older predecessor of TLS. It is obsolete and insecure, though people still say SSL when they mean TLS.

  • SSRF vulnerabilities

    Server-side request forgery: making a server send requests to places the attacker chooses, such as internal services or cloud metadata endpoints.

  • Stack overflow vulnerabilities

    A buffer overflow on the stack, where data overwrites adjacent memory such as return addresses.

  • Stalkerware threats

    Software secretly installed on someone’s device to monitor them, often by a partner or acquaintance.

  • Standard grc

    A mandatory specification that supports a policy, such as the required password length or approved encryption algorithms.

  • Stateful firewall controls

    A firewall that tracks active connections and allows return traffic for connections it has seen.

  • Statement of Applicability (SoA) grc

    A document in ISO/IEC 27001 listing which controls apply, why, and whether they are implemented.

  • Static analysis ops

    Examining code or a file without running it.

  • Steganography foundations

    Hiding a message inside another file, such as an image, so that its very existence is not obvious. This differs from encryption, which makes the content unreadable but visible.

  • STIX and TAXII ops

    Standards for describing threat intelligence (STIX) and exchanging it automatically (TAXII).

  • Stored XSS vulnerabilities

    Cross-site scripting where the malicious script is saved on the server, such as in a comment, and runs for everyone who views it.

  • STRIDE vulnerabilities

    A threat-modeling mnemonic: Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, Elevation of privilege.

  • Stuxnet threats

    A sophisticated worm discovered in 2010 that targeted industrial control systems, widely cited as an early example of malware causing physical damage to equipment.

  • Subdomain takeover vulnerabilities

    Claiming a forgotten cloud resource that a subdomain still points to, letting an attacker serve content on the organization’s domain.

  • Subnet foundations

    A smaller logical segment of an IP network. Subnets help organize networks and limit how far traffic and attackers can travel.

  • Supply chain attack threats

    Compromising a supplier, software update or dependency to reach many downstream victims.

  • Suricata ops

    An open-source network threat detection engine that can inspect traffic and generate alerts.

  • Surveillance audit grc

    A periodic follow-up audit that checks a certified organization still conforms.

  • Switch foundations

    A device that connects devices on the same local network and forwards traffic only to the right port.

  • Symmetric encryption foundations

    Encryption that uses the same secret key to lock and unlock data. It is fast and used for bulk data (AES is the best-known example), but both sides must share the key safely.

  • SYN flood threats

    A denial-of-service attack that sends many TCP connection requests without completing them, exhausting the target’s resources.

  • Syslog ops

    A standard protocol and format for sending log messages to a central server.

  • System hardening controls

    Reducing a system’s attack surface by removing unneeded software and services, changing defaults and applying secure configuration.

T

  • Tabletop exercise ops

    A discussion-based rehearsal where a team walks through a scenario, such as a ransomware attack, to test plans and roles.

  • Tailgating threats

    Following an authorized person through a secured door without using credentials of your own.

  • Tampering threats

    Changing data, code or messages without authorization.

  • TCP foundations

    Transmission Control Protocol: a reliable, connection-based transport protocol used by web, email and many other services.

  • TCP/IP foundations

    The pair of protocols that address and reliably deliver data across the internet.

  • Tech support scam threats

    A scam in which a caller or pop-up claims your computer is infected and pushes you to pay or give remote access.

  • Telemetry ops

    Data collected from systems about their activity and state, used for monitoring.

  • Third-party risk management grc

    Identifying and managing the risks that come from vendors, suppliers and partners with access to your data or systems.

  • Threat threats

    Anything that could exploit a vulnerability and cause harm — a person, a piece of code, an event.

  • Threat actor threats

    Any person or group that carries out, or plans to carry out, a malicious cyber activity.

  • Threat feed ops

    A stream of indicators and information about threats from a provider.

  • Threat hunting ops

    Proactively searching an environment for hidden threats instead of waiting for alerts.

  • Threat intelligence ops

    Evidence-based information about threats and adversaries that helps organizations make decisions and detect or prevent attacks.

  • Threat intelligence platform (TIP) ops

    A system for collecting, organizing and sharing threat intelligence.

  • Threat modeling vulnerabilities

    Structured thinking about what can go wrong in a system: what you are protecting, who might attack, how, and what to do about it.

  • Three lines model grc

    A governance model: operational management owns risk (first line), risk and compliance functions oversee it (second line), and internal audit gives independent assurance (third line).

  • Tier 1 analyst ops

    A first-line SOC analyst who triages alerts and handles routine cases.

  • Tier 2 analyst ops

    A more experienced SOC analyst who investigates escalated incidents in depth.

  • Tier 3 analyst ops

    A senior SOC analyst who handles complex incidents, threat hunting and detection engineering.

  • Time bomb threats

    A logic bomb that triggers at a specific date or time.

  • Time-of-check to time-of-use (TOCTOU) vulnerabilities

    A race condition in which something changes between the moment it is checked and the moment it is used.

  • Timeline analysis ops

    Ordering events by time to reconstruct what happened during an incident.

  • TLS foundations

    Transport Layer Security: the protocol that encrypts and authenticates traffic between a client and a server. It is the successor to SSL and what makes HTTPS secure.

  • Tokenization controls

    Replacing sensitive data, such as a card number, with a meaningless token and keeping the real value in a secured vault.

  • TOTP controls

    Time-based one-time password: a short code derived from a shared secret and the current time, typically valid for 30 seconds, shown by authenticator apps.

  • Traffic Light Protocol (TLP) ops

    A set of colour labels that show how widely shared information may be passed on.

  • Triage ops

    Quickly assessing and prioritizing alerts or incidents to decide what to handle first and how.

  • Triton (TRISIS) ops

    Malware discovered in 2017 that targeted safety instrumented systems at an industrial facility.

  • Trojan threats

    Malware disguised as legitimate software that performs hidden malicious actions once installed.

  • True negative ops

    No alert, and indeed no threat.

  • True positive ops

    An alert that correctly identifies a real threat.

  • Trusted Platform Module (TPM) controls

    A hardware chip that securely stores keys and checks system integrity.

  • TTPs ops

    Tactics, techniques and procedures: the patterns of behavior that describe how an adversary operates.

  • Two-factor authentication (2FA) controls

    MFA using exactly two factors, commonly a password and a one-time code.

  • Typosquatting threats

    Registering look-alike domain names, such as a misspelling of a brand, to catch mistyped addresses or fool users.

U

  • UDP foundations

    User Datagram Protocol: a faster, connectionless transport protocol with no delivery guarantee, used by DNS queries, streaming and games.

  • Unrestricted file upload vulnerabilities

    Allowing users to upload files without proper checks, which may let attackers upload and run malicious code.

  • URL foundations

    Uniform Resource Locator: the address of a resource on the web, such as https://example.com/page.

  • USB drop attack threats

    Leaving infected USB sticks where victims will find and plug them in.

  • Use after free vulnerabilities

    A memory bug in which a program keeps using memory after it has been released, which attackers can exploit.

  • User and entity behaviour analytics (UEBA) ops

    Analytics that learn normal behaviour of users and devices and flag deviations.

V

  • Vendor email compromise threats

    Fraud in which attackers compromise or imitate a supplier’s email to redirect payments.

  • Vendor risk assessment grc

    Evaluating the security and reliability of a supplier before and during a relationship.

  • Verbose error messages vulnerabilities

    Error pages that reveal technical details such as stack traces or database names, which help attackers.

  • Virtual machine foundations

    A software-emulated computer that runs its own operating system on top of a hypervisor, sharing the physical hardware with other virtual machines.

  • Virtual private cloud (VPC) controls

    A logically isolated private network inside a public cloud where you control addressing, routing and access rules.

  • Virtualization foundations

    Running multiple isolated virtual systems on one physical machine.

  • Virus threats

    Malware that attaches itself to legitimate files or programs and spreads when they are run or shared.

  • Vishing threats

    Voice phishing: social engineering by phone call.

  • VLAN foundations

    Virtual local area network: a way to split one physical network into separate logical networks.

  • Voice cloning threats

    Using AI to imitate a real person’s voice, which scammers use in phone fraud.

  • Volatility ops

    A popular open-source framework for memory forensics.

  • VPN foundations

    Virtual private network: an encrypted tunnel between a device and another network, used to protect traffic on untrusted networks or to reach private resources.

  • Vulnerability vulnerabilities

    A weakness in code, configuration, or process that could be exploited.

  • Vulnerability assessment vulnerabilities

    Systematically identifying and ranking weaknesses, usually with scanners, without necessarily exploiting them. Penetration testing goes further by exploiting them.

  • Vulnerability disclosure vulnerabilities

    The process of reporting a security flaw to the owner or vendor, and sometimes to the public.

  • Vulnerability disclosure policy (VDP) ops

    A public statement explaining how researchers can report vulnerabilities safely.

  • Vulnerability management vulnerabilities

    The ongoing process of discovering, prioritizing, fixing and verifying fixes for vulnerabilities.

  • Vulnerability scanning vulnerabilities

    Using automated tools to check systems for known weaknesses. Results need validating because scanners produce false positives.

  • Vulnerable and outdated components vulnerabilities

    Using libraries, frameworks or software with known flaws that have not been patched.

W

  • WAN foundations

    Wide area network: a network spanning large distances, such as links between offices.

  • Wardriving threats

    Driving around to discover and map wireless networks.

  • Watering hole attack threats

    Compromising a website that a target group frequently visits so that its visitors are infected.

  • Weak password policy vulnerabilities

    Rules that allow short, simple or reused passwords, making guessing easier.

  • Weaponization threats

    Packaging an exploit with a payload so it can be delivered to a target. A stage of the cyber kill chain.

  • Web application firewall (WAF) controls

    A firewall that filters HTTP traffic to and from a web application to block attacks such as SQL injection and XSS. It complements, but does not replace, secure code.

  • Web filtering controls

    Blocking access to harmful or inappropriate websites.

  • Web server foundations

    Software that receives requests from browsers and returns web pages or data.

  • Whaling threats

    Spear phishing aimed at senior executives or other high-value targets.

  • Whistleblowing grc

    Reporting wrongdoing within an organization, ideally through protected channels.

  • White hat foundations

    An ethical hacker who tests systems with the owner’s permission to find and report weaknesses so they can be fixed. Penetration testers and many bug bounty hunters fall here.

  • Wi-Fi foundations

    Wireless networking based on the IEEE 802.11 standards.

  • Wiper malware threats

    Malware designed to destroy data or systems rather than hold them for ransom.

  • Wireshark ops

    A free packet analyser that captures and displays network traffic in detail, used for troubleshooting and investigation.

  • Worm threats

    Malware that spreads by itself across networks without needing a user to run anything.

  • WPA3 foundations

    The current Wi-Fi security standard, with stronger protection against password guessing than WPA2.

  • Write blocker ops

    A device or software that lets investigators read a drive without altering it.

X

  • XDR ops

    Extended detection and response: extends EDR by correlating data across endpoints, email, network, cloud and identity.

  • XXE vulnerabilities

    XML external entity attack: abusing XML parsers that process external entities to read files or reach internal systems.

Y

  • YARA ops

    A tool and rule language for identifying and classifying malware based on patterns in files or memory.

Z

  • Zeek ops

    An open-source network analysis framework that records detailed logs of network activity.

  • Zero standing privilege controls

    A model in which no one has permanent high-level access; privileges are granted only when needed.

  • Zero trust controls

    Verify everything, trust nothing by default — even inside your own network.

  • Zero-click exploit vulnerabilities

    An attack that compromises a device without any action by the victim, such as opening a message.

  • Zero-day threats

    A vulnerability that is unknown to the vendor or has no patch available yet, so defenders have had zero days to fix it.

  • Zombie threats

    A computer controlled remotely by an attacker as part of a botnet, usually without the owner knowing.

  • ZTNA controls

    Zero trust network access: giving users access to specific applications after verifying identity and device, rather than placing them on the whole network as a traditional VPN does.