Security Scanning#616
Draft
turtle0x1 wants to merge 1 commit into
Draft
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Using OVAL sources we scan software snapshots of running instances for known vulns.
Todo later (I dont use them)
I've deployed a Ubuntu/Debian instance (with apache+nginx) and waiting for them to get vuln before merging (even though there is a test to ensure it works how I want, I do want to see a real instance go vulnerable before merging - just have to wait a while, apache/nginx/kernel always finds itself in trouble).
A lot of of security frameworks demand "you show mitigations are applied within X days" - while ensuring your system has "auto sec updates on" usually suffices (most do by default), actually having an interface to review this always nice.
Close #584