Dashboard

Dashboard

The Dashboard provides visualizations of data about the errors found during Bridgecrew Cloud scans.

Active Policies

This scorecard shows the breakdown of all enabled policies.
Failed policies - the number of Policies whose checks resulted in at least one resource in error.
Passed policies - the number of Policies whose checks resulted in no errors.
Suppressed policies - the number of Policies whose current checks resulted in at least one resource in error that was suppressed, and no other resources in errors.

Unresolved Errors

This scorecard shows the total number of errors across all resources.
The severity based breakdown trend illustrates the number of errors daily, per severity.

Errors by Service

This shows the proportion of errors per cloud service connected to Bridgecrew Cloud.

Accounts

This shows: (1) which cloud accounts (AWS, Azure and Google) are connected to Bridgecrew Cloud (2) the monthly error trend (3) number of resources monitored in total.
You can search or select the accounts to include in the display.

Repositories

This shows which Git Repositories are connected to Bridgecrew Clouds and shows the monthly error trend and number of resources monitored in total.
You can search or select Repositories to include in the display.

Errors by Policy

This shows which Policies have the highest percent of errors out of all policy-checks performed.

Errors by Benchmark

This shows which compliance benchmarks have the highest percent of errors out of all benchmarks analyzed. It also includes a breakdown of errors by the number of failed, passed and suppressed checks.

Errors by Category

This shows which categories include the highest percent of errors out of all resource types analyzed.

Resource Status - Last 30 Days

This shows the 30-day trend of Passed, Failed, Suppressed for selected Resources.

When you click on a specific day, the label shows the date and the number of Resources which Passed, Failed or have been Suppressed.

Updated 4 months ago


Dashboard


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.