Commercial Vehicle Service Provider Center --> Security Credentials Registry:
check driver log activity
Definitions
check driver log activity (Information Flow): The CV Service Provider periodically checks the Security Credentials Registry for driver log data collected by another CV Service Provider. If there is data available, the CV Service Provider will download that data directly from the other CV Service Provider so that a complete driver log can be provided. This is relevant when a driver uses multiple OBEs from different CV Service Providers to enter their driver log.
Commercial Vehicle Service Provider Center (Source Physical Object): The 'Commercial Vehicle Service Provider Center' is an Australia-specific physical object that provides data exchange and commercial vehicle tracking services to other parties involved in commercial vehicle management. It also manages CV OBEs and the operational software on those devices.
Security Credentials Registry (Destination Physical Object): The 'Security Credentials Registry' is an Australia-specific physical object that provides access information (e.g., the network address) of the commercial vehicle driver logs and security credentials that enable secure traceable access to driver logs. The SCR receives frequent updates of driver activity to determine the CVOBE-SP(s) that store the driver logs. In terms of US physical objects, the SCR is a Cooperative ITS Credentials Management System (CCMS) with included Object Registration and Discovery Service (ORDS) functionality and specific driver log monitoring extensions.
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) - Secure Internet (ITS) (32)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
Development needed |
Security
|
|
TransNet
|
|||
Access
Internet Subnet Alternatives |
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 | Regional |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Source |
Authenticable | True |
Encrypt | True |
Interoperability | Description |
---|---|
Regional | Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | High | High | Moderate | |
Basis | Driver log contains PII, at least a code or identifier assoicated with a driver, and also implies a response that contains more detailed PII. This is personal and competitive with regulatory use. It should be available only to the intended recipient. | Driver log data is covered under commercial regulatory schemes in most jurisdictions. Forgery of driver log data would have significant competitive implications, not to mention being a regulatory violation. | This flow is used for near-real time driver logs (work diaries) for commercial vehicle operators. It needs to be timely and correct so that operators are not unnecessarily delayed or penalized. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |