GitHub AE is currently under limited release. Please contact our Sales Team to find out more.

Configuring secret scanning for your repositories

You can configure how GitHub scans your repositories for secrets.

People with admin permissions to a repository can enable secret scanning for the repository.

Secret scanning is available as part of GitHub Advanced Security, which is free during the beta release. For more information, see "About GitHub Advanced Security."

In this article

Note: Secret scanning for organization-owned repositories is currently in beta and subject to change.

Enabling secret scanning for repositories

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

  2. Under your repository name, click Settings. Repository settings button

  3. In the left sidebar, click Security & analysis. "Security & analysis" tab in repository settings

  4. Before you can enable secret scanning, you need to enable GitHub Advanced Security first. To the right of "GitHub Advanced Security", click Enable. Enable GitHub Advanced Security for your repository

  5. Click Enable GitHub Advanced Security for this repository to confirm the action. Confirm enabling GitHub Advanced Security for your repository

  6. To the right of "Secret scanning", click Enable. Enable secret scanning for your repository

Excluding alerts from secret scanning in repositories

You can use a secret_scanning.yml file to exclude directories from secret scanning. For example, you can exclude directories that contain tests or randomly generated content.

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

  2. Above the list of files, using the Add file drop-down, click Create new file. "Create new file" in the "Add file" dropdown

  3. In the file name field, type .github/secret_scanning.yml.

  4. Under Edit new file, type paths-ignore: followed by the paths you want to exclude from secret scanning.

    paths-ignore:
      - "foo/bar/*.js"
    

    You can use special characters, such as * to filter paths. For more information about filter patterns, see "Workflow syntax for GitHub Actions."

    Notes:

    • If there are more than 1,000 entries in paths-ignore, secret scanning will only exclude the first 1,000 directories from scans.
    • If secret_scanning.yml is larger than 1 MB, secret scanning will ignore the entire file.

You can also ignore individual alerts from secret scanning. For more information, see "Managing alerts from secret scanning."

Further reading

Did this doc help you?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.