# 20 terms a reader meets, each with a sourced example

Glossary, read 19 Nov 2026

**The short answer.** Twenty terms from zero-day response, each defined in words quoted from NIST, CISA, FIRST or MITRE, or from the Clock rules, with a dated 2026 example such as the BeyondTrust flaw exploited on 29 Aug 2026, 47 days before its advisory. Every entry names its source and shows a read date of 19 Nov 2026.

- [Attack surface](#attack-surface)
- [Binding operational directive](#binding-operational-directive)
- [Compensating control](#compensating-control)
- [CVE identifier](#cve-identifier)
- [CVSS](#cvss)
- [CWE](#cwe)
- [Disclosure Clock](#disclosure-clock)
- [Disclosure date](#disclosure-date)
- [Emergency directive](#emergency-directive)
- [EPSS](#epss)
- [Forensic triage](#forensic-triage)
- [Incident](#incident)
- [Indicator of compromise](#indicator-of-compromise)
- [Known Exploited Vulnerabilities catalog](#kev-catalog)
- [Mitigation](#mitigation)
- [Patch management](#patch-management)
- [Remediation](#remediation)
- [Security advisory](#security-advisory)
- [Software bill of materials](#software-bill-of-materials)
- [Zero-day vulnerability](#zero-day-vulnerability)

## Attack surface

NIST CSRC defines an attack surface as "The set of points on the boundary of a system, a system component, or an environment where an attacker can try to enter, cause an effect on, or extract data from, that system, component, or environment."

Example: BeyondTrust advised on 15 Oct 2026, for CVE-2026-102764, that [self-hosted Remote Support appliances](/playbooks/remote-support-tool/) expose only the parts users need and restrict /login and /appliance to trusted networks, which shrinks the reachable points. (example from [BeyondTrust advisory BT26-05](https://www.beyondtrust.com/trust-center/security-advisories/bt26-05), read 19 Nov 2026) ([source](https://csrc.nist.gov/glossary/term/attack_surface), read 19 Nov 2026)

## Binding operational directive

CISA describes a binding operational directive as "a compulsory direction to federal, executive branch, departments, and agencies for purposes of safeguarding federal information and information systems." BOD 26-04, Prioritizing Security Updates Based on Risk, is the current directive on remediation timelines for known exploited vulnerabilities.

Example: BOD 26-04, dated 10 Jun 2026, revokes BOD 22-01 and BOD 19-02. For CVE-2026-0322 its timeline began when CISA added the flaw to the catalog on 14 Oct 2026. (CVE-2026-0322 example from [CISA catalog entry](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-0322), read 19 Nov 2026) ([source](https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk), read 19 Nov 2026)

## Compensating control

NIST CSRC defines a compensating security control as "A management, operational, and/or technical control (i.e., safeguard or countermeasure) employed by an organization in lieu of a recommended security control in the low, moderate, or high baselines that provides equivalent or comparable protection for an information system."

Example: For Cisco ISE CVE-2026-76460, disclosed 16 Sep 2026, Cisco listed no workaround and offered infrastructure access control lists, which limit who reaches the API without fixing the flaw. (example from [Cisco advisory cisco-sa-ISE-ABP-VNSW7Tn5](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ISE-ABP-VNSW7Tn5), read 19 Nov 2026) ([source](https://csrc.nist.gov/glossary/term/compensating_security_control), read 19 Nov 2026)

## CVE identifier

NIST CSRC gives Common Vulnerabilities and Exposures (CVE) as "A dictionary of common names for publicly known information system vulnerabilities." The identifier is a name only. Severity comes from CVSS, and exploitation status comes from sources such as the CISA catalog.

Example: CVE-2026-109618 and CVE-2026-109619 are two names for PHP flaws disclosed on 21 Oct 2026, both fixed in PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. (example from [PHP security advisory GHSA-w8hw-w9fx-j79w](https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w), read 19 Nov 2026) ([source](https://csrc.nist.gov/glossary/term/common_vulnerabilities_and_exposures), read 19 Nov 2026)

## CVSS

The FIRST CVSS v4.0 specification says "The Base Score reflects the severity of a vulnerability according to its intrinsic characteristics which are constant over time and assumes the reasonable worst-case impact across different deployed environments." Threat and Environmental metrics then adjust the result for exploitation and for the local setting.

Example: Palo Alto Networks rated PAN-OS CVE-2026-0322, disclosed 14 Oct 2026, 8.6 on CVSS 4.0, and 8.5 when the management interface sits behind a single jump box. (example from [Palo Alto Networks advisory CVE-2026-0322](https://security.paloaltonetworks.com/CVE-2026-0322), read 19 Nov 2026) ([source](https://www.first.org/cvss/v4-0/specification-document), read 19 Nov 2026)

## CWE

The MITRE CWE FAQ defines a weakness as "a condition in a software, firmware, hardware, or service component that, under certain circumstances, could contribute to the introduction of vulnerabilities." One weakness type can sit behind many CVE records, so a CWE names the kind of flaw, not the single bug.

Example: [FortiMail](/playbooks/email-gateway/) CVE-2026-104286, disclosed 1 Oct 2026, carries CWE-22, path traversal; the Fortinet advisory and the CISA catalog also list CWE-158, a null byte weakness. (example from [Fortinet advisory FG-IR-26-175](https://fortiguard.fortinet.com/psirt/FG-IR-26-175), read 19 Nov 2026) ([source](https://cwe.mitre.org/about/faq.html), read 19 Nov 2026)

## Disclosure Clock

The Disclosure Clock is this site's dataset of days from disclosure to first dated exploitation for headline bugs of 2026. Disclosure is the vendor advisory date, or the NVD published date when none is stated. First exploitation is the earliest dated public report, else the CISA catalog date added, which is an upper bound on the first exploitation date.

Example: Read 19 Nov 2026: 33 bugs have a dated exploitation, the median is 2 days, 24 were exploited within 7 days, 16 within 1 day and 12 on or before disclosure day. ([source](https://zerodayplaybook.com/#zp-clock), read 19 Nov 2026)

## Disclosure date

The disclosure date is the day a vendor advisory made a vulnerability public, or the NVD published date when no advisory states one. The Disclosure Clock counts days to first exploitation from it. A researcher post or a CISA catalog listing does not set it. Vendors can revise advisories later.

Example: WordPress published the 7.1.4 release note for CVE-2026-119977 on 28 Oct 2026 and NVD published the record on 31 Oct 2026, so the Clock uses 28 Oct, and exploitation on 3 Nov 2026 is day 6. (example from [WordPress 7.1.4 release note](https://wordpress.org/news/2026/10/wordpress-7-1-4) and the [NVD record](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-119977), read 19 Nov 2026) ([source](https://zerodayplaybook.com/#zp-clock), read 19 Nov 2026)

## Emergency directive

CISA's page for ED 26-03 cites 44 U.S.C. section 3553(h), which lets the Secretary of Homeland Security "issue an emergency directive to the head of an agency to take any lawful action with respect to the operation of the information system" in response to a substantial threat. Each directive sets actions and deadlines.

Example: ED 26-03 on Cisco SD-WAN, issued 25 Feb 2026, set an inventory deadline of 26 Feb, updates by 27 Feb, and reports to CISA on 26 Feb, 5 Mar, 12 Mar and 23 Mar 2026. ([source](https://www.cisa.gov/news-events/directives/v1-ed-26-03-mitigate-vulnerabilities-cisco-sd-wan-systems), read 19 Nov 2026)

## EPSS

FIRST describes the Exploit Prediction Scoring System as "a data-driven machine-learning model that estimates the probability that a published CVE will be exploited in the wild in the next 30 days." It publishes a probability from 0 to 1 for every CVE each day. It forecasts; the CISA catalog records exploitation that has happened.

Example: Cisco ISE CVE-2026-76460 was in the CISA catalog on its disclosure day, 16 Sep 2026, so for that flaw exploitation was a recorded fact rather than a 30 day forecast. (example from [CISA catalog entry](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-76460), read 19 Nov 2026) ([source](https://www.first.org/epss/), read 19 Nov 2026)

## Forensic triage

For the shortest timeline, BOD 26-04 says the agency must complete remediation or mitigation within three days and "carry out a forensic triage of the asset to assess whether the system is compromised." Each CISA catalog entry states whether forensic triage applies. Patching alone does not answer whether an attacker got in first.

Example: Adobe Commerce and Magento CVE-2026-75650 was exploited from 4 Sep 2026, three days before the 7 Sep advisory; the catalog entry of 8 Sep marks forensic triage Yes, due 11 Sep. (CVE-2026-75650 example from [CISA catalog entry](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-75650), read 19 Nov 2026) ([source](https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk), read 19 Nov 2026)

## Incident

NIST CSRC defines an incident as "An occurrence that actually or potentially jeopardizes the confidentiality, integrity, or availability of an information system." A vulnerability alone is not an incident; exploitation, or reasonable suspicion of it, turns a patching task into incident response with a record and an owner.

Example: For Cisco ISE CVE-2026-76460, disclosed 16 Sep 2026, Cisco advised that anyone who suspects compromise re-image the affected nodes, so a suspected hit became a rebuild. (example from [Cisco advisory cisco-sa-ISE-ABP-VNSW7Tn5](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ISE-ABP-VNSW7Tn5), read 19 Nov 2026) ([source](https://csrc.nist.gov/glossary/term/incident), read 19 Nov 2026)

## Indicator of compromise

NIST SP 800-61r3, as shown in the NIST CSRC glossary, defines indicators of compromise as "Technical artifacts or observables that suggest that an attack is imminent or is currently underway or that a compromise may have already occurred." Vendors publish them in advisories, and they go stale as attackers change infrastructure.

Example: For CVE-2026-0322, disclosed 14 Oct 2026, Palo Alto Networks tied three addresses to limited exploit attempts: 66[.]42[.]72[.]14, 208[.]83[.]239[.]114 and 149[.]248[.]47[.]234. (example from [Palo Alto Networks advisory CVE-2026-0322](https://security.paloaltonetworks.com/CVE-2026-0322), read 19 Nov 2026) ([source](https://csrc.nist.gov/glossary/term/indicator_of_compromise), read 19 Nov 2026)

## Known Exploited Vulnerabilities catalog

CISA states it "maintains the authoritative source of vulnerabilities that have been exploited in the wild." Each entry carries a date added. The Disclosure Clock treats that date as an upper bound on first exploitation when no earlier dated report exists, since exploitation can start before CISA lists the flaw.

Example: VMware ESX CVE-2026-41709 was disclosed on 29 Jul 2026 and added to the catalog on 28 Oct 2026, 91 days later, so 28 Oct is an upper bound on when exploitation began. (example from [CISA catalog entry](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-41709), read 19 Nov 2026) ([source](https://www.cisa.gov/known-exploited-vulnerabilities-catalog), read 19 Nov 2026)

## Mitigation

NIST SP 800-216, in the NIST CSRC glossary, defines mitigation as "The temporary reduction or lessening of the impact of a vulnerability or the likelihood of its exploitation." A mitigation buys time for the patch. It needs an owner, a stated cost and a date on which it is removed.

Example: For ScreenConnect CVE-2026-84869, disclosed 3 Sep 2026, ConnectWise advised deselecting the TransferFiles permission in every role until 26.6.5, released 8 Sep 2026; the cost is that technicians cannot transfer files in sessions. (example from [ConnectWise bulletin of 8 Sep 2026](https://www.connectwise.com/company/trust/security-bulletins/2026-09-08-screenconnect-bulletin), read 19 Nov 2026) ([source](https://csrc.nist.gov/glossary/term/mitigation), read 19 Nov 2026)

## Patch management

NIST SP 800-40 Rev. 4 opens its abstract: "Enterprise patch management is the process of identifying, prioritizing, acquiring, installing, and verifying the installation of patches, updates, and upgrades throughout an organization." Emergency patching runs the same steps on a shorter clock, and verification is the step teams most often skip.

Example: Microsoft fixed [Windows](/playbooks/windows-endpoint-os/) AFD CVE-2026-68820 in the cumulative updates of 11 Aug 2026, the day the flaw was disclosed and exploited, so installation and verification had to start on day zero. (example from [Microsoft August 2026 CVRF feed](https://api.msrc.microsoft.com/cvrf/v3.0/cvrf/2026-Aug), read 19 Nov 2026) ([source](https://csrc.nist.gov/pubs/sp/800/40/r4/final), read 19 Nov 2026)

## Remediation

BOD 26-04 treats an asset as remediated when "the vulnerability is eliminated through patching, decommissioning the system, or another action." A mitigation that lowers risk without removing the flaw does not meet that test, although the directive lets removing a system from the internet change the timeline that applies.

Example: FortiMail CVE-2026-104286, disclosed 1 Oct 2026, is remediated by upgrading to 8.0.2, 7.6.7 or 7.4.9 or later; turning off the IBE service only mitigates it. (example from [Fortinet advisory FG-IR-26-175](https://fortiguard.fortinet.com/psirt/FG-IR-26-175), read 19 Nov 2026) ([source](https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk), read 19 Nov 2026)

## Security advisory

The OASIS Common Security Advisory Framework 2.0 describes security advisories as "structured information on products, vulnerabilities and the status of impact and remediation among interested parties." Vendor advisories are the source for affected and fixed versions. Read the advisory itself before any summary, because vendors revise advisories after first publication.

Example: The Palo Alto Networks advisory for CVE-2026-0322, published 14 Oct 2026, lists fixed builds per PAN-OS train and states that no workaround exists. (example from [Palo Alto Networks advisory CVE-2026-0322](https://security.paloaltonetworks.com/CVE-2026-0322), read 19 Nov 2026) ([source](https://docs.oasis-open.org/csaf/csaf/v2.0/os/csaf-v2.0-os.html), read 19 Nov 2026)

## Software bill of materials

NIST CSRC defines a software bill of materials as "A formal record containing the details and supply chain relationships of various components used in building software." In a disclosure it answers which applications embed the affected library, and its date shows how current that answer is.

Example: The Node.js advisory of 21 Oct 2026 for CVE-2026-111497 covers any [software embedding Brotli](/playbooks/dependency/) 1.0.3 to 1.2.0; fixes are Brotli 1.0.10, 1.1.1 and 1.2.1, and a Node.js upgrade fixes only the bundled copy. (example from [Node.js October 2026 security releases](https://nodejs.org/en/blog/vulnerability/october-2026-security-releases), read 19 Nov 2026) ([source](https://csrc.nist.gov/glossary/term/software_bill_of_materials), read 19 Nov 2026)

## Zero-day vulnerability

NIST CSRC defines a zero-day attack, not the vulnerability itself, as "An attack that exploits a previously unknown hardware, firmware, or software vulnerability." A zero-day vulnerability is the flaw such an attack uses. On the Disclosure Clock the practical test is dated exploitation before the vendor advisory, which leaves defenders no patch on the day exploitation starts.

Example: BeyondTrust CVE-2026-102764 was exploited from 29 Aug 2026, 47 days before the advisory of 15 Oct 2026; Adobe CVE-2026-75650 was exploited from 4 Sep 2026 and had its advisory on 7 Sep. (examples from [BeyondTrust advisory BT26-05](https://www.beyondtrust.com/trust-center/security-advisories/bt26-05) and [Fastly on Style Smuggler](https://www.fastly.com/blog/what-is-style-smuggler-cve-2026-75650), read 19 Nov 2026) ([source](https://csrc.nist.gov/glossary/term/zero_day_attack), read 19 Nov 2026)

## Related pages

- [The Disclosure Clock: median 2 days to exploitation](/clock/)

## Sources

- https://csrc.nist.gov/glossary/term/attack_surface (read 19 Nov 2026)
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk (read 19 Nov 2026)
- https://csrc.nist.gov/glossary/term/compensating_security_control (read 19 Nov 2026)
- https://csrc.nist.gov/glossary/term/common_vulnerabilities_and_exposures (read 19 Nov 2026)
- https://www.first.org/cvss/v4-0/specification-document (read 19 Nov 2026)
- https://cwe.mitre.org/about/faq.html (read 19 Nov 2026)
- https://zerodayplaybook.com/#zp-clock (read 19 Nov 2026)
- https://www.cisa.gov/news-events/directives/v1-ed-26-03-mitigate-vulnerabilities-cisco-sd-wan-systems (read 19 Nov 2026)
- https://www.first.org/epss/ (read 19 Nov 2026)
- https://csrc.nist.gov/glossary/term/incident (read 19 Nov 2026)
- https://csrc.nist.gov/glossary/term/indicator_of_compromise (read 19 Nov 2026)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog (read 19 Nov 2026)
- https://csrc.nist.gov/glossary/term/mitigation (read 19 Nov 2026)
- https://csrc.nist.gov/pubs/sp/800/40/r4/final (read 19 Nov 2026)
- https://docs.oasis-open.org/csaf/csaf/v2.0/os/csaf-v2.0-os.html (read 19 Nov 2026)
- https://csrc.nist.gov/glossary/term/software_bill_of_materials (read 19 Nov 2026)
- https://csrc.nist.gov/glossary/term/zero_day_attack (read 19 Nov 2026)

Last reviewed 19 Nov 2026. Canonical: https://zerodayplaybook.com/glossary/
