Welcome to the Bridegecrew. You'll find comprehensive guides and documentation to help you start working with Bridegecrew as quickly as possible, as well as support if you get stuck. Let's go!
Suppressions are used in Bridgecrew to flag either falsely detected errors and/or justify accepted risk. You can suppress a specific resource or a group of resources under a specific policy. As a result, these resources are no longer in error and are moved to a trackable "suppressed" state. They continue to appear in dashboards and compliance reports.
You'll now find all of your incoming Bridgecrew notifications in one place—the Notification Center.
GitHub’s security capabilities combine all the tooling necessary to foster collaboration between security and engineering in a unified space and an automated workflow. With GitHub code scanning, Bridgecrew now provides native IaC security scanning for any GitHub repository.
GitLab is one of the fastest-growing source control and multi-purpose developer platforms. Bridgecrew already supports native integration with repos hosted on GitLab.com and now we are adding support to self-managed GitLab as well.
Tired of typing the same parameters over and over again? Our Jira integration became easier to use with the addition of issue templates.
The Bridgecrew dashboard got its first major face lift with a sleek new widget-based design.
Creating custom bridgecrew policies is now generally available on the Bridgecrew platform.
Control user access to accounts, repositories and actions using the new User Management feature.
The AWS Remediation CloudFormation stack just got a huge update.
Our customers have requested to get a weekly updates of everything that happened on their connected accounts. So we listened and came up with a condensed view of everything you should know about what Bridgecrew has observed in the past 7 days.