add metadata to cisco meraki nested playbooks

This commit is contained in:
Vitalii Uslystyi 2022-08-26 09:42:37 +03:00
Родитель 23946c195b
Коммит 0246ad8239
1 изменённых файлов: 23 добавлений и 1 удалений

Просмотреть файл

@ -1,7 +1,29 @@
{
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"metadata": {},
"metadata": {
"title": "Cisco Meraki - Block URL",
"description": "Once a new Microsoft Sentinel incident is created, this playbook gets triggered and performs the following actions:\n 1. Fetches a list of potentially malicious URLs.\n 2. For each URL in the list, checks if the URL is blocked by the network of the organization.\n - If URL is allowed by the network, then incident comment is created saying URL is allowed.\n - If URL is blocked by the network, then incident comment is created saying URL is blocked.\n - If URL is not blocked by the network and not part of the network, that URL is blocked by playbook.",
"prerequisites": [
"1. Deploy the Cisco Meraki Custom Connector before the deployment of this playbook under the same subscription and same resource group. Capture the name of the connector during deployment.",
"2. Cisco Meraki API Key should be known to establish a connection with Cisco Meraki Custom Connector. [Refer here](https://developer.cisco.com/meraki/api-v1/#!getting-started/authorization)",
"3. Organization name should be known. [Refer here](https://developer.cisco.com/meraki/api-v1/#!getting-started/find-your-organization-id)",
"4. Network name should be known.[Refer here](https://developer.cisco.com/meraki/api-v1/#!getting-started/find-your-network-id)"
],
"lastUpdateTime": "2022-08-26T07:00:00.000Z",
"entities": [
"url"
],
"tags": [
"Remediation"
],
"support": {
"tier": "microsoft"
},
"author": {
"name": "Microsoft"
}
},
"parameters": {
"PlaybookName": {
"type": "string",