ArmisUpdateAlertStatus

Summary

This playbook would be responsible to update the Alert status from the sentinel to the Armis Portal.

Prerequisites

1. The Armis Alerts data connector should be configured to send appropriate armis alerts events to Microsoft Sentinel.
2. Store Armis API secret key in Key Vault and obtain keyvault name and tenantId. a. Create a Key Vault with unique name b. Go to KeyVault -> secrets -> Generate/import and create 'ArmisAPISecretKey' for storing Armis API Secret Key

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 paramteres:
   • Playbook Name: Enter the playbook name here
   • Armis Instance Base URL : Base URL of Armis Instance
   • keyvaultname: Name of keyvault where secrets are stored
   • tenantId: TenantId where keyvault is located

Post-Deployment instructions

a. Authorize connections

Once deployment is complete, authorize each connection like microsoft sentinel, Key vault.

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 other connections

b. Configurations in Microsoft Sentinel

1. In Microsoft Sentinel, analytical rules should be configured to trigger an incident. An incident should have the alertID - custom entity that contains alertId of each generated Armis alert and alertStatus - custom entity that contains alertStatus of each generated Armis alerts. It can be obtained from the corresponding field in Armis Alerts custom logs. Check the documentation to learn more about adding custom entities to incidents.
2. Configure the automation rules to trigger the playbook.

Sample Analytics rule query

<Armis Alerts Table Name> | where Type == "<Type filed of sentinel customlog table>" and status_s == "<Armis Alert Status>"