Discharge7443/fleet
1
0
Fork 0
Code Issues Pull Requests Actions 18 Packages Projects Releases Wiki Activity
Files
imgbot
fleet/ee/vulnerability-dashboard
T
History
ImgBotApp b54e502802 [ImgBot] Optimize images 
*Total -- 959.95kb -> 938.88kb (2.2%)

/assets/images/osquery-certificate.svg -- 8.48kb -> 6.30kb (25.77%)
/assets/images/sign-up-pencil.svg -- 2.36kb -> 1.79kb (24.21%)
/assets/images/key.svg -- 1.40kb -> 1.17kb (16.34%)
/assets/images/swoop-arrow.svg -- 1.65kb -> 1.39kb (15.98%)
/website/assets/images/icon-checkmark-circle.svg -- 0.47kb -> 0.43kb (8.06%)
/server/fleet/testdata/icons/org_logo_css.svg -- 3.16kb -> 3.07kb (2.97%)
/website/assets/images/background-report-cta-top.svg -- 2.57kb -> 2.51kb (2.17%)
/website/assets/images/background-report-cta-bottom.svg -- 2.59kb -> 2.54kb (2.15%)
/website/assets/fonts/fontawesome-webfont.svg -- 433.96kb -> 425.36kb (1.98%)
/ee/vulnerability-dashboard/assets/fonts/fontawesome-webfont.svg -- 433.96kb -> 425.36kb (1.98%)
/website/assets/images/call-to-action-banner-background.svg -- 1.79kb -> 1.76kb (1.53%)
/website/assets/images/EpicGames_White_Solid_RGB.svg -- 5.87kb -> 5.81kb (0.95%)
/website/assets/images/EpicGames_Black_Solid_RGB.svg -- 5.69kb -> 5.64kb (0.86%)
/assets/images/fleet-logo.svg -- 1.17kb -> 1.16kb (0.67%)
/orbit/cmd/desktop/fleet-logo.svg -- 1.17kb -> 1.16kb (0.67%)
/website/assets/images/press-kit/fleet-logo-mark.svg -- 1.18kb -> 1.17kb (0.66%)
/website/assets/images/state-of-device-management-hero-background.svg -- 7.38kb -> 7.35kb (0.49%)
/assets/images/fleet-logo-text-black.svg -- 4.82kb -> 4.79kb (0.49%)
/assets/images/fleet-logo-text-white.svg -- 5.01kb -> 4.99kb (0.47%)
/assets/images/schedule.svg -- 23.31kb -> 23.22kb (0.42%)
/website/assets/images/github-mark-24x24.svg -- 1.30kb -> 1.29kb (0.38%)
/assets/images/check.svg -- 0.27kb -> 0.27kb (0.36%)
/website/assets/images/press-kit/fleet-logo-white.svg -- 4.93kb -> 4.92kb (0.32%)
/website/assets/images/press-kit/fleet-logo-dark.svg -- 4.94kb -> 4.93kb (0.24%)
/assets/images/laptop-plus.svg -- 0.50kb -> 0.50kb (0.19%)

Signed-off-by: ImgBotApp <ImgBotHelp@gmail.com>
2026-08-08 02:10:54 +00:00
..
api
…
assets
…
config
…
scripts
…
tasks
…
views
…
.dockerignore
…
.editorconfig
…
.eslintignore
…
.eslintrc
…
.gitignore
…
.htmlhintrc
…
.lesshintrc
…
.npmrc
…
.sailsrc
…
app.js
…
CHANGELOG.md
…
crontab
…
docker-compose.yml
…
Dockerfile
…
entrypoint.sh
…
Gruntfile.js
…
package.json
…
README.md
…

README.md

fleet-vulnerability-dashboard

Report and track progress on fixing and prioritizing thousands of installed CVEs.

screenshot of dashboard: overview

How does it work?

CVEs are detected and annotated using NVD, CVSS, EPSS, CISA KEVs, osquery, and Fleet.

screenshot of dashboard: list

Why a separate repo?

Should we move this to a subdirectory of fleetdm/confidential and have it deploy from there?

  • Philosophy: Why do we use one repo?
  • See also: The "broken windows effect"
  • Decision: No. On 2023-07-14, we decided to keep it here so Stephan, Finn, and all other relevant folks from Fastly can access the code and collaborate.
  • Update: 2023-11-06: The best thing is to move this in the ee/ directory of fleetdm/fleet. That achieves the goal of making it source available, but still paid. Logistics to enable this involve changing hosted deployments to deploy from within a nested subdirectory (something we've done before)

Cosmogony

f.k.a. "scooper"

Original raw notes and context: (private google doc since it contains competitor information: https://docs.google.com/document/d/1ByNWY6n_C-rvL75lI6jca2OniHt5FqA5_nYMf61S0pM/edit#)

Running the vulnerability dashboard with Docker.

To run a local vulnerability dashboard with docker, you can follow these instructions.

  1. Clone this repo

  2. Update the following ENV variables ee/vulnerability-dashboard/docker-compose.yml file:

  3. sails_custom__fleetBaseUrl: The full URL of your Fleet instance. (e.g., https://fleet.example.com)

  4. sails_custom__fleetApiToken: An API token for an API-only user on your Fleet instance.

  5. Open the ee/vulnerability-dashboard/ folder in your terminal

  6. Run docker-compose up --build to build the vulnerability dashboard's Docker image.

The first time the vulnerability dashboard starts it will Initalize the database and run the update-reports script before the server starts.

  1. Once the container is done building, the vulnerability dashboard will be available at http://localhost:1337

You can login with the default admin login:

  • Email address: admin@example.com

  • Password: abc123

How it's made

This is a Sails v1 application:

Reference in New Issue View Git Blame Copy Permalink