-
Notifications
You must be signed in to change notification settings - Fork 360
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhance precision of the vulnerability detection POC documentation #7183
Labels
Comments
2 tasks
Rebits
changed the title
Vulnerability Detection POC is too vague
Enhance precision of the vulnerability detection POC documentation
Apr 10, 2024
Closed
Delayed 1 day, in rework after the PR review. |
Dwordcito
added
type/change
Change requested
type/enhancement
Enhancement issue
and removed
type/bug
Bug issue
type/change
Change requested
labels
Apr 18, 2024
Merged
Merged
Delayed ETA due to refactor required after review |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Due to the Vulnerability Detection refactor, the associated proof of concept documentation changed accordingly. However, the current Proof of Concept (POC) provided lacks sufficient clarity and detail regarding the behavior of the module and how to obtain the presented results. Specifically, the section on Visualizing the alerts is incomplete, as it fails to trigger alerts without the installation of a vulnerable package in an already running environment. This behavior is further elaborated upon in issue #21659.
Moreover, there is a notable absence of information pertaining to the inventory, dashboard, or various use cases such as identifying new vulnerabilities, upgrading vulnerable packages, or removing vulnerable packages.
To address these shortcomings, it is proposed to reorganize and introduce new sections to fully elucidate the module's potential. These additions should encompass all necessary instructions to enable users to replicate the POC effectively.
The text was updated successfully, but these errors were encountered: