Before you begin

This article covers how to create a standard integration using the Cyara Integration Hub, for more detailed walkthroughs on how to integrate to a specific service such as Splunk, ServiceNow or Jira click the links below.

• Creating a Jira Integration
• Creating a ServiceNow Integration
• Creating a Splunk Integration

Before you create an integration, ensure that the Integration Hub is first enabled, and that you have created an Impersonation User to access the Cyara API, click the links below for more information.

• Enabling the Integration Hub
• Creating an Impersonation User

Creating an Integration

 To create an integration to a 3rd party service, follow the steps below.

1. Login to your Cyara Portal and click on the Tools > Integrations menu in the top toolbar.
2. Here you will see a list of your previously configured integrations
   
3. Click on New Integration to start building.
4. Select the Type from the available drop down menu.
5. Integrations are split into three main Types (Accelerators, Incidents and Log Aggregators). Each integration type will offer different fields for mapping Cyara platform data to. For more information on the differences between integration types, read the Integration Types article.
6. Enter a Name for the integration and select an Impersonation User if needed (Currently only the Splunk integration requires an Impersonation User).
7. For most integrations you will be prompted to enter an API URL of the service that you're integrating with, as well as some login credentials to authenticate the REST requests that Integration Hub will make.
8. In the Field Selection section, you can map Cyara data to fields within the 3rd party application. For standard integration types such as Jira, ServiceNow and Splunk, Cyara has pre-configured the field types and they are available in the dropdown menu as follows.
   
9. Alternatively you can create a custom field mapping using the New Custom Field button. When entering a new custom field you will be prompted for the following information.
   1. A Field Name. This is the property name to be sent to the external service.
   2. A Display Name. This is the name for the field shown when a user creates an incident.
   3. A Field Type. Select the appropriate type from the available dropdown. A Choice for multiple fixed values. A Single or Multiple line text input or use Lookup for values that are built using an API call.
   4. Field Value. This can either be a constant or a template for the integration to send to the external service. For a Choice field enter these as comma separated values, the first value will be used as the default.
   5. The final checkboxes allow you to configure field properties such as Required, Read-Only and Overridable.
10. Enter each field that requires mapping and click Save Details.