Group-IB TI - Enrich incident with WHOIS data

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Content Index


Triggered by a Microsoft Sentinel incident. Runs a Group-IB WHOIS lookup for every IP and domain entity on the incident and posts registration and ownership details back as incident comments.

Attribute Value
Type Playbook
Solution Group-IB
Source View on GitHub

Logic App Connectors

This playbook uses 2 Logic App connectors / built-in actions:

Connector / Action Type Connections Actions
azuresentinel Managed 1 1
http Built-in 0 4
Action parameters (URLs, paths, function IDs)

azuresentinel (Managed)

Action Method Endpoint Other
Add_comment_to_incident post /Incidents/Comment —

http (Built-in)

Action Method Endpoint Other
WHOIS_IP GET https://tap.group-ib.com/api/v2/utils/graph/ip —
TI_Lookup_IP POST [variables('WorkspaceQueryEndpoint')] —
WHOIS_Domain GET https://tap.group-ib.com/api/v2/utils/graph/domain —
TI_Lookup_Domain POST [variables('WorkspaceQueryEndpoint')] —

Additional Documentation

📄 Source: GIBTIA_Enrich_WHOIS/readme.md

Triggered by a Microsoft Sentinel incident. Runs a Group-IB WHOIS lookup for every IP and domain entity on the incident and posts registration and ownership details back as incident comments.

Quick Deployment

Deploy to Azure

Prerequisites

Entity types: ip, dns

Post-deployment

  1. Authorize the Microsoft Sentinel API connection.
  2. Assign the Microsoft Sentinel Responder role to the playbook's managed identity so it can add incident comments.
  3. Set the GIBUsername and GIBApiKey parameters.
  4. Attach the playbook to an automation rule so it runs when an incident is created.

Part of the Group-IB Threat Intelligence integration. See the Playbooks readme for the full catalog, architecture and deployment order.


Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Playbooks · Back to Group-IB