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

Tenable report field name change #11102

Closed
1 of 3 tasks
WojTecH94 opened this issue Oct 21, 2024 · 3 comments
Closed
1 of 3 tasks

Tenable report field name change #11102

WojTecH94 opened this issue Oct 21, 2024 · 3 comments
Labels

Comments

@WojTecH94
Copy link
Contributor

WojTecH94 commented Oct 21, 2024

Few weeks ago Tenable changed one of the fields in its csv reports.
Was: "Solution"
Now it is: "Steps to Remediate"

Bug description
When importing new scans from tenable (csv format) mitigation field in DefectDojo is not filled.

Steps to reproduce
Steps to reproduce the behavior:

  1. Import scan (csv format) from tenable (current version)

Expected behavior
"Steps to Remediate" field is imported into DD's Mitigation

Deployment method (select with an X)

  • Docker Compose
  • Kubernetes
  • GoDojo

Sample scan files
tenable_sample_scan.csv

Additional context (optional)
Not sure what about older version of reports (for example if someone does not update tenable)... with old field name: should we care about them? If not, then fix is simple and I can do it.

@WojTecH94 WojTecH94 added the bug label Oct 21, 2024
manuel-sommer added a commit to manuel-sommer/django-DefectDojo that referenced this issue Oct 21, 2024
@manuel-sommer
Copy link
Contributor

See PR @WojTecH94

@WojTecH94
Copy link
Contributor Author

@manuel-sommer so thats how you do it :D Tested it locally, seems fine, thanks 👍

mtesauro pushed a commit that referenced this issue Oct 26, 2024
* 🐛 fix tenable #11102

* add unittest
@mtesauro
Copy link
Contributor

Closing as PR is merged and will be in the next release. Feel free to reopen if there's an issue post the release.

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

3 participants