-
Notifications
You must be signed in to change notification settings - Fork 160
New Scanner: OpenVas #1642
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
Comments
Hi, |
Hi, we have it on the road map. So maybe we will look into this topic in the next weeks/montsh. |
@STeXE89 We're looking into OpenVAS. Problem is that OpenVAS is a quite complicated beast and it would lead to massive work to integrate it into these cureCodeBox. We're even not sure if it's feasible. Could you please describe your concrete use case in detail? |
I am also really interested in an implementation of OpenVAS into SecureCodeBox. The streamlined deployment and configuration of scans and checks would help us a lot and getting rid of GSAD would also be great since we don't have multiple platforms for handling our scan results. |
Hi @moxli, thanks for your answer. To be honest, we have no experience with OpenVAS. @Zero3141 looked into itand it is a quite complicated setup with roundabout 9 containers necessary for OpenVAS. We're not sure if it's worth or feasible at all to integrate it. Since you're not the first one asking for OpenVAS, we don;t want to simply ignore your request. Could you tell use a bit more in detail what kind of scans you perform with OpenVAS and what types of vulns it finds. The question we want to answer: Does it generate findings we could also find with the current available scanners of the secureCodeBox or does it generate complete different findings we also want to find with the secureCodeBox. In latter case it wouldbe worth the effort to extract the scanner from the OpenVAS setupt and try to integrate it. OTOH would it be a solution to use secureCodeBox and OpenVAS side-by-side and feed the findings into one DefectDojo? |
Hi @Weltraumschaf, Thanks for your interest. I understand that full integration is hard work. Thank you! |
Hi, |
Signed-off-by: Sven Strittmatter <[email protected]>
Signed-off-by: Sven Strittmatter <[email protected]>
Signed-off-by: Sven Strittmatter <[email protected]>
Signed-off-by: Sven Strittmatter <[email protected]>
Signed-off-by: Sven Strittmatter <[email protected]>
Signed-off-by: Sven Strittmatter <[email protected]>
Signed-off-by: Sven Strittmatter <[email protected]>
Signed-off-by: Sven Strittmatter <[email protected]>
Hi @Weltraumschaf and @STeXE89, I've had a look at the OpenVAS scanner. It seems quite difficult to integrate. They use a proprietary protocol to send messages between docker containers. If you want to integrate it, it might be possible to use only the openvas-scanner container, but it requires some reverse engineering of the protocol and I'm not sure of the viability of this. You could opt to run openVAS in the cluster as a fixed instance, and find a way to interface with it using SCB data via cascading rules if at all possible, but that will likely cause scalability issues. If all you need is data from OpenVAS to in your DefectDojo instance, It might be best to create a cron job that pipes the data from OpenVAS to DefectDojo. DefectDojo already has an integration for OpenVAS, but if that does not suffice, it might be good to open an issue at DefectDojo for OpenVAS integration. I don't know why it would be beneficial to add that to SCB. |
Signed-off-by: Sven Strittmatter <[email protected]>
Signed-off-by: Sven Strittmatter <[email protected]>
Signed-off-by: Sven Strittmatter <[email protected]>
Signed-off-by: Sven Strittmatter <[email protected]>
Signed-off-by: Sven Strittmatter <[email protected]>
Signed-off-by: Sven Strittmatter <[email protected]>
Hi @STeXE89, sorry for the long time to wait for an answer. We investigated this topic and like @Stijn-FE already mentioned: It's not that easy. The TL;DR ist: We will not integrate OpenVAS into the secureCodeBox. A more detailed explanation you can find in our architecture decision record No. 19. In our opinion it will be a better aproach to operate secureCodeBox and OpenVAS side-by-side and aggregate the findings in one DefectDojo. If you need to trigger OpenVAS scans from the secureCodeBox (e.g. for found hosts or such), you may do this by writing a custom read hook which triggers OpenVAS by it's API. If you need support about how to write such a hook, feel free to reach us out in our Slack. |
Signed-off-by: Sven Strittmatter <[email protected]>
Signed-off-by: Sven Strittmatter <[email protected]>
HI,
I think it is also very useful for other testers to have the OpenVas tool integrated in the secureCodeBox suite.
I often carry out security tests using openvas, and others on the frontends using ZAP, it would be very useful to have OpenVas integrated and be able to manage everything from a single tool: secureCodeBox.
Thank you
The text was updated successfully, but these errors were encountered: