1GLOBAL SECURITY SYSTEM GLOBAL SECURITY SYSTEM FOR CONTAINERIZED COMMERCEFOR CONTAINERIZED COMMERCEENSE623 System Engineering Design ProjectFall 2006Professor: Dr. Mark AustinSana Shaikh and Jason SmithDecember 5, 20062HistoryHistory The events of September 11th sparked immediate attention to aspects of our society which appeared vulnerable to future attack.  Containerized commerce or intermodalismpresented one of the greatest risks due to the following;– most often unrevealed (type and source), – is transported quickly, – and is completely global In order to mitigate the risks international and national regulations and security tools were/are urgently needed.3Project GoalsProject Goals With increased complexity of today's transportation system and high tech security tools there is a great need to clearly represent both the multiple user domains and multiple states that a container undergoes throughout the process. These domains and states must be considered when developing and implementing regulations and security systems. This project aims at studying the current global security system for containerized commerce from the following three aspects: – developing a high level model which will be used to recognize vulnerabilities and requirements of a secure system. As identifiable vulnerabilities are discovered, further drilling down may be conducted to better analyze the specifics. Standard UML visualrepresentations will be utilized to accurately define system behavior and structure. – from the models developed and governmental regulatory feedback/studies a list of requirements and specifications of a secure system will be created and mapped. – tools such as LTSA will be used to model the system and verify whether the specifications of the system satisfy the properties required of its behavior.4MotivationMotivation 90% of the world’s goods are transported by containerized commerce If a containerized commerce is tracked and its contents are monitored using the correct metrics, the overall security of international transportation will increase, despite the cost of the systemSource: http://ken.mit.edu/images/posters/8.pdf5Requirement CollectionRequirement Collection USCG Headquarters LCDR Michael Dolan Cargo & Facilities Division  Port Of BaltimoreMelvin P. JacksonSenior Security Specialist6Container TypesContainer Types Dry Freight Container - used for goods that are not affected by most weather conditions such as clothing, automobiles, etc. Insulated Containers - used for goods that are weather sensitive such as electronics and foods but do not require refrigeration. Refrigerated Containers - used for goods that must remain at specific temperature and humidity levels such as frozen foods, perishable foods, and medicine. Open Top, Flat Rack, or Platform Containers - used for goods that require very little protection from the elements and may or may not be oversized such as gravel, waste, airplane wing, etc..Source: http://ken.mit.edu/images/posters/8.pdf7Framework and LimitationsFramework and Limitations Framework: The system is a cradle (supplier) to grave (customer) high level representation a global container’s security measures throughout multiple states. It can be used for • empty or loaded containers,• all modes of transportation, and• any iteration of carrier to port interface.  Limitations: The following scenarios have been omitted from the analysis due to available information and time constraints.• Use of container other than “sealable containers”. • Containers without means to seal (ie. open top, flat rack, and platform containers) have not been specifically addressed.• Presence of inter-governmental agreements (ie. NAFTA, EU, etc.) that precede international and national security regulations (ie. ISPS & MTSA)• Variations for changes in security levels• Attacker scenario8BoundaryBoundary Boundary: Since it is only a high level representation it does not include specific use case details. In order to allow modularity, the use cases represent commonalities throughout varying types of carriers and national requirements. The scope is limited only to the security aspects of container security without respect to time or costs. For the purposes of this paper, security is defined as precautions taken to guard against crime, attack, sabotage, or, espionage towards a nation. It does not include protection from theft, asylum seekers, or transportation of illegal materials for personal gain.9Use Case; ActorsUse Case; Actors Supplier Carrier Port Authority Border Protection Official CustomerTractor TrailerPort210High Level Use Case DiagramHigh Level Use Case DiagramSupplierCarrierCreate Packing ListPort AuthorityBorder Protection OfficialVerify integrityof containerStuff ContainerSeal containerRelease ContainerReceive ContainerFreight ForwarderConsolidatorCreates ocean billof ladingTransport ContainerStore ContainerInspect containerCBP«extends»Container screeningSubmit cargodeclaration«uses»«extends»«extends»Release/ReceivePackageCustomer«extends»«extends»11High Level Activity DiagramHigh Level Activity DiagramCreate Bill of LadingVerify Container IntegrityStore ContainerStuff ContainerSeal ContainerStore ContainerRelease ContainerReceive ContainerTransport ContainerRelease ContainerReceive ContainerScreen ContainerStore ContainerInspect ContainerSeal ContainerRelease ContainerSupplierCarrierPortAuthorityBorderProtectionAgencyReceive ContainerYesSubmit Cargo DeclarationCustomerIs Container Crossing Border?Is Carrier Ready For Container?Release ContainerIs ContainerAt FinalDestination?YesNoIs ContainerHigh Risk?ConsolidatorCreate Packing ListRelease Receive PackageCreate Bill of LadingVerify Container IntegrityStore ContainerStuff ContainerSeal ContainerStore ContainerRelease ContainerIs Container Packed By Consolidator?Create Bill Of Lading May Be Conducted By Alternate Actor; Freight Forwarder (Not Depicted In This Diagram)Release Receive PackageRelease ContainerReceive ContainerRelease Container12Tractor TrailerTractor TrailerBasic ScenarioBasic ScenarioTractor Trailer13GoalGoal Ensure security throughout the lifecycle of containerized commerce.14High Level RequirementsHigh Level Requirements•At least one packing list should be created for every container•If a supplier uses a consolidator, there must be a legal agreement between the supplier