Workflow Integrations
StackHawk integrates with third-party development tools to automate security workflows. Integrations connect via OAuth, API keys, or add-on tokens depending on the provider.
All StackHawk integrations can be managed from the Integrations page.
Notification Integrations
These integrations trigger events in notification, logging, and messaging platforms when HawkScan runs.
Project Management Integrations
Create tickets and manage scan findings from StackHawk in your project management tools.
SAST Integrations
Link findings between StackHawk and SAST (Static Application Security Testing) providers.
Compliance Management
Track compliance certification and reporting requirements.
Other Integrations
Build custom integrations using webhooks.
Integrations FAQ
How are Integrations assigned in StackHawk?
StackHawk integrations are associated with a user’s organization, and can be managed in the integrations tab of the web platform. Because integrations are assigned to the user’s organization, the user that established the integration can leave the organization and the integrations will continue to operate.
How can I remove an Integration?
Integrations are generally bound two-ways: an integration can be removed either via StackHawk or from the integration provider.
To remove an integration via the StackHawk Platform, go to its integration configuration page. Under the Danger Zone settings, choose to remove the integration from the organization.
To fully remove some integrations, you may need to additionally remove the app or add-on from the integration provider as well.
A removed integration can always be recreated.
What permissions am I giving the Integration?
A common pattern of OAuth 2.0 integrations is a request of certain assigned permissions, or scopes. Each integration provider has their own defined scopes and what permissions each scope entails. To learn more about what permission StackHawk requests, visit the integration’s docs. As part of authorizing an integration, you will be asked to verify approval of the requested scopes for your integration.
For non-OAuth 2.0 integrations, such as add-ons, the permissions are detailed in the installation.
What happens if an Integration changes?
StackHawk and the third-party integration provider each reserve the right to make changes to how their services operate and how the integration operates. For the most part, changes to the integration will update automatically or new configuration options will be made available to support any changes.
If a change to the integration requires additional scopes, you will need to reauthorize the integration with the expanded scopes to use the updated functionality. You can still use an existing integration with its existing scopes.
Request an Integration
If there is functionality you would like to see with an existing integration, or a third-party tool you would like StackHawk to integrate with, contact StackHawk Support.