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

{Enhancement} HTML toggles for false positives #193

Closed
muddydev opened this issue Dec 7, 2021 · 3 comments · Fixed by #306
Closed

{Enhancement} HTML toggles for false positives #193

muddydev opened this issue Dec 7, 2021 · 3 comments · Fixed by #306
Assignees
Labels
EMBArk enhancement New feature or request help wanted Extra attention is needed

Comments

@muddydev
Copy link

muddydev commented Dec 7, 2021

This is a tall order but would be nice for the roadmap

In most cases. the discoveries for the CVEs don't actually affect the product. For example, if I'm running a kernel version that has 200 CVE's and 7 exploits. When I look at those findings I notice the CVE's are just a raw version analysis but if you dig down into the CVE it can say stuff like "If IPV6 is enabled" "IF the following flag is enabled in x config". IT would be nice to have the ability to go into the HTML report and maybe toggle stuff off that you know is a false positive.

Kina like this project lets you do https://github.com/Guezone/SECMON.

The toggling could let you generate an XML or something that logs the CVE's that you could apply to your next scan --fpxml

@m-1-k-3
Copy link
Member

m-1-k-3 commented Dec 7, 2021

Thanks for your feedback. We will evaluate Kina. The idea is great.

@m-1-k-3 m-1-k-3 added EMBArk enhancement New feature or request help wanted Extra attention is needed labels Dec 7, 2021
@m-1-k-3
Copy link
Member

m-1-k-3 commented Dec 7, 2021

As EMBA will not address this and the right area for this is EMBArk I will move this issue. See e-m-b-a/embark#21

@m-1-k-3 m-1-k-3 closed this as completed Dec 7, 2021
@m-1-k-3
Copy link
Member

m-1-k-3 commented Sep 13, 2022

Does it makes sense to load a CVE blacklist file from the config directory?

The idea is that you can for example place multiple CVE lists in the config directory and create a scan profile per cve list. This give you the possibility to collect the kernel CVEs into a file and ignore it in the future. Another possibility would be to generate CVE lists for Metasploit exploits and so you can generate a scan profile for Metasploit exploits and so on.

As an initial implementation I will include a blacklist that will get checked for CVEs and the included CVEs are ignored from further processing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EMBArk enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants