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

Design: Finding details can be much clearer #373

Open
TwistMeister opened this issue Dec 1, 2022 · 1 comment
Open

Design: Finding details can be much clearer #373

TwistMeister opened this issue Dec 1, 2022 · 1 comment
Assignees
Labels
design rocky Issues related to Rocky

Comments

@TwistMeister
Copy link
Contributor

When viewing a findings details a user should also be informed about:

  • Recommended course of action/possible fixes
  • A list with websites where more information about the finding/issue can be found
  • Risk level (severity AND CVSS-rating)
  • The location (could be physically or virtually) of each occurrence
  • Add "reproduction" and "evidence" (formerly/currently "Proof")
  • "Reproduction" is content from the command line. Output/code (use HTML-tag) which has been ran by the KAT run time, including parameters, env image and OOI
  • "Evidence" should link to raw data from the Boefje
@TwistMeister
Copy link
Contributor Author

@dekkers dekkers transferred this issue from minvws/nl-kat-rocky Feb 28, 2023
@dekkers dekkers added the rocky Issues related to Rocky label Feb 28, 2023
@github-project-automation github-project-automation bot moved this to Incoming features / Need assessment in KAT Jun 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design rocky Issues related to Rocky
Projects
Status: Incoming features / Need assessment
Development

No branches or pull requests

6 participants