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

Improve Findings Tracking and Funneling Feature #2338

Open
4 tasks
shyam0904a opened this issue Oct 14, 2024 · 0 comments
Open
4 tasks

Improve Findings Tracking and Funneling Feature #2338

shyam0904a opened this issue Oct 14, 2024 · 0 comments
Labels
enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned

Comments

@shyam0904a
Copy link

Additional context
Apart from Mute option, another useful feature would be to provide options such as closed(which would rescan to check the vulnerability), in progress, closed with exception ( mute with providing justification ). This helps the platform to get better picture of overall status and timeline.
Another feature is for segregating findings by severity. This would help prioritize findings and maintain SLA's

Is your feature request related to a problem? Please describe.
A issue that i face is that the misconfigurations are populated and the post tracking part is very frustrating to handle, This would be better if tracking feature of findings in portal is created.

Describe the solution you'd like

Describe alternatives you've considered
nil

Components/Services

  • [+] UI/Frontend
  • [+] API/Backend
  • Agent
  • Deployment/YAMLs
  • CI/CD Integration
  • Other (specify)

Additional context
image

@shyam0904a shyam0904a added enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned labels Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned
Projects
None yet
Development

No branches or pull requests

1 participant