-- [Use Code Scanning with CodeQL]
When using CodeQL, what extension stores query suite definitions?
Query suite definitions in CodeQL are stored using the .qls file extension. A query suite defines a collection of queries to be run during an analysis and allows for grouping them based on categories like language, security relevance, or custom filters.
In contrast:
.ql files are individual queries.
.qll files are libraries used by .ql queries.
.yml is used for workflows, not query suites.
-- [Use Code Scanning with CodeQL]
Which of the following steps should you follow to integrate CodeQL into a third-party continuous integration system? (Each answer presents part of the solution. Choose three.)
When integrating CodeQL outside of GitHub Actions (e.g., in Jenkins, CircleCI):
Install the CLI: Needed to run CodeQL commands.
Analyze code: Perform the CodeQL analysis on your project with the CLI.
Upload scan results: Export the results in SARIF format and use GitHub's API to upload them to your repo's security tab.
You don't need to write custom queries unless extending functionality. ''Processing alerts'' happens after GitHub receives the results.
-- [Configure and Use Code Scanning]
After investigating a code scanning alert related to injection, you determine that the input is properly sanitized using custom logic. What should be your next step?
When you identify that a code scanning alert is a false positive---such as when your code uses a custom sanitization method not recognized by the analysis---you should dismiss the alert with the reason 'false positive.' This action helps improve the accuracy of future analyses and maintains the relevance of your security alerts.
As per GitHub's documentation:
'If you dismiss a CodeQL alert as a false positive result, for example because the code uses a sanitization library that isn't supported, consider contributing to the CodeQL repository and improving the analysis.'
By dismissing the alert appropriately, you ensure that your codebase's security alerts remain actionable and relevant.
-- [Configure GitHub Advanced Security Tools in GitHub Enterprise]
What step is required to run a SARIF-compatible (Static Analysis Results Interchange Format) tool on GitHub Actions?
When using a SARIF-compatible tool within GitHub Actions, it's necessary to explicitly add a step in your workflow to upload the analysis results. This is typically done using the upload-sarif action, which takes the SARIF file generated by your tool and uploads it to GitHub for processing and display in the Security tab. Without this step, the results won't be available in GitHub's code scanning interface.
-- [Configure and Use Dependency Management]
You have enabled security updates for a repository. When does GitHub mark a Dependabot alert as resolved for that repository?
A Dependabot alert is marked as resolved only after the related pull request is merged into the repository. This indicates that the vulnerable dependency has been officially replaced with a secure version in the active codebase.
Simply generating a PR or passing checks does not change the alert status; merging is the key step.
Jeffrey Nelson
8 days agoMatthew Anderson
25 days agoOlivia Jones
1 month agoCrystal Hall
2 months agoBarbara Green
2 months agoSharon Green
3 months agoStephanie Howard
3 months agoRichard Jones
3 months agoAmy Lee
3 months agoAngela Reed
3 months agoOlivia Stewart
2 months agoLucia
4 months agoLauran
4 months agoMaryann
4 months agoMicheline
5 months agoThersa
5 months agoLorriane
5 months agoGretchen
5 months agoJesse
6 months agoKrissy
6 months agoDick
6 months agoGianna
6 months agoEllsworth
7 months agoDaniela
7 months agoCaprice
7 months agoQuiana
7 months agoLanie
8 months agoJuan
8 months agoDarrin
8 months agoGregoria
8 months agoKathryn
9 months agoCarmela
9 months agoDella
9 months agoTesha
9 months agoAlva
10 months agoVerona
10 months agoMadalyn
10 months agoMargarett
10 months agoDaren
10 months agoCora
11 months agoJesus
11 months ago