참고: 보호 푸시로서의 Secret scanning은(는) 현재 베타 버전이며 변경될 수 있습니다.
About metrics for secret scanning push protection
The metrics overview for secret scanning push protection helps you to understand how well you are preventing security leaks in your organization or across organizations in your enterprise. You can use the metrics to assess how push protection is performing, and to easily identify the repositories where you may need to take action in order to prevent leaks of sensitive information.
The overview shows you a summary of how many pushes containing secrets have been successfully blocked by push protection, as well as how many times push protection was bypassed.
You can also find more granular metrics, such as:
- The secret types that have been blocked or bypassed the most
- The repositories that have had the most pushes blocked
- The repositories that are bypassing push protection the most
- The percentage distribution of reasons that users give when they bypass the protection
Use the date picker to set the time range that you want to view alert activity and metrics for, and click in the search box to add further filters on the alerts and metrics displayed. For more information, see "보안 개요에서 경고 필터링."
You can see secret scanning metrics if you have:
- The
admin
role for the repository. - A custom repository role with the "View secret scanning results" fine-grained permissions for the repository. For more information, see "사용자 지정 리포지토리 역할 정보."
- Access to alerts for the repository. For more information, see "리포지토리에 대한 보안 및 분석 설정 관리."
The metrics are based on activity from the default period or your selected period.
Viewing metrics for secret scanning push protection for an organization
-
GitHub.com에서 조직의 기본 페이지로 이동합니다.
-
조직 이름에서 보안을 클릭합니다.
-
In the sidebar, under "Metrics", click Secret scanning.
-
Click on an individual secret type or repository to see the associated 비밀 검사 경고 for your organization.
-
You can use the options at the top of the page to filter the group of repositories that you want to see secret scanning metrics for.
- Use the date picker to set the time range that you want to view metrics for. Note that the date used by the date picker corresponds to the date a secret was bypassed on.
- Click in the search box to add further filters on the secret scanning metrics displayed. For more information, see "보안 개요에서 경고 필터링."
Viewing metrics for secret scanning push protection for an enterprise
You can view metrics for secret scanning push protection across organizations in an enterprise. 보안 개요에 표시되는 정보는 리포지토리 및 조직에 대한 액세스 권한에 따라 다르며, GitHub Advanced Security이(가) 해당 리포지토리 및 조직에서 사용되는지 여부에 따라 달라집니다. 자세한 내용은 "보안 개요"을(를) 참조하세요.
Tip
You can use the owner
filter in the search field to filter the data by organization. If you're an owner of an 관리형 사용자가 있는 엔터프라이즈, you can use the owner-type
filter to filter the data by the type of repository owner, so that you can view data from either organization-owned repositories or user-owned repositories. For more information, see "보안 개요에서 경고 필터링."
-
GitHub Enterprise Cloud으로 탐색합니다.
-
GitHub의 오른쪽 위 모서리에서 프로필 사진을 클릭한 다음 엔터프라이즈를 클릭합니다.
-
엔터프라이즈 목록에서 보려는 엔터프라이즈를 클릭합니다.
-
왼쪽 사이드바에서 코드 보안을 클릭합니다.
-
In the sidebar, click Secret scanning metrics.
-
Click on an individual secret type or repository to see the associated 비밀 검사 경고 for your enterprise.
-
You can use the options at the top of the page to filter the group of repositories that you want to see secret scanning metrics for.
- Use the date picker to set the time range that you want to view metrics for. Note that the date used by the date picker corresponds to the date a secret was bypassed on.
- Click in the search box to add further filters on the secret scanning metrics displayed. For more information, see "보안 개요에서 경고 필터링."