Shodan - Enrich Incident IPs and Domain Names

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

↑ Back to Content Index

When a new sentinel incident is created, this playbook gets triggered and fetches geo location and running services details for IP addresses and domain names from Shodan.io.

Attribute Value
Type Playbook
Solution Shodan
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 4
ShodanCustomConnector Custom 1 2
Action parameters (URLs, paths, function IDs)

azuresentinel (Managed)

Action Method Endpoint Other
Add_comment_to_incident_(V3) post /Incidents/Comment —
Add_comment_to_incident_(V3)_2 post /Incidents/Comment —
Entities_-_Get_DNS post /entities/dnsresolution —
Entities_-_Get_IPs post /entities/ip —

ShodanCustomConnector (Custom)

Action Method Endpoint Other
ResolveDomainName get /dns/resolve —
GetServiceDetailsForIP get /shodan/host/@{encodeURIComponent(items('For_each_IP_Address'))} —

Additional Documentation

📄 Source: ShodanPlaybooks/Shodan-EnrichIPAndDomain/readme.md

Shodan-EnrichIPAndDomain

Summary

The playbook can be triggered manually or automatically from an Incident context to fetch geo location and running services details from Shodan.io of IP addresses and Domain Names. This playbook performs following actions:

  1. Get the domain names and IP addresses from incident.
  2. Resolve domain names to IP addresses.
  3. Query Shodan.io to fetch geo location and running services details for all the IP addresses.
  4. Collect all the details and format as table.
  5. Add the collected details as comment to the incident.



Prerequisites

  1. Prior to the deployment of this playbook, Shodan Logic App Custom Connector needs to be deployed under the same subscription.
  2. Refer to Shodan Logic App Custom Connector documentation for deployment instructions.

Deployment instructions

  1. To deploy the Playbook, click the Deploy to Azure button. This will launch the ARM Template deployment wizard.
  2. Fill in the required parameters:
    • Playbook Name
    • Custom Connector Name

Deploy to Azure Deploy to Azure

Post-Deployment instructions

a. Authorize connections

Once deployment is complete, authorize each connection.

  1. Select the Microsoft Sentinel connection resource
  2. Click Edit API connection blade
  3. Click Authorize/Provide credentials
  4. Click Save
  5. Repeat these steps for other connections

b. Configurations in Sentinel

  1. In Microsoft Sentinel, analytical rules should be configured to trigger an incident that contains IP Addresses and/or Domain Names. In the Entity mapping section of the analytics rule creation workflow, IP Address should be mapped to Address identifier of the IP entity type, and Domain Name should be mapped to DomainName identifier of the Domain entity type.

    Check the documentation to learn more about mapping entities.

  2. Configure the automation rules to trigger the playbook. Check the documentation to learn more about automation rules.

c. Assign Playbook Microsoft Sentinel Responder Role

  1. Select the Playbook (Logic App) resource
  2. Click on Identity Blade
  3. Choose System assigned tab
  4. Click on Azure role assignments
  5. Click on Add role assignments
  6. Select Scope - Resource group
  7. Select Subscription - where Playbook has been created
  8. Select Resource group - where Playbook has been created
  9. Select Role - Microsoft Sentinel Responder
  10. Click Save

References

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

↑ Back to Playbooks · Back to Shodan