This Torq workflow template serves the business need for maintaining security compliance by automating the process of enabling encryption on AWS S3 buckets upon receiving an alert from Orca about disabled encryption. It identifies the bucket owner using tags, notifies them via Slack, and requests authorization to enable AES256 encryption. If approved, it applies the changes and triggers a verification scan. Rejection leads to creating a Jira ticket for follow-up, ensuring consistent security posture and regulatory compliance.
Trigger
Orca
Use Cases
CSPM
Workflow Breakdown
Retrieve tags on the AWS bucket
Reach out to the bucket owner or Slack channel, notify them about the issue
Suggest to remediate by enabling default AES256 encryption on the bucket
Apply changes if the user approves and kick off a verification scan
If user or channel rejects, collect a reason and open a follow-up Jira ticket
Update comments on the Orca security alert id that was provided
Vendors
AWS, Slack, Utils, Orca, Jira Cloud
Workflow Output
Success/Failure via Jira issues and Slack messages
Tips
Setup the integrations and Jira details in the first Set Workflow Variables step