Liongard Ideas Portal

Submit and upvote ideas to make Liongard better. You get 20 votes so vote wisely. 🙂

To learn more about our Ideas Portal, check out our FAQs.
To schedule a feedback session with a member of the Liongard Research Team, click here.

See what we've shipped by clicking here!

Updating Roarbot Comments on Change Alerts

"For alerts on change notifications, the process is we detect a change, review it then close the ticket. Now, the next time a change is detected, it's reopening the ticket but the only update is "Roar has determined the finding has not been remediated...". For this to work properly it needs to include the actual change data also."

The expected behavior is that Roarbot is smart enough to differentiate between standard alerts (i.e. license expirations) and change alerts (i.e. public facing exposed ports list has changed). For change alerts, it doesn't make sense for Roarbot to comment that the issue has not been remediated. Instead, we'd like to see Roarbot comment on a new change, and include the change in the comment.

Submitted on behalf of Steve from RUN.

  • Guest
  • Jul 24 2020
  • Shipped
Last Reviewed Date 2020-09-08
  • Sep 18, 2020

    Admin response

    Hi Everyone,

    Our latest release includes an improvement to our alerts where if a change alert is re-opened, Liongard is now including a Roarbot comment with the Change Detection that causes that alert to re-open. Thanks everyone for your feedback and votes on this idea!

  • Attach files
  • Jessie Schoepflin commented
    27 Jul, 2020 04:47pm

    I agree. More info into the reopening of alerts would be very helpful.

  • Steve King commented
    24 Jul, 2020 06:28pm

    This looks great, and will help make Change Notification alerts much more useful!