Azure-Sentinel/Playbooks/Get-AlienVault_OTX
dicolanl 525d001024 Updating Deploy buttons and links part 1 2021-06-16 00:25:40 +00:00
..
azuredeploy.json Update to correct template input button and major revision to the logic app 2020-11-19 17:34:49 -06:00
readme.md Updating Deploy buttons and links part 1 2021-06-16 00:25:40 +00:00

readme.md

Get-AlienValut_OTX_V2

author: Andrew Blumhardt

This is a Logic App to import threat indicators from AlienVault into Azure Sentinel using the Graph Security API.

Refer to the following link for a more detailed description: https://azurecloudai.blog/2020/11/19/how-to-connect-alienvault-otx-to-azure-sentinel/

Summary:

Designed to exceed the 1000 workflow limit for large datasets by breaking the results into pages. Set the Lookback to gather historic IOC data. Prevents failed collections when results exceed 1000 records. Tested using 200k records (5 years).

Instructions:

  1. Get an API key from AlienVault: https://otx.alienvault.com/
  2. Create an App Registration in Azure AD: http://thewindowsupdate.com/2020/02/11/bring-your-threat-intelligence-to-azure-sentinel/
  3. Import the Logic App (disabled by default)
  4. Set the run variables (Tennant ID, Client ID, App Secret, and OTX API Key).
  5. Enable and run.

Historic Data Lookback (RUN ONCE):

  1. Set the lookback days to a desired value (example 365)
  2. Enable and run the Logic App (estimate 10 minutes processing time for every 10k records)
  3. Set the Lookback days to the default 1 day

Notes:

  1. API sets a record lookup URL for the profile page on AlienVault in “additionalInformation”
  2. API uses the “FileCreatedDateTime” column to log the time ingested

App Registration Troubleshooting:

  1. Make sure to Grant Admin Consent on the API Permission page
  2. Your App Registration can be assigned to roles at the workspace or RG. You may need to assign additional credentials.

During testing the provider returned some incorrectly formatted records. This was only observed in large collections. The app does not have error checking. Incorrectly formatted records will fail if encountered but the overall app will complete. This will cause the log to show the parent app as failed.

Documentation references:

  • Azure Management groups as containers of subscriptions to monitor
  • Azure Active Directory registered application, assigned with RBAC roles
  • Logic App alternative that Combines Sentinel and Defender TI collection
  • Deploy to Azure Deploy to Azure Gov