Game 1 – Malicious User

In this game, the PDMS user tries to interfere with the computation of the number of bike trips in order to get the maximum benefit. Initially, the genuine GPS data of the user are already collected and stored inside the PDMS. If computed by the correct code, they would account for 22/60 bike trips between home and work. In the following versions of the PDMS, two properties are either disabled or enabled:
  • End-to-end access control: When this property is enabled, the Core enforces access control of the stored data.
  • Secure communications (authenticity): When this property is enabled, the Core verifies that the identity of the Data Tasks matches the ones in the Manifest file previously sent by the Employer and approved by the PDMS user.

PDMS version 

  • End-to-end access control: YES
  • Secure communications (authenticity): YES
Before the computation, the user sends a data modification request to the Core. What will happen during the computation ? Enter your guess on the right  ⇒⇒⇒

— waiting for input —

  
Ecological bonus considered:*

PDMS version 

  • End-to-end access control: NO
  • Secure communications (authenticity): YES
Before the computation, the user sends a data modification request to the Core. What will happen during the computation ? Enter your guess on the right  ⇒⇒⇒

— waiting for input —

  
Ecological bonus considered:*

PDMS version 

  • End-to-end access control: YES
  • Secure communications (authenticity): NO
The user tries a different kind of attack. They do not modify the data stored by the PDMS. Instead, they code a program and launch it when the Core requests the launch of the ComputeBikeStats data task. What will happen during the computation ? Enter your guess on the right  ⇒⇒⇒




— waiting for input —

  
Ecological bonus considered:*

Comments are closed.