US Edition Austin, TX UTC 00:00:00

Traffic Light Protocol (TLP 2.0): RED, AMBER+STRICT, GREEN, CLEAR

What TLP:RED, AMBER, AMBER+STRICT, GREEN and CLEAR allow under FIRST's TLP 2.0, how to write the labels, and what changed from TLP 1.0.

The Traffic Light Protocol (TLP) is a set of labels that tell a recipient how far they may pass on a piece of information. FIRST's TLP 2.0 standard defines four labels, TLP:RED, TLP:AMBER, TLP:GREEN and TLP:CLEAR, and TLP:AMBER+STRICT is a stricter form of AMBER that the source must name explicitly. In short: RED means the named recipients only, AMBER+STRICT means your own organisation only, AMBER adds your clients, GREEN means the wider community, and CLEAR means no restriction. FIRST describes TLP 2.0 as authoritative from August 2022.

This guide covers what each label permits, how AMBER and AMBER+STRICT differ, how to write the label correctly, and what changed from TLP 1.0. Everything below follows the FIRST TLP 2.0 standard, as read in October 2026.

The TLP 2.0 labels at a glance

  • TLP:RED: for the individual recipients only. Nobody else may receive it. In a meeting, that means the people present.
  • TLP:AMBER: for the recipient's organisation and its clients, on a need-to-know basis.
  • TLP:AMBER+STRICT: AMBER restricted to the recipient's organisation only, with no sharing to clients.
  • TLP:GREEN: for the recipient's community, but not through publicly accessible channels.
  • TLP:CLEAR: for anyone, with no disclosure limit beyond ordinary copyright rules.

The labels describe how far the information may be shared, not how technically dangerous it is.

What each label means in practice

TLP:RED

The standard says sources may use RED when the information cannot be effectively acted upon without significant risk to the privacy, reputation or operations of the organisations involved. Recipients may not share it with anyone else. If you receive a RED indicator list and think your SOC team needs it, you cannot forward it; you must ask the source for permission first.

TLP:AMBER+STRICT

This label limits the information to the recipient's own organisation. Clients and customers are excluded. FIRST notes that a source who wants sharing restricted to the organisation only must specify TLP:AMBER+STRICT, so a plain AMBER does not carry that limit.

TLP:AMBER

FIRST says sources may use AMBER when information requires support to be acted upon effectively, yet carries risk if shared outside the organisations involved. Recipients may share it inside their organisation and with clients, but only as far as needed to protect those parties and prevent further harm. A managed security provider, for example, could pass AMBER detection logic to customers who need it, and no further.

TLP:GREEN

FIRST says sources may use GREEN when information is useful to increase awareness within a wider community. Recipients may share it with peers and partner organisations in their community, but not through publicly accessible channels such as a blog, a public repository or social media. If the sender does not define the community, the standard says to assume the cybersecurity and defence community.

TLP:CLEAR

CLEAR applies when the information carries minimal or no foreseeable risk of misuse and may be released publicly under the applicable rules. It may be shared without restriction, subject to standard copyright rules.

TLP:AMBER vs TLP:AMBER+STRICT

The only difference is the audience. Plain AMBER lets the recipient pass the information to their organisation and to clients who need it. AMBER+STRICT stops at the organisation's edge. If you are unsure which one a sender meant, treat an unqualified AMBER as the broader label, and ask before sharing with customers when the content is sensitive.

AMBER+STRICT is therefore the right choice when the sender would be uncomfortable with a third-party client seeing the material, for instance when it names a victim or an unpatched weakness.

TLP:CLEAR vs TLP:WHITE

TLP:CLEAR is the TLP 2.0 name for what TLP 1.0 called TLP:WHITE. Both mean no limit on disclosure. FIRST lists TLP 1.0 as deprecated and TLP:WHITE does not appear among the valid TLP 2.0 labels, so new documents should use CLEAR. An older report marked WHITE was meant as unrestricted, but it is worth checking whether the publisher has updated it.

What changed from TLP 1.0

TLP 1.0 had four labels: RED, AMBER, GREEN and WHITE. TLP 2.0 changed the set in two visible ways:

  • WHITE was renamed CLEAR.
  • AMBER+STRICT was added as an option, so a sender can restrict sharing to one organisation only.

FIRST lists TLP 1.0 as deprecated in August 2022. CISA publishes its own TLP guidance, and its page states that the agency officially adopted FIRST's TLP version 2.0 standard on November 1, 2022. If you work with US government partners, expect 2.0 labels.

How to write a TLP label correctly

The standard sets out a few formatting rules that are easy to get wrong:

  • No spaces inside the label, and capitals recommended. Write TLP:AMBER+STRICT, not "TLP: Amber Strict".
  • Do not translate the label. The text around it can be in another language, but the label stays in its original form.
  • In email and chat, put the label directly before the information, and it should also appear in the email subject line. The end of the labelled text should be marked.
  • In documents, put the label in the header and footer of every page, in 12-point type or greater for users with low vision. Right-justifying the label is recommended.

The standard also publishes colour values, all on a black background (#000000). As of October 2026 the font colours are #FF2B2B for RED, #FFC000 for AMBER, #33FF00 for GREEN and #FFFFFF for CLEAR. The page lists no values for a white background and none specific to AMBER+STRICT, so check the current standard before building templates.

Common mistakes

  • Treating TLP as a security classification. CISA says TLP is not a control marking or classification scheme, was not designed to set licensing, handling or encryption rules, and is not intended to affect freedom-of-information laws.
  • Forwarding without permission. If you need a wider audience than the label allows, the standard requires you to ask the source first.
  • Ignoring extra restrictions. A source may add conditions on top of a label, and recipients must follow them.
  • Posting GREEN material publicly. GREEN is for the community, not for public channels.
  • Leaving material unlabelled. The standard makes the source responsible for ensuring recipients understand and can follow the label.

Where TLP shows up in security work

You will meet TLP in vulnerability disclosures, incident reports, threat intelligence feeds and information-sharing communities. It sits alongside other shared vocabularies such as the MITRE ATT&CK tactics list and scoring systems like EPSS. For more on the topic, browse our Security coverage, including vulnerabilities, and the guides section.

Frequently asked questions

What is the difference between TLP:AMBER and TLP:AMBER+STRICT?

AMBER allows sharing inside the recipient's organisation and with clients who need the information. AMBER+STRICT allows sharing inside the organisation only.

Is TLP:CLEAR the same as TLP:WHITE?

CLEAR replaced WHITE in TLP 2.0, which FIRST describes as authoritative from August 2022. CLEAR means the information may be shared without restriction, subject to standard copyright rules.

Can I share TLP:GREEN information publicly?

No. GREEN information may be shared with peers and partner organisations in your community, but not through publicly accessible channels.

Is TLP a classification system?

No. CISA states that TLP is not a control marking or classification scheme, and that it was not designed to set licensing, handling or encryption rules.

Where should the TLP label go in an email?

Put it directly before the labelled content and in the subject line, and mark where the labelled text ends. The label must not contain spaces and should be in capitals.