Before
An analyst likely reviewed the incoming security alert, copied its name and description, opened the issue-tracking system, selected the appropriate project and task type, and created the ticket manually. Each alert required a separate handoff and manual re-entry before it became trackable work.
How it works
- Receive a security alert from Google Alert Center.
- Use the alert name and description to populate the Jira task summary and content.
- Create a Task in the MDE project for follow-up.
Workflow details
- Alert intake: The workflow receives a security alert from Google Alert Center, including information such as the alert name, description, severity, timestamp, source, user, IP address, location, and device.
- Field selection: It uses the alert name as the Jira issue summary and the alert description as the issue content, preserving the primary context needed to understand why the ticket was created.
- Issue classification: The workflow creates the ticket in the MDE project and assigns it the Task issue type.
- Automated handoff: A Jira issue is created automatically through the configured Jira connection after the alert is received, without requiring an analyst to re-enter the alert information.
- Operational result: Each qualifying alert produces a trackable Jira task for follow-up, while the workflow stops if the issue-creation action fails.
What changed
Security alerts now become Jira tasks automatically as soon as they are received, with the key alert name and description transferred into the ticket. The manual ticket-creation handoff is removed, while any subsequent investigation or follow-up remains with the responsible team.
Work removed
Reviewing each alert for ticket creation, copying the alert name and description, opening the issue tracker, selecting the MDE project and Task type, and manually submitting the ticket.
Expected outcome
At least one manual ticket-creation sequence is removed for each processed alert, providing consistent Jira task creation for incoming security events.
