Global Security System for Containerized Commerce - Project | ENSE 623, Study Guides, Projects, Research of Engineering

Download Global Security System for Containerized Commerce - Project | ENSE 623 and more Study Guides, Projects, Research Engineering in PDF only on Docsity! 1 GLOBAL SECURITY SYSTEM FOR CONTAINERIZED COMMERCE ENSE623 System Engineering Design Project Fall 2006 Professor: Dr. Mark Austin Sana Shaikh and Jason Smith December 5, 2006 2 History  The events of September 11th sparked immediate attention to aspects of our society which appeared vulnerable to future attack.  Containerized commerce or intermodalism presented 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. 5 Requirement Collection  USCG Headquarters LCDR Michael Dolan Cargo & Facilities Division  Port Of Baltimore Melvin P. Jackson Senior Security Specialist 6 Container 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.pdf 7 Framework 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 scenario 10 High Level Use Case Diagram Supplier Carrier Create Packing List Port Authority Border Protection Official Verify integrity of container Stuff Container Seal container Release Container Receive Container Freight Forwarder Consolidator Creates ocean bill of lading Transport Container Store Container Inspect container CBP «extends» Container screening Submit cargo declaration «uses» «extends» «extends» Release/Receive Package Customer «extends» «extends» 11 High Level Activity Diagram Create Bill of Lading Verify Container Integrity Store Container Stuff Container Seal Container Store Container Release Container Receive Container Transport Container Release Container Receive Container Screen Container Store Container Inspect Container Seal Container Release Container Supplier Carrier Port Authority Border Protection Agency Receive Container Yes Submit Cargo Declaration Customer Is Container Crossing Border? Is Carrier Ready For Container? Release Container Is Container At Final Destination? Yes No Is Container High Risk? Consolidator Create Packing List Release Receive Package Create Bill of Lading Verify Container Integrity Store Container Stuff Container Seal Container Store Container Release Container Is Container Packed By Consolidator? Create Bill Of Lading May Be Conducted By Alternate Actor; Freight Forwarder (Not Depicted In This Diagram) Release Receive Package Release Container Receive Container Release Container 12 Tractor TrailerTractor Trailer Basic Scenario Tractor Trailer Requirement z 7A 72 Fo ot Use Case O2 | 03 | 04 |05 106 | 07 | 08) 09] 10) 11 12 cr sin ie fF BCL easyPDF Printer Driver 16 Verification using LTSA  LTSA is a verification tool for concurrent systems. It mechanically checks that the specification of a concurrent system satisfies the properties required of its behavior. In addition, LTSA supports specification animation to facilitate interactive exploration of system behavior.  A system in LTSA is modeled as a set of interacting finite state machines. The properties required of the system are also modeled as state machines. LTSA performs compositional reachability analysis to exhaustively search for violations of the desired properties. More formally, each component of a specification is described as a Labelled Transition System (LTS), which contains all the states a component may reach and all the transitions it may perform. Source: http;//www.doc.ic.ac.uk/ltsa 17 MSC Plug-in  The MSC plug-in is an extension to the Labeled Transition System Analyzers (LTSA) which allows models to be described by graphically editing sets of scenarios in the form of message sequence charts. The LTSA can be used to detect the presence of implied scenarios in the system as part of an iterative design process Source: http;//www.doc.ic.ac.uk/ltsa/msc Edit | Output | Draw Sint [ey hMsé Supplierflow | Carricrflow | BPAFlow | Portauthorityflow | Carrieflow1 | Carrierflowz | Supplier Carrier Borderpro... Port Customer releaseContainer, created usini gg BCL easyPDF Gi ECL saayr (GEESE | rier to Customer bMSC Edit | Qutput | Draw hmsc | Supplierflo om | PortAuthorityFlow Carrieflow! | Carrierflow2 ‘Supplier Carrier Borderpra, Port Customer releaseContainer ‘ed usin easyPDF  ion to Carrier bMSC et = 7 rder Protect le Oo Edit | Output | Draw MSE Editor | MSC | Supplierflow | Carirflon(“BPAFiW [Bart thoityfiw | Carrieflowl | Carrierflowe | ‘Supplier Carrier Borderpro... Port Customer releaseContainer inter Driver  Edit | Output | Draws (MC TEdiber| MSC | Supplierflow | Carrierflow | BPAflow | Portéuthorityflow | Carrieflowt< Carrierflow2 | Supplier Carrier Borderpra.. Port Customer relesseContainer, ‘ed usin easyPDF eM Leste ese al eae | File Edit Check Build Window Help Options B | | = ra | Ba| @| | Cu &| Hl | i1)}|[archtecturemodel Edit | output (BFSMl) msc Editor | Carrier Borderprotectian supplier.camier.releaseContaimer [Architecturesodel inter Driver  Supplier Borderprotection Customer Port \|ArchitectureModel carrier supplier.caiecarier borderprotection.2eleaseClontainer camier.customer.releaseContainer supplier cirri zeleaseConta camvier port sborderprotection carrier zeleaseCoendActionport carrier releaseContainer canter port releaseContainer carrier customer releaseContainer carrier port releaseContainer cartler.customner releaseContainer camer borderprotection.zeleaseContainer cr sin ie fF BCL easyPDF Printer Driver Ret Bere tere | File Edit Check Build Window Help Options Bi || tel) |Be{ a] | <- Edit | Output (IBFSMl) msc Editor | =| Il | i0)}| [architecturemodel carrier port releaseContamer Borderprotection Customer endAction W|ArchitectureModel port camer releaseContamer inter Driver  tecture Model - LTS cartier borderprotection releaseContainer IRorderprotectian (Customer Port ><|@|X |S) carrier customer.releaseContacarrier borderprotection.releaseContainer supp lier carrier. releamier port 2eleaport.carrier relcarrier. customer releaseConndAction bordexprotection.canier released ArchitectureModel cartier port releaseCiontainer camer customer releaseContainer sin (@ BCL easyPDF Printer Driver (GEESE | 32 Validation and Verification using LTSA (contd.)  Properties we are checking using LTSA – Deadlock (safety) – Progress (liveness) – Implied Scenarios 35 Implied Scenarios  The plug-in didn’t detect any implied scenarios. 36 Manual LTS Verification  Currently working on verifying the LTS generated using MSC plug-in by creating an LTS manually 37 Advancements & Technology  RFID – Radio Frequency Identification – Active vs. Passive – Smart Seals  NII – Non Intrusive Inspection – X-Ray Scans – Radiation Detectors  Standards – ISPS – International Ship & Port Facility Security Code – MTSA – Maritime Transportation Security Act Source: www.ops.fhwa.dot.gov