Skip to main content
Publicamos actualizaciones para la documentación con frecuencia y es posible que aún se esté traduciendo esta página. Para obtener la información más reciente, visite la documentación en inglés.
� 

� 

Esta versión de GitHub Enterprise se discontinuó el 2022-10-12. No se realizarán lanzamientos de patch, ni siquiera para problemas de seguridad críticos. Para obtener rendimiento mejorado, seguridad mejorada y nuevas características, actualice a la versión más reciente de GitHub Enterprise. Para obtener ayuda con la actualización, póngase en contacto con el soporte técnico de GitHub Enterprise.

Securing your repository

En este artículo

You can use a number of GitHub features to help keep your repository secure.

Who can use this feature

Repository administrators and organization owners can configure repository security settings.

Introduction

This guide shows you how to configure security features for a repository. You must be a repository administrator or organization owner to configure security settings for a repository.

Your security needs are unique to your repository, so you may not need to enable every feature for your repository. For more information, see "GitHub security features."

Algunas características están disponibles para todos los repositorios. Las características adicionales se encuentran disponibles para las empresas que utilizan la GitHub Advanced Security. Para más información, consulte "Acerca de GitHub Advanced Security".

Managing access to your repository

The first step to securing a repository is to set up who can see and modify your code. For more information, see "Managing repository settings."

From the main page of your repository, click Settings, then scroll down to the "Danger Zone."

Setting a security policy

  1. From the main page of your repository, click Security.
  2. Click Security policy.
  3. Click Start setup.
  4. Add information about supported versions of your project and how to report vulnerabilities.

For more information, see "Adding a security policy to your repository."

Managing the dependency graph

Los propietarios de la empresa pueden configurar el gráfico de dependencias y Dependabot alerts para una empresa. Para más información, vea "Habilitación del gráfico de dependencias para la empresa" y "Habilitación de Dependabot para la empresa".

For more information, see "Exploring the dependencies of a repository."

Managing Dependabot alerts

Dependabot alerts are generated when GitHub identifies a dependency in the dependency graph with a vulnerability.

Los propietarios de la empresa pueden configurar el gráfico de dependencias y Dependabot alerts para una empresa. Para más información, vea "Habilitación del gráfico de dependencias para la empresa" y "Habilitación de Dependabot para la empresa".

For more information, see "About Dependabot alerts."

Managing dependency review

Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "About dependency review."

Dependency review is a GitHub Advanced Security feature. To enable dependency review for a repository, ensure that the dependency graph is enabled and enable GitHub Advanced Security.

  1. From the main page of your repository, click Settings.
  2. Click Security & analysis.
  3. Check that dependency graph is configured for your enterprise.
  4. If GitHub Advanced Security is not already enabled, click Enable.

Configuring code scanning

You can set up code scanning to automatically identify vulnerabilities and errors in the code stored in your repository by using a CodeQL analysis workflow or third-party tool. For more information, see "Setting up code scanning for a repository."

Code scanning is available for organization-owned repositories if your enterprise uses GitHub Advanced Security.

Configuring secret scanning

Secret scanning is available for organization-owned repositories if your enterprise uses GitHub Advanced Security. Secret scanning may already be enabled for your repository, depending upon your organization's settings.

  1. From the main page of your repository, click Settings.
  2. Click Security & analysis.
  3. If GitHub Advanced Security is not already enabled, click Enable.
  4. Next to Secret scanning, click Enable.

Next steps

You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see "Viewing and updating Dependabot alerts," "Managing code scanning for your repository," and "Managing alerts from secret scanning."