Misbehavior Authority --> Intermediate CA:
certificate revocations
Definitions
certificate revocations (Information Flow): List of unexpired certificate identifiers that are no longer considered trustworthy by the CCMS.
Misbehavior Authority (Source Physical Object): The 'Misbehavior Authority' is a component of the CCMS that receives reports of malicious or potentially malicious application activities, analyzes them, and determines whether or not to take mitigating actions.
Intermediate CA (Destination Physical Object): An 'intermediate certificate authority' (ICA) is a certificate authority (CA) whose certificate was issued by another CA and whose main responsibility is to issue certificates to another CA; that is, an authorization certificate authority, and enrollment certificate authority or another ICA.
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
- US: Security Credentials - Guaranteed Secure Internet (ITS) (0)
Selected Solution
Solution Description
ITS Application Entity
No Standard Needed |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
|
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 | False |
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 | Not Applicable | High | High | |
Basis |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |