Inte-Bonding ServiceNow Ahlsell > OCD added service Managed SIEM

During the e-bonding between Ahlsell ServiceNow and OCD ServiceNow, one service got lost in space and therefor are not part of the e-bonding.

We would like to add that service to the e-bonding so the process between Ahlsell and OCD works seamless.

Name of the service: “Managed Threat Detection [Log] - Managed SIEM”

Example from Jean-Louis from OCD.

serviceName parameter is sent by customer when they create a ticket on OCD side to target a specific contract, see example payload:

{

"id":"INC0052155",

"sysId":"06f8a95997434a50c903f80de053af89",

"shortDescription":"Test incident Demo Please ignore",

"description":"Test incident Demo",

"state":"Pending OCD",

"operationDate":"2024-06-26 12:27:04",

"serviceName":"Managed Threat Detection [XDR]",

"impact":"3",

"urgency":"3",

"comments":""

}

To meet the new requirement on OCD side, we have introduced an additionalserviceName value to the enumerated list (attached latest version of the swagger file).

ServiceName list was

ServiceName list is now

To raise a ticket on Managed SIEM contract, customer should send the value "Managed Threat Detection [Log] - Managed SIEM" in the serviceName parameter.

Next step for customer is to assess what are the required changes on their system to be able to send this information with the creation payload.

Developments are ready on OCD TEST env, they can send creation requests there when their TEST env is ready as well.

Kind regards,

Jean-Louis