Supplementary Authorization Server --> Registration Authority:
registered EEs
This triple is bi-directional. See also
Registration Authority --> Supplementary Authorization Server: registered EEs
Definitions
registered EEs (Information Flow): List of registered end entities and/or end entities receiving auth tokens for non-security critical interactions with CCMS.
Supplementary Authorization Server (Source Physical Object): The 'supplementary authorization server' is a component of the CCMS that provides authorization tokens to end entities for use in authorizing operations that are not critical for security.
Registration Authority (Destination Physical Object): The 'Registration Authority' (RA) is a component of the CCMS that is the main point of contact for an end entity, and is responsible for provisioning the end entity with authorization and successor enrollment
Included In
This Triple is in the following Service Packages:
- None
This triple is associated with the following Functional Objects:
- None
This Triple is described by the following Functional View Data Flows:
- None
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 |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |