Security Center
The security center shows the security of many repositories at once, so that you do not have to open each repository to see where findings are. There are two of them:
- the organization security center at
/{org}/-/security, in the Security tab of an organization - the instance security center at
/-/admin/security, underSite Administration > Security
Both are read only. Findings are still handled on the page of their repository (or package). A valid license is required.
Who sees what
Section titled “Who sees what”- Site administrators and owners of an organization see every repository of the organization.
- Other members see the repositories whose permissions give them access to the security tab of the repository. A stranger of a public repository does not see its findings.
- The instance security center is for site administrators only.
Organization security center
Section titled “Organization security center”| Page | Content |
|---|---|
| Overview | Open findings by type and severity, findings that are new in the last 7 days, critical and high findings, scan coverage, mean time to fix, a trend chart of the open findings, the repositories and packages with the most risk |
| Findings | The findings of all repositories, with filters |
| Secrets | Open secret findings, and what push protection blocked, let through and only reported in the last 30 days |
| Coverage | Which scans each repository has switched on, per type, and push protection |
| Packages | The findings of the packages of the organization, see Package scanning |
Instance security center
Section titled “Instance security center”It is the same view over every repository of the instance, with these pages: Overview, Findings, Secrets, Owners, Scans and Packages.
- Secrets also lists the access tokens that were revoked after they leaked. These entries are recorded under the holder of the token, so they are listed here only.
- Owners lists organizations and users with their risk and scan coverage. Owners with open findings come first, most severe first.
- Scans shows running and failed scans, with a Repositories and a Packages tab.
- Packages also has a scan every package action.
The totals of the overview are cached for two minutes.
How the numbers are counted
Section titled “How the numbers are counted”- Only the default branch of each repository is counted, so a branch that is scanned twice does not count twice.
- Open findings are the findings with the open status. Repositories and packages are counted together, and the type list has a Packages row. Package numbers only appear where package scanning is on.
- New in 7 days counts findings first reported in the last 7 days, whatever became of them.
- Mean time to fix is the time between the report and the fix of the findings that a commit fixed in the last 90 days. Dismissed findings do not count.
- The trend chart is rebuilt from the creation and closing times of the findings, so it is an approximation: a finding that was reopened counts as open for its whole life.
- Coverage: a repository without its own configuration reads the scan defaults of its owner. A type is fully covered when every scanner of that type that detects by itself is on, and partially covered when only some are. Scanners driven by agents and scanners that only import uploaded reports are not counted.
Push protection
Section titled “Push protection”Secret push protection records what it did in the audit log (repository:pushprotection:block, repository:pushprotection:bypass and repository:pushprotection:report). The Secrets pages list these entries and count them over the last 30 days. A blocked push leaves no finding, only the audit entry, which holds the rule, the path and the line but never the secret itself.
The Secrets page warns when audit records are kept for fewer days than the page counts. See Audit Log.