Skip to content
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

Closed
Rebits opened this issue Apr 10, 2024 · 2 comments · Fixed by #7215
Closed

Enhance precision of the vulnerability detection POC documentation #7183

Rebits opened this issue Apr 10, 2024 · 2 comments · Fixed by #7215
Assignees
Labels
level/task Task issue type/enhancement Enhancement issue

Comments

@Rebits
Copy link
Member

Rebits commented Apr 10, 2024

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.

image

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.

@Rebits Rebits added level/task Task issue type/bug Bug issue labels Apr 10, 2024
@Rebits Rebits changed the title Vulnerability Detection POC is too vague Enhance precision of the vulnerability detection POC documentation Apr 10, 2024
@wazuhci wazuhci moved this to Backlog in Release 4.8.0 Apr 11, 2024
@GabrielEValenzuela GabrielEValenzuela linked a pull request Apr 15, 2024 that will close this issue
@wazuhci wazuhci moved this from Backlog to Pending review in Release 4.8.0 Apr 15, 2024
@wazuhci wazuhci moved this from Pending review to In review in Release 4.8.0 Apr 16, 2024
@Dwordcito
Copy link
Member

Delayed 1 day, in rework after the PR review.

@Dwordcito Dwordcito added type/change Change requested type/enhancement Enhancement issue and removed type/bug Bug issue type/change Change requested labels Apr 18, 2024
@javimed javimed linked a pull request Apr 18, 2024 that will close this issue
@javimed javimed mentioned this issue Apr 18, 2024
@sebasfalcone
Copy link
Member

sebasfalcone commented Apr 19, 2024

Delayed ETA due to refactor required after review

@wazuhci wazuhci moved this from In review to In progress in Release 4.8.0 Apr 19, 2024
@wazuhci wazuhci moved this from In progress to Done in Release 4.8.0 Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task Task issue type/enhancement Enhancement issue
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

5 participants