Explain with AI for Signature Triggered Events

We have played with the new feature "Explain with AI". We have seen that in case the block is triggered by a signature ( injection, XSS, etc) it is not providing the detection context ( where it was see , what specific path triggered it, etc). The details are very vague and not able to fingerpoint the exact string of the detection.

This will be really useful to understand the blocks and work on them when they are FP.

Thanks,


  • Monica Popescu
  • Sep 30 2024
  • Attach files