What Are the Benefits of C-TPAT in 2018?

Introduction

The need to maintain safe and secure logistics and supply chain channels is receiving a lot of importance and attention worldwide. Once such legislation aimed at accomplishing this particular task, known as the C-TPAT, is the focal point of this article.

What Is the C-TPAT?

C-TPAT officially stands for the Customs-Trade Partnership Against Terrorism. It is led by the United States Customs and Border Protection (CBP). The primary objective of this legislation is to help improve the level of security of the lines of shipping against any act of terrorism, including those that are cyber-related. It was also created to further fortify the United States border and to ensure the free flow of goods and products.

It is important to note that this program is completely voluntary; no single business entity (which are primarily the importers) are required to join. If they do, however, they can become eligible to receive assistance in not only securing their cargo from the point of origin, but also in ensuring that it reaches the U.S. port of destination safely. This partnership is also geared towards the transportation carriers, freight consolidators, cargo brokers and manufacturers.

The C-TPAT was initially launched in November 2001 and started out with just seven members. Now it has grown over 11,400 certified partners and is still growing. Approximately 54% of this total membership is comprised solely of importers.

The Security and Accountability for Every Port Act of 2006 further provides support for the C-TPAT partnership by implementing extremely strict oversight requirements.

The Business Entities That Can Join C-TPAT

Just about any organization that is involved in the import and export business can enroll in and become official members of the C-TPAT. Examples of this include:

  • Importers and exporters that are based in the United States
  • Freight carriers based (Read more...)

*** This is a Security Bloggers Network syndicated blog from InfoSec Resources authored by Ravi Das (writer/revisions editor). Read the original post at: http://feedproxy.google.com/~r/infosecResources/~3/gXa2keDysbI/