Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
TLP is a four-colour labelling scheme that tells the recipient of shared security information exactly how far they may pass it on, using terms both parties already understand.

What Is the Traffic Light Protocol?
The Traffic Light Protocol solves a small problem that blocks a large amount of useful sharing: when somebody hands you sensitive information, how far may you pass it on? TLP answers with a colour label applied by the originator. It carries no legal force, but it is understood across incident response teams, sector sharing communities, and national bodies worldwide, which makes it the common vocabulary for handling restrictions.
The scheme was created in the early 2000s by what is now the NCSC, and is maintained today by FIRST, the Forum of Incident Response and Security Teams. TLP 2.0, published in August 2022, is the current version.
| Label | Who may receive it |
|---|---|
| TLP:RED | Only the individuals named in the exchange. Not your colleagues, not your manager, not your incident channel. |
| TLP:AMBER+STRICT | Your organisation only. Clients, contractors, and parent companies are excluded. |
| TLP:AMBER | Your organisation and clients who need it to protect themselves. |
| TLP:GREEN | The wider community and peer organisations, but not published publicly or posted online. |
| TLP:CLEAR | No restriction. Publish freely, subject to copyright. |
Two changes in TLP 2.0 are worth knowing. AMBER+STRICT was added because the original AMBER allowed onward sharing with clients, which many originators had not intended; the new label closes that. And TLP:WHITE was renamed TLP:CLEAR, with the meaning unchanged. Older documents still use WHITE, and tooling should treat the two as equivalent.
Labels go in the subject line of an email, in the header and footer of a document, and at the top of a chat message, written in capitals in the exact form TLP:AMBER. In structured data, STIX marking definitions carry the label with the object, so the restriction travels with the indicator rather than being lost when somebody copies a hash out of a report.
A few rules prevent most disputes. Only the originator may change a label; if you need wider distribution, ask. Where a report mixes sensitivities, label at the highest level and consider issuing a lower-marked extract for broader circulation—this is how the NCSC and most sector bodies publish, with a restricted version for members and a public summary. If something arrives unlabelled and is clearly sensitive, ask the sender rather than guessing, and treat it as AMBER in the meantime.
The most common failure is labelling everything AMBER out of caution, which trains recipients to ignore the label entirely. The second is receiving TLP:RED material and forwarding it into a group chat because that is where incidents get discussed—a reflex worth addressing in training, since RED genuinely means the named individuals only. The third is assuming the protocol has legal weight. It does not. If information must be protected contractually, you need a non-disclosure agreement; TLP is an expectation of good faith between professionals, and its effectiveness depends entirely on reciprocity.
A subtler issue is data protection. Shared security information sometimes contains personal data—an employee’s address in a phishing header, a named individual in an insider case. TLP governs distribution but does not provide a lawful basis under UK GDPR for processing that data, nor does it discharge your obligations if you redistribute it. Minimise personal data before sharing, and keep the two questions separate in your head.
TLP is just as useful inside an organisation as between them. Mark incident updates so that a technical finding circulated to the response team is not forwarded to a business distribution list before legal has reviewed it. Teach the labels alongside the incident process rather than as a separate policy, and make the handling expectations concrete: which systems may hold AMBER+STRICT material, who may brief RED content, and what happens when an item needs re-marking.
Communities that depend on the protocol—an ISAC, CiSP, or a bilateral exchange with a peer—work only while members honour it. Breaking a label once costs an organisation access it will not easily regain.
At Privia Security, we set up sharing handling rules alongside response processes in our investigation and incident response services.
It was renamed TLP:CLEAR in version 2.0, published by FIRST in August 2022, with no change in meaning: unrestricted distribution subject to copyright. The rename avoided the implication that white carried any racial connotation and made the intent clearer. Older material still uses WHITE, and tools should accept both labels as equivalent.
No. It records the originator’s expectation and relies on professional reciprocity, not on law or contract. If information must be protected enforceably, use a non-disclosure agreement or contractual confidentiality terms alongside the label. In practice the social sanction is effective, because an organisation that breaks a marking loses access to the community that supplied it.
AMBER permits sharing within your organisation and with clients who need the information to protect themselves. AMBER+STRICT limits it to your organisation only, excluding clients, contractors, and group companies. The stricter label was added in TLP 2.0 because many originators had assumed AMBER meant organisation-only and were surprised to find material reaching third parties.
Ask the sender what marking they intended, and treat it as TLP:AMBER until they answer. Never assume unlabelled means public, particularly for incident detail shared in a conversation. If you are the originator, label everything you send, including short messages, because a habit applied inconsistently is the one people stop checking.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.