Introducing Incidents 2.0 for faster runtime exploration 🔥
over 1 year ago by Gilad Mark
Runtime security alerts are your top priorities. Reviewing and prioritizing incidents including non-compliant resources based solely on severity and benchmarks without the context of the resource that is associated with specific policy is not enough. Bridgecrew now offers advanced capabilities on our Incidents 2.0 page. Explore, manage, and fix your open runtime incidents across cloud providers (AWS, Azure, GCP) and Kubernetes workloads faster with our revamped navigation and visualizations.
Key changes and additions include:
- View and filter incidents based on resource properties such as -
- Whether a resource is traced - filter for resources that include Bridgecrew’s tracing tags (yor_trace). Resources with trace enabled can link from a runtime incident to the relevant code in the Projects page in order to fix issues in code and maintain GitOps best practices.
- Whether a resource is unencrypted - when data storage is not encrypted, the severity of an incident is higher due to the decreased protections for data.
- Whether a resource is publicly accessible - resources that are publicly exposed pose a higher risk for exploitation.
- Whether a resource has specific tags - tags can be used to clarify the criticality of a cloud resource, the environment, or other details that may impact the risk of an incident.
- Traced resources will include a link to the Projects page to easily fix a runtime incident by fixing the IaC template that caused the incident.
- Focus on what is urgent and riskiest by using Bridgecrew out-of-the-box presets which enable different point of views, and create custom presets for your specified needs.
- Explore previous versions of your environment by looking at specific ranges of when open incidents were first identified.
Incidents screen