- TLP 2.0 replaced TLP:WHITE with TLP:CLEAR and added TLP:AMBER+STRICT.
- TLP:AMBER includes the recipient's clients by default. Use TLP:AMBER+STRICT to keep information inside one organization.
- TLP is not a classification scheme and is not legally binding. It does not override laws or contracts.
What is the Traffic Light Protocol (TLP)?
The Traffic Light Protocol is a simple way to say who may see a piece of security information. FIRST, the Forum of Incident Response and Security Teams, maintains the standard. In its words, "TLP is a set of four labels used to indicate the sharing boundaries to be applied by the recipients" (FIRST). The current version is 2.0: "TLP version 2.0 is the current version of TLP standardized by FIRST. It is authoritative from August 2022 onwards" (FIRST).
Two roles matter. The source is whoever shares the information, and it picks the label. The recipient follows the label. FIRST puts the duty on the source: "The source is responsible for ensuring that recipients of TLP-labeled information understand and can follow TLP sharing guidance" (FIRST). A recipient who wants to share more widely has one route: "If a recipient needs to share information more widely than indicated by the TLP label it came with, they must obtain explicit permission from the source" (FIRST).
TLP is a sharing convention, not a law. CISA, the US Cybersecurity and Infrastructure Security Agency, notes: "Unlike formal classification systems, TLP is not legally binding" (CISA fact sheet), and its user guide adds that "TLP is not legally binding and does not override legal restrictions or obligations" (CISA user guide). FIRST also says "TLP was not designed to handle licensing terms, nor information handling or encryption rules" (FIRST).
What do TLP:RED, TLP:AMBER, TLP:GREEN and TLP:CLEAR mean?
The table follows FIRST's definitions. "The four TLP labels are: TLP:RED, TLP:AMBER, TLP:GREEN, and TLP:CLEAR" (FIRST). AMBER+STRICT is a stricter form of AMBER, not a fifth color. Three words have set meanings in the standard: an organization is a group bound by formal membership and common policies; clients are those who receive cybersecurity services from that organization; a community is a wider group with common goals and informal trust, such as a sector's security practitioners.
| Label | Who may receive it | When a source uses it |
|---|---|---|
| TLP:RED | Only the individual recipients. In a meeting, only those present. | When acting on it carries significant risk for the privacy, reputation or operations of the organizations involved |
| TLP:AMBER+STRICT | Members of the recipient's own organization, need to know | When it needs support to act on but carries risk if shared outside the organization |
| TLP:AMBER | Members of the recipient's organization and its clients, need to know | When it needs support to act on but carries risk if shared outside the organizations involved |
| TLP:GREEN | Peers and partner organizations in the community, not public channels | When it is useful to raise awareness in the wider community |
| TLP:CLEAR | Anyone. No limit on disclosure, subject to copyright | When it carries minimal or no foreseeable risk of misuse |
In FIRST's wording: TLP:RED is "For the eyes and ears of individual recipients only, no further disclosure"; TLP:GREEN recipients "may share TLP:GREEN information with peers and partner organizations within their community, but not via publicly accessible channels"; and "Subject to standard copyright rules, TLP:CLEAR information may be shared without restriction" (FIRST). Where no community is named for GREEN, FIRST says to "assume the cybersecurity/defense community."
What is the difference between TLP:AMBER and TLP:AMBER+STRICT?
The difference is the recipient's clients. Under TLP:AMBER, "Recipients may share TLP:AMBER information with members of their own organization and its clients, but only on a need-to-know basis to protect their organization and its clients and prevent further harm" (FIRST). FIRST explains why clients are in: "Clients are by default included in TLP:AMBER so that the recipients may share information further downstream in order for clients to take action to protect themselves."
TLP:AMBER+STRICT removes the clients. CISA's page says: "Recipients may share TLP:AMBER+STRICT information only with members of their own organization on a need-to-know basis to protect their organization and prevent further harm" (CISA). So a managed security provider that receives an AMBER report can warn its customers. If the report says AMBER+STRICT, it cannot.
Neither label lets a recipient pass the information to its own outside service providers. FIRST's use cases say: "Do not share TLP:AMBER with outside organizations that provide you services without permission from the originator" (FIRST use cases). The same applies to AMBER+STRICT.
What changed from TLP 1.0 to TLP 2.0?
CISA's fact sheet lists two major changes: "TLP:CLEAR replaces TLP:WHITE" and "The new TLP:AMBER+STRICT supplements TLP:AMBER, designating that the information may be shared with the recipient's organization only" (CISA fact sheet). It also records that "The Cybersecurity and Infrastructure Security Agency will officially move from TLP 1.0 to TLP 2.0 on November 1, 2022." FIRST's site marks TLP 1.0 as deprecated in August 2022.
| TLP 1.0 | TLP 2.0 | |
|---|---|---|
| Label for public information | TLP:WHITE | TLP:CLEAR |
| Organization-only sharing | No label for it | TLP:AMBER+STRICT |
| TLP:AMBER | Restricted to the participants' organizations | Recipient organization and its clients, need to know |
On the written form, FIRST says the labels "MUST not contain spaces and SHOULD be in capitals" (FIRST). Old documents marked TLP:WHITE are still around; when you reissue one, use TLP:CLEAR.
How do you mark an email or a document with TLP?
For email and chat, FIRST says the label and any added limits go "directly prior to the information itself", and "The TLP label SHOULD be in the subject line of email" (FIRST). For documents: "TLP-labeled documents MUST indicate the TLP label of the information, as well as any additional restrictions, in the header and footer of each page."
- Put the label at the start of the subject line and again right before the information.
- Use one overall label for a mixed report: FIRST's use cases say it "should be the most restrictive TLP that is used anywhere in the information."
- Mark the start and end of any part that carries a different label, such as indicators that may go to the community.
- Give a standing chat channel a default label in its pinned message or banner; otherwise readers may assume TLP:CLEAR.
- Add plain-language limits when needed, such as "do not share outside the EU". FIRST allows extra restrictions, and recipients must follow them.
Example: a phishing notice with two TLP labels
The notice below is an illustration written for this page, not a real company's message. The domain and address are reserved for documentation. The overall label is the most restrictive one, and the indicators that may travel further are marked as a separate TLP:GREEN block.
Subject: TLP:AMBER+STRICT Phishing kit targeting our customer sign-in page
TLP:AMBER+STRICT
Share only inside your own organization, on a need-to-know basis.
Summary: since 03:10 UTC a phishing site has copied our sign-in page and
sends stolen passwords to a server we do not control. We are working with
the hosting provider to take it down.
Start of TLP:GREEN
Indicators you may share with your sector community (not publicly):
phishing domain signin-support.example.net
collection server 203.0.113.45
End of TLP:GREEN
Return to TLP:AMBER+STRICT
Context: two staff accounts were targeted. Names, ticket numbers and the
hosting provider's contact stay inside your organization.
To share any part of this more widely, ask the sender first.
A recipient may pass the two indicators to its sector sharing group. Everything else stays inside its own organization.
Can you share TLP information with an ISAC or a service provider?
An ISAC (information sharing and analysis center) is a sharing group for one sector, such as finance or health care. CISA's user guide says a member of an ISAC's management body may pass TLP:AMBER to the members when the information was sent to the ISAC, but "You may not share TLP:AMBER+STRICT information with members unless you obtain permission from the originator to do so" (CISA user guide). TLP:RED is not shared at all.
For service providers, the default answer is no for AMBER and AMBER+STRICT, as above. FIRST suggests that a source who wants providers involved say so in writing, and recommends sharing with them only as AMBER+STRICT, so the provider cannot pass it to its other clients (FIRST use cases). It also warns: "Note that TLP may not be able to support all legal regimes that require or restrict further sharing of information." This is general information, not legal advice.
Common mistakes with the Traffic Light Protocol
Most mistakes come from treating TLP as a rough sense of sensitivity rather than a list of who may receive.
- Writing "TLP Amber" or "AMBER" without the prefix. The label is TLP:AMBER, in capitals, with no spaces.
- Forwarding a TLP:AMBER report to an outside consultant, lawyer or managed provider without asking the source.
- Assuming TLP:AMBER+STRICT allows sharing with clients. It does not.
- Posting TLP:GREEN indicators on a public blog or a public repository. GREEN stays inside the community.
- Still using TLP:WHITE in new material, or inventing labels such as "TLP:YELLOW". FIRST treats only its listed labels as valid.
- Treating TLP as if it settled legal questions. It does not override a contract, a law or a regulator's request.
Which incident records can a company share outside, given TLP?
TLP marks set who may receive a record, so they also mark what can never leave the company. AI data buyers have asked Origin for the records of companies that run and defend their own infrastructure: incidents joined to the change that fixed them (the ticket, the chat thread, the config diff or pull request, the outcome), configuration history, ordered logs of an attack and the response, and the runbooks, SOC tickets, on-call records and postmortems of the same period. A company's own incident records are its own to label and to share. Records it received from others under TLP:RED, TLP:AMBER or TLP:AMBER+STRICT stay out, and so does TLP:GREEN material, which may not leave the community. Only the source can widen those limits. The same line is drawn on the security incident data page.
Origin is an independent data partner. Your company decides what is shared and signs any license itself, and a buyer may pay Origin when a deal closes.
- Received intelligence: remove every advisory, report, indicator list and chat message that arrived under RED, AMBER, AMBER+STRICT or GREEN, including quotes pasted into your own tickets.
- Mixed tickets: where an analyst copied a shared indicator into your own case, cut that part and keep your own work. See the incident timeline template.
- Client environments: records about a client's systems stay out unless that client has agreed. See SOC case data.
- Personal data and secrets: mask staff and customer names, and anonymize addresses (anonymizing pcap files and logs).
Does your company hold records like these? See what your data is worth.
Common questions
What does TLP:AMBER+STRICT mean?
TLP:AMBER+STRICT means the recipient may share the information only with members of its own organization, on a need-to-know basis. It is stricter than TLP:AMBER, which also allows sharing with the organization's clients. FIRST added AMBER+STRICT in TLP 2.0 in August 2022 so sources could keep information inside one organization.
Who can you share TLP:GREEN information with?
You may share TLP:GREEN information with peers and partner organizations within your community, but not through publicly accessible channels such as a public website or social media. If the source does not define the community, FIRST says to assume the cybersecurity or cyber defense community. A source can narrow it, for example to one sector.
What replaced TLP:WHITE?
TLP:CLEAR replaced TLP:WHITE when FIRST published TLP 2.0 in August 2022. The meaning is the same: there is no limit on disclosure, subject to standard copyright rules. CISA moved to TLP 2.0 on 1 November 2022. New material should use TLP:CLEAR; older documents may still say TLP:WHITE.
Is the Traffic Light Protocol legally binding?
No. CISA says TLP is not legally binding and does not override legal restrictions or obligations, and FIRST says it is not a formal classification scheme and was not designed to handle licensing terms. It is a sharing convention that security teams agree to follow. Contracts, laws and regulators can still require or forbid disclosure.
Can I forward a TLP:AMBER report to my managed security provider?
Not without permission. FIRST's use cases say not to share TLP:AMBER or TLP:AMBER+STRICT information with outside organizations that provide you services unless the originator permits it, through a standing agreement, an answer to your request or instructions with the information. Ask the sender first, and expect AMBER+STRICT terms.
Can a company share its own incident reports marked TLP:AMBER?
Yes. A company that wrote a report is its source, so the label it chose limits its recipients, not the company itself. The company can relabel or share its own records as it decides. What it cannot share is information it received from others under RED, AMBER, AMBER+STRICT or GREEN without the source's permission.
