I figured that someone may need this. This snippet is a workflow that lives off of a specific Surface Command query that gets all AWS Inspector issues, aligns them to their hosts, and syncs tickets in Jira. It will automatically remove remediated assets from tickets and put a comment when it does to leave a trail. To ensure that new assets with issues that already have a ticket also have a way to measure SLAs via the ticket dates, if an existing issue is missing an asset, a new ticket is created for that asset. It will also assume that if a query comes back with issues missing, then the jira issue that still exists is likely remediated and will transition it to a closed status with a comment.
It’s a very niche use case, but also a great starting point for using Surface Command queries to make Jira tickets.
), you will not be able to unless you edit the file first to update the REPLACE_WITH_xxxx connection IDs. You can just use any valid random GUID id value and just let the Rapid7 UI provide the interface to update the connections.