Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 08:58:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 111

Update Vulnerability-Processing.md (#11049)

Browse source
This commit is contained in:
Jacob Shandling 2023-04-07 13:38:53 -07:00 committed by GitHub
parent fe2f3c3473
commit 6ece25d80d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/Using-Fleet/Vulnerability-Processing.md
View file

@ -15,7 +15,7 @@ Vulnerability processing in Fleet detects vulnerable software installed on your
Vulnerable software can have one or more vulnerabilities (CVEs).
For Fleet Premium users, each CVE includes its CVSS base score (reported by the [National Vulnerability Database](https://nvd.nist.gov/)), probability of exploit (reported by [FIRST](https://www.first.org/epss/)), and whether or not their is a known exploit in the wild (reported by the [Cybersecurity & Infrastructure Security Agency](https://www.cisa.gov/known-exploited-vulnerabilities-catalog)).
For Fleet Premium users, each CVE includes its CVSS base score (reported by the [National Vulnerability Database](https://nvd.nist.gov/)), probability of exploit (reported by [FIRST](https://www.first.org/epss/)), and whether or not there is a known exploit in the wild (reported by the [Cybersecurity & Infrastructure Security Agency](https://www.cisa.gov/known-exploited-vulnerabilities-catalog)).
Fleet's strategy for detecting vulnerabilities (CVEs) varies according to the host's platform and
the software in question. For macOS and Windows hosts, in general,