Border Inspection System --> Freight Equipment:
container seal interrogation
Definitions
container seal interrogation (Information Flow): Customs inspection of the electronic seal on a container to verify the container has not been opened or tampered with; requires proper authentication.
Border Inspection System (Source Physical Object): 'Border Inspection System' represents data systems used at the border for the inspection of people or goods. It supports immigration, customs (trade), agricultural, and FDA inspections as applicable. It includes sensors and surveillance systems to identify and classify drivers and their cargo as they approach a border crossing, the systems used to interface with the back-office administration systems and provide information on status of the crossing or events.
Freight Equipment (Destination Physical Object): 'Freight Equipment' represents a freight container, intermodal chassis, or trailer and provides sensory, processing, storage, and communications functions necessary to support safe, secure and efficient freight operations. It provides equipment safety data and status and can alert the appropriate systems of an incident, breach, or tamper event. It also provides accurate position information to support in-transit visibility of freight equipment.
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
None |
Communication Solutions
- (None-Data) - BTP/GeoNetworking/G5 (42)
- (None-Data) - LTE-V2X WSMP (44)
- (None-Data) - WAVE WSMP (46)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
ETSI 302 890-1 Addressed Elsewhere |
Facilities
Development needed |
Security
|
|
TransNet
|
|||
Access
|
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
Characteristics
Characteristic | Value |
---|---|
Time Context | Recent |
Spatial Context | Adjacent |
Acknowledgement | False |
Cardinality | Broadcast |
Initiator | Source |
Authenticable | True |
Encrypt | False |
Interoperability | Description |
---|---|
National | This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Low | Moderate | Low | |
Basis | The presence of electronic locks will most likely be observable by looking at the cargo doors and the other information is not sensitive in nature. | The container seal status returned after this interrogation will not have a HIGH integrity, as such is interrogation does not require a HIGH integrity. If the integrity of the container seal status is somehow possible to raise to a HIGH, then this could also have a HIGH integrity. | If this interrogation is not received, the system will not broadcast its Container Seal Status. However, there are multiple chances for this data to be transmitted and received. Additionally, if this information is never received the vehicle will be handled in the same way that it was prior to the implementation of this system. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |