Azure-Sentinel/DataConnectors/MCASActivityPlaybook
dicolanl 4a23af9be0 Updating Deploy buttons and links part 2 2021-06-16 01:40:49 +00:00
..
azuredeploy.json MCAS Update 2021-05-11 22:37:28 +00:00
lastrun-MCAS.json MCASActivity Data Connector 2021-05-06 19:33:35 +00:00
readme.md Updating Deploy buttons and links part 2 2021-06-16 01:40:49 +00:00

readme.md

Ingest MCAS (Microsoft Cloud App Security) Activities

Author: Nicholas DiCola

Get-MCASActivity playbook ingests MCAS Activities via (API)[https://docs.microsoft.com/cloud-app-security/api-activities-list] and writes them to a custom log table called MCASActivity_CL.

There are a number of configuration steps required to deploy the Logic App playbooks.

Configuration Steps

  1. Generate a MCAS (API Token)[https://docs.microsoft.com/cloud-app-security/api-authentication]. Settings -> Security Extensions -> API tokens.
  2. Deploy the ARM template and fill in the parameters.
"APIToken": This is the MCAS API Token
"MCASURL": This is the MCAS URL.  See About in the portal for specfici url.
"workspaceId": The Sentinel Workspace ID
"workSpaceKey": The Sentinel Workspace Key
  1. There is a json file (lastrun-MCAS.json).
  2. Upload the lastrun-MCAS.json to the storage account mcasactivitylogicapp container.
  3. Get the Storage Access Key
  4. Go to the azureblob-MCASActivity connection resource.
  5. Click Edit API Connection.
  6. Enter the storage account name and access key. Click Save.
  7. The playbooks are deployed as disabled since the json file and connection has to be authorized. Go to the playbook and click Enable.

Note: there is a parsers (here)[https://github.com/Azure/Azure-Sentinel/tree/master/Parsers/MCAS] to make the logs more readable

Deploy the Logic App template

Deploy to Azure Deploy to Azure Gov