Commercial Vehicle Check Equipment --> Security Credentials Registry:
request driver log address

Definitions

request driver log address (Information Flow): CV Check Equipment requests the web address to access the driver log from the Security Credentials Registry.

Commercial Vehicle Check Equipment (Source Physical Object): 'Commercial Vehicle Check Equipment' supports automated vehicle identification at mainline speeds for credential checking, roadside safety inspections, and weigh-in-motion using two-way data exchange. These capabilities include providing warnings to the commercial vehicle drivers, their fleet managers, and proper authorities of any safety problems that have been identified, accessing and examining historical safety data, and automatically deciding whether to allow the vehicle to pass or require it to stop with operator manual override. Commercial Vehicle Check Equipment also provides supplemental inspection services such as expedited brake inspections, the use of operator hand-held devices, mobile screening sites, on-board safety database access, and the enrollment of vehicles and carriers in the electronic clearance program.

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:

Communication Solutions

  • (None-Data) - Secure Internet (ITS) (43)
Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

(None-Data) - Secure Internet (ITS)

Solution Description

This solution is used within Australia, Canada, the E.U. and the U.S.. It combines standards associated with (None-Data) with those for I-I: Secure Internet (ITS). The (None-Data) standards include an unspecified set of standards at the upper layers. The I-I: Secure Internet (ITS) standards include lower-layer standards that support secure communications between ITS equipment using X.509 or IEEE 1609.2 security certificates.

ITS Application Entity
Mind the gapMind the gapMind the gap

Development needed
Click gap icons for more info.

Mgmt
Facilities
Mind the gap

Development needed
Security
Mind the gapMind the gap
TransNet
Access

Internet Subnet Alternatives
TransNet TransNet

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Access Access

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

ITS Application ITS Application

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Mgmt Mgmt

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Facility Facility

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Security Security

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

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
Local In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides.

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. There are alternative mechanisms for exchanging the driver log, though all have a negative impact on the driver's time, which is why MODERATE and not LOW.


Security Characteristics Value
Authenticable True
Encrypt True