Mapping DLP incident status with Netskope
The incident status mapping section enables the users to provide the mappings between the DLP Incident status in ServiceNow and Netskope Object status.
시작하기 전에
The mapping will be used when ingesting any DLP incident from Netskope to ServiceNow as well as syncing any state change of DLP incident in ServiceNow back to Netskope.
Synchronize the status of the DLP incidents ingested on the ServiceNow with the DLP incident of Netskope. Map the ServiceNow Incident Status field with the Netskope Object Status field.
Role required: sn_dlir.admin
이 태스크 정보
You need to create a one-to-one incident status mapping of Netskope and ServiceNow status.
프로시저
-
Map the DLP Incident Status with Netskope Object Status (Duplicate Netskope state can also be mapped).
The status sync from ServiceNow to Netskope will be disabled if you don’t create a mapping record.중요사항:You need to map all the Netskope object statuses to all ServiceNow statuses. Select the source in order to sync DLP Incident status back to Netskope object.The following information and alert messages are displayed when you map the incident status, review the messages and proceed further.주:
- Status mapping is case-sensitive.
- Provide the internal name of the default status (For example: new, in_progress, closed) or exact name of status in case of custom state for the Netskope Object Status fields.
경고:Do not modify the status on the Netskope platform after completing the status mapping configuration from here.표 1. Netskope DLP Incident Status Mapping Field Description Name Name of the mapping record. Source The configured Netskope Endpoint source from where you want to sync the incident status. DLP Incident Status Indicates the list of DLP incidents status. Netskope Object Status Indicates the list of Netskope object status.
결과
After successfully creating the record for status mapping, whenever there is an update on ServiceNow DLP incident’s state then it will automatically reflect it on Netskope side as per the mapping.