Skip to content

Commit e0d1027

Browse files
SopuruvalentijnscholtenMaffooch
authored
Updated Documentation on Anchore Enterprise (#12058)
* Updated Anchore Enterprise Documentation to fit parser. Note Anchore Engine is EOL replacement is Anchore Enterprise * Fix missing test link in documentation and bumped up chart version * Update helm/defectdojo/Chart.yaml Co-authored-by: Cody Maffucci <46459665+Maffooch@users.noreply.github.com> * Update anchore_engine.md --------- Co-authored-by: valentijnscholten <valentijnscholten@gmail.com> Co-authored-by: Cody Maffucci <46459665+Maffooch@users.noreply.github.com>
1 parent 9134295 commit e0d1027

1 file changed

Lines changed: 31 additions & 3 deletions

File tree

Lines changed: 31 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,43 @@
11
---
2-
title: "Anchore-Engine"
2+
title: "Anchore Enterprise Vulnerability"
33
toc_hide: true
44
---
55

66
### File Types
77
DefectDojo parser accepts a .json file.
88

9-
Using the [Anchore CLI](https://docs.anchore.com/current/docs/using/cli_usage/images/inspecting_image_content/) is the most reliable way to generate an Anchore report which DefectDojo can parse. When generating a report with the Anchore CLI, please use the following command to ensure complete data: `anchore-cli --json image vuln <image:tag> all`
9+
You can generate vulnerability data using the Anchore Enterprise CLI tool, [Anchorectl](https://docs.anchore.com/current/docs/using/cli_usage/images/inspecting_image_content/), or through the Enterprise UI.
10+
11+
## Generating a Vulnerability Report:
12+
Using Anchorectl: Run the following command to generate a vulnerability report in JSON format
13+
14+
`anchorectl image vulnerabilities ubuntu:latest -o json `
15+
16+
Using the Anchore UI: Navigate to the desired image in the Anchore Enterprise UI, click on the Vulnerabilities tab, and download the report in JSON format.
1017

1118
### Acceptable JSON Format
19+
1220
All properties are strings and are required by the parser. As the parser evolved, two anchore engine parser JSON formats are present till now. Both ([old](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/anchore_engine/many_vulns.json) / [new](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/anchore_engine/new_format_issue_11552.json)) are supported.
1321

22+
~~~
23+
24+
{
25+
26+
"vulnerabilityId": "CVE-2023-24531",
27+
"cves": "CVE-2023-24531",
28+
"severity": "Critical",
29+
"detectedAt": "2025-03-18T08:09:03Z",
30+
"packageType": "Go",
31+
"path": "/usr/local/bin/gosu",
32+
"package": "stdlib-go1.18.2",
33+
"fixAvailable": "1.21.0-0",
34+
"fixObservedAt": "2025-03-18T08:09:03Z",
35+
"link": "https://nvd.nist.gov/vuln/detail/CVE-2023-24531",
36+
"nvdCvssBaseScore": 9.8
37+
38+
}
39+
~~~
40+
41+
1442
### Sample Scan Data
15-
Sample Anchore-Engine scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/anchore_engine).
43+
Sample Anchore-Engine scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/anchore_engine)

0 commit comments

Comments
 (0)