Originating Case Decision Sync

Originating Case Decision Sync

Originating Case Decision Sync

This automation returns an investigation's requested status, disposition, and comment to the originating security event system. It updates or closes the original case when applicable and reports when a hunt has no originating case to update.

Case routing

Investigation

Incident Response

Integration

Trigger

The flow is triggered by a case update containing the source system, case identifier, requested status, disposition, and comment.

Outcome

It produces the update result for the originating case or returns a skipped status when the investigation has no source case.

Trigger

The flow is triggered by a case update containing the source system, case identifier, requested status, disposition, and comment.

Outcome

It produces the update result for the originating case or returns a skipped status when the investigation has no source case.

Before

An analyst had to locate the original notable event, offense, or incident in the relevant security console after completing an investigation. They then had to copy the decision, comment, and closure information into the source system using its specific workflow.

How it works

  1. Receive the investigation decision and identify the originating source and case.
  2. Validate the source and translate the requested status and disposition into the appropriate case update.
  3. Add the note or comment, close the case when requested, and return the result or a no-case outcome.

Workflow details

  • Receive and prepare: The flow accepts the originating system, case identifier, requested status, disposition, and comment, then translates the decision into the format required by the selected branch.
  • Route to the source: It validates whether the source is Splunk, QRadar, Sentinel, or a hunt without a source case. Unsupported sources fail clearly, while hunt results are skipped without making an external update.
  • Apply the decision: For Splunk, the notable event is marked in progress or closed with the mapped disposition and comment. For QRadar, the flow adds a note and closes the offense when requested. For Sentinel, it rereads the incident, adds the comment, and preserves existing incident fields while applying the requested status and closure classification.
  • Return the outcome: The flow returns the case identifier, source, and resulting status, including a skipped result when no originating SIEM case exists.

What changed

The originating case is updated directly from the investigation decision, with source-specific status, note, comment, and closure handling performed automatically; unsupported sources fail clearly and cases without an origin are reported as skipped.

Work removed

Finding the original SIEM case, switching to the source console, copying the investigation comment, entering the disposition, and manually closing the case when required.

Expected outcome

One recurring case lookup and one manual SIEM update can be removed for each supported investigation, helping prevent cases from remaining open solely because the decision was recorded elsewhere.

Related flows

Related flows

Explore more workflows with similar topics or tools.

Automated Security Alert Enrichment

This automation runs a complex query against Log Analytics to retrieve Azure Sentinel alerts or other security logs, converts the returned data into JSON, and uses it to update security alerts with additional information. It replaces a manual search-and-update process with a consistent enrichment workflow.

This automation runs a complex query against Log Analytics to retrieve Azure Sentinel alerts or other security logs, converts the returned data into JSON, and uses it to update security alerts with additional information. It replaces a manual search-and-update process with a consistent enrichment workflow.

Explore use case

Explore use case

Automated Notable Event Status Updates

This automation receives notable security alerts, locates the corresponding notable event through a controlled search process, and updates its status with a comment in the security platform. It also monitors search completion and emails an administrator when the search fails.

This automation receives notable security alerts, locates the corresponding notable event through a controlled search process, and updates its status with a comment in the security platform. It also monitors search completion and emails an administrator when the search fails.

Explore use case

Explore use case

Single-Session User Activity Investigation Reports

This automation investigates the actions performed during a single Azure Active Directory session after a suspicious event. It retrieves the relevant audit history, organizes key activity details into a Workbook, and shares the completed report back with the investigating team.

This automation investigates the actions performed during a single Azure Active Directory session after a suspicious event. It retrieves the relevant audit history, organizes key activity details into a Workbook, and shares the completed report back with the investigating team.

Explore use case

Explore use case

Less busywork. More possibility.

Let your agents handle the routine. Make room for what comes next.

Automation intelligence, delivered monthly.

Product releases, automation playbooks, and security research โ€” straight to your inbox. No spam, unsubscribe anytime.

ยฉ 2026 Mindflow โ€” All rights reserved.

SOC 2 Type II
ISO 27001
GDPR
France 2030
Bpifrance
รŽle-de-France

Less busywork. More possibility.

Let your agents handle the routine. Make room for what comes next.

Automation intelligence, delivered monthly.

Product releases, automation playbooks, and security research โ€” straight to your inbox. No spam, unsubscribe anytime.

ยฉ 2026 Mindflow โ€” All rights reserved.

SOC 2 Type II
ISO 27001
GDPR
France 2030
Bpifrance
รŽle-de-France

Automation intelligence, delivered monthly.

Product releases, automation playbooks, and security research โ€” straight to your inbox. No spam, unsubscribe anytime.

ยฉ 2026 Mindflow โ€” All rights reserved.

SOC 2 Type II
ISO 27001
GDPR
France 2030
Bpifrance
รŽle-de-France
To embed a website or widget, add it to the properties panel.