Fix for vulns not included in host/endpoint views after reopening #9077
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
…pening Fix for vulnerabilities not included in host/endpoint views after reopening: #8450
Contextual Security AnalysisAs DryRun Security performs checks, we’ll summarize them here. You can always dive into the results in the section below for checks.
Chat with your AI-powered Security Buddy by typing Install and configure more repositories at DryRun Security |
Maffooch
approved these changes
Dec 12, 2023
devGregA
approved these changes
Dec 12, 2023
blakeaowens
approved these changes
Dec 12, 2023
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.
Fix for vulnerabilities not included in host/endpoint views after reopening. More info: #8450
After commenting the lines on test environment, vulnerabilities that were reopened are properly shown on endpoint and host view. I was trying to find out how "status_finding__mitigated" filter works but couldn't find it. In my opinion it is not necessary to check it when "mitigated__isnull" filter is also verified.