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

Add an other Aqua scan format #11957

Open
kzzz1 opened this issue Mar 5, 2025 · 6 comments
Open

Add an other Aqua scan format #11957

kzzz1 opened this issue Mar 5, 2025 · 6 comments
Labels

Comments

@kzzz1
Copy link

kzzz1 commented Mar 5, 2025

When I run GET api/v2/risks/vulnerabilities in Aqua Security, I get a scan report listing vulnerabilities in my image, but the report generated is not supported for parsing in DefectDojo. Is it possible to add that new format report?

Sample file

api.json

@kzzz1 kzzz1 added the bug label Mar 5, 2025
@valentijnscholten
Copy link
Member

Can you point us to the documentation of this format? Is there an official name for this type of report? Are you able to contribute a PR?

@kzzz1
Copy link
Author

kzzz1 commented Mar 10, 2025

Here is the doc of the api/v2/risks/vulnerabilities endpoint:

api/v2/risks/vulnerabilities

The command list all vulnerabilities found in images

Image

@kzzz1
Copy link
Author

kzzz1 commented Mar 10, 2025

I could try a PR

@valentijnscholten
Copy link
Member

Thanks. I cannot access that documentation as I don't have an aquasec account. PRs are welcome. Just want to make sure this is a common use case to generated these reports/exports and not just an API endpoint that is being called and not used by many users.
I noticed the exsiting aqua parser in Defect Dojo has no documentation at all. It looks like it is for Aquasec DevOps reports?

@kzzz1
Copy link
Author

kzzz1 commented Mar 12, 2025

From what I know, the actual aqua formats covered by the parser are CICD reports and also scan results from a call to
GET /api/v1/scanner/registry/Docker%20Hub/image/mongo:latest/scan_result (like many_v2.json .... I know the file name is confusing)

That report generated over the api/v1 doesnt include de cvssv3 score, resulting in discording aqua severity when I import the scan in Defect Dojo vs what I see in the Aqua UI... I contacted Aqua Support and they told me to use the api/v2/risks/vulnerabilities endpoint instead. Saying that the other one was probably getting obsolete.

@valentijnscholten
Copy link
Member

OK, might be a good idea with the PR to update also the docs for the existing parser.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants