-- [Use Code Scanning with CodeQL]
Which CodeQL query suite provides queries of lower severity than the default query suite?
The security-extended query suite includes additional CodeQL queries that detect lower severity issues than those in the default security-and-quality suite.
It's often used when projects want broader visibility into code hygiene and potential weak spots beyond critical vulnerabilities.
The other options listed are paths to language packs, not query suites themselves.
-- [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.
Steven Jackson
10 days agoJoseph Cooper
24 days agoSandra Roberts
1 month agoJeffrey Nelson
2 months agoMatthew Anderson
2 months agoOlivia Jones
3 months agoCrystal Hall
3 months agoBarbara Green
4 months agoSharon Green
4 months agoStephanie Howard
5 months agoRichard Jones
4 months agoAmy Lee
4 months agoAngela Reed
4 months agoOlivia Stewart
4 months agoLucia
5 months agoLauran
6 months agoMaryann
6 months agoMicheline
6 months agoThersa
6 months agoLorriane
7 months agoGretchen
7 months agoJesse
7 months agoKrissy
7 months agoDick
8 months agoGianna
8 months agoEllsworth
8 months agoDaniela
8 months agoCaprice
9 months agoQuiana
9 months agoLanie
9 months agoJuan
9 months agoDarrin
10 months agoGregoria
10 months agoKathryn
10 months agoCarmela
10 months agoDella
11 months agoTesha
11 months agoAlva
11 months agoVerona
11 months agoMadalyn
12 months agoMargarett
12 months agoDaren
12 months agoCora
1 year agoJesus
1 year ago