jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

more edits to map topic

Browse Source
This commit is contained in:
Anne-Marie
2024-07-26 14:53:33 +00:00
parent fcbcae22d8
commit 464e39cda2
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/code-security/secret-scanning/managing-alerts-from-secret-scanning/about-alerts.md
View File

@@ -44,7 +44,7 @@ When {% data variables.product.company_short %} detects a supported secret in a
## About push protection alerts
Push protection scans pushes from contributors for supported secrets. If push protection detects a supported secret, it will block the push. When a contributor bypasses push protection to push a secret to the repository, a push protection alert is generated and displayed in the **Security** tab of the repository.
Push protection scans pushes for supported secrets. If push protection detects a supported secret, it will block the push. When a contributor bypasses push protection to push a secret to the repository, a push protection alert is generated and displayed in the **Security** tab of the repository. To see all push protection alerts for a repository, you must filter by `bypassed: true` on the alerts page. For more information, see "[AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning/viewing-alerts#filtering-alerts)."
{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}

4
content/code-security/secret-scanning/managing-alerts-from-secret-scanning/evaluating-alerts.md
View File

@@ -1,6 +1,6 @@
---
title: Evaluating alerts from secret scanning
intro: 'You can view alerts for secrets checked in to your repository and you can use filters to help you prioritize alerts.'
intro: 'There are some additional features that can help you evaluate alerts and prioritize their remediation, such as checking the secret''s validity.'
permissions: 'People with admin access to a {% ifversion fpt %}public {% endif %}repository can view secret scanning alerts for the repository.'
product: '{% data reusables.gated-features.secret-scanning %}'
versions:
@@ -22,7 +22,7 @@ allowTitleToDifferFromFilename: true
There are some additional features that can help you to evaluate alerts in order to better prioritize and manage them. You can:
* Check the validity of a secret, to see if the secret is still active. {% ifversion fpt or ghes %}**Applies to {% data variables.product.company_short %} tokens only**.{% endif %} For more information, see "[Checking a secret's validity](#checking-a-secrets-validity)."{% ifversion secret-scanning-validity-check-partner-patterns %}
* Perform an "on-demand" validity check, to get the most up to date validiation status. For more information, see "[Performing an on-demand-validity-check](#performing-an-on-demand-validity-check)."{% endif %}{% ifversion secret-scanning-github-token-metadata %}
* Perform an "on-demand" validity check, to get the most up to date validation status. For more information, see "[Performing an on-demand-validity-check](#performing-an-on-demand-validity-check)."{% endif %}{% ifversion secret-scanning-github-token-metadata %}
* Review a token's metadata. **Applies to {% data variables.product.company_short %} tokens only**. For example, to see when the token was last used. For more information, see "[Reviewing {% data variables.product.company_short %} token metadata](#reviewing-github-token-metadata)."{% endif %}
## Checking a secret's validity