Hard limiting of number of issue occurrences
pending feedback
T
Teal blue Butterfly
There is a hard limit applied for number of occurrences where after an issue/vulnerability occurred for 1000 times in scan results, harness STO is not scrutinizing the other number of occurrences.
Expected Solution:
The STO should have an ability to report all the occurrences of the vulnerability/issue in scan results.
Log In
Canny AI
Merged in a post:
Hard limiting Applied for Number of issue/vulnerability occurrences-STO
T
Teal blue Butterfly
There is a hard limit applied for number of occurrences where after an issue/vulnerability occurred for 1000 times, its not scrutinizing the other number of issue/vulnerability occurrences.
Expected Solution:
There shouldn't be hard limiting applied for issue/vulnerability occurrences and harness-STO should report all the issue/vulnerability occurrences without any hardlimiting.
Pritesh Chandaliya
pending feedback
Pritesh Chandaliya
under review
We used to support more number of occurrences, but if a issue has more than 1000 occurrences then it does not make developer life easy but tough. So that's why we show top 1000 occurrences by severity, once the developer remediates the top ones, we will then show up the next 1000 in the next scan. Does that help? Teal blue Butterfly