User Tools

Site Tools


leaks-when-analysis

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
leaks-when-analysis [2018/11/20 11:59]
pullonen
leaks-when-analysis [2018/11/20 12:00] (current)
pullonen
Line 1: Line 1:
-====== Leaks-when analyser ======+====== ​SQL Leaks-when analyser ======
  
 Leaks-when analyser has a a user-facing frontend application (part of [[sql-privacy-analyser|SQL-privacy analyser]]) that allows to extend models by attaching SQL scripts to its elements. SQL queries are added to tasks and SQL database schemas are added to data objects. SQL scripts are attached by adding specific labels into the XML code of the model. The editor uses [[https://​github.com/​pleak-tools/​pleak-leaks-when-ast-transformation|pleak-leaks-when-ast-transformation]] component as a communication provider between the editor and [[https://​github.com/​pleak-tools/​pleak-leaks-when-analysis|pleak-leaks-when-analysis]] tool to perform an analyze on the extended model to combine and present the results. Editor, connector component and analysis tool have separate codebases, but they are all required to use the full functionality of the analyser. Leaks-when analyser has a a user-facing frontend application (part of [[sql-privacy-analyser|SQL-privacy analyser]]) that allows to extend models by attaching SQL scripts to its elements. SQL queries are added to tasks and SQL database schemas are added to data objects. SQL scripts are attached by adding specific labels into the XML code of the model. The editor uses [[https://​github.com/​pleak-tools/​pleak-leaks-when-ast-transformation|pleak-leaks-when-ast-transformation]] component as a communication provider between the editor and [[https://​github.com/​pleak-tools/​pleak-leaks-when-analysis|pleak-leaks-when-analysis]] tool to perform an analyze on the extended model to combine and present the results. Editor, connector component and analysis tool have separate codebases, but they are all required to use the full functionality of the analyser.
Line 24: Line 24:
 Clicking on tasks or data objects opens a menu on the right side of the page (in sidebar). You can add SQL scripts (in a form of stored procedures and queries) to tasks. Database information (in a form of database schemas) can be added to data objects. Clicking on tasks or data objects opens a menu on the right side of the page (in sidebar). You can add SQL scripts (in a form of stored procedures and queries) to tasks. Database information (in a form of database schemas) can be added to data objects.
  
-**Running analysis**+**Running ​the analysis** 
 First select the data objects that are of interest. Clicking on LeaksWhen Report button opens analysis results panel (entitled Analysis results) on the right side of the page (in sidebar). There you can see analysis results for each selected task (ordered as they are ordered on the model). Under each task you can expand the view to see all attributes in this table and open attribute specific result-graphs by clicking "View graph" links. First select the data objects that are of interest. Clicking on LeaksWhen Report button opens analysis results panel (entitled Analysis results) on the right side of the page (in sidebar). There you can see analysis results for each selected task (ordered as they are ordered on the model). Under each task you can expand the view to see all attributes in this table and open attribute specific result-graphs by clicking "View graph" links.
  
 **Output interpretation** **Output interpretation**
 +
 SQL leaks-when output is a directed graph where the final node is a Filter. The first input (leaks) to the filter corresponds to the computation of the value that is given as output and the second input (when) corresponds to the conditions under which the computed value appears in the output. The other branches summarize the computations carried out by the workflow. SQL leaks-when output is a directed graph where the final node is a Filter. The first input (leaks) to the filter corresponds to the computation of the value that is given as output and the second input (when) corresponds to the conditions under which the computed value appears in the output. The other branches summarize the computations carried out by the workflow.
  
leaks-when-analysis.txt · Last modified: 2018/11/20 12:00 by pullonen