Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1383980%22%20slang%3D%22en-US%22%3EUsing%20Azure%20Playbooks%20to%20import%20text-based%20threat%20indicators%20to%20Azure%20Sentinel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1383980%22%20slang%3D%22en-US%22%3E%3CP%3E%3CFONT%20size%3D%226%22%3EIntroduction%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EAzure%20Sentinel%20provides%20two%20built%20in%20data%20connectors%20for%20importing%20threat%20intelligence%2C%20the%20%3CEM%3EThreat%20Intelligence%20%E2%80%93%20TAXII%3C%2FEM%3E%20data%20connector%2C%20and%20the%20%3CEM%3EThreat%20Intelligence%20%E2%80%93%20Platforms%3C%2FEM%3E%20data%20connector.%26nbsp%3BThese%20data%20connectors%20are%20suitable%20for%20most%20use%20cases%20%E2%80%93%20as%20explained%20in%20our%20previous%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fazure-sentinel%2Fbring-your-threat-intelligence-to-azure-sentinel%2Fba-p%2F1167546%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Edetailed%20blog%3C%2FA%3E.%20However%2C%20some%20open%20source%20threat%20intelligence%20is%20shared%20as%20text-based%20files%20which%20cannot%20be%20accessed%20directly%20from%20these%20data%20connectors.%20This%20blog%20describes%20how%20to%20use%20Azure%20Sentinel%20Playbooks%20to%20obtain%20text-based%20threat%20indicators%20from%20an%20online%20source%2C%20and%20import%20them%20directly%20into%20the%20%3CEM%3EThreatIntelligenceIndicator%3C%2FEM%3E%20table%20where%20they%20can%20be%20used%20by%20all%20the%20built-in%20Sentinel%20analytics%20templates%20to%20generate%20security%20incidents.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20Playbooks%20described%20in%20this%20post%20were%20created%20to%20allow%20Azure%20Sentinel%20customers%20to%20import%20Microsoft%E2%80%99s%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fsecurity%2Fblog%2F2020%2F05%2F14%2Fopen-sourcing-covid-threat-intelligence%2F%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ECOVID-19%20related%20threat%20indicators%3C%2FA%3E%20published%20on%20GitHub.%20However%2C%20these%20Playbooks%20can%20easily%20be%20modified%20to%20point%20to%20any%20other%20source%20of%20a%20text-based%20indicator%20feed.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%226%22%3EPlaybook%20architecture%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EThese%20Azure%20Sentinel%20Playbooks%20work%20in%20tandem%20to%20read%20indicators%20from%20a%20source%20location%20and%20import%20the%20indicators%20to%20the%20ThreatIntelligenceIndicator%20table%20in%20Logs.%20Let%E2%80%99s%20take%20a%20closer%20look%20at%20the%20functionality%20of%20each%20Playbook.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3EPlaybook%201%20(C19IndicatorProcessor)%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EC19IndicatorProcessor%20Playbook%20performs%20the%20following%20steps%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ETriggered%20on%20a%20defined%20schedule%3C%2FLI%3E%0A%3CLI%3EReads%20the%20indicators%20from%20GitHub%3C%2FLI%3E%0A%3CLI%3ETransforms%20the%20indicators%20from%20the%20text-based%20source%20to%20the%20appropriate%20tiIndicator%20JSON%20format%3C%2FLI%3E%0A%3CLI%3EUses%20the%20Batch%20action%20to%20send%20the%20indicators%20to%20the%20second%20Playbook%20(C19ImportToSentinel)%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CDIV%20id%3D%22tinyMceEditorJason%20Wescott_0%22%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Figure1.jpg%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F191389i0A3E079F2182228B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Figure1.jpg%22%20alt%3D%22Figure1.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3EPlaybook%202%20(C19ImportToSentinel)%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EC19ImportToSentinel%20Playbook%20performs%20the%20following%20steps%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EBegins%20with%20a%20Batch%20Messages%20trigger%20to%20receive%20indicators%20sent%20by%20the%20first%20Playbook%20(C19IndiatorProcessor)%20and%20groups%20the%20indicators%20into%20batches%20of%2010%3C%2FLI%3E%0A%3CLI%3ESubmits%20each%20batch%20of%20indicators%20to%20Azure%20Sentinel%20using%20the%20Microsoft%20Graph%20Security%20Logic%20App%20connector%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22Figure2.jpg%22%20style%3D%22width%3A%20630px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F191140iA76C8D2E33F153B7%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Figure2.jpg%22%20alt%3D%22Figure2.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CDIV%20id%3D%22tinyMceEditorJason%20Wescott_1%22%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CP%3E%3CFONT%20size%3D%226%22%3EDeploy%20the%20Playbooks%20to%20Azure%20Sentinel%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EThe%20Playbook%20templates%20can%20be%20downloaded%20from%20GitHub%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FAzure%2FAzure-Sentinel%2Ftree%2Fmaster%2FPlaybooks%2FGet-Microsoft-Covid19-Indicators%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eat%20this%20location%3C%2FA%3E.%20%3CU%3EIt%20is%20important%20to%20deploy%20the%20C19ImportToSentinel%20Playbook%20before%20deploying%20the%20C19IndicatorProcessor%20playbook%3C%2FU%3E.%20Since%20these%20Playbooks%20rely%20on%20the%20Batch%20action%2C%20there%20is%20a%20natural%20dependency%20created%20between%20the%20two%20Playbooks.%20The%20C19IndicatorProcessor%20Playbook%20has%20a%20reference%20to%20the%20Batch%20endpoint%20published%20by%20the%20C19ImportToSentinel%20Playbook.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFollow%20these%20steps%20to%20deploy%20the%20two%20Playbooks%20to%20your%20Azure%20Sentinel%20instance.%3C%2FP%3E%0A%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E1.%26nbsp%3B%20Open%20the%20Azure%20portal%20and%20search%20for%20and%20select%2C%20%3CSTRONG%3EDeploy%20a%20custom%20template%3C%2FSTRONG%3E.%3C%2FP%3E%0A%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22Figure3.jpg%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F191141i2D3A9AB6A2384EDB%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22Figure3.jpg%22%20alt%3D%22Figure3.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E2.%26nbsp%3B%20Select%2C%20%3CSTRONG%3EBuild%20your%20own%20template%3C%2FSTRONG%3E%20in%20the%20editor%20from%20the%20list%20of%20options.%3C%2FP%3E%0A%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E3.%26nbsp%3B%20In%20the%20Edit%20template%20window%2C%20replace%20the%20default%20JSON%20with%20the%20contents%20of%20the%20C19ImportToSentinel.json%20template%20file%20and%20select%20%3CSTRONG%3ESave%3C%2FSTRONG%3E.%3C%2FP%3E%0A%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E4.%26nbsp%3B%20In%20the%20Custom%20deployment%20window%2C%20select%20the%20Resource%20Group%20where%20you%20have%20your%20Azure%20Sentinel%20instance%2C%20and%20under%20Settings%2C%20input%20your%20user%20name%20which%20will%20be%20used%20to%20deploy%20the%20Playbook%2C%20and%20select%20%3CSTRONG%3EPurchase%3C%2FSTRONG%3E.%3C%2FP%3E%0A%3CP%20class%3D%22lia-indent-padding-left-60px%22%3E%3CSTRONG%3ENote%3A%3C%2FSTRONG%3E%20It%20is%20highly%20recommended%20to%20leave%20the%20Playbook%20Name%20to%20the%20default%20setting.%20However%2C%20if%20you%20rename%20the%20Playbook%20you%20will%20need%20to%20reference%20this%20new%20name%20when%20deploying%20the%20second%20Playbook.%3C%2FP%3E%0A%3CP%20class%3D%22lia-indent-padding-left-60px%22%3E%3CSTRONG%3ENote%3A%3C%2FSTRONG%3E%20While%20the%20confirmation%20button%20is%20labeled%20Purchase%2C%20there%20is%20no%20charges%20associated%20with%20obtaining%20these%20Playbooks.%3C%2FP%3E%0A%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E5.%26nbsp%3B%20After%20a%20minute%20or%20two%20the%20Playbook%20will%20be%20visible%20under%20Azure%20Sentinel%20Playbooks.%3C%2FP%3E%0A%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E6.%26nbsp%3B%20Repeat%20these%20same%20steps%20(1-5)%20for%20the%20C19IndicatorProcessor%20Playbook%20with%20the%20only%20difference%20being%20on%20step%20(4)%20there%20is%20an%20additional%20option%20under%20Settings%20where%20you%20will%20input%20the%20name%20you%20used%20for%20the%20first%20Playbook%20you%20deployed.%3C%2FP%3E%0A%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22Figure4.jpg%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F191142iE9D36C4E23F02E83%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22Figure4.jpg%22%20alt%3D%22Figure4.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EOnce%20deployed%20there%20is%20a%20final%20configuration%20step%20to%20import%20the%20threat%20indicators.%20The%20C19ImportToSentinel%20includes%20an%20action%20to%20submit%20the%20indicators%20to%20Azure%20Sentinel%20using%20the%20Microsoft%20Graph%20Security%20API.%20In%20order%20to%20receive%20the%20indicators%20in%20your%20Azure%20Sentinel%20instance%2C%20you%20will%20need%20to%20enable%20the%20%3CEM%3EThreat%20Intelligence%20-%20Platforms%3C%2FEM%3E%20data%20connector.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22Figure5.jpg%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F191463iB9AAE8203D1676C2%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Figure5.jpg%22%20alt%3D%22Figure5.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAlso%2C%20you%20will%20need%20to%20open%20the%20C19ImportToSentinel%20Playbook%20and%20configure%20the%20connection%20for%20the%20%3CEM%3ESubmit%20multiple%20tiIndicators%3C%2FEM%3E%20action%20as%20shown%20below.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22Figure6.jpg%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F191465i5B3166FB1FEDF09D%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22Figure6.jpg%22%20alt%3D%22Figure6.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EConfiguring%20this%20connection%20you%20will%20be%20asked%20to%20login%20to%20Azure%20Active%20Directory%20and%20consent%20for%20the%20permissions%20needed%20for%20the%20Playbook%20to%20submit%20threat%20indicators%20to%20the%20Graph%20Security%20API.%20You%20need%20to%20authenticate%20with%20as%20a%20user%20with%20an%20Azure%20Active%20Directory%20Limited%20Administrator%20Role%20of%20Global%20Administrator.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%226%22%3ESummary%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EOnce%20deployed%20to%20your%20Azure%20Sentinel%20instance%2C%20these%20Playbooks%20will%20operate%20in%20tandem%20to%20import%20indicators%20on%20a%20regular%20schedule%20so%20you%20will%20always%20have%20the%20latest%20threat%20intelligence%20data%20provided%20by%20the%20source.%20This%20post%20covered%20an%20example%20source%20from%20Microsoft%20for%20COVID-19%20indicators%20hosted%20on%20GitHub%20but%20you%20can%20easily%20modify%20the%20%3CEM%3EHTTP%3C%2FEM%3E%20action%20to%20point%20to%20a%20different%20text-based%20indicator%20feed%2C%20and%20update%20the%20%3CEM%3ESelect%3C%2FEM%3E%20action%20to%20parse%20the%20original%20text-based%20feed%20into%20tiIndicators%20format%20for%20import%20into%20Azure%20Sentinel.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1383980%22%20slang%3D%22en-US%22%3E%3CP%3EImport%20threat%20indicators%20to%20Azure%20Sentinel%20from%20any%20text-based%20feed%20with%20Azure%20Logic%20App%20Playbooks.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1383980%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Sentinel%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EThreat%20Intelligence%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1404609%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20Azure%20Playbooks%20to%20import%20text-based%20threat%20indicators%20to%20Azure%20Sentinel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1404609%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F118392%22%20target%3D%22_blank%22%3E%40Jason%20Wescott%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20sharing%20this%20playbook.%20Looks%20very%20interesting.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20deploying%20the%20%3CSPAN%3EC19ImportToSentinel%20json%20%3C%2FSPAN%3Efile%20but%20apparently%20it%20contains%20features%20not%20supported%20in%20Australia%20East%20region.%3C%2FP%3E%3CP%3EMessage%20is%3A%3C%2FP%3E%3CP%3E%22The%20resource%20group%20is%20in%20a%20location%20that%20is%20not%20supported%20by%20one%20or%20more%20resources%20in%20the%20template.%20Please%20choose%20a%20different%20resource%20group.%22%3CBR%20%2F%3EDo%20you%20know%20of%20any%20specific%20content%20that%20could%20be%20blocking%20it%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWould%20you%20be%20able%20to%20share%20all%20the%20contents%20for%20each%20of%20the%20steps%20on%20the%20playbook%20so%20we%20can%20try%20replicating%20them%20one%20by%20one%20and%20find%20out%20what%20might%20not%20be%20supported%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3CBR%20%2F%3ECaio%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1406925%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20Azure%20Playbooks%20to%20import%20text-based%20threat%20indicators%20to%20Azure%20Sentinel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1406925%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F536747%22%20target%3D%22_blank%22%3E%40caiodaruizcorrea%3C%2FA%3E%2C%26nbsp%3BI%20messaged%20you%20directly%20to%20investigate%20what%20you%20are%20seeing.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3CBR%20%2F%3E%3CBR%20%2F%3EJason%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

Introduction

Azure Sentinel provides two built in data connectors for importing threat intelligence, the Threat Intelligence – TAXII data connector, and the Threat Intelligence – Platforms data connector. These data connectors are suitable for most use cases – as explained in our previous detailed blog. However, some open source threat intelligence is shared as text-based files which cannot be accessed directly from these data connectors. This blog describes how to use Azure Sentinel Playbooks to obtain text-based threat indicators from an online source, and import them directly into the ThreatIntelligenceIndicator table where they can be used by all the built-in Sentinel analytics templates to generate security incidents.

 

The Playbooks described in this post were created to allow Azure Sentinel customers to import Microsoft’s COVID-19 related threat indicators published on GitHub. However, these Playbooks can easily be modified to point to any other source of a text-based indicator feed.

 

Playbook architecture

These Azure Sentinel Playbooks work in tandem to read indicators from a source location and import the indicators to the ThreatIntelligenceIndicator table in Logs. Let’s take a closer look at the functionality of each Playbook.

 

Playbook 1 (C19IndicatorProcessor)

C19IndicatorProcessor Playbook performs the following steps:

  • Triggered on a defined schedule
  • Reads the indicators from GitHub
  • Transforms the indicators from the text-based source to the appropriate tiIndicator JSON format
  • Uses the Batch action to send the indicators to the second Playbook (C19ImportToSentinel)
 

Figure1.jpg

 

 

Playbook 2 (C19ImportToSentinel)

C19ImportToSentinel Playbook performs the following steps:

  • Begins with a Batch Messages trigger to receive indicators sent by the first Playbook (C19IndiatorProcessor) and groups the indicators into batches of 10
  • Submits each batch of indicators to Azure Sentinel using the Microsoft Graph Security Logic App connector

Figure2.jpg

 

 

Deploy the Playbooks to Azure Sentinel

The Playbook templates can be downloaded from GitHub at this location. It is important to deploy the C19ImportToSentinel Playbook before deploying the C19IndicatorProcessor playbook. Since these Playbooks rely on the Batch action, there is a natural dependency created between the two Playbooks. The C19IndicatorProcessor Playbook has a reference to the Batch endpoint published by the C19ImportToSentinel Playbook.

 

Follow these steps to deploy the two Playbooks to your Azure Sentinel instance.

1.  Open the Azure portal and search for and select, Deploy a custom template.

Figure3.jpg

 

2.  Select, Build your own template in the editor from the list of options.

3.  In the Edit template window, replace the default JSON with the contents of the C19ImportToSentinel.json template file and select Save.

4.  In the Custom deployment window, select the Resource Group where you have your Azure Sentinel instance, and under Settings, input your user name which will be used to deploy the Playbook, and select Purchase.

Note: It is highly recommended to leave the Playbook Name to the default setting. However, if you rename the Playbook you will need to reference this new name when deploying the second Playbook.

Note: While the confirmation button is labeled Purchase, there is no charges associated with obtaining these Playbooks.

5.  After a minute or two the Playbook will be visible under Azure Sentinel Playbooks.

6.  Repeat these same steps (1-5) for the C19IndicatorProcessor Playbook with the only difference being on step (4) there is an additional option under Settings where you will input the name you used for the first Playbook you deployed.

Figure4.jpg

Once deployed there is a final configuration step to import the threat indicators. The C19ImportToSentinel includes an action to submit the indicators to Azure Sentinel using the Microsoft Graph Security API. In order to receive the indicators in your Azure Sentinel instance, you will need to enable the Threat Intelligence - Platforms data connector.

Figure5.jpg

 

Also, you will need to open the C19ImportToSentinel Playbook and configure the connection for the Submit multiple tiIndicators action as shown below.

Figure6.jpg

 

Configuring this connection you will be asked to login to Azure Active Directory and consent for the permissions needed for the Playbook to submit threat indicators to the Graph Security API. You need to authenticate with as a user with an Azure Active Directory Limited Administrator Role of Global Administrator.

 

 

Summary

Once deployed to your Azure Sentinel instance, these Playbooks will operate in tandem to import indicators on a regular schedule so you will always have the latest threat intelligence data provided by the source. This post covered an example source from Microsoft for COVID-19 indicators hosted on GitHub but you can easily modify the HTTP action to point to a different text-based indicator feed, and update the Select action to parse the original text-based feed into tiIndicators format for import into Azure Sentinel.

2 Comments
Senior Member

Hi @Jason Wescott ,

 

Thanks for sharing this playbook. Looks very interesting.

 

I tried deploying the C19ImportToSentinel json file but apparently it contains features not supported in Australia East region.

Message is:

"The resource group is in a location that is not supported by one or more resources in the template. Please choose a different resource group."
Do you know of any specific content that could be blocking it?

 

Would you be able to share all the contents for each of the steps on the playbook so we can try replicating them one by one and find out what might not be supported?

 

Thanks,
Caio

Microsoft

Hi @caiodaruizcorrea, I messaged you directly to investigate what you are seeing.

 

Thanks,
Jason