Prisma & Sentinel Integration.

[VBisht2]

We are in situation where we wanted to have a Prisma Console integration with Sentinel but not through the MS Native Tool (MS Connector).

Wanted to see the possibility of the if at prisma end we hv intelligence to send not all the alerts but on entitled/legitimated to turn into incident ..then these incidents can be send to Syslog….then at Syslog can connect to A log collector IP as destination and from there it can go to Sentinel to process further.

So the communication like

Prisma >>Alerts>>Incident >>Syslog>>>>>>>Log Collector >>Sentinel.

** Prisma to run intelligence to send only those alerts to Syslog are entitled to convert into Incidents

**Syslog to able to connect IP Address of Log Collector.

[MRehan]

Thanks for the message. Few points

1) Why do you want to take the syslog route to Sentinel when eventually Prisma Cloud can send alerts to Sentinel directly?
2) Could you please explain converting alerts into incidents? I believe when alerts hit the sentinel, Sentinel can do anything with these alerts. Sentinel is SIEM tool, it can remove the duplicates,  create incidents etc. 

By the way, there is another option to integrate Prisma Cloud with Sentinel apart from the connector. This is done through Azure Logic Apps.  In connector setup,  Sentinel pulls the alerts from Prisma while in Logic Apps setup, Prisma cloud pushes the alerts to Azure Logic Apps through webhook and webhook forward these alerts to Sentinel.

https://github.com/Azure/Azure-Sentinel/tree/master/Playbooks/Ingest-Prisma

In AWS setup, Prisma can send alerts to SQS and SQS can send the alerts to syslog but not sure if Azure Service Bus supports this.