You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
+12-9Lines changed: 12 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,9 +28,9 @@ topics:
28
28
You can define custom patterns to identify secrets that are not detected by the default patterns supported by {% data variables.product.prodname_secret_scanning %}. For example, you might have a secret pattern that is internal to your organization. For details of the supported secrets and service providers, see "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns)."
29
29
30
30
You can define custom patterns for your enterprise, organization, or repository. {% data variables.product.prodname_secret_scanning_caps %} supports up to
31
-
{%- ifversion fpt or ghec or ghes > 3.3 %} 500 custom patterns for each organization or enterprise account, and up to 100 custom patterns per repository.
32
-
{%- elsif ghes = 3.3 %} 100 custom patterns for each organization or enterprise account, and 20 per repository.
33
-
{%- else %} 20 custom patterns for each organization or enterprise account, and per repository.
31
+
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-7297 %} 500 custom patterns for each organization or enterprise account, and up to 100 custom patterns per repository.
32
+
{%- elsif ghes = 3.2 %} 20 custom patterns for each organization or enterprise account, and per repository.
33
+
{%- else %} 100 custom patterns for each organization or enterprise account, and 20 per repository.
34
34
{%- endif %}
35
35
36
36
{% ifversion ghes < 3.3 %}
@@ -67,7 +67,7 @@ Before defining a custom pattern, you must ensure that {% data variables.product
67
67
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
68
68
{% data reusables.repositories.navigate-to-ghas-settings %}
69
69
{% data reusables.advanced-security.secret-scanning-new-custom-pattern %}
70
-
{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %}
70
+
{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}{% ifversion secret-scanning-custom-enterprise-35 %}
71
71
1. When you're ready to test your new custom pattern, to identify matches in the repository without creating alerts, click **Save and dry run**.
72
72
{% data reusables.advanced-security.secret-scanning-dry-run-results %}
73
73
{% endif %}
@@ -122,7 +122,7 @@ Before defining a custom pattern, you must ensure that you enable {% data variab
122
122
{% data reusables.repositories.navigate-to-ghas-settings %}
123
123
{% data reusables.advanced-security.secret-scanning-new-custom-pattern %}
124
124
{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
- At the enterprise level, only the creator of a custom pattern can edit the pattern, and use it in a dry run.
147
147
- Enterprise owners can only make use of dry runs on repositories that they have access to, and enterprise owners do not necessarily have access to all the organizations or repositories within the enterprise.
@@ -158,8 +158,8 @@ Before defining a custom pattern, you must ensure that you enable secret scannin
158
158
{% data reusables.enterprise-accounts.advanced-security-security-features %}
1. When you're ready to test your new custom pattern, to identify matches in the enterprise without creating alerts, click **Save and dry run**.
163
163
{% data reusables.advanced-security.secret-scanning-dry-run-select-repos %}
164
164
{% data reusables.advanced-security.secret-scanning-dry-run-results %}
165
165
{%- endif %}
@@ -175,7 +175,10 @@ When you save a change to a custom pattern, this closes all the {% data variable
175
175
* For a repository or organization, display the "Security & analysis" settings for the repository or organization where the custom pattern was created. For more information, see "[Defining a custom pattern for a repository](#defining-a-custom-pattern-for-a-repository)" or "[Defining a custom pattern for an organization](#defining-a-custom-pattern-for-an-organization)" above.
176
176
* For an enterprise, under "Policies" display the "Advanced Security" area, and then click **Security features**. For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above.
177
177
2. Under "{% data variables.product.prodname_secret_scanning_caps %}", to the right of the custom pattern you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}.
178
-
3. When you have reviewed and tested your changes, click **Save changes**.
0 commit comments