Incident Data Publishing
- 11 Sep 2023
- 1 Minute to read
- Print
- DarkLight
- PDF
Incident Data Publishing
- Updated on 11 Sep 2023
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
About this Article
This article provides information about the usage of Incident Data Publishing functionality.
Pre-Requisite
- VSP must be installed and an application must be provisioned
Procure Sample Customer
- Copy the Virsec provided Sample Consumer IncidentConsumer.jar from Artifactory from the directory <VSP_Release_Version>/utils/containers onto the CMS VM
Enable Incident Data Publishing
This feature enables Incident data publishing to the topic: ZS-INCIDENT-PUBLISH located on the CMS container/pod
A super admin can enable Incident data publishing as described below
- Navigate to Administration > Configurations in the left navigation pane and expand Incident Data Publishing
- Turn ON Enable/Disable Incident Data Publishing and select the data format as JSON or XML. Click SAVE
Sample Application Execution
- On the container/pod where the sample application is copied, execute the below command to set up listener to the topic: ZS-INCIDENT-PUBLISH
java -jar IncidentConsumer.jar <CMS_IP_Address>:9092 java -jar IncidentConsumer.jar <CMS_IP_Address>:9092 >> <Log_File_Name> # To redirect output to a logfile
- The received Incident information is displayed on the CMS
Disable Incident Data Publishing
- Navigate to Administration > Configurations in the left navigation pane and expand Incident Data Publishing
- Turn OFF Enable/Disable Incident Data Publishing. Click SAVE
Was this article helpful?