CiscoUmbrella-BlockDomain

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

↑ Back to Content Index

This playbook showcases an example of triggering an incident within a targeted Teams channel and opening up a ticket within Service Now. Additionally The playbook will also list playbooks that can be initiated from teams using an adaptive card and callbacks that will take action upon certain entities identified in the incident.

Attribute Value
Type Playbook
Solution CiscoUmbrella
Source View on GitHub

Additional Documentation

📄 Source: CiscoUmbrellaPlaybooks/CiscoUmbrella-BlockDomain/readme.md

Summary

When a new sentinel incident is created, this playbook gets triggered and performs the following actions

  1. Obtains domains from URL entities in the incident.
  2. Optionally adds these domains to a customer's domain lists using Cisco Cloud Security Enforcement API.
  3. Adds comment to incident with information about posted domains.


Prerequisites

  1. Prior to the deployment of this playbook, Cisco Cloud Security Enforcement Connector needs to be deployed under the same subscription.
  2. Obtain Cisco Cloud Security API credentials. Refer to Cisco Cloud Security Enforcement Custom Connector documentation.

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: Enter the playbook name here

Deploy to Azure Deploy to Azure

Post-Deployment instructions

a. Authorize connections

Once deployment is complete, authorize each connection.

  1. Click the Microsoft Sentinel connection resource
  2. Click edit API connection
  3. Click Authorize
  4. Sign in
  5. Click Save
  6. Repeat steps for Cisco Cloud Security Enforcement connector API Connection. Provide your key and the secret for authorizing.

b. Configurations in Sentinel

  1. In Microsoft sentinel, analytical rules should be configured to trigger an incident with a malicious URL. In the Entity mapping section of the analytics rule creation workflow, malicious URL should be mapped to Url identifier of the URL entity type. Check the documentation to learn more about mapping entities.
  2. Configure the automation rules to trigger the playbook.

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

↑ Back to Playbooks · Back to CiscoUmbrella