www.cisa.gov Open in urlscan Pro
2a02:26f0:3400:296::447a  Public Scan

Form analysis
2 forms found in the DOM

<form class="gsc-search-box gsc-search-box-tools" accept-charset="utf-8">
  <table cellspacing="0" cellpadding="0" role="presentation" class="gsc-search-box">
    <tbody>
      <tr>
        <td class="gsc-input">
          <div class="gsc-input-box" id="gsc-iw-id1">
            <table cellspacing="0" cellpadding="0" role="presentation" id="gs_id50" class="gstl_50 gsc-input" style="width: 100%; padding: 0px;">
              <tbody>
                <tr>
                  <td id="gs_tti50" class="gsib_a"><input autocomplete="off" type="text" size="10" class="gsc-input" name="search" title="search" aria-label="search" id="gsc-i-id1" dir="ltr" spellcheck="false"
                      style="width: 100%; padding: 0px; border: none; margin: 0px; height: auto; outline: none;"></td>
                  <td class="gsib_b">
                    <div class="gsst_b" id="gs_st50" dir="ltr"><a class="gsst_a" href="javascript:void(0)" title="Clear search box" role="button" style="display: none;"><span class="gscb_a" id="gs_cb50" aria-hidden="true">×</span></a></div>
                  </td>
                </tr>
              </tbody>
            </table>
          </div>
        </td>
        <td class="gsc-search-button"><button class="gsc-search-button gsc-search-button-v2"><svg width="13" height="13" viewBox="0 0 13 13">
              <title>search</title>
              <path
                d="m4.8495 7.8226c0.82666 0 1.5262-0.29146 2.0985-0.87438 0.57232-0.58292 0.86378-1.2877 0.87438-2.1144 0.010599-0.82666-0.28086-1.5262-0.87438-2.0985-0.59352-0.57232-1.293-0.86378-2.0985-0.87438-0.8055-0.010599-1.5103 0.28086-2.1144 0.87438-0.60414 0.59352-0.8956 1.293-0.87438 2.0985 0.021197 0.8055 0.31266 1.5103 0.87438 2.1144 0.56172 0.60414 1.2665 0.8956 2.1144 0.87438zm4.4695 0.2115 3.681 3.6819-1.259 1.284-3.6817-3.7 0.0019784-0.69479-0.090043-0.098846c-0.87973 0.76087-1.92 1.1413-3.1207 1.1413-1.3553 0-2.5025-0.46363-3.4417-1.3909s-1.4088-2.0686-1.4088-3.4239c0-1.3553 0.4696-2.4966 1.4088-3.4239 0.9392-0.92727 2.0864-1.3969 3.4417-1.4088 1.3553-0.011889 2.4906 0.45771 3.406 1.4088 0.9154 0.95107 1.379 2.0924 1.3909 3.4239 0 1.2126-0.38043 2.2588-1.1413 3.1385l0.098834 0.090049z">
              </path>
            </svg></button></td>
        <td class="gsc-clear-button">
          <div class="gsc-clear-button" title="clear results">&nbsp;</div>
        </td>
      </tr>
    </tbody>
  </table>
</form>

<form class="gsc-search-box gsc-search-box-tools" accept-charset="utf-8">
  <table cellspacing="0" cellpadding="0" role="presentation" class="gsc-search-box">
    <tbody>
      <tr>
        <td class="gsc-input">
          <div class="gsc-input-box" id="gsc-iw-id2">
            <table cellspacing="0" cellpadding="0" role="presentation" id="gs_id51" class="gstl_51 gsc-input" style="width: 100%; padding: 0px;">
              <tbody>
                <tr>
                  <td id="gs_tti51" class="gsib_a"><input autocomplete="off" type="text" size="10" class="gsc-input" name="search" title="search" aria-label="search" id="gsc-i-id2" dir="ltr" spellcheck="false"
                      style="width: 100%; padding: 0px; border: none; margin: 0px; height: auto; outline: none;"></td>
                  <td class="gsib_b">
                    <div class="gsst_b" id="gs_st51" dir="ltr"><a class="gsst_a" href="javascript:void(0)" title="Clear search box" role="button" style="display: none;"><span class="gscb_a" id="gs_cb51" aria-hidden="true">×</span></a></div>
                  </td>
                </tr>
              </tbody>
            </table>
          </div>
        </td>
        <td class="gsc-search-button"><button class="gsc-search-button gsc-search-button-v2"><svg width="13" height="13" viewBox="0 0 13 13">
              <title>search</title>
              <path
                d="m4.8495 7.8226c0.82666 0 1.5262-0.29146 2.0985-0.87438 0.57232-0.58292 0.86378-1.2877 0.87438-2.1144 0.010599-0.82666-0.28086-1.5262-0.87438-2.0985-0.59352-0.57232-1.293-0.86378-2.0985-0.87438-0.8055-0.010599-1.5103 0.28086-2.1144 0.87438-0.60414 0.59352-0.8956 1.293-0.87438 2.0985 0.021197 0.8055 0.31266 1.5103 0.87438 2.1144 0.56172 0.60414 1.2665 0.8956 2.1144 0.87438zm4.4695 0.2115 3.681 3.6819-1.259 1.284-3.6817-3.7 0.0019784-0.69479-0.090043-0.098846c-0.87973 0.76087-1.92 1.1413-3.1207 1.1413-1.3553 0-2.5025-0.46363-3.4417-1.3909s-1.4088-2.0686-1.4088-3.4239c0-1.3553 0.4696-2.4966 1.4088-3.4239 0.9392-0.92727 2.0864-1.3969 3.4417-1.4088 1.3553-0.011889 2.4906 0.45771 3.406 1.4088 0.9154 0.95107 1.379 2.0924 1.3909 3.4239 0 1.2126-0.38043 2.2588-1.1413 3.1385l0.098834 0.090049z">
              </path>
            </svg></button></td>
        <td class="gsc-clear-button">
          <div class="gsc-clear-button" title="clear results">&nbsp;</div>
        </td>
      </tr>
    </tbody>
  </table>
</form>

Text Content

Skip to main content

An official website of the United States government

Here’s how you know

Here’s how you know

Official websites use .gov
A .gov website belongs to an official government organization in the United
States.

Secure .gov websites use HTTPS
A lock (LockA locked padlock) or https:// means you’ve safely connected to the
.gov website. Share sensitive information only on official, secure websites.


Cybersecurity & Infrastructure Security Agency
America's Cyber Defense Agency

Search

×

search
 

Menu
Close
×

search
 

 * Topics
   Topics
   Cybersecurity Best Practices
   Cyber Threats and Advisories
   Critical Infrastructure Security and Resilience
   Election Security
   Emergency Communications
   Industrial Control Systems
   Information and Communications Technology Supply Chain Security
   Partnerships and Collaboration
   Physical Security
   Risk Management
   How can we help?
   GovernmentEducational InstitutionsIndustryState, Local, Tribal, and
   TerritorialIndividuals and FamiliesSmall and Medium BusinessesFind Help
   Locally
 * Spotlight
 * Resources & Tools
   Resources & Tools
   All Resources & Tools
   Services
   Programs
   Resources
   Training
   Groups
 * News & Events
   News & Events
   News
   Events
   Cybersecurity Alerts & Advisories
   Directives
   Request a CISA Speaker
   Congressional Testimony
 * Careers
   Careers
   Benefits & Perks
   HireVue Applicant Reasonable Accommodations Process
   Hiring
   Resume & Application Tips
   Students & Recent Graduates
   Veteran and Military Spouses
   Work @ CISA
 * About
   About
   Culture
   Divisions & Offices
   Regions
   Leadership
   Doing Business with CISA
   Contact Us
   Site Links
   Reporting Employee and Contractor Misconduct
   CISA GitHub

Report a Cyber Issue
America's Cyber Defense Agency
Breadcrumb
 1. Home
 2. News & Events
 3. News

Share:


Blog


TRAFFIC LIGHT PROTOCOL (TLP) DEFINITIONS AND USAGE

Released
August 16, 2022
Revised
August 22, 2022
Related topics:
Cyber Threats and Advisories


On November 1, 2022, CISA officially adopted FIRST Standard Definitions and
Usage Guidance - Version 2.0 and will update this page to reflect the new
version. See CISA's TLP 2.0 User Guide and TLP: Moving to Version 2.0 Fact Sheet
for details.


INTRODUCTION

The Traffic Light Protocol (TLP) was created in order to facilitate greater
sharing of information. TLP is a set of designations used to ensure that
sensitive information is shared with the appropriate audience. It employs four
colors to indicate expected sharing boundaries to be applied by the
recipient(s). TLP only has four colors; any designations not listed in this
standard are not considered valid by FIRST.

TLP provides a simple and intuitive schema for indicating when and how sensitive
information can be shared, facilitating more frequent and effective
collaboration. TLP is not a "control marking" or classification scheme. TLP was
not designed to handle licensing terms, handling and encryption rules, and
restrictions on action or instrumentation of information. TLP labels and their
definitions are not intended to have any effect on freedom of information or
"sunshine" laws in any jurisdiction.

TLP is optimized for ease of adoption, human readability and person-to-person
sharing; it may be used in automated sharing exchanges but is not optimized for
that use.

TLP is distinct from the Chatham House Rule (when a meeting, or part thereof, is
held under the Chatham House Rule, participants are free to use the information
received, but neither the identity nor the affiliation of the speaker(s), nor
that of any other participant, may be revealed.), but may be used in conjunction
if it is deemed appropriate by participants in an information exchange.

The source is responsible for ensuring that recipients of TLP information
understand and can follow TLP sharing guidance.

If a recipient needs to share the information more widely than indicated by the
original TLP designation, they must obtain explicit permission from the original
source.

 


DEFINITIONS


TLP: RED

Not for disclosure, restricted to participants only.


TLP: AMBER+STRICT

Limited disclosure, restricted to participants’ organization.


TLP: AMBER

Limited disclosure, restricted to participants’ organization and its clients
(see Terminology Definitions).


TLP: GREEN

Limited disclosure, restricted to the community.


TLP: CLEAR

Disclosure is not limited.


TLP:RED

When should it be used? Sources may use TLP:RED when information cannot be
effectively acted upon without significant risk for the privacy, reputation, or
operations of the organizations involved. For the eyes and ears of individual
recipients only, no further.

How should it be shared? Recipients may not share TLP:RED information with any
parties outside of the specific exchange, meeting, or conversation in which it
was originally disclosed. In the context of a meeting, for example, TLP:RED
information is limited to those present at the meeting. In most circumstances,
TLP:RED should be exchanged verbally or in person.


TLP:AMBER+STRICT

When should it be used? Sources may use TLP:AMBER+STRICT when information
requires support to be effectively acted upon, yet carries risk to privacy,
reputation, or operations if shared outside of the organization.

How should it be shared? 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.


TLP:AMBER

When should it be used? Sources may use TLP:AMBER when information requires
support to be effectively acted upon, yet carries risk to privacy, reputation,
or operations if shared outside of the organizations involved. Note that
TLP:AMBER+STRICT should be used to restrict sharing to the recipient
organization only.

How should it be shared? Recipients may share TLP:AMBER information with members
of their own organization and its clients on a need-to-know basis to protect
their organization and its clients and prevent further harm.


TLP:GREEN

When should it be used? Sources may use TLP:GREEN when information is useful to
increase awareness within their wider community.

How should it be shared? Recipients may share TLP:GREEN information with peers
and partner organizations within their community, but not via publicly
accessible channels. Unless otherwise specified, TLP:GREEN information may not
be shared outside of the cybersecurity or cyber defense community.


TLP:CLEAR

When should it be used? Sources may use TLP:CLEAR when information carries
minimal or no foreseeable risk of misuse, in accordance with applicable rules
and procedures for public release.

How should it be shared? Recipients may share this information without
restriction. Information is subject to standard copyright rules.


OTHER USAGE


HOW TO USE TLP IN EMAIL

TLP-designated email correspondence should indicate the TLP color of the
information in the Subject line and in the body of the email, prior to the
designated information itself. The TLP color must be in capital letters:
TLP:RED, TLP:AMBER, TLP:GREEN, or TLP:CLEAR.


HOW TO USE TLP IN DOCUMENTS

TLP-designated documents should indicate the TLP color of the information in the
header and footer of each page. To avoid confusion with existing control marking
schemes, it is advisable to right-justify TLP designations. The TLP color should
appear in capital letters and in 12 pt type or greater.

RGB:
TLP:RED : R=255, G=0, B=51, background: R=0, G=0, B=0
TLP:AMBER : R=255, G=192, B=0, background: R=0, G=0, B=0
TLP:GREEN : R=51, G=255, B=0, background: R=0, G=0, B=0
TLP:CLEAR : R=255, G=255, B=255, background: R=0, G=0, B=0

CMYK:
TLP:RED : C=0, M=100, Y=79, K=0, background: C=0, M=0, Y=0, K=100
TLP:AMBER : C=0, M=25, Y=100, K=0, background: C=0, M=0, Y=0, K=100
TLP:GREEN : C=79, M=0, Y=100, K=0, background: C=0, M=0, Y=0, K=100
TLP:CLEAR : C=0, M=0, Y=0, K=0, background: C=0, M=0, Y=0, K=100


RESOURCES


TLP 2.0 FACT SHEET

NOV 01, 2022 |
Download File (PDF, 298.15 KB)


TLP 2.0 USER GUIDE

NOV 01, 2022 |
Download File (PDF, 449.13 KB)


CISA UPGRADES TO TLP 2.0

NOV 01, 2022 | ALERT



RELATED ARTICLES

Aug 08, 2023
Blog


CISA AND FEMA PARTNER TO PROVIDE $374.9 MILLION IN GRANTS TO BOLSTER STATE AND
LOCAL CYBERSECURITY

Aug 08, 2023
Blog


CISA RECOGNIZES MARK BUCHHOLZ DURING BI-ANNUAL SAFECOM MEETING

Aug 04, 2023
Blog


CISA CYBERSECURITY STRATEGIC PLAN: SHIFTING THE ARC OF NATIONAL RISK TO CREATE A
SAFER FUTURE

Aug 03, 2023
Blog


A CALL TO ACTION: BOLSTER UEFI CYBERSECURITY NOW

Return to top
 * Topics
 * Spotlight
 * Resources & Tools
 * News & Events
 * Careers
 * About

Cybersecurity & Infrastructure Security Agency
 * Facebook
 * Twitter
 * LinkedIn
 * YouTube
 * Instagram
 * RSS

CISA Central 888-282-0870 Central@cisa.dhs.gov(link sends email)
DHS Seal
CISA.gov
An official website of the U.S. Department of Homeland Security
 * About CISA
 * Accessibility
 * Budget and Performance
 * DHS.gov
 * FOIA Requests
 * No FEAR Act
 * Office of Inspector General
 * Privacy Policy
 * Subscribe
 * The White House
 * USA.gov
 * Website Feedback