Skip navigation

Direct Integration of TSVM and TAO for incident and change management in ticketing tools like service-now, remedy,etc...

score 115
You have not voted. On Roadmap

Hello Team,

 

There are multiple open vulnerabilities open on multiple target servers, we can follow below process to close that vulnerabilities:-

 

1 Import vulnerabilities

2 auto-map assets and vulnerabilities

3 create remediation job

4 deploy remediation job

 

but whenever we deploy any patches to close vulnerabilities we required proper approval for that and to track this incident and change comes into the picture.

 

There are different different ticketing solutions present in customers locations and True-sight atrium Orchestrator has capabilities to integrate with multiple ticketing tool

 

So I am proposing below solution:-

 

1 Import vulnerabilities

2 auto-map assets and vulnerabilities

3 create remediation job  --> TSVM will send details to TAO ( Job name, Target servers, open Vulnerabilities) using SNMP trap or through direct adapter.

4 deploy remediation job  --> TSVM will send remediation job details to TAO using SNMP trap or through direct adapter.

 

TAO will create incident/ change in ticking tool like service now using the data getting in 3rd step.

TAO will close the same incident/ change in ticking tool like service now using the data getting in 4th step.

 

I hope I have explain complete Scenario, Let me know if you have any questions.

 

Note:- Above solution is already present only for remedy and it required below integrations:-

1 TSA <-> Remedy,

2 TSA <-> TAO,

3 TSVM <-> TAO

 

If above solution is successfully provided the we required only single integration of TSVM <-> TAO and it will work for all ticketing tools.

 

Regards,

Akash Vekhande

 

 

 

  1. C Atrium Orchestrator Content 20.15

 

  1. C Atrium Orchestrator Content 20.15

Comments

Vote history