Skip to content
This repository was archived by the owner on Oct 14, 2020. It is now read-only.

Commit a8f6eeb

Browse files
authored
Merge pull request #74 from secureCodeBox/feature/improve-readme-files
Bugfixing some typos
2 parents 00f2c05 + ec04180 commit a8f6eeb

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

hooks/persistence-defectdojo/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,16 +4,16 @@ path: "hooks/persistence-defectdojo"
44
category: "hook"
55
type: "persistenceProvider"
66
state: "roadmap"
7-
usecase: "Publishes all Scan Findings to elasticsearch (ECK)."
7+
usecase: "Publishes all Scan Findings to DefectDojo."
88
---
99

1010
<!-- end -->
1111

1212
## About
1313

14-
DefectDojo is an OpenSource Tools for importing and managing findings of security scanner. The DefectDojo persistence provider can be used to create new Engagements for SecurityTests run via the secureCodeBox and import all findings which were identified.
14+
DefectDojo is an open-source tool for importing and managing findings of security scanners. The DefectDojo persistence provider can be used to create new Engagements for SecurityTests run via the secureCodeBox and import all findings which were identified automatically to DefectDojo.
1515

16-
Tools which are supported by the secureCodeBox and DefectDojo (OWASP ZAP, Arachni & Nmap) this is done by importing the raw scan report into DefectDojo. Findings by other secureCodeBox supported scanners are currently not directly supported by DefectDojo. These findings are imported via a generic finding api of defectDojo, which might cause some loss of information about the findings.
16+
Tools which are supported both by the secureCodeBox and DefectDojo (OWASP ZAP & Nmap) this is done by importing the raw scan report into DefectDojo. Findings by other secureCodeBox supported scanners are currently not directly supported by DefectDojo. These findings are imported via a generic finding API of DefectDojo, which might cause some loss of information on the findings.
1717

1818
To learn more about DefectDojo visit [DefectDojo GitHub] or [DefectDojo Website].
1919

0 commit comments

Comments
 (0)