enrich alert using zap internal event with request /response fetching

[mohamedkhalil rouissi]

Is it possible that when the event generator raises an alert, we retrieve the source message ID, read its metadata, and then send a webhook to another API containing the alert metadata along with the related request and response?

[Simon Bennetts]

Yes, you will be able to do this with an extender script.

We have an example which listens for events from one specific publisher:

https://github.com/zaproxy/community-scripts/blob/main/extender/ZAP%20onEvent%20Handler.js

You should be able to change that to meet your requirements.

If you're not sure of how to do what you want then explain what you are looking for in detail.

Cheers,

Simon

[mohamedkhalil rouissi]

correct if am wrong if am going to send alert from zap to server using webhook first i should catch the event fir alert added then take the messagesourceid to fetch the request/response and should be done only if theres href.add event ? 

--
ZAP by Checkmarx: https://www.zaproxy.org/
---
You received this message because you are subscribed to the Google Groups "ZAP User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zaproxy-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/zaproxy-users/e22b0629-49e8-4b72-b6a2-782c07b2671en%40googlegroups.com.

[mohamedkhalil rouissi]

using getHistoryReference()

[Simon Bennetts]

You can just listen for an "alert.added" event: https://github.com/zaproxy/zaproxy/blob/main/zap/src/main/java/org/zaproxy/zap/extension/alert/AlertEventPublisher.java

You can then get the history reference as per https://github.com/zaproxy/community-scripts/blob/main/standalone/Loop%20through%20history%20table.js

It should be available at that stage, so no need to listen for the "href.added" event.

Cheers,

Simon