Blog post

Do you know which use cases SELFY tackles?

Use case definition is a very important step of Systems Engineering in large scale projects such as SELFY to meet everyone at the same perspective and provide a clear understanding of problems and solutions.

The SELFY toolbox, a set of cybersecurity tools focused on situational awareness, cooperative resilience, and trust and secure data exchange, is to be validated in three different macro scenarios.

These three scenarios also correspond to three different validation environments of SELFY which are real-world Validation, laboratory/HIL (Hardware-In-the-Loop) validation and simulation validation.

Let’s have a look at SELFY’s use cases together.


Use case 1: Resilient cooperative mechanisms for Vulnerable Road User (VRU) safety


Illustration of the VRUs use case

The increasing number of automated vehicles requires improving the safety of Vulnerable Road Users (VRUs), such as pedestrians and cyclists, and, for this end, having smart cooperation between automated vehicles, human controlled vehicles, and VRUs themselves.

Resilient cooperative mechanisms for VRU Safety scenario consist of perception, situational awareness, communication, and decision-making, supported by risk assessment. To succeed with this mission, the elements of the cooperative system must behave correctly and safely, while avoiding imprecisions and malfunctions. Trust must also be guaranteed by providing resilience against any kind of cyber-attack.

In this scenario, that will be deployed in a real-world environment, a Road-Side Unit (RSU) and reliable target vehicle will send out coherent messages including their own perceptions and indicating that there are VRUs in the area.

On the other hand, in this scenario we will have an ego vehicle, equipped with sensors that perceive the environment. When it turns right, the ego vehicle system will indicate free space around the VRUs, which will be faulty as the vehicle will be hacked. The vehicle will be able to know that its own perception is wrong by comparing it with RSU information and a reliable target perception. The ego vehicle then will make a risk assignment to the current situation to decide the safety operational mode.

SELFY tools will support cooperative VRU safety by providing trustworthy communications between CCAM elements and offering resilience and safety reaction.

Use case 2: Secure empowerment of backend system for traffic management system

Illustration of the use case testing the security of the traffic management backend system

The CCAM ecosystem requires secure and robust remote data connections to cloud servers. In the future, every OEM will probably need to establish Vehicle Security Operations Centers (VSOCs) to monitor cybersecurity of their vehicles and to report security incidences, anomalies, and hazards.

Traffic Management Systems or specific OEMs shall have the possibility to set their own parameters to the VSOC that may include trust level, depending on the road and vehicles conditions, allowed maneuvers, reaction, and degraded modes, among others. The VSOC owns a set of tools to audit the system, plus high-level algorithms like Artificial Immune System (AIS) Defense, to recognize threats, deploy responses, as well as regulate the system by providing healing recipes, software updates or mitigation actions instructions.

SELFY toolbox will include solutions with the secure empowerment of backend system scenario to all these challenges.

In this scenario, to be tested in a laboratory environment, the AIS at vehicle side will detect suspicious behavior of an ego vehicle and informs the AIS at RSU side. Chances are that the AIS (RSU) knows about this suspicious behavior or not. If the AIS (RSU) does not know about this suspicious behavior, it will inform the VSOC and the VSOC can ask the Audit Box tool to audit the ego vehicle involved.

Thanks to vehicle audit/pentesting management system, the Audit Box tool being developed under the project framework may detect a wrong/corrupted/attacked/not updated software and request the VSOC to update the software to that ego vehicle. On the other hand, the Secure Over-The-Air (SOTA) tool, which provides the system software updates safely when vulnerabilities in SW, protocols or devices arise. The VSOC informs the AIS (RSU) about this action. If it happens to another vehicle, the AIS (RSU) will already have this info and share it with this new vehicle.

Illustration of the platooning SELFY use case

Platooning, a technology allowing that several automotive vehicles drive together safely and high speed, is one of the most representative cooperative maneuvers providing two main benefits: fuel consumption reduction and a traffic congestion decrease thanks to a more efficient use of the road network.

However, platooning requires a strong communication link among each of the vehicles of the group. This link must be resilient in terms of security and safety. SELFY tools aim to provide a strong and robust link to the platoons to avoid possible risks.

SELFY provides a strong and robust link to the platoon, avoiding possible risks like unstable strings due to bad spacing policy, in terms of actuation saturation; collisions with vulnerable road users or high collisions probabilities that foster a platoon split to ensure safety.

To be tested in a simulation environment, this use case will assume that an intermediate ego vehicle in a platoon suffers a cyber-attack and loses its localization capability. Then, the ego vehicle will collect available operational data from adjacent vehicles to infer kinematic information, and finally, the vehicle enters an appropriate safe operational mode and leaves the platoon.


Author: FEV Turkey