MAHE
Back to Tracks
Track_03 in Collaboration withCybersecurity Partner

CYBER
SECURITY.

Defend the connected fleet. Develop novel security mechanisms or detection frameworks addressing vulnerabilities in the Software-Defined Vehicle (SDV) ecosystem.

Round 01 vs Round 02

Round 01: Participants must write a detailed proposal addressing their chosen theme.
Round 02: Shortlisted teams will develop and build working prototypes during the offline hackathon.

Problem Statements

Teams will select one of the following domains to design a problem statement, architecture, and proof-of-concept.

Problem Statement 01

Vehicle Control System Intrusion Detection

Software-defined vehicles rely on electronic control units and software-driven actuators to control steering, braking, torque delivery, and energy management. Malicious manipulation of control signals could compromise vehicle safety or propagate across fleets.

Focus Areas
  • Detection of malicious actuator commands.
  • Intrusion detection in CAN/Ethernet vehicle networks.
  • Edge-AI anomaly detection models.
  • Distinguishing abnormal driving patterns from cyber attacks.
Example Directions
  • - AI models detecting unauthorized torque/brake commands
  • - Behavioral anomaly detection on actuator signals
  • - Lightweight IDS deployed on vehicle control units
Problem Statement 02

Secure Vehicle–Infrastructure Interaction

Vehicles increasingly interact with external infrastructure such as EV charging stations, roadside units, and cloud services. These interactions introduce potential attack vectors including malware injection, identity spoofing, and billing fraud.

Focus Areas
  • Secure authentication between EVs and charging stations.
  • Detection of malicious charging infrastructure.
  • Secure V2X communication mechanisms.
  • Identity protection and transaction security.
Example Directions
  • - Secure Plug-and-Charge authentication frameworks
  • - Detection of compromised charging stations
  • - Cryptographic identity validation for EV infrastructure
Problem Statment 03

Secure Software Lifecycle & OTA Updates

Software-defined vehicles depend on frequent over-the-air updates to deliver new features, patches, and improvements. Ensuring the authenticity and integrity of these updates is critical to prevent large-scale compromise.

Focus Areas
  • Cryptographic verification of OTA updates.
  • Blockchain-based update validation.
  • Secure firmware distribution frameworks.
  • Post-quantum update authentication.
Example Directions
  • - Distributed ledger-based OTA verification
  • - Secure firmware trust chains
  • - Detection of tampered update packages

Cyber Track Submissions Closed

Submissions for the Cybersecurity track are now closed. Thank you to all teams who submitted their work.

Submission window has ended