If you are using Terraform Cloud to operate and manage your cloud provisioning lifecycle, you are probably aware if the benefits of predictable deployment outcomes. One important pillar of that process is ensuring security and compliance standards are met on every resource block.
There are endless options to provision and configure resources in the public cloud. While cloud provider consoles and SDKs register changes in standard logging solutions like AWS CloudTrail or Google's StackDriver, it's becoming increasingly difficult to use these logs to keep track of meaningful configuration changes. IaC introduces an additional layer of complexity by storing configuration changes in git logs and state files.
Fixing misconfigured cloud resources isn't just about replacing configuration variables. Before changing existing configurations, we should make sure we know how those configurations are currently being used throughout our IaC dependencies.
It's been a long time since we upgraded the experience of our native Incidents filters.
Developing secure IAM requires iterative and ongoing effort. That's why we're adding continuous IAM right-sizing insights to Bridgecrew's core platform. With IAM Insights, Bridgecrew continuously collects permission entitlement configurations and evaluates them against actual activity telemetry. The result is actionable, codified recommendations on how to reduce the permission of existing IAM entities including users, roles, groups, and policy docs.
Investigating resource errors becomes a lot simpler with Bridgecrew's new UI and metadata around resources. By including a full array of metadata entities pulled from cloud provider APIs and related configurations defined using IaC, Bridgecrew hopes to make it easier to understand risk and be able to action errors faster.
Show off your cloud security efforts with Bridgecrew's README badges!
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.