Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊
This playbook search for indicators in Minemeld related to the entities(IP, filehash, URL) gathered from Sentinel incident. If the search result is positive a comment stating the indicator is already present or it creates a new indicator in Minemeld.
| Attribute | Value |
|---|---|
| Type | Playbook |
| Solution | Minemeld |
| Source | View on GitHub |
📄 Source: MinemeldPlaybooks/Minemeld-CreateIndicator/readme.md
## Summary When a new Microsoft Sentinel incident is created, this playbook gets triggered and performs below actions 1. Searches for the matching indicator info of Entities (IP Address, FileHash, URL) in Minemeld 2. If indicators are not found, this playbook adds the new indicators to Minemeld Local database (Separate indicators for each IP Address, FileHash, URL that are present in Sentinel incident)
requisites 1. Minemeld Custom Connector needs to be deployed prior to the deployment of this playbook under the same subscription. 2. Basic authentication of user and password is required for accessing Minemeld API.
Deploy the playbook by clicking on "Deploy to Azure" button. This will take you to deploying an ARM Template wizard.
Fill in the required parameters:
Once deployment is complete, you will need to 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 Minemeld Api Connection (For authorizing the Minemeld GraphQL API connection, user and password to be provided)
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊