Answer: Apply and enforce a basic security configuration on your organizations that includes code scanning, secret scanning, and secrets push protection, and to enforce code scanning on pull requests, enable the Require code scanning results rule in your ruleset. Status: Confirmed Entry: tool/github-copilot/permissions-and-security/scan-code-vulnerabilities Revision: 3 Digest: sha256:bda77dbb525c2729 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:35:14Z Last changed: 2026-11-18T13:14:54Z (pull request enforcement rule: — → Require code scanning results) Last verified: 2026-11-20T13:18:04Z Next check: 2026-11-21T13:18:04Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of recommended security features | code scanning, secret scanning, and secrets push protection | [1] | 2026-11-20 pull request enforcement rule | Require code scanning results | [1] | 2026-11-20 automatic scanning of Copilot cloud agent code | automatically scanned for vulnerable patterns and secrets such as API keys | [1] | 2026-11-20 Sources: [1] GitHub. "Maintaining codebase standards in a GitHub Copilot rollout - GitHub Docs". https://docs.github.com/en/copilot/tutorials/roll-out-at-scale/govern-at-scale/maintain-codebase-standards Role: primary. Accessed: 2026-11-20T13:18:04Z Quote: "We recommend including code scanning, secret scanning, and secrets push protection." (Supports: recommended security features) Quote: "enable the Require code scanning results rule." (Supports: pull request enforcement rule) Quote: "code created by Copilot cloud agent is automatically scanned for vulnerable patterns and secrets such as API keys" (Supports: automatic scanning of Copilot cloud agent code) Snapshot SHA-256: 711e9f8885cc1bf605277a33d504e9a17807f8efafb7d144148c6840fc23543f (captured 2026-11-20T13:18:02Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-18T13:14:54Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:18:04Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:18:04Z Last attempt: 2026-11-20T13:18:04Z Notes and limitations: Extracted automatically from a single official source (section "3. Scan code for vulnerabilities"). Related: https://latestn.com/tool/github-copilot/permissions-and-security/sdk-authentication How does authentication work in the GitHub Copilot SDK? https://latestn.com/tool/github-copilot/permissions-and-security/sdk-per-session-github-token How do I pass a per-session GitHub token in the GitHub Copilot SDK? https://latestn.com/tool/github-copilot/permissions-and-security/sdk-refresh-tokens How do I refresh server-to-server tokens for the GitHub Copilot SDK? https://latestn.com/tool/github-copilot/permissions-and-security/run-commands-in-sandbox How do I run GitHub Copilot CLI commands in a sandbox? https://latestn.com/tool/github-copilot/permissions-and-security/sandbox-permission-levels What permission levels does GitHub Copilot CLI local sandboxing support for filesystem access? https://latestn.com/tool/github-copilot/permissions-and-security/sandbox-policies How do I configure the sandbox filesystem and network policies for GitHub Copilot? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T13:14:54Z | changed | pull request enforcement rule: — → Require code scanning results | [1] 2026-11-18T13:14:54Z | changed | enforcement rule: Require code scanning results → — | [1] 2026-11-16T13:02:44Z | changed | enforcement rule: — → Require code scanning results | [1] 2026-11-16T13:02:44Z | changed | pull request rule: Require code scanning results → — | [1] 2026-11-13T03:35:14Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/permissions-and-security/scan-code-vulnerabilities/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/github-copilot/permissions-and-security/scan-code-vulnerabilities POST: https://latestn.com/dispute/tool/github-copilot/permissions-and-security/scan-code-vulnerabilities with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/permissions-and-security/scan-code-vulnerabilities?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I scan code for vulnerabilities during a GitHub Copilot rollout? Revision 3, last verified 2026-11-20T13:18:04Z. https://latestn.com/tool/github-copilot/permissions-and-security/scan-code-vulnerabilities (accessed 2026-11-21T09:53:22Z). @misc{LatestN_tool_github_copilot_permissions_and_security_scan_code_vulnerabilities_r3, title = {How do I scan code for vulnerabilities during a GitHub Copilot rollout?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/permissions-and-security/scan-code-vulnerabilities}}, note = {Revision 3; digest sha256:bda77dbb525c2729; last verified 2026-11-20T13:18:04Z; accessed 2026-11-21T09:53:22Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/github-copilot/permissions-and-security/scan-code-vulnerabilities