Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • W Wiki Home
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards
Collapse sidebar
  • VM4SEC Wiki
  • Wiki Home
  • Wiki
  • Quantitative Security Assessment (QSA)

Quantitative Security Assessment (QSA) · Changes

Page history
Update Quantitative Security Assessment (QSA) authored Mar 10, 2022 by Miltos's avatar Miltos
Hide whitespace changes
Inline Side-by-side
Quantitative-Security-Assessment-(QSA).md
View page @ a76f33e9
......@@ -27,7 +27,7 @@ In the above endpoint, you should replace the <your_local_host_ip> placeho
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#mongodb).
**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).
**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 .env 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)
......
Clone repository
  • Project Management API
  • Quantitative Security Assessment (QSA)
  • VM4SEC Dashboard
  • Vulnerability Prediction (VP)
  • Walkthrough
  • Home