{"meta":{"title":"Proteger o repositório","intro":"O Bate-papo do Copilot pode ajudar você a proteger seu repositório e seu código.","product":"GitHub Copilot","breadcrumbs":[{"href":"/pt/copilot","title":"GitHub Copilot"},{"href":"/pt/copilot/tutorials","title":"Tutoriais"},{"href":"/pt/copilot/tutorials/copilot-chat-cookbook","title":"Livro de Receitas do GitHub Copilot Chat"},{"href":"/pt/copilot/tutorials/copilot-chat-cookbook/analyze-security","title":"Analisar a segurança"},{"href":"/pt/copilot/tutorials/copilot-chat-cookbook/analyze-security/secure-your-repository","title":"Proteger seu repositório"}],"documentType":"article"},"body":"# Proteger o repositório\n\nO Bate-papo do Copilot pode ajudar você a proteger seu repositório e seu código.\n\n## Configurar recursos de segurança essenciais\n\n### Cenário de exemplo\n\nDigamos que você criou recentemente um repositório para um novo aplicativo Web, deseja protegê-lo e não sabe por onde começar.\n\nO Bate-papo do Copilot pode orientar você na configuração dos recursos de segurança mais essenciais para garantir que o repositório permaneça seguro.\n\n### Solicitação de exemplo\n\n```copilot copy prompt\nProvide step-by-step instructions on how to enable the following essential security features in my GitHub repository:\n\n* Secret scanning\n* Push protection\n* Dependabot alerts\n* Dependabot security updates\n* Branch protection rules, including enforced code reviews before merging\n\nExplain why each feature is important and how it helps secure my repository.\n```\n\n### Exemplo de resposta\n\nO Bate-papo do Copilot fornece informações sobre cada recurso de segurança e explica como habilitá-lo.\n\n```markdown\nWhy it's important:\n\nSecret scanning automatically detects accidentally committed secrets (API keys, credentials, etc.) in your repository.\n\nHow it helps:\n\nLeaked secrets can allow attackers to access systems, steal data, or cause other harm. Early detection prevents misuse.\n\nHow to Enable:\n\n1. Go to your repository on GitHub.\n1. Click on Settings.\n1. In the left sidebar, click Code security.\n1. Scroll to Secret scanning.\n1. Ensure \"Secret scanning\" and \"Push protection\" are both enabled.\n1. If not, click Enable.\n```\n\n## Incentivar contribuições seguras e práticas recomendadas com uma política de segurança\n\n### Cenário de exemplo\n\nDigamos que você queira compartilhar sua project publicamente e deseja definir uma política de segurança clara para orientar os usuários sobre como relatar com segurança as vulnerabilidades encontradas em seu repositório.\n\nO Bate-papo do Copilot pode escrever uma política de segurança para seu repositório.\n\n### Solicitação de exemplo\n\n```copilot copy prompt\nWrite a GitHub security policy (SECURITY.md) for my repository. The policy should include:\n\n* A clear description of how users can report security vulnerabilities.\n* A response timeline for security issues.\n* Guidelines for responsible disclosure.\n* Supported versions of the software.\n\nFormat it as a well-structured Markdown document.\n```\n\n### Saída de exemplo\n\nO Bate-papo do Copilot produz um arquivo `SECURITY.md` que você pode confirmar em seu repositório.\n\n```markdown\n# Security Policy\n\nThank you for helping to keep this project and its users secure! This document outlines the security policy and responsible disclosure guidelines for this repository.\n\n## Reporting a Vulnerability\n\nIf you discover a security vulnerability, please report it by emailing **security@yourdomain.com** or by using the GitHub [security advisories](https://github.com/octocat/octocat-repo/security/advisories) feature.\n**Do not** report security vulnerabilities via public GitHub issues or pull requests.\n\nWhen reporting a vulnerability, please include as much information as possible to help us understand and reproduce the issue:\n- A clear description of the vulnerability.\n- Steps to reproduce the issue.\n- Any relevant logs, screenshots, or proof-of-concept code.\n- Your assessment of the potential impact.\n\n## Response Timeline\n\nWe take security issues seriously and will respond according to the following guidelines:\n- **Acknowledgment:** We will acknowledge receipt of your report within **3 business days**.\n- **Investigation:** We will investigate and assess the report as quickly as possible, usually within **7 business days**.\n- **Resolution:** Once a fix is identified, we will work to release a security update promptly. We will coordinate with you as needed, especially if you are the reporter.\n- **Disclosure:** We will notify the community of the vulnerability and fix via a GitHub security advisory, and credit the reporter as appropriate.\n\n## Responsible Disclosure Guidelines\n\nTo protect users of this project, we ask that you:\n- Avoid public disclosure of the vulnerability until it has been investigated and patched.\n- Allow us a reasonable amount of time to resolve the issue before any public disclosure.\n- Provide relevant details privately (see \"Reporting a Vulnerability\" above).\n- Act in good faith and avoid exploiting the vulnerability beyond what is necessary for your report.\n\nWe are committed to working with security researchers and the community to ensure a safe and secure software ecosystem.\n```\n\n## Leitura adicional\n\n* [Engenharia de prompts para o GitHub Copilot Chat](/pt/copilot/using-github-copilot/prompt-engineering-for-github-copilot)\n* [Práticas recomendadas para usar GitHub Copilot](/pt/copilot/using-github-copilot/best-practices-for-using-github-copilot)"}