Octomerger Bot
Binary file not shown.
|
Before Width: | Height: | Size: 72 KiB After Width: | Height: | Size: 118 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 14 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.0 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 44 KiB After Width: | Height: | Size: 61 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 28 KiB After Width: | Height: | Size: 35 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 8.7 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 66 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 39 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 65 KiB After Width: | Height: | Size: 73 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 40 KiB After Width: | Height: | Size: 32 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 41 KiB After Width: | Height: | Size: 33 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 61 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 17 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 24 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 27 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 29 KiB After Width: | Height: | Size: 47 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 69 KiB After Width: | Height: | Size: 34 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB |
@@ -57,5 +57,5 @@ When you enable one or more security and analysis features for existing reposito
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -63,7 +63,7 @@ Before defining a custom pattern, you must ensure that {% data variables.product
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
After your pattern is created, {% data reusables.secret-scanning.secret-scanning-process %} For more information on viewing {% data variables.secret-scanning.alerts %}, see "[AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning)."
|
||||
|
||||
@@ -131,7 +131,7 @@ Before defining a custom pattern, you must ensure that you enable {% data variab
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in repositories in your organization, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.secret-scanning.alerts %}, see "[AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning)."
|
||||
|
||||
@@ -182,7 +182,7 @@ Before defining a custom pattern, you must ensure that you enable secret scannin
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in repositories within your enterprise's organizations with {% data variables.product.prodname_GH_advanced_security %} enabled, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.secret-scanning.alerts %}, see "[AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning)."
|
||||
|
||||
@@ -200,7 +200,7 @@ When you save a change to a custom pattern, this closes all the {% data variable
|
||||
{% data reusables.advanced-security.secret-scanning-enable-push-protection-custom-pattern %}
|
||||
1. Optionally, to disable push protection for your custom pattern, click **Disable**.
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
## Removing a custom pattern
|
||||
|
||||
@@ -211,5 +211,3 @@ When you save a change to a custom pattern, this closes all the {% data variable
|
||||
1. To the right of the custom pattern you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
|
||||
1. Review the confirmation, and select a method for dealing with any open alerts relating to the custom pattern.
|
||||
1. Click **Yes, delete this pattern**.
|
||||
|
||||
|
||||
|
||||
@@ -34,29 +34,11 @@ shortTitle: Manage secret alerts
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
1. In the left sidebar, click **{% data variables.product.prodname_secret_scanning_caps %} alerts**.
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghae %}
|
||||
|
||||
{% endif %}
|
||||
1. Under "{% data variables.product.prodname_secret_scanning_caps %}" click the alert you want to view.
|
||||
{% ifversion fpt %}
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghec %}
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghes %}
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghae %}
|
||||
|
||||
{% endif %}{% ifversion secret-scanning-validity-check %}
|
||||
1. Check the validity of the secret and follow the remediation steps.
|
||||
1. In the left sidebar, under "Vulnerability alerts", click **{% data variables.product.prodname_secret_scanning_caps %}**.
|
||||
1. Under "{% data variables.product.prodname_secret_scanning_caps %}" click the alert you want to view.{% ifversion secret-scanning-validity-check %}
|
||||
1. Optionally, if the leaked secret is a {% data variables.product.company_short %} token, check the validity of the secret and follow the remediation steps.
|
||||
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -79,16 +61,13 @@ shortTitle: Manage secret alerts
|
||||
|
||||
|
||||
{% else %}
|
||||
2. To dismiss an alert, select the "Mark as" dropdown menu and click a reason for resolving an alert.
|
||||
1. To dismiss an alert, select the "Mark as" dropdown menu and click a reason for resolving an alert.
|
||||
|
||||
|
||||
|
||||
{% endif %}{% ifversion secret-scanning-dismissal-comment %}
|
||||
3. Optionally, add a dismissal comment. The dismissal comment will be added to the alert timeline and can be used as justification during auditing and reporting. You can view the history of all dismissed alerts and dismissal comments in the alert timeline. You can also retrieve or set a comment by using the {% data variables.product.prodname_secret_scanning_caps %} API. The comment is contained in the `resolution_comment` field. For more information, see "[AUTOTITLE](/rest/secret-scanning#update-a-secret-scanning-alert)" in the REST API documentation.
|
||||
|
||||
|
||||
|
||||
4. Click **Close alert**.
|
||||
1. Optionally, in the "Comment" field, add a dismissal comment. The dismissal comment will be added to the alert timeline and can be used as justification during auditing and reporting. You can view the history of all dismissed alerts and dismissal comments in the alert timeline. You can also retrieve or set a comment by using the {% data variables.product.prodname_secret_scanning_caps %} API. The comment is contained in the `resolution_comment` field. For more information, see "[AUTOTITLE](/rest/secret-scanning#update-a-secret-scanning-alert)" in the REST API documentation.
|
||||
1. Click **Close alert**.
|
||||
{% endif %}
|
||||
|
||||
## Securing compromised secrets
|
||||
|
||||
@@ -1,9 +1,12 @@
|
||||
1. Enter the details for your new custom pattern:
|
||||
1. You must at least provide the name for your pattern, and a regular expression for the format of your secret pattern.
|
||||
1. Enter the details for your new custom pattern. You must at least provide the name for your pattern, and a regular expression for the format of your secret pattern.
|
||||
1. In the "Pattern name" field, type a name for your pattern.
|
||||
1. In the "Secret format" field, type a regular expression for the format of your secret pattern.
|
||||
1. You can click **More options {% octicon "chevron-down" aria-label="down" %}** to provide other surrounding content or additional match requirements for the secret format.
|
||||
1. Provide a sample test string to make sure your configuration is matching the patterns you expect.
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. When you're satisfied with your new custom pattern, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}**Publish pattern**{% else %}**Create pattern**.{% endif %}
|
||||
1. When you're satisfied with your new custom pattern, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}**Publish pattern**{% else %}**Create pattern**{% endif %}.
|
||||
|
||||
@@ -1,9 +1,10 @@
|
||||
{%- ifversion custom-pattern-dry-run-ga %}
|
||||
1. Search for and select up to 10 repositories where you want to perform the dry run.
|
||||
|
||||
|
||||
|
||||
1. When you're ready to test your new custom pattern, click **Run**.
|
||||
{%- else %}
|
||||
1. Search for and select up to 10 repositories where you want to perform the dry run.
|
||||
|
||||
1. When you're ready to test your new custom pattern, click **Dry run**.
|
||||
{%- endif %}
|
||||
|
||||
@@ -1,12 +1,9 @@
|
||||
{%- ifversion custom-pattern-dry-run-ga %}
|
||||
1. Select the repositories where you want to perform the dry run.
|
||||
* To perform the dry run across the entire organization, select **All repositories in the organization**.
|
||||
|
||||
* To specify the repositories where you want to perform the dry run, select **Selected repositories**, then search for and select up to 10 repositories.
|
||||
|
||||
1. When you're ready to test your new custom pattern, click **Run**.
|
||||
{%- else %}
|
||||
1. Search for and select up to 10 repositories where you want to perform the dry run.
|
||||
|
||||
1. When you're ready to test your new custom pattern, click **Dry run**.
|
||||
{%- endif %}
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
1. Under "{% data variables.product.prodname_secret_scanning_caps %}", under "Push protection", click **Enable all**.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Optionally, click "Automatically enable for repositories added to {% data variables.product.prodname_secret_scanning %}."{% ifversion secret-scanning-custom-link-on-block %}
|
||||
3. Optionally, to include a custom link in the message that members will see when they attempt to push a secret, click **Add a resource link in the CLI and web UI when a commit is blocked**, then type a URL, and click **Save link**.
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
@@ -3,4 +3,4 @@
|
||||
1. Optionally, click "Automatically enable for repositories added to {% data variables.product.prodname_secret_scanning %}."{% ifversion push-protection-custom-link-orgs %}
|
||||
1. Optionally, to include a custom link in the message that members will see when they attempt to push a secret, select **Add a resource link in the CLI and web UI when a commit is blocked**, then type a URL, and click **Save link**.
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
Reference in New Issue
Block a user