4a23af9be0 | ||
---|---|---|
.. | ||
azuredeploy.json | ||
lastrun-MCAS.json | ||
readme.md |
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
- Generate a MCAS (API Token)[https://docs.microsoft.com/cloud-app-security/api-authentication]. Settings -> Security Extensions -> API tokens.
- 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
- There is a json file (lastrun-MCAS.json).
- Upload the lastrun-MCAS.json to the storage account mcasactivitylogicapp container.
- Get the Storage Access Key
- Go to the azureblob-MCASActivity connection resource.
- Click Edit API Connection.
- Enter the storage account name and access key. Click Save.
- 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