The functionality, safety, and performance of ADFs utilizing data from external sources via V2X communication face the risk of being compromised by malicious entities. These entities can potentially inject data that poses risks to the receiving ADFs. Authentication methods are crucial for distinguishing between authorized and trustworthy parties and unauthorized, potentially malicious entities. Additionally, well-known cryptography algorithms safeguard message payload integrity across various layers, preventing tampering. However, simply verifying digital certificates and signatures isn’t foolproof.
Legitimate V2X devices might have their certificates stolen or be compromised, enabling attackers to inject false information or tamper the message with malicious content. Even malfunctioning sensors in a genuine V2X device could transmit false or inaccurate data. These threats, often originating from trusted devices, are termed misbehaviors and can significantly impact traffic safety. Misbehavior detection becomes vital, identifying and mitigating these activities to maintain the reliability, security, and effectiveness of V2X systems in real-world scenarios.
Main Question
Are authentication and misbehaviour detection methods applied to the external communicating parties providing data to ADFs?
Sub-Questions:
- Is the ADF adopting authentication schemes when providing data to other parties?
- Is the ADF implementing message integrity check using any known standardized cryptography algorithms?
- Are methods in place to verify that received data is trustworthy?
- Is misbehaviour detection in place to ensure the trustworthiness of data from a legitimate V2X device?
- Are message consistency check and plausibility check implemented in misbehaviour detection?
- Is misbehaviour reporting implemented and integrated with a common European C-ITS security scheme or a proprietary scheme?