Connecting Neurons for SOM to ADO

perform the following procedures to connect to your ado instance credentials and initial setup log into as an administrator and open the ticket sharing and synchronization (tss) workspace select new ticket sharing and synchronization enter the integration name (example ado) select incident from the business object name menu select enabled from the status menu in the service name field, find and select ado save four new tabs now appear after the credentials tab filters , field mapping , data mapping , and data rules the credentials tab now contains three additional fields a service url relevant ado instance url (example https //dev azure com/yourcompany ) b username jira account username (example adousername\@company com ) c auth token token provided by ado (example token1232323232323) save filters tab in the filters tab, click new connector service filters in the new connector service filters dialog, select summary from the incident/ivnt securityincident field name menu in the incident/ivnt securityincident field name field, enter trojan depending on environment and criteria, choosing the security incident’s category field (with, for example “data breach” as field value) might be more appropriate or practical operation with next filter determines how filtering works with other filters select the appropriate operator (and or or) (example add a “ransomware detected” filter) when all appropriate filters have been added, save field mapping tab in the field mapping tab, click new connector service field mapping a in the new connector service field mapping dialog, select summary for the incident/ivnt securityincident field name b enter system title for the ado field name c enter system title for the service field depth d select poll this field for any changes e save click new connector service field mapping a in the new connector service field mapping dialog, select status for the incident/ivnt securityincident field name b enter system state for the ado field name this field is in lowercase in jira c enter system state for the service field depth d select poll this field for any changes e save click new connector service field mapping a in the new connector service field mapping dialog, select description for the incident/ivnt securityincident field name b enter system description for the ado field name c enter system description for the service field depth d select poll this field for any changes e save click new connector service field mapping a in the new connector service field mapping dialog, select provide default value (to switch field mapping from ado to ism) b enter project for the ado field name c enter the name of the ado project for the default value d save data mapping tab in the data mapping tab, click new connector service data mapping a in the new connector service field mapping dialog, select incident/ivnt securityincident)=status ado=system state for the connector service field b enter resolved for the incident/ivnt securityincident field value c enter resolved for the ado field value d save click new connector service data mapping a select incident/ivnt securityincident=status ado=system state for the connector service field b enter logged for the incident/ivnt securityincident field value c enter committed for the ado field value d save click new connector service data mapping a select iincident/ivnt securityincident=status ado=system state for the connector service field b enter active for the incident/ivnt securityincident field value c enter new for the ado field value d save click new connector service data mapping a select ncident/ivnt securityincident=status ado=system state for the connector service field b enter closed for the incident/ivnt securityincident field value c enter done for the ado field value d save data rules tab in the data rules tab, select new connector service field constraint a in the field mapping value menu, select incident/ivnt securityincident=status ado=system state\[resolved,resolved] b in the business object field name menu, select causecode c enter vulnerability for the business object field value this is an example; you need to match whatever cause codes you have set up in your incident or security incident objects d save click new connector service field constraint a in the field mapping value menu, select incident/ivnt securityincident=status ado=system state\[resolved,resolved] b in the business object field name menu, select resolution c enter data rules resolution for the business object field value this is an example; you need to match whatever resolution values you have set up in your incident or security incident objects d save additional operations click the additional operations tab if the tab is not visible, you may have to refresh or go to list view and select your tss again select the following options push comments added in heat to ado pull comments added in ado to heat push attachments added in heat to ado pull attachments added in ado to heat in the comment business object menu, select journal#notes save comment field mapping click the comment field mapping tab if the tab is not visible, you may have to refresh or go to list view and select your tss again click new comment field mapping a in the incident/ivnt securityincident field name menu, select notes b enter description for the ado field name c save click new comment field mapping a in the incident field name menu, select subject b enter summary for the jira field name c save