This workflow template guides users through addressing Orca Security alerts for AWS S3 buckets with versioning disabled. It begins by retrieving tag details to identify the bucket owner, then reaches out via Slack for consent to enable bucket versioning. Upon approval, versioning is enabled and a verification scan initiated. If consent is denied or unresponsive, it captures a reason and generates a follow-up Jira ticket, updating the alert details accordingly. The process enhances Cloud Security Posture Management (CSPM) by ensuring S3 data protection compliance.
Trigger
Orca
Use Cases
CSPM
Workflow Breakdown
Retrieve details on tags on the bucket
Reach out to the bucket owner or Slack channel, notify them about the issue
Suggest to remediate by enabling versioning on the bucket
Apply the 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 remediation details on the Orca Security alert provided
Vendors
AWS, Slack, Utils, Orca, Jira Cloud
Workflow Output
Success/Failure - Jira Ticket
Tips
Setup Jira and Slack channel variables in the first variables step