Update severity classification #20
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Although most contest platforms directly choose their High and Medium level findings without considering impact and likelihood classification, CodeHawks is different than these platforms. That is because in Sherlock; there is no Low findings, and in C4; they are considered Quality Assurance and auditors submit them with their informational findings. Furthermore what I saw from Patrick Collins' live judging, he tries to categorize findings with their Impact and Likelihood levels, hence I decided to write a documentation that will follow Patrick's way of judging. Proper documentation is needed because that way everything becomes clearer for both auditors and judges.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
kosedogus
changed the title
|
Hello @kosedogus the changes you suggested are explained on: https://docs.codehawks.com/hawks-auditors/how-to-evaluate-a-finding-severity We always have window for improvement, so if you think we might add something to the link above, let us know. |
|
Closing because this is explained. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Although most contest platforms directly choose their High and Medium level findings without considering impact and likelihood classification, CodeHawks is different than these platforms. That is because in Sherlock; there is no Low findings, and in C4; they are considered Quality Assurance and auditors submit them with their informational findings. Furthermore what I saw from Patrick Collins' live judging, he tries to categorize findings with their Impact and Likelihood levels, hence I decided to write a documentation that will follow Patrick's way of judging. Proper documentation is needed because that way everything becomes clearer for both auditors and judges.