At Bugcrowd, we are well aware that extensibility is a core concern for customers. Siloed solutions are a major source of fragmentation in cybersecurity environments, so seamless integrations with your existing development and security processes is one of the Bugcrowd Security Knowledge Platform’s most important design principles. Its rich library of connectors and APIs allows you to quickly become productive for immediate impact on your security posture.
- Immediate business updates. Webhooks let applications receive information in a simple, efficient way as new data becomes available, without having them constantly poll Bugcrowd for changes. That makes webhooks a great option for use cases like notifications, messages, and alerts, especially when automation is a requirement, such as sending them on specific days or times.
- Specificity. Webhooks let you directly connect specific parts of an application instead of having to build a complete framework for the entire app. For example, you may want to create alerts about a very specific type of event, but you don’t want to have to write a lot of code for it. When the Bugcrowd event happens, that specific part of your custom application will be invoked.
- Self-service setup. Because Webhooks rely only on HTTP for transport, adding a webhook to an application is quick and pretty much effortless out of the box.
We’re happy to announce that you can now get those benefits with Bugcrowd by making applications react to events through a new Outgoing Webhooks integration. For example, you can set up custom security workflows to activate when Bugcrowd submissions are created, triaged, or receive comments.
The process is simple, just look for the new tile in Settings > Integrations:
Next, all that is needed is to specify a name, consumer URL, and desired triggering events (for example, when a submission is created).
And, you’re off!
We hope you find this new type of extensibility useful. For more information about Bugcrowd APIs and webhooks, explore our docs.