Hi Craig,
could you please guide us where to set permission of the Arcsight service running/executing the script.
The same has been getting executed when we are using actual eventID in place of "$eventId" in parameter section.
EX:
/usr/bin/python2.7 /opt/resilient/arcsight/alert/resilient_arcsight_alert.py --type event --id "254253625" : Getting executed successfully and also events are getting generated on Resilient
/usr/bin/python2.7 /opt/resilient/arcsight/alert/resilient_arcsight_alert.py --type event --id "$eventId" : No events are getting generated on Resilient
Please suggest if we have missed something
--
Thanks,
Ravi
------------------------------
Fms SOC
------------------------------
Original Message:
Sent: 02-05-2019 02:11 PM
From: CRAIG ROBERTS
Subject: Arcsight Integration with Resilient
This can sometimes happen due to the permissions of the Arcsight service running/executing the script.
Check the scripts permissions and owner matches your arcsight service (or the arcsight user is able to execute them).
Original Message:
Sent: 02-05-2019 02:01 AM
From: Fms SOC
Subject: Arcsight Integration with Resilient
Hi Team,
Greetings for the day!
We are in process of integration Arcsight with resilient. Till now, we are able to send test events (Using EventID) successfully manually (Using : /usr/bin/python2.7 /opt/resilient/arcsight/alert/resilient_arcsight_alert.py --type event --id "$eventId" OR python resilient_arcsight_alert.py --type event --id <event_id> --dry-run).
1. But unfortunately the same has not been getting executed using Arcsight Console Rule "Action". I mean incidents are not getting forwarded automatically using rule action.
Please let me know if anyone faced the same problem, your any suggestions would be a great help to us.
--
Thanks
------------------------------
Fms SOC
Ravi Sharma
------------------------------