Skip to content
GitLab

Quantitative Security Assessment (QSA) · Changes

Page history
Update Quantitative Security Assessment (QSA) authored by Miltos's avatar Miltos
Hide whitespace changes
Inline Side-by-side
Quantitative-Security-Assessment-(QSA).md
View page @ 6e10f69e
......@@ -25,9 +25,9 @@ The above command will download the Docker Image of the latest version of the QS
In the above endpoint, you should replace the <your_local_host_ip> placeholder with the IP of your local machine on which the QSA docker container is running.
The environmental variables DB_IP and DB_PORT should be used in order to define the IP and the PORT of the MongoDB, in which the results of the analysis should be stored. This is necessary if you are willing to use the [Dashboard]() instead of the standalone service, as the Dashboard receives the results of the QSA analysis directly from the MongoDB. Setting up a MongoDB for the purposes of the VM4SEC Platform is an easy process. Instructions on how to set up the dedicated MongoDB can be found [here]().
The environmental variables DB_IP and DB_PORT should be used in order to define the IP and the PORT of the MongoDB, in which the results of the analysis should be stored. This is necessary if you are willing to use the [Dashboard](VM4SEC-Dashboard) instead of the standalone service, as the Dashboard receives the results of the QSA analysis directly from the MongoDB. Setting up a MongoDB for the purposes of the VM4SEC Platform is an easy process. Instructions on how to set up the dedicated MongoDB can be found [here](VM4SEC-Dashboard).
**Attention:** You can use a different port than the 8080 on your local machine, as long as the correct mapping is done in the _docker run_ command. For instance, if you wish the docker container to listen to the 8089 port, you should define "-p 8089:8080" in the aforementioned commands. It should be noted, that in that case, if you are willing to use also the Dashboard, this change should be applied to the Docker File of the dashboard in order to declare where the services reside. For more information please check the [Dashboard Wiki Page]().
**Attention:** You can use a different port than the 8080 on your local machine, as long as the correct mapping is done in the _docker run_ command. For instance, if you wish the docker container to listen to the 8089 port, you should define "-p 8089:8080" in the aforementioned commands. It should be noted, that in that case, if you are willing to use also the Dashboard, this change should be applied to the Docker File of the dashboard in order to declare where the services reside. For more information please check the [Dashboard Wiki Page](VM4SEC-Dashboard).
# Execution of the QSA mechanism (as a Microservice)
......@@ -35,7 +35,7 @@ In this section, we describe how the QSA mechanism can be used as an individual
## Execution of the Docker Container
Having the QSA Container already deployed on your local machine (see the [Installation](Installation-directly-from-DockerHub) section for more information), it can be started, paused, and stopped using common Docker commands. In particular, in order to start the QSA mechanism you need to execute the following command on your terminal:
Having the QSA Container already deployed on your local machine (see the Installation section above for more information), it can be started, paused, and stopped using common Docker commands. In particular, in order to start the QSA mechanism you need to execute the following command on your terminal:
~~~
docker start vm4sec-qsa
......