User Tools

Site Tools


pe-bpmn-editor_pebpmn

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
pe-bpmn-editor_pebpmn [2018/05/15 16:51]
admin
pe-bpmn-editor_pebpmn [2020/03/17 17:44] (current)
pullonen
Line 1: Line 1:
 ====== Privacy-Enhanced BPMN ====== ====== Privacy-Enhanced BPMN ======
  
-Extension ​of the BPMN concrete syntax ​to add Privacy Enhanced Technologies (PETs) ​is done using stereotypes with the general ​[[pe-bpmn-editor_stereotypes|stereotypes]]. The stereotype characterizes the changed type of the BPMN construct. Parameter ​(it has similarity to the tag in UMLis the variable, that gives additional details about the execution ​of the action. Some goals result in a series of tasks, for example data protection allows adding protection with Protect and removing it with Open while others have one task. The parameter ​describes the task, whereas the inputs and outputs should be clearly modelled as data objects or data collections in BPMN.+PE-BPMN is an extension ​of BPMN language ​to add Privacy Enhanced Technologies (PETs) ​information via privacy ​[[pe-bpmn-editor_stereotypes|stereotypes]]. The stereotype characterizes the changed type of the BPMN construct (task, data object or message flow). We have derived ​the stereotypes based on the actions ​of the technologies and made sure that the technologies achieving common privacy goals are as similar as possible to each other. Some privacy protection ​goals result in a series of tasks, for example data protection allows adding protection with Protect and removing it with Open type of tasks. The stereotype parameters further ​describes the task, whereas the inputs and outputs ​of the tasks should be clearly modelled as data objects or data collections in BPMN.
  
-Access specification can, for example, specify the decryption key or the sets of shares that qualify to +There are different possible parameters a stereotype can have.  ​Access specification can, for example, specify the decryption key or the sets of shares that qualify to open the secret. For integrity protection, this specifies what is necessary to check the integrity in Open. Privacy requirements can specify security parameters or other properties of the scheme that should be used. The user interface of Pleak asks for the parameters and specifications based on the chosen stereotype ​and the restrictions are documented on the pages of the stereotypes.
-open the secret. For integrity protection, this specifies what is necessary to check the integrity in Open. +
-Privacy requirements can specify security parameters or other properties of the scheme that should be +
-used. The computation script is the script or query that will be executed. The script fully characterizes +
-the computations ​and dependency between inputs and outputs.+
pe-bpmn-editor_pebpmn.1526392292.txt.gz · Last modified: 2019/10/01 13:53 (external edit)