You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All findings are currently added to one flat list, both in the web UI, and in the findings variable that can be used in the project design HTML.
For some use cases, pentesters want to group certain findings (e.g., if the pentest included two different applications, etc.). We currently allow manual sorting of findings. Pentesters could add a finding field like section or group and insert headings in the project design correspondingly.
This is, however, cumbersome and more difficult to implement.
We, therefore, want to introduce the possibility to manually add sections between findings. We will probably introduce this as a finding field, that is then also rendered in the web UI correctly. Drag and drop of findings between sections should also be possible (also if default finding ordering is enabled).
We should leave the current findings variable in the project design as a flat list to be backwards-compatible. We might introduce a new variable (like finding_groups) which might be a dictionary with the group name as the key and the list of findings.
This would make grouping findings easier.
The text was updated successfully, but these errors were encountered:
All findings are currently added to one flat list, both in the web UI, and in the
findings
variable that can be used in the project design HTML.For some use cases, pentesters want to group certain findings (e.g., if the pentest included two different applications, etc.). We currently allow manual sorting of findings. Pentesters could add a finding field like
section
orgroup
and insert headings in the project design correspondingly.This is, however, cumbersome and more difficult to implement.
We, therefore, want to introduce the possibility to manually add sections between findings. We will probably introduce this as a finding field, that is then also rendered in the web UI correctly. Drag and drop of findings between sections should also be possible (also if default finding ordering is enabled).
We should leave the current
findings
variable in the project design as a flat list to be backwards-compatible. We might introduce a new variable (likefinding_groups
) which might be a dictionary with the group name as the key and the list of findings.This would make grouping findings easier.
The text was updated successfully, but these errors were encountered: