US: UBL - Secure Internet (ITS)
Description:
This solution is used within Canada and the U.S.. It combines standards associated with US: UBL with those for I-I: Secure Internet (ITS). The US: UBL standards include upper-layer standards required to implement shipment related information flows. 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.Relevant Regions:
- Canada
- United States
Comm Profile: I-I: Secure Internet (ITS)
Comm Class: WAN - Wide Area Network
Standards in Profile:
| Level | Standard |
|---|---|
| Access | Internet Subnet Alternatives |
| Mgmt | Bundle: SNMPv3 MIB |
| Security | Secure Session Alternatives |
| TransNet | Internet Transport Alternatives |
| TransNet | IP Alternatives |
Data Profile: US: UBL
Standards in Profile:
| Level | Standard |
|---|---|
| Facilities | OASIS UBL |
| Facilities | W3C XML |
| ITS Application Entity | OASIS UBL |
| Security | OASIS UBL |
Solution Issues Severity: 9
The severity issue score calculation only includes issues associated with standards that are included by default.
Solution Issues:
| Default | Severity | Name | Type | Description |
|---|---|---|---|---|
| False | Medium | Option not standardized | Standardization Gap | The option set includes at least one option that is not (yet) defined in a standard. |
| False | Medium | Uncertainty about trust revocation mechanism | Security Gap | The mechanisms used to prevent bad actors from sending authorized messages is unproven. |
| True | Medium | Outdated security reference | Security Gap | The standard solution includes an outdated security reference. |
| True | Medium | Secure data access not provided | Security Gap | The solution does not define rules on how the application entity authenticates requests to accept or provide data. |
| True | Medium | Unvetted by community | Standardization Gap | The proposed solution uses a suite of standards that is accepted within some communities, but has not necessarily been accepted for use within the context of this information triple. |