Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-04-21 21:47:20 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 117
fleet/ee/vulnerability-dashboard
History
Eric ef2ce8bd7f
Vulnerability dashboard: Update result name in MySQL query. (#35368) 
Changes:
- Updated the query to find critically vulnerable rare software for
MySQL databases to return affected host names as `hostNames`
2025-11-07 14:38:17 -06:00
..
api Vulnerability dashboard: Update result name in MySQL query. (#35368) 2025-11-07 14:38:17 -06:00
assets Vulnerability dashboard: Add new homepage (#35253) 2025-11-07 12:01:57 -06:00
config Vulnerability dashboard: Add new homepage (#35253) 2025-11-07 12:01:57 -06:00
scripts Vuln dashboard: Update query to find Vulnerability records with no associated VulnerabilityInstall records. (#20203) 2024-07-03 13:41:35 -05:00
tasks Add fleet-vulnerability-dashboard repo to ee/ folder (#17428) 2024-03-13 13:06:11 -05:00
views Vulnerability dashboard: Add new homepage (#35253) 2025-11-07 12:01:57 -06:00
.dockerignore Vulnerability dashboard: Add a way to start a local vulnerability dashboard with Docker (#17676) 2024-03-21 16:31:20 -05:00
.editorconfig Add fleet-vulnerability-dashboard repo to ee/ folder (#17428) 2024-03-13 13:06:11 -05:00
.eslintignore Add fleet-vulnerability-dashboard repo to ee/ folder (#17428) 2024-03-13 13:06:11 -05:00
.eslintrc Add fleet-vulnerability-dashboard repo to ee/ folder (#17428) 2024-03-13 13:06:11 -05:00
.gitignore Add fleet-vulnerability-dashboard repo to ee/ folder (#17428) 2024-03-13 13:06:11 -05:00
.htmlhintrc Add fleet-vulnerability-dashboard repo to ee/ folder (#17428) 2024-03-13 13:06:11 -05:00
.lesshintrc Add fleet-vulnerability-dashboard repo to ee/ folder (#17428) 2024-03-13 13:06:11 -05:00
.npmrc Add fleet-vulnerability-dashboard repo to ee/ folder (#17428) 2024-03-13 13:06:11 -05:00
.sailsrc Add fleet-vulnerability-dashboard repo to ee/ folder (#17428) 2024-03-13 13:06:11 -05:00
app.js Add fleet-vulnerability-dashboard repo to ee/ folder (#17428) 2024-03-13 13:06:11 -05:00
CHANGELOG.md Add fleet-vulnerability-dashboard repo to ee/ folder (#17428) 2024-03-13 13:06:11 -05:00
crontab Vulnerability dashboard: Add a way to start a local vulnerability dashboard with Docker (#17676) 2024-03-21 16:31:20 -05:00
docker-compose.yml Vuln-dash: Update sails app configuration in docker-compose.yml (#19686) 2024-06-12 10:15:52 -05:00
Dockerfile [StepSecurity] Apply security best practices (#17811) 2024-03-22 16:19:11 -05:00
entrypoint.sh Vulnerability dashboard: Add a way to start a local vulnerability dashboard with Docker (#17676) 2024-03-21 16:31:20 -05:00
Gruntfile.js Add fleet-vulnerability-dashboard repo to ee/ folder (#17428) 2024-03-13 13:06:11 -05:00
package.json Bump grunt from 1.0.4 to 1.5.3 in /ee/vulnerability-dashboard (#17600) 2024-03-21 13:41:49 -05:00
README.md Update vulnerability dashboard to deploy from a parentless commit (#31887) 2025-08-14 09:58:25 -05:00

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: