Ohio Certification System
Status: Future
Description
The 'Certification System' verifies that devices and applications meet standards for participation in the ITS environment. Particular requirements vary depending on the type of certification; applications may be certified for performance and adherence to standards or specifications; devices may be similarly certified, and will also typically be subject to security–related interrogation.
Stakeholders
| Stakeholder | Role | Role Status |
|---|
| DriveOhio | Owns | Planned |
|---|
Physical Objects
Functional Objects
| Functional Object | Description | User Defined |
|---|
| Certification of Applications | 'Certification of Applications' verifies the performance and integrity of software for use in the ITS environment. It interacts with and monitors software in device configurations and verifies that the software is able to operate as specified; it may also certify that the software meets the requirements associated with particular services and should be entitled to application–specific credentials. | False |
|---|
| Certification of Devices | 'Certification of Devices' verifies the performance, integrity and functionality of devices, including necessary firmware, for use in the ITS environment. It monitors software and hardware including radios, processors and tamper–related sensors to verify that the device and its operating software is able to operate as specified; it may also certify that the hardware and firmware meet the requirements associated with particular services and should be entitled to device–specific credentials. | False |
|---|
| ITS Management Support | 'ITS Management Support' provides management of the ITS Object. This includes management of regulatory information and policies, management of application processes, management of communication system configuration and update management, communications interfaces, protocol–specific techniques to ensure interoperability such as service advertisements, communications congestion management and interference management, local device states and communications information, billing management, fault management, service level and performance monitoring. | False |
|---|
| ITS Security Support | 'ITS Security Support' provides communications and system security functions to the ITS Object, including privacy protection functions. It may include firewall, intrusion management, authentication, authorization, profile management, identity management, cryptographic key management. It may include a hardware security module and security management information base. | False |
|---|
Physical Standards
| Document Number | Title | Description |
|---|
| ISO 21217 | Intelligent transport systems –– Communications access for land mobiles (CALM) –– Architecture | ISO 21217 describes the communications reference architecture of nodes called "ITS station units" designed for deployment in ITS communication networks. While it describes a number of ITS station elements, whether or not a particular element is implemented in an ITS station unit depends on the specific communication requirements of the implementation. It also describes the various communication modes for peer–to–peer communications over various networks between ITS communication nodes. These nodes may be ITS station units as described in the document or any other reachable nodes. ISO 21217 specifies the minimum set of normative requirements for a physical instantiation of the ITS station based on the principles of a bounded secured managed domain. |
|---|
| NIST FIPS PUB 140–2 | Security Requirements for Cryptographic Modules | This Federal Information Processing Standard (140–2) specifies the security requirements that will be satisfied by a cryptographic module, providing four increasing, qualitative levels intended to cover a wide range of potential applications and environments. The areas covered, related to the secure design and implementation of a cryptographic module, include specification; ports and interfaces; roles, services, and authentication; finite state model; physical security; operational environment; cryptographic key management; electromagnetic interference/electromagnetic compatibility (EMI/EMC); self–tests; design assurance; and mitigation of other attacks. |
|---|
Interfaces To
(View Context Diagram)