Engineer working on a laptop connected to a device test rig, surrounded by wiring harnesses and test hardware

Firmware vulnerabilities & fixes

NIST SP 800-150: cyber threat information sharing, explained

Last updated:

NIST SP 800-150, Guide to Cyber Threat Information Sharing (October 2016), organizes what an organization can share into five types of cyber threat information — indicators, TTPs, security alerts, threat intelligence reports, and tool configurations — and tells an organization how to stand up and participate in sharing relationships for exchanging it: not just what to share, but with whom, under what rules, and how to make the information actionable once it arrives. NIST's own abstract frames the stakes directly: "organizations that share cyber threat information can improve their own security postures as well as those of other organizations." The guide was written primarily for US federal agencies but, per its own Section 1.2, is "intended to be applicable to a wide variety of governmental and non-governmental organizations" — a device maker's PSIRT or an OT asset owner's security team can use the same structure.

Key takeaways

  • SP 800-150 predates the formats most sharing communities use now.
  • One format detail catches device makers out.
  • For a hardware or firmware maker, the sector your customers sit in usually decides the community.
  • Section 4 is the part most summaries skip, and it is the part a PSIRT uses daily.

What counts as "threat information"?

Section 2.1 breaks cyber threat information into five types, moving from raw to refined: indicators (technical artifacts such as a malicious IP, domain or file hash), TTPs (tactics, techniques and procedures describing an actor's behavior at increasing levels of detail), security alerts (human-readable advisories and vulnerability notes, sourced from places like US-CERT, ISACs, the NVD or PSIRTs), threat intelligence reports (prose analysis that adds context for a decision-maker), and tool configurations (concrete artifacts such as IDS signatures or firewall rules built from the other four types). The guide's own framing is that most organizations already produce several of these internally as part of routine incident response — SP 800-150's stated goal is to extend that internal practice "across organizational boundaries."

Which formats carry each type today?

SP 800-150 predates the formats most sharing communities use now. Its Section 4.5.2 only says that standard formats suit "time-critical exchanges" and that organizations should pick formats with "a high degree of maturity, broad adoption", pointing to work at OASIS and the IETF (SP 800-150 PDF). For a device maker, three OASIS standards now cover most of the ground:

SP 800-150 type Common machine-readable format Device-maker example
Indicators STIX 2.1 Indicator objects with a pattern Hash of a malicious firmware image seen in the field; C2 domain a botnet uses against your routers
TTPs STIX 2.1 Attack Pattern, Malware, Intrusion Set objects How an actor abuses an exposed management port on your product family
Security alerts CSAF 2.0 csaf_security_advisory; csaf_vex for affected / not-affected status Your own advisory for a fixed CVE in a gateway firmware release
Threat intelligence reports STIX 2.1 Report object, or a PDF / web page A sector ISAC write-up of a campaign against building controllers
Tool configurations STIX 2.1 Course of Action; vendor-specific rule files Firewall rule set customers can apply until they patch

Transport is a separate layer. TAXII 2.1 (OASIS Standard, 10 June 2021) defines an HTTPS API built around Collections, a "logical group of CTI objects" that consumers request; the Channels section of TAXII 2.1 is marked RESERVED. CSAF uses its own distribution model instead: a provider-metadata.json file, suggested at /.well-known/csaf/provider-metadata.json, pointing to a directory or ROLIE feed of advisories. For guidance on which CSAF profile to publish, see CSAF and VEX for device makers.

How do you stand up a sharing relationship?

Section 3 lays out the steps in order: define sharing goals and objectives; identify the internal sources that already produce shareable information; scope what will be shared and with whom; establish sharing rules that "control the publication and distribution of threat information"; join a sharing community; and plan ongoing support so the relationship survives past its first incident. The guide is explicit that sharing agreements should be set up before an incident, not during one — "rather than attempting to establish sharing agreements during an active cyber incident, organizations should plan ahead and have agreements in place before incidents occur."

How do sharing designations work with the Traffic Light Protocol?

Section 3.4.2 points to the Traffic Light Protocol (TLP) as the framework for marking how far a piece of shared information may travel, and Table 3-3 reproduces it under the explicit label "Traffic Light Protocol, Version 1.0" — four colors (RED, AMBER, GREEN, WHITE), each paired with a one-line "when should it be used" and "how may it be shared" rule. That table is a 2016 snapshot, not the current standard: FIRST, the body that maintains TLP, states its authoritative version today is TLP 2.0, in effect since August 2022 — the same RED/AMBER/GREEN core, but AMBER now splits into AMBER and a stricter AMBER+STRICT (no sharing with clients), and WHITE was renamed TLP:CLEAR. A team adopting SP 800-150's sharing-rules chapter today should carry over the concept of graduated sharing designations but apply FIRST's current five-label TLP v2.0, not the four-label v1.0 table printed in the document.

One format detail catches device makers out. The CSAF 2.0 schema's distribution.tlp.label field accepts only AMBER, GREEN, RED and WHITE, with a default URL pointing at FIRST's TLP page. A public advisory you would mark TLP:CLEAR in an email therefore carries WHITE inside a CSAF 2.0 file. The CSAF 2.1 Committee Specification Draft 04 (21 October 2026) lists separate distribution requirements for TLP:CLEAR and for TLP:AMBER, TLP:AMBER+STRICT and TLP:RED. Our TLP guide covers the label rules themselves.

Who do you actually share with?

Section 3.5 names the realistic set of sharing partners: ISACs, domestic and foreign CERTs/CSIRTs, Information Sharing and Analysis Organizations (ISAOs), DHS's Automated Indicator Sharing (AIS) initiative, vulnerability repositories, law enforcement, vendors, managed security service providers, ISPs, supply-chain partners, sector peers, business partners and customers. The guide distinguishes informal communities — "self-organizing groups that largely operate through voluntary cooperation" under "basic rules of conduct" — from more structured ones with defined membership and formal agreements, and notes that community composition often follows a geographic, sector, or threat-specific boundary rather than a single universal model.

For a hardware or firmware maker, the sector your customers sit in usually decides the community. The National Council of ISACs, formed in 2003, says it "comprises 28 organizations"; its member list includes the Auto-ISAC (vehicle OEMs and suppliers), the E-ISAC (electric sector), Health-ISAC, IT-ISAC and WaterISAC. A maker of medical devices, grid equipment or vehicle components gains most from the ISAC its asset-owner customers already read, because that is where reports about its products will surface first.

What should happen when an alert or indicator arrives?

Section 4 is the part most summaries skip, and it is the part a PSIRT uses daily. Section 4.2 says to first decide whether an alert "came from a trusted, reliable source", then weigh severity, the number of affected systems, mission impact and the operational cost of the fix. Section 4.3 lists the processing steps for indicators. As a working sequence for a device maker:

  1. Validateintegrity and provenance (signatures, hashes). For CSAF, requirement 19 of the standard (one of the trusted-provider requirements) says every document "SHALL have at least one OpenPGP signature file", so check it before trusting the content.
  2. Decrypt and decompressfeeds as needed.
  3. Extractthe content of interest: CVE IDs, affected product names, versions, indicators.
  4. Prioritizeby source value, confidence and effort. For vulnerabilities, KEV and EPSS give a defensible order.
  5. Categorizeby handling designation: TLP:AMBER material may not go into a public ticket.
  6. Matchagainst what you ship. Here the input is a per-release component list, which is why a firmware SBOM matters: without it, "are we affected?" becomes a manual search through build trees.
  7. Storethe result in a knowledgebase. Section 4.4 lists what to record: source, sharing rules, collection date, validity period, associated CVE / CPE / CWE records, actors and targeted systems. It also warns that "an indicator knowledgebase is an attractive target of attack".

Section 4.3 also sets five qualities for a good indicator — timely, relevant, accurate, specific, actionable. Use the same five words to grade the feeds you subscribe to.

What should a device maker publish outward?

Section 4.5 notes that "many organizations only consume indicators" and lists what producers must decide: metadata, data formats, protection of sensitive data and how sharing rules change over time. It asks producers to provide a way to publish, update and retract indicators, and a feedback channel for partners. For a device maker, the outward stream usually looks like this:

  • Security advisories for fixed vulnerabilities, in human-readable form plus CSAF, with product identifiers customers can match.
  • Exploitability statements (VEX) for high-profile CVEs in components you ship, so customers can close tickets for products that are not affected. The free VEX generator writes CycloneDX or CSAF VEX from a status the engineer chooses.
  • Indicators you observe against your own products in the field (scanning patterns, malicious firmware hashes), shared with your sector ISAC under TLP:AMBER or TLP:GREEN.
  • Mitigation configurations customers can apply before they patch.

Section 4.5.1 adds a detail worth copying: a marking such as "downgraded to GREEN as of 12/20/2015", so a restricted item can be released later without being re-issued.

How does SP 800-150 line up with NIS2 and the CRA?

SP 800-150 is US guidance, but EU law now describes much the same activity. NIS2 Article 29 has Member States ensure that entities can exchange, "on a voluntary basis", information on "cyber threats, near misses, vulnerabilities, techniques and procedures, indicators of compromise, adversarial tactics, threat-actor-specific information, cybersecurity alerts and recommendations regarding configuration of cybersecurity tools", within communities of essential and important entities "and where relevant, their suppliers or service providers". The Cyber Resilience Act puts sharing duties on manufacturers in Annex I Part II.

SP 800-150 element NIS2 Article 29 CRA Annex I Part II
Indicators, TTPs "indicators of compromise, adversarial tactics", "techniques and procedures" —
Security alerts "cybersecurity alerts", "vulnerabilities" Point (4): after a fix, share and publicly disclose fixed vulnerabilities, affected products, impact, severity and remediation
Tool configurations "recommendations regarding configuration of cybersecurity tools" —
Sharing community Arrangements within communities of entities and their suppliers Point (6): measures to facilitate sharing about vulnerabilities in the product and in third-party components, including a reporting contact
Sharing rules Voluntary, under arrangements Point (5): a coordinated vulnerability disclosure policy

The CRA also makes manufacturers notify actively exploited vulnerabilities to the CSIRT designated as coordinator and to ENISA (Article 14); see CRA vulnerability reporting. That is a legal duty, separate from the voluntary sharing SP 800-150 describes. NIS2 itself is covered in our NIS2 guide.

Worked example: how would a gateway maker run one advisory through the cycle?

Synthetic example; the company, product and versions are invented for illustration.

A maker of industrial Wi-Fi gateways (call it Example Gateways) is a member of a sector ISAC.

  1. Inbound alertThe ISAC shares a TLP:AMBER report: an open-source web server library has a remotely exploitable flaw, already used against building-control devices. A CVE ID is included.
  2. Validate and categorizeThe PSIRT confirms the report came through the ISAC portal and files it in an access-restricted ticket because of the AMBER marking.
  3. MatchThe team searches the stored SBOMs for gateway firmware 3.2 and 3.3. Version 3.2 ships the vulnerable library version; 3.3 ships a fixed one.
  4. Decide and fixThe fix is a library bump in a 3.2.1 maintenance release. Engineers note that 3.3 is not affected because the fixed version is present.
  5. PublishWhen 3.2.1 is out, the PSIRT publishes a public advisory as a web page and a CSAF 2.0 document (tlp.label WHITE), plus a VEX statement marking 3.3 as not affected.
  6. Share backThe PSIRT posts scanning patterns it saw against exposed gateways to the ISAC as TLP:GREEN indicators, with collection dates and a validity period, and asks members for feedback.

What are the common pitfalls?

  • Joining a community without an intake path. Section 4.1 warns that new members "may require time to integrate new threat information sources". Decide who reads the feed before you subscribe.
  • Pasting AMBER content into public trackers. Handling designations are part of the agreement; a leak can end the relationship.
  • Using TLP v1.0 labels in human text and v2.0 in machine text (or the reverse). Keep a written mapping, especially CLEAR → WHITE in CSAF 2.0.
  • Sharing indicators with no metadata. Without source, date and validity, recipients cannot age them out (Section 4.5.1).
  • Treating sharing as only inbound. SP 800-150 Section 2.2 describes the goal as allowing "one organization's detection to become another's prevention"; that only works if someone publishes.

What is a workable starting point?

  1. Inventory what you already produce before looking outwardMost organizations generate indicators, alerts and TTP observations internally as a side effect of incident response; SP 800-150's first step is identifying those existing sources, not building new collection from scratch.
  2. Write sharing rules before you need themDecide in advance what can be shared, with whom, and under what designation — doing this mid-incident is the failure mode the guide calls out explicitly.
  3. Use TLP v2.0, not the v1.0 table in the 2016 PDFThe concept (graduated, labeled sharing designations) is still sound; the specific four-color table in SP 800-150 predates FIRST's current five-label standard.
  4. Match the community to the goalAn informal, voluntary-cooperation community suits ad hoc indicator exchange; a sector ISAC or ISAO suits a sustained, higher-trust relationship — SP 800-150's own taxonomy is a useful checklist when choosing which to join first.
  5. Tie sharing to incident responseSP 800-150 says it "expands upon" Section 4, Coordination and Information Sharing, of SP 800-61; see NIST SP 800-61 for how sharing fits the response cycle.

On the inbound side, SoftWSP extracts a CycloneDX 1.6 SBOM from a firmware image and matches its components against NVD, the CISA KEV catalog, FIRST EPSS scores and CISA's CSAF ICS advisories. It then drafts a cited report for an engineer to review, and watchlist alerts fire on a CVE ID or a vendor/product name. It does not exchange STIX or TAXII, publish CSAF or write VEX; those outward steps stay with your PSIRT. SoftWSP's PSIRT setup work builds the intake, triage and disclosure process around them, and the same program is the natural place to formalize what a hardware or firmware maker shares outward with its sector's ISAC or ISAO: see PSIRT.

This guide summarises NIST Special Publication 800-150 (October 2016), FIRST's current Traffic Light Protocol standard and the OASIS STIX 2.1, TAXII 2.1 and CSAF 2.0 specifications, as checked on 11 November 2026; it does not constitute security or compliance advice.

Put this guide to work

Frequently asked questions

What is NIST SP 800-150?

A NIST Special Publication titled "Guide to Cyber Threat Information Sharing," published in October 2016 (35 pages) by NIST's Chris Johnson, Lee Badger and David Waltermire together with Julie Snyder and Clem Skorupka of The MITRE Corporation. NIST's own abstract states the publication "provides guidelines for establishing and participating in cyber threat information sharing relationships," helping organizations "establish information sharing goals, identify cyber threat information sources, scope information sharing activities, develop rules that control the publication and distribution of threat information, engage with existing sharing communities, and make effective use of threat information." Per the document's own Section 1.2, it is "written primarily for federal agencies" but "intended to be applicable to a wide variety of governmental and non-governmental organizations," with a named audience that includes CSIRTs, CISOs, CIOs, privacy officers and security program managers.

What counts as "cyber threat information" under SP 800-150?

The guide's Section 2.1 names five major types. **Indicators** are "technical artifacts or observables that suggest an attack is imminent or is currently underway or that a compromise may have already occurred" (an IP address, a malicious file hash, a suspicious domain). **Tactics, techniques, and procedures (TTPs)** "describe the behavior of an actor," from high-level tactics down to detailed procedures. **Security alerts** (advisories, bulletins, vulnerability notes) are "brief, usually human-readable" notices, sourced from places such as US-CERT, ISACs, the National Vulnerability Database and PSIRTs. **Threat intelligence reports** are prose documents giving the context a decision-maker needs. **Tool configurations** are concrete artifacts such as IDS signatures, firewall rules or ACLs built from the other four types.

What is the Traffic Light Protocol (TLP) that SP 800-150 documents, and is it still current?

SP 800-150's Section 3.4.2 names the Traffic Light Protocol as the framework it uses for "sharing designations," and Table 3-3 reproduces what the document itself labels **"Traffic Light Protocol, Version 1.0"** — four colors, RED/AMBER/GREEN/WHITE, each with a short recipient-sharing rule (for example, TLP:RED recipients "may not share TLP:RED information with any parties outside of the specific exchange"). That table is now outdated: FIRST, the protocol's maintaining body, states its current standard is **TLP Version 2.0, authoritative from August 2022**, which keeps RED/AMBER/GREEN, splits AMBER into AMBER and a stricter **AMBER+STRICT**, and renames WHITE to **TLP:CLEAR**. SP 800-150 itself has not been revised since October 2016 to reflect that change — a team citing this guide's sharing-designation table today should use FIRST's current TLP v2.0 labels, not the Version 1.0 table printed in the 2016 NIST document.

Who does SP 800-150 say organizations actually share threat information with?

Section 3.5 lists "examples of potential sharing partners" as "ISACs, domestic and foreign Computer Emergency Readiness Teams (CERTs) or CSIRTs, Information Sharing and Analysis Organizations (ISAOs), DHS Automated Indicator Sharing (AIS) initiative, threat and vulnerability repositories, law enforcement agencies, product vendors, managed security service providers, internet service providers, supply chain partners, industry sector peers, business partners, and customers." The guide's own glossary (Appendix B) defines an ISAO as "any entity or collaboration created or employed by public- or private sector organizations, for purposes of gathering and analyzing critical cyber and related information in order to better understand security problems and interdependencies related to cyber systems." Section 3.5 also distinguishes informal, self-organizing communities that "largely operate through voluntary cooperation" under "basic rules of conduct" from more formally structured ones.

Sources

  1. NIST CSRC: SP 800-150 publication page (abstract, keywords, topics, document history, DOI)
  2. NIST SP 800-150: Guide to Cyber Threat Information Sharing (full text PDF, October 2016)
  3. FIRST: Traffic Light Protocol (TLP) — current standard, Version 2.0
  4. NIST CSRC: SP 800-61 Rev. 3 publication page (the incident-response guide SP 800-150 builds on, now restructured around CSF 2.0)
  5. OASIS: STIX Version 2.1 (OASIS Standard, Errata 01) — STIX Domain Objects
  6. OASIS: TAXII Version 2.1 (OASIS Standard, 10 June 2021) — Collections and Channels
  7. OASIS: Common Security Advisory Framework (CSAF) Version 2.0 (OASIS Standard, 18 November 2022) — TLP label, distribution roles, provider-metadata.json
  8. OASIS: CSAF Version 2.1, Committee Specification Draft 04 (21 October 2026)
  9. National Council of ISACs: home and member ISACs
  10. EUR-Lex: Directive (EU) 2022/2555 (NIS2), Article 29 cybersecurity information-sharing arrangements
  11. EUR-Lex: Regulation (EU) 2024/2847 (Cyber Resilience Act), Article 14 and Annex I Part II
Was this guide helpful?

In this cluster