Title: Retrieve DefectDojo finding ID from SecureCodeBox finding ID · Issue #536 · secureCodeBox/secureCodeBox · GitHub
Open Graph Title: Retrieve DefectDojo finding ID from SecureCodeBox finding ID · Issue #536 · secureCodeBox/secureCodeBox
X Title: Retrieve DefectDojo finding ID from SecureCodeBox finding ID · Issue #536 · secureCodeBox/secureCodeBox
Description: ➹ New Feature implementation request Is your feature request related to a problem? As a secureCodeBox user with DefectDojo integration I would like to know what DefectDojo finding was created for each secureCodeBox finding (and vice-vers...
Open Graph Description: ➹ New Feature implementation request Is your feature request related to a problem? As a secureCodeBox user with DefectDojo integration I would like to know what DefectDojo finding was created for e...
X Description: ➹ New Feature implementation request Is your feature request related to a problem? As a secureCodeBox user with DefectDojo integration I would like to know what DefectDojo finding was created for e...
Opengraph URL: https://github.com/secureCodeBox/secureCodeBox/issues/536
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Retrieve DefectDojo finding ID from SecureCodeBox finding ID","articleBody":"## ➹ New Feature implementation request\r\n\r\n### Is your feature request related to a problem?\r\nAs a secureCodeBox user with DefectDojo integration I would like to know what DefectDojo finding was created for each secureCodeBox finding (and vice-versa).\r\n\r\nThis would be useful in a case where you create a custom hook which sends notifications for very specific finding cases with a link to the DefectDojo finding. DefectDojo's notification support is very limited. \r\n\r\n### Possible solutions\r\nThese are some possible solutions that I came up with. I'm very happy to hear any other solutions!\r\n\r\n1. It would make sense if the `unique_id_from_tool` field in the Finding model refers to SecureCodeBox's finding ID. Currently, however, the finding filters don't include this field yet (i.e. no way to get finding from the `unique_id_from_tool` field). This field is already updated with DefectDojo's generic importer, but some other existing importers write their own unique id into it. We would need to patch the created findings after creation.\r\n2. The DefectDojo persistence provider updates the Minio finding so that it includes the DefectDojo finding ID.\r\n3. The DefectDojo persistence provider is a ReadAndWriteHook which writes a map of `SecureCodeBox ID` -\u003e `DefectDojo ID` back to the scan spec.\r\n","author":{"url":"https://github.com/EndPositive","@type":"Person","name":"EndPositive"},"datePublished":"2021-07-02T11:52:00.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/536/secureCodeBox/issues/536"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:b52a02bc-e8d9-c94c-dfa3-ab865b42d7b9 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 9AF8:2E9694:298FB09:39A74C7:6977ADD3 |
| html-safe-nonce | 0780d79d68f6edd5e31813a5db3d3cf7d65002f99dded00de607b27eea95e8ca |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5QUY4OjJFOTY5NDoyOThGQjA5OjM5QTc0Qzc6Njk3N0FERDMiLCJ2aXNpdG9yX2lkIjoiNTAyNTYxMTYwNzg1ODE5NTkyMyIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 200dccc6ca1ed31fe547b8baa3e76aadf579fd806695ef38aff8d9a198fbad7a |
| hovercard-subject-tag | issue:935697866 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/secureCodeBox/secureCodeBox/536/issue_layout |
| twitter:image | https://opengraph.githubassets.com/b2aa26578182ea17b76c6072e55914ad10f23605df6241cf2ce2ceaeaabea5e3/secureCodeBox/secureCodeBox/issues/536 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/b2aa26578182ea17b76c6072e55914ad10f23605df6241cf2ce2ceaeaabea5e3/secureCodeBox/secureCodeBox/issues/536 |
| og:image:alt | ➹ New Feature implementation request Is your feature request related to a problem? As a secureCodeBox user with DefectDojo integration I would like to know what DefectDojo finding was created for e... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | EndPositive |
| hostname | github.com |
| expected-hostname | github.com |
| None | cd86879038a75d35d75e56f263b8ad57328b023c6a7de3aa5f9ca0dfd46935bb |
| turbo-cache-control | no-preview |
| go-import | github.com/secureCodeBox/secureCodeBox git https://github.com/secureCodeBox/secureCodeBox.git |
| octolytics-dimension-user_id | 34573705 |
| octolytics-dimension-user_login | secureCodeBox |
| octolytics-dimension-repository_id | 80711933 |
| octolytics-dimension-repository_nwo | secureCodeBox/secureCodeBox |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 80711933 |
| octolytics-dimension-repository_network_root_nwo | secureCodeBox/secureCodeBox |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 8458c691435c924883b72423ecd12134159e1b18 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width