Add CodeQL analysis workflow configuration - #1
Open
xhuff wants to merge 1 commit into
Open
Conversation
Signed-off-by: Xander Huff <xander.huff@emerson.com>
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.
Per NI Secure Development Lifecycle (SDL) guidance, enable Static Analysis Security Testing (SAST) via CodeQL
Analyzing source code and configuration prior to compilation provides a highly scalable method of security code review and helps ensure that secure policies are being followed. SAST is typically integrated into the commit pipeline to identify vulnerabilities each time the software is built or packaged. However, some offerings integrate into the developer environment to spot certain flaws such as the existence of unsafe or other banned functions and replace those with safer alternatives as the developer is actively coding. Development teams may decide the optimal frequency for performing SAST scans based on the product(s) they develop and may deploy multiple tactics—to balance productivity with adequate security coverage.
NOTE: this was an auto-generated change