Skip to main content

Enterprise Server 3.15 está disponível no momento como versão release candidate.

Habilitar a verificação de segredos que não são de provedor

Você pode habilitar secret scanning para detectar segredos potenciais adicionais nos níveis de repositório e organização.

Quem pode usar esse recurso?

Proprietários de repositórios, proprietários de organizações, gerentes de segurança e usuários com a função de administrador

Scanning for non-provider patterns is available for the following repositories:

  • Public, private, and internal repositories in organizations using GitHub Enterprise Cloud with GitHub Advanced Security enabled

Enabling scanning for non-provider patterns

Note

The detection of non-provider patterns is currently in beta and subject to change.

You can enable scanning for non-provider patterns. Non-provider patterns correspond to secrets such as private keys and they have a higher ratio of false positives.

For more information about non-provider patterns, see "Supported secret scanning patterns."

Enabling detection of non-provider patterns for a repository

  1. On GitHub, navigate to the main page of the repository.

  2. Under your repository name, click Settings. If you cannot see the "Settings" tab, select the dropdown menu, then click Settings.

    Screenshot of a repository header showing the tabs. The "Settings" tab is highlighted by a dark orange outline.

  3. In the "Security" section of the sidebar, click Code security and analysis.

  4. Under Secret scanning, to the right of "Non-provider patterns", click Enable.

Enabling detection of non-provider patterns for an organization

You can enable scanning for non-provider patterns at the organization level by applying a custom security configuration. For more information, see "Creating a custom security configuration."

Further reading