Skip to content
GitLab

dependability toolbox description · Changes

Page history
Update dependability toolbox description authored by Ilias's avatar Ilias
Show whitespace changes
Inline Side-by-side
dependability-toolbox-description.md
View page @ c4185d50
...@@ -14,6 +14,10 @@ The overall structure of the Dependability Toolbox is depicted in the figure bel ...@@ -14,6 +14,10 @@ The overall structure of the Dependability Toolbox is depicted in the figure bel
As can be seen by this figure, the Dependability Toolbox back-end is actually a Microservice, which consists of the three aforementioned web services, i.e., Quantitative Security Assessment, Vulnerability Prediction, and Optimum Checkpoint Interval Recommendation. This microservice has been implemented as an individual Docker Image, which is deployed as an individual Docker Container. An independent MongDB database has been implemented, for storing the results of the three web services that the Dependability Toolbox provides. Although the database has been developed as a standalone Docker Container, access is only feasible through dedicated APIs that are provided by the Dependability Toolbox back-end. Finally, as can be seen by the figure above, the SDK4ED Dashboard communicates with the Dependability Toolbox back-end for invoking its services and visualizing their results in an intuitive and easy-to-understand manner. As can be seen by this figure, the Dependability Toolbox back-end is actually a Microservice, which consists of the three aforementioned web services, i.e., Quantitative Security Assessment, Vulnerability Prediction, and Optimum Checkpoint Interval Recommendation. This microservice has been implemented as an individual Docker Image, which is deployed as an individual Docker Container. An independent MongDB database has been implemented, for storing the results of the three web services that the Dependability Toolbox provides. Although the database has been developed as a standalone Docker Container, access is only feasible through dedicated APIs that are provided by the Dependability Toolbox back-end. Finally, as can be seen by the figure above, the SDK4ED Dashboard communicates with the Dependability Toolbox back-end for invoking its services and visualizing their results in an intuitive and easy-to-understand manner.
### Exploitable Vulnerability Identification
Part of Dependability Toolbox is the Exploitable Vulnerability Identification Tool (EVIT), as well.
EVIT is an optional feature that has been added in SDK4ED platform in order to assess the criticality of static analysis alerts [link](https://gitlab.seis.iti.gr/sdk4ed/evit/wikis/Exploitable-Vulnerability-Identification).
## External References ## External References
For more information about the Dependability Toolbox we highly recommend the reader to have a look at the following resources: For more information about the Dependability Toolbox we highly recommend the reader to have a look at the following resources:
......