Product guides

Integrations in the Console

Suggest Edits

Code Defender has a variety of integrations to work with your current tech stack and maximize your team’s efficiency. You can access integrations from Code Defender’s Product Settings > Integrations > Integration Settings.

Slack

The Slack integration lets Code Defender send automated notifications and messages to Slack channels you specify.

  1. On the Slack integration, select Add integration.
  2. Complete the following fields:
    • Integration name: The name of your Slack integration and how it will appear in the HUMAN console.
    • Slack webhook URL: The webhook URL for your Slack integration. Must be in the form https://hooks.slack.com.
    • Slack channel: The Slack channel Code Defender should send messages to. Must be in the form #slack-channel.
  3. Select Test to confirm your integration is working.
  4. Once your test is successful, select Save.

Your integration has been successfully created.

Email

The Email integration lets Code Defender send automated emails when an alert is triggered.

  1. On the Email integration, select Add integration.
  2. Complete the following fields:
    • Integration name: The name of your Email integration and how it will appear in the HUMAN console.
    • Email: The email addresses Code Defender should send emails to. Press Enter after each email to add multiple addresses.
  3. Select Test to confirm your integration is working.
  4. Once your test is successful, select Save.

Your integration has been successfully created.

Jira

The Jira integration lets you create Jira issues from Code Defender alerts.

Prerequisites

Before you start, you must create a ticket field called Labels in the the Jira Project you want to enable the integration on. See Atlassian's help article for more information.

Integrate Jira

  1. On the Jira integration, select Add integration.
  2. Complete the following fields:
    • Integration name: The name of your Email integration and how it will appear in the HUMAN console.
    • Jira webhook URL: The webhook URL for your Jira integration. Must be in the form https://<companyname>.atlassian.net/rest/api/2/issue/. Note that the v2 API address is mandatory.
    • Jira project ID: The ID for the Jira project Code Defender should create issues in. The ID should be a number. See Jira's article for more information.
    • API token: Your Jira API token. Only API tokens created by the Default reporter email are allowed. Otherwise, the integration will fail. We do not support tokens with scopes, so only regular tokens are allowed.
    • Default reporter email: The email address for the default reporter for issues.
    • Desired issue type: The type of task Code Defender should create for issues by default. The selected task type must also exist in the specified Jira project. This field is optional.
    • Add event risk level priority: Choose whether to assign the ticket a priority level. If you choose to add one, Code Defender will assign the ticket priority based on the incident’s risk level. For example, high-risk incidents will create a high-priority issue. The priority field must exist in the issue in Jira for this feature to sync properly. This field is optional.
  3. Select Test to confirm your integration is working.
  4. Once your test is successful, select Save.

Your integration has been successfully created.

Datadog Incidents

The Datadog Incidents integration lets you send Code Defender alerts to your Datadog application.

  1. On the Datadog Incidents integration, click Add Integration.
  2. Complete the following fields:
    • Integration name: The name of your Datadog integration and how it will appear in the HUMAN console.
    • Datadog Instance Webhook URL: The webhook URL for the instance you want to send Code Defender incidents to.
    • Application Key: The Datadog application key with incident_write permissions for the instance.
    • API Key: Your Datadog API key.
  3. Click Test connection to confirm your integration is working.
  4. Once your test is successful, click Save changes.

PagerDuty Events

The PaterDuty Events integration lets you send events from Code Defender to create incidents.

📘

Note

The PagerDuty Events integration is a separate integration from the PagerDuty integration. To integrate with the latter, you must contact our team instead. For more, see our help article.

  1. On the PagerDuty Events integration, select Add integration.
  2. Complete the following fields:
    • Integration name: The name of your PagerDuty Event integration and how it will appear in the HUMAN console.
    • Webhook URL: The webhook URL for the PagerDuty Event you are integrating with. Must be in the form https://events.pagerduty.com/v2/enque.
    • API key: Your PagerDuty API authentication key.
  3. Select Test to confirm your integration is working.
  4. Once your test is successful, select Save.

Your integration has been successfully created.

Splunk

The Splunk integration lets you search and visualize data sent from Code Defender. CD exports these logs in JSON.

  1. On the Splunk integration, select Add Integration.
  2. Complete the following fields:
    • Integration name: The name of your Splunk integration and how it will appear in the HUMAN console.
    • Splunk webhook URL: The webhook URL for your Splunk integration. Must be in the form https://<customer-identifier>.splunkcloud.com/services/collector.
    • API token: Your Splunk API token.
    • Custom Splunk index: The Splunk index that HUMAN should send information to. This field is optional.
  3. Select Test connection to confirm your integration is working.
  4. Once your test is successful, select Save changes.

Your integration has been successfully created.

GCS Bucket

The Google Cloud Storage (GCS) Bucket integration lets you send Code Defender alerts to your GCS Bucket.

  1. On the GCS bucket integration, click Add Integration.
  2. Complete the following fields:
    • Integration name: The name of your GCS Bucket integration and how it will appear in the HUMAN console.
    • Bucket name: The name of the Bucket you want to send Code Defender data to.
    • Service account authentication JSON: Upload your Bucket’s service account key in JSON. Be sure you create a service account with sufficient permissions to write to the Bucket and share that user’s authentication file.
    • Compression type: Optionally choose a compression type when sending files to your Bucket.
  3. Click Test connection to confirm your integration is working.
  4. Once your test is successful, click Save changes.

HTTP Webhook

The HTTP Webhook integration lets you send HTTP requests from Code Defender whenever there’s a critical event. These include:

  • PCI scope changes
  • Newly detected client-side risks

You must have Code Defender Admin permissions to create webhooks.

  1. On the HTTP Webhook integration, click Add Integration.
  2. Complete the following fields:
    • Integration name: The name of your webhook integration and how it will appear in the HUMAN console.
    • Webhook URL: The endpoint URL that this webhook will be sent to.
    • Method: The HTTP method for the webhook.
    • Protocol: The protocol for the webhook to use.
    • SSL Certificate: If you selected TLS as the Protocol, you also need to provide an SSL client certificate. TCP protocols do not need to provide this.
    • Body Pattern: Customize the webhook body pattern as needed. This field is optional.
    • Headers: Add any header names and values as needed. If any duplicate header keys are provided, the webhook will only send the latest one. This field is optional.
  3. Click Test to validate your integration.
  4. Once your test is successful, click Save.

Updated about 1 month ago