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

Optimize frontend #298

Open
2 of 9 tasks
pablosnt opened this issue Mar 29, 2024 · 0 comments · May be fixed by #308
Open
2 of 9 tasks

Optimize frontend #298

pablosnt opened this issue Mar 29, 2024 · 0 comments · May be fixed by #308
Assignees
Labels
breaking Breaking changes
Milestone

Comments

@pablosnt
Copy link
Owner

pablosnt commented Mar 29, 2024

  • Upgrade dependencies to the latest version
  • Move project to Nuxt.js
  • Improve code organization and remove code duplication
  • Adapt frontend to the latest backend changes
  • Fix schedule and repeat forms in Task modal when Rekono is running in Docker. Change feature name to monitoring

Discover assets > Assess the assets for vulns > Prioritize the discovered vulns and present them in a way that's easy to digest

  • Improve dashboards

    • Focus on assets (hosts, ports and technologies) by vulnerabilities (sorted by priority)
    • Findings by time, to see if the assets have fixed some of them
    • Findings by triaging status
    • Fixed findings by time
  • Improve Findings page

    • Focus on assets (hosts, ports and technologies) by vulnerabilities (sorted by severity)
    • Show findings without requiring target filtering

      The problem is that I have 40-100 targets in project and after scanning I get 150 finding. In current implementation I need to manually change target then change finding type (path, host vulnerability) and I need to spend a lot of type for manually check all target and all findings instead of get full information about all targets in project.

  • Improve Task page

    • Display executions as a graph grouping them by those that could be executed in parallel
    • If one execution is clicked the plain output and detected findings should be displayed somewhere
    • Skipped message should be displayed directly in the execution box within the graph
  • Change background image

@pablosnt pablosnt added the breaking Breaking changes label Mar 29, 2024
@pablosnt pablosnt added this to the 2.0.0 milestone Mar 29, 2024
@pablosnt pablosnt self-assigned this Apr 2, 2024
@pablosnt pablosnt linked a pull request Apr 13, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Breaking changes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant