зеркало из https://github.com/github/docs.git
[2023-01-19]: Secret scanning: Validity check for GitHub tokens - [Public Beta] (#33762)
Co-authored-by: github-actions <github-actions@github.com> Co-authored-by: mchammer01 <42146119+mchammer01@users.noreply.github.com>
This commit is contained in:
Sophie
GitHub
Родитель
79ff2bc7f6
Коммит
5b47de1184
Двоичный файл не отображается.
|
До Ширина: | Высота: | Размер: 221 KiB После Ширина: | Высота: | Размер: 108 KiB |
Двоичный файл не отображается.
|
До Ширина: | Высота: | Размер: 89 KiB После Ширина: | Высота: | Размер: 61 KiB |
Двоичный файл не отображается.
|
После Ширина: | Высота: | Размер: 69 KiB |
|
|
@ -21,7 +21,7 @@ shortTitle: Manage secret alerts
|
|||
---
|
||||
|
||||
{% data reusables.secret-scanning.beta %}
|
||||
{% data reusables.secret-scanning.secret-scanning-alerts-beta %}
|
||||
{% data reusables.secret-scanning.secret-scanning-alerts-beta %}
|
||||
|
||||
## Managing {% data variables.secret-scanning.alerts %}
|
||||
|
||||
|
|
@ -35,41 +35,61 @@ shortTitle: Manage secret alerts
|
|||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
1. In the left sidebar, click **Secret scanning alerts**.
|
||||
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 "Secret scanning" click the alert you want to view.
|
||||
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-partner-documentation-link-UI %}
|
||||
1. To dismiss an alert, select the "Dismiss alert" dropdown menu and click a reason for resolving an alert.
|
||||
|
||||
{% endif %}{% ifversion secret-scanning-validity-check %}
|
||||
1. Check the validity of the secret and follow the remediation steps.
|
||||
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Validity check for {% data variables.product.company_short %} tokens is currently in public beta and subject to change.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data variables.product.company_short %} provides information about the validity of the secret, for {% data variables.product.company_short %} tokens only.
|
||||
|
||||
| Validity | Result |
|
||||
|-------------------------|--------------------------------------------------------------------------------|
|
||||
| Active secret | {% data variables.product.company_short %} confirmed this secret is active |
|
||||
| Active secret | {% data variables.product.company_short %} checked with this secret's provider and found that the secret is active |
|
||||
| Possibly active secret | {% data variables.product.company_short %} does not support validation checks for this token type yet |
|
||||
| Possibly active secret | {% data variables.product.company_short %} could not verify this secret |
|
||||
| Secret appears inactive | You should make sure no unauthorized access has already occurred |
|
||||
{% endif %}{% ifversion secret-scanning-partner-documentation-link-UI %}
|
||||
1. To dismiss an alert, select the "Close as" dropdown menu and click a reason for resolving an alert.
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
1. To dismiss an alert, select the "Mark as" dropdown menu and click a reason for resolving an alert.
|
||||
2. To dismiss an alert, select the "Mark as" dropdown menu and click a reason for resolving an alert.
|
||||
|
||||
|
||||
|
||||
|
||||
{% endif %}{% ifversion secret-scanning-dismissal-comment %}
|
||||
1. 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 "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/secret-scanning#update-a-secret-scanning-alert)" in the REST API documentation.
|
||||
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 "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/secret-scanning#update-a-secret-scanning-alert)" in the REST API documentation.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Dismiss alert**.
|
||||
4. Click **Close alert**.
|
||||
{% endif %}
|
||||
|
||||
## Securing compromised secrets
|
||||
|
|
|
|||
|
|
@ -0,0 +1,7 @@
|
|||
# Reference: #8576.
|
||||
# Documentation for secret scanning: validity check for GitHub tokens.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.9'
|
||||
ghae: '>=3.9'
|
||||
Загрузка…
Ссылка в новой задаче