Repackaging - Trend Micro Apex One (MMA to AMA Migration)

.script/tests/detectionTemplateSchemaValidation/ValidConnectorIds.json

@@ -205,5 +205,6 @@
   "vArmourACAma",
   "ContrastProtectAma",
   "ClarotyAma",
-  "illusiveAttackManagementSystemAma"
+  "illusiveAttackManagementSystemAma",
+  "TrendMicroApexOneAma"
 ]

Solutions/Trend Micro Apex One/Analytic Rules/TMApexOneAttackDiscoveryDetectionRisks.yaml

@@ -8,6 +8,9 @@ requiredDataConnectors:
   - connectorId: TrendMicroApexOne
     dataTypes:
       - TMApexOneEvent
+  - connectorId: TrendMicroApexOneAma
+    dataTypes:
+      - TMApexOneEvent
 queryFrequency: 1h
 queryPeriod: 1h
 triggerOperator: gt
@@ -29,5 +32,5 @@ entityMappings:
     fieldMappings:
       - identifier: Name
         columnName: AccountCustomEntity
-version: 1.0.0
+version: 1.0.1
 kind: Scheduled

Solutions/Trend Micro Apex One/Analytic Rules/TMApexOneCommandLineSuspiciousRequests.yaml

@@ -8,6 +8,9 @@ requiredDataConnectors:
   - connectorId: TrendMicroApexOne
     dataTypes:
       - TMApexOneEvent
+  - connectorId: TrendMicroApexOneAma
+    dataTypes:
+      - TMApexOneEvent
 queryFrequency: 1h
 queryPeriod: 1h
 triggerOperator: gt
@@ -30,5 +33,5 @@ entityMappings:
     fieldMappings:
       - identifier: Name
         columnName: AccountCustomEntity
-version: 1.0.0
+version: 1.0.1
 kind: Scheduled

Solutions/Trend Micro Apex One/Analytic Rules/TMApexOneCommandsInRequest.yaml

@@ -8,6 +8,9 @@ requiredDataConnectors:
   - connectorId: TrendMicroApexOne
     dataTypes:
       - TMApexOneEvent
+  - connectorId: TrendMicroApexOneAma
+    dataTypes:
+      - TMApexOneEvent
 queryFrequency: 1h
 queryPeriod: 1h
 triggerOperator: gt
@@ -27,5 +30,5 @@ entityMappings:
     fieldMappings:
       - identifier: Url
         columnName: UrlCustomEntity
-version: 1.0.0
+version: 1.0.1
 kind: Scheduled

Solutions/Trend Micro Apex One/Analytic Rules/TMApexOneDvcAccessPermissionWasChanged.yaml

@@ -8,6 +8,9 @@ requiredDataConnectors:
   - connectorId: TrendMicroApexOne
     dataTypes:
       - TMApexOneEvent
+  - connectorId: TrendMicroApexOneAma
+    dataTypes:
+      - TMApexOneEvent
 queryFrequency: 1h
 queryPeriod: 1h
 triggerOperator: gt
@@ -42,5 +45,5 @@ entityMappings:
     fieldMappings:
       - identifier: Name
         columnName: AccountCustomEntity
-version: 1.0.1
+version: 1.0.2
 kind: Scheduled

Solutions/Trend Micro Apex One/Analytic Rules/TMApexOneInboundRemoteAccess.yaml

@@ -8,6 +8,9 @@ requiredDataConnectors:
   - connectorId: TrendMicroApexOne
     dataTypes:
       - TMApexOneEvent
+  - connectorId: TrendMicroApexOneAma
+    dataTypes:
+      - TMApexOneEvent
 queryFrequency: 1h
 queryPeriod: 1h
 triggerOperator: gt
@@ -31,5 +34,5 @@ entityMappings:
     fieldMappings:
       - identifier: Name
         columnName: AccountCustomEntity
-version: 1.0.0
+version: 1.0.1
 kind: Scheduled

Solutions/Trend Micro Apex One/Analytic Rules/TMApexOneMultipleDenyOrTerminateActionOnSingleIp.yaml

@@ -8,6 +8,9 @@ requiredDataConnectors:
   - connectorId: TrendMicroApexOne
     dataTypes:
       - TMApexOneEvent
+  - connectorId: TrendMicroApexOneAma
+    dataTypes:
+      - TMApexOneEvent
 queryFrequency: 1h
 queryPeriod: 1h
 triggerOperator: gt
@@ -29,5 +32,5 @@ entityMappings:
     fieldMappings:
       - identifier: Address
         columnName: IPCustomEntity
-version: 1.0.0
+version: 1.0.1
 kind: Scheduled

Solutions/Trend Micro Apex One/Analytic Rules/TMApexOnePossibleExploitOrExecuteOperation.yaml

@@ -8,6 +8,9 @@ requiredDataConnectors:
   - connectorId: TrendMicroApexOne
     dataTypes:
       - TMApexOneEvent
+  - connectorId: TrendMicroApexOneAma
+    dataTypes:
+      - TMApexOneEvent
 queryFrequency: 1h
 queryPeriod: 1h
 triggerOperator: gt
@@ -32,5 +35,5 @@ entityMappings:
     fieldMappings:
       - identifier: Name
         columnName: AccountCustomEntity
-version: 1.0.2
+version: 1.0.3
 kind: Scheduled 

Solutions/Trend Micro Apex One/Analytic Rules/TMApexOneRiskCnCEvents.yaml

@@ -8,6 +8,9 @@ requiredDataConnectors:
   - connectorId: TrendMicroApexOne
     dataTypes:
       - TMApexOneEvent
+  - connectorId: TrendMicroApexOneAma
+    dataTypes:
+      - TMApexOneEvent
 queryFrequency: 1h
 queryPeriod: 1h
 triggerOperator: gt
@@ -29,5 +32,5 @@ entityMappings:
     fieldMappings:
       - identifier: Name
         columnName: AccountCustomEntity
-version: 1.0.0
+version: 1.0.1
 kind: Scheduled

Solutions/Trend Micro Apex One/Analytic Rules/TMApexOneSpywareWithFailedResponse.yaml

@@ -8,6 +8,9 @@ requiredDataConnectors:
   - connectorId: TrendMicroApexOne
     dataTypes:
       - TMApexOneEvent
+  - connectorId: TrendMicroApexOneAma
+    dataTypes:
+      - TMApexOneEvent
 queryFrequency: 1h
 queryPeriod: 1h
 triggerOperator: gt
@@ -30,5 +33,5 @@ entityMappings:
     fieldMappings:
       - identifier: Name
         columnName: AccountCustomEntity
-version: 1.0.0
+version: 1.0.1
 kind: Scheduled

Solutions/Trend Micro Apex One/Analytic Rules/TMApexOneSuspiciousConnections.yaml

@@ -8,6 +8,9 @@ requiredDataConnectors:
   - connectorId: TrendMicroApexOne
     dataTypes:
       - TMApexOneEvent
+  - connectorId: TrendMicroApexOneAma
+    dataTypes:
+      - TMApexOneEvent
 queryFrequency: 1h
 queryPeriod: 1h
 triggerOperator: gt
@@ -31,5 +34,5 @@ entityMappings:
     fieldMappings:
       - identifier: Name
         columnName: AccountCustomEntity
-version: 1.0.0
+version: 1.0.1
 kind: Scheduled

Solutions/Trend Micro Apex One/Data Connectors/TrendMicro_ApexOne.json

@@ -1,6 +1,6 @@
 {
     "id": "TrendMicroApexOne",
-    "title": "Trend Micro Apex One",
+    "title": "[Deprecated] Trend Micro Apex One via Legacy Agent",
     "publisher": "Trend Micro",
     "descriptionMarkdown": "The [Trend Micro Apex One](https://www.trendmicro.com/en_us/business/products/user-protection/sps/endpoint.html) data connector provides the capability to ingest [Trend Micro Apex One events](https://docs.trendmicro.com/en-us/enterprise/trend-micro-apex-central-2019-online-help/appendices/syslog-mapping-cef.aspx) into Microsoft Sentinel. Refer to [Trend Micro Apex Central](https://docs.trendmicro.com/en-us/enterprise/trend-micro-apex-central-2019-online-help/preface_001.aspx) for more information.",
     "additionalRequirementBanner": "This data connector depends on a parser based on Kusto Function to work as expected [**TMApexOneEvent**](https://aka.ms/sentinel-TMApexOneEvent-parser) which is deployed with the Microsoft Sentinel Solution.",

Solutions/Trend Micro Apex One/Data Connectors/template_TrendMicro_ApexOneAMA.json

@@ -0,0 +1,118 @@
+{
+    "id": "TrendMicroApexOneAma",
+    "title": "[Recommended] Trend Micro Apex One via AMA",
+    "publisher": "Trend Micro",
+    "descriptionMarkdown": "The [Trend Micro Apex One](https://www.trendmicro.com/en_us/business/products/user-protection/sps/endpoint.html) data connector provides the capability to ingest [Trend Micro Apex One events](https://docs.trendmicro.com/en-us/enterprise/trend-micro-apex-central-2019-online-help/appendices/syslog-mapping-cef.aspx) into Microsoft Sentinel. Refer to [Trend Micro Apex Central](https://docs.trendmicro.com/en-us/enterprise/trend-micro-apex-central-2019-online-help/preface_001.aspx) for more information.",
+    "additionalRequirementBanner": "This data connector depends on a parser based on Kusto Function to work as expected [**TMApexOneEvent**](https://aka.ms/sentinel-TMApexOneEvent-parser) which is deployed with the Microsoft Sentinel Solution.",
+    "graphQueries": [
+        {
+            "metricName": "Total data received",
+            "legend": "TrendMicroApexOne",
+            "baseQuery": "CommonSecurityLog\n |where DeviceVendor =~ 'Trend Micro'\n |where DeviceProduct =~ 'Apex Central'\n  |extend sent_by_ama = column_ifexists('CollectorHostName','')\n |where isnotempty(sent_by_ama)"
+        }
+    ],
+    "sampleQueries": [
+        {
+            "description" : "All logs",
+            "query": "\nTMApexOneEvent\n| sort by TimeGenerated"
+        }
+    ],
+    "dataTypes": [
+        {
+            "name": "CommonSecurityLog (TrendMicroApexOne)",
+            "lastDataReceivedQuery": "CommonSecurityLog\n |where DeviceVendor =~ 'Trend Micro'\n |where DeviceProduct =~ 'Apex Central'\n  |extend sent_by_ama = column_ifexists('CollectorHostName','')\n |where isnotempty(sent_by_ama)\n            | summarize Time = max(TimeGenerated)\n            | where isnotempty(Time)"
+        }
+    ],
+    "connectivityCriterias": [
+        {
+            "type": "IsConnectedQuery",
+            "value": [
+                "CommonSecurityLog\n |where DeviceVendor =~ 'Trend Micro'\n |where DeviceProduct =~ 'Apex Central'\n  |extend sent_by_ama = column_ifexists('CollectorHostName','')\n |where isnotempty(sent_by_ama)\n | summarize LastLogReceived = max(TimeGenerated)\n | project IsConnected = LastLogReceived > ago(30d)"
+            ]
+        }
+    ],
+    "availability": {
+        "status": 1,
+        "isPreview": false
+    },
+    "permissions": {
+        "resourceProvider": [
+            {
+                "provider": "Microsoft.OperationalInsights/workspaces",
+                "permissionsDisplayText": "read and write permissions are required.",
+                "providerDisplayName": "Workspace",
+                "scope": "Workspace",
+                "requiredPermissions": {
+                    "write": true,
+                    "read": true,
+                    "delete": true
+                }
+            },
+            {
+                "provider": "Microsoft.OperationalInsights/workspaces/sharedKeys",
+                "permissionsDisplayText": "read permissions to shared keys for the workspace are required. [See the documentation to learn more about workspace keys](https://docs.microsoft.com/azure/azure-monitor/platform/agent-windows#obtain-workspace-id-and-key).",
+                "providerDisplayName": "Keys",
+                "scope": "Workspace",
+                "requiredPermissions": {
+                    "action": true
+                }
+            }
+        ],
+		"customs": [
+      {
+        "description": "To collect data from non-Azure VMs, they must have Azure Arc installed and enabled. [Learn more](https://docs.microsoft.com/azure/azure-monitor/agents/azure-monitor-agent-install?tabs=ARMAgentPowerShell,PowerShellWindows,PowerShellWindowsArc,CLIWindows,CLIWindowsArc)"
+      },
+      {
+        "description": "Common Event Format (CEF) via AMA and Syslog via AMA data connectors must be installed [Learn more](https://learn.microsoft.com/azure/sentinel/connect-cef-ama#open-the-connector-page-and-create-the-dcr)"
+      }	  
+    ]
+    },
+    "instructionSteps": [
+        {
+            "title": "", 
+            "description": ">This data connector depends on a parser based on a Kusto Function to work as expected [**TMApexOneEvent**](https://aka.ms/sentinel-TMApexOneEvent-parser) which is deployed with the Microsoft Sentinel Solution.",
+            "instructions": [ 
+				       {
+                    "parameters": {
+                        "title": "1. Kindly follow the steps to configure the data connector",
+                        "instructionSteps": [
+                            {
+                                "title": "Step A. Configure the Common Event Format (CEF) via AMA data connector",
+                                "description": "_Note:- CEF logs are collected only from Linux Agents_\n\n1. Navigate to Microsoft Sentinel workspace ---> configuration ---> Data connector blade .\n\n2. Search for 'Common Event Format (CEF) via AMA' data connector and open it.\n\n3. Check If there is no existing DCR configured to collect required facility of logs, Create a new DCR (Data Collection Rule)\n\n\t_Note:- It is recommended to install minimum 1.27 version of AMA agent [Learn more](https://learn.microsoft.com/azure/azure-monitor/agents/azure-monitor-agent-manage?tabs=azure-portal ) and ensure there is no duplicate DCR as it can cause log duplicacy_\n\n4. Run the command provided in the CEF via AMA data connector page to configure the CEF collector on the machine",
+                                "instructions": [
+                                ]
+                            },
+                            {
+                                "title": "Step B. Forward Common Event Format (CEF) logs to Syslog agent",
+                                "description": "[Follow these steps](https://docs.trendmicro.com/en-us/enterprise/trend-micro-apex-central-2019-online-help/detections/logs_001/syslog-forwarding.aspx) to configure Apex Central sending alerts via syslog. While configuring, on step 6, select the log format **CEF**.",
+                                "instructions": [
+                                ]
+                            },
+							{
+								"title": "Step C. Validate connection",
+								"description": "Follow the instructions to validate your connectivity:\n\nOpen Log Analytics to check if the logs are received using the CommonSecurityLog schema.\n\nIt may take about 20 minutes until the connection streams data to your workspace.\n\nIf the logs are not received, run the following connectivity validation script:\n\n 1. Make sure that you have Python on your machine using the following command: python -version\n\n2. You must have elevated permissions (sudo) on your machine",
+								"instructions": [
+									{
+										"parameters": {
+										"label": "Run the following command to validate your connectivity:",
+										"value": "sudo wget -O Sentinel_AMA_troubleshoot.py https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/Syslog/Sentinel_AMA_troubleshoot.py&&sudo python Sentinel_AMA_troubleshoot.py --cef"
+										},
+										"type": "CopyableLabel"
+									}
+								]
+							}							
+                        ]
+                    },
+                    "type": "InstructionStepsGroup"
+                }
+            ]    
+        },
+
+
+
+        {
+            "title": "2. Secure your machine ",
+            "description": "Make sure to configure the machine's security according to your organization's security policy\n\n\n[Learn more >](https://aka.ms/SecureCEF)"
+        }
+    ]
+}

Solutions/Trend Micro Apex One/Data/Solution_Trend Micro Apex One.json

@@ -2,12 +2,13 @@
   "Name": "Trend Micro Apex One",
   "Author": "Microsoft - support@microsoft.com",
   "Logo": "<img src=\"https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Logos/Trend_Micro_Logo.svg\" width=\"75px\" height=\"75px\">",
-  "Description": "The [Trend Micro Apex One](https://www.trendmicro.com/business/products/user-protection/sps/endpoint.htmlhttps:/www.trendmicro.com/business/products/user-protection/sps/endpoint.html) solution for Microsoft Sentinel enables ingestion of [Trend Micro Apex One events](https://docs.trendmicro.com/enterprise/trend-micro-apex-central-2019-online-help/appendices/syslog-mapping-cef.aspx) into Microsoft Sentinel. Refer to [Trend Micro Apex Central](https://docs.trendmicro.com/enterprise/trend-micro-apex-central-2019-online-help/preface_001.aspx) for more information. \r\n \r\n  **Underlying Microsoft Technologies used:**\n\nThis solution takes a dependency on the following technologies, and some of these dependencies either may be in [Preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) state or might result in additional ingestion or operational costs:\r\n \r\n  a. [Agent-based log collection (CEF over Syslog) ](https://docs.microsoft.com/azure/sentinel/connect-common-event-format)",
+  "Description": "The [Trend Micro Apex One](https://www.trendmicro.com/business/products/user-protection/sps/endpoint.htmlhttps:/www.trendmicro.com/business/products/user-protection/sps/endpoint.html) solution for Microsoft Sentinel enables ingestion of [Trend Micro Apex One events](https://docs.trendmicro.com/enterprise/trend-micro-apex-central-2019-online-help/appendices/syslog-mapping-cef.aspx) into Microsoft Sentinel. Refer to [Trend Micro Apex Central](https://docs.trendmicro.com/enterprise/trend-micro-apex-central-2019-online-help/preface_001.aspx) for more information. \n\r\n1. **Trend Micro Apex One via AMA** - This data connector helps in ingesting Trend Micro Apex One logs into your Log Analytics Workspace using the new Azure Monitor Agent. Learn more about ingesting using the new Azure Monitor Agent [here](https://learn.microsoft.com/azure/sentinel/connect-cef-ama). **Microsoft recommends using this Data Connector**.\n\r\n2. **Trend Micro Apex One via Legacy Agent** - This data connector helps in ingesting Trend Micro Apex One logs into your Log Analytics Workspace using the legacy Log Analytics agent.\n\n**NOTE:** Microsoft recommends installation of Trend Micro Apex One via AMA Connector. Legacy connector uses the Log Analytics agent which is about to be deprecated by **Aug 31, 2024,** and thus should only be installed where AMA is not supported. Using MMA and AMA on same machine can cause log duplication and extra ingestion cost [more details](https://learn.microsoft.com/en-us/azure/sentinel/ama-migrate).",
   "Data Connectors": [
-    "Data Connectors/TrendMicro_ApexOne.json"
+    "Data Connectors/TrendMicro_ApexOne.json",
+	"Data Connectors/template_TrendMicro_ApexOneAMA.json"
   ],
   "Parsers": [
-    "Parsers/TMApexOneEvent.txt"
+    "Parsers/TMApexOneEvent.yaml"
   ],
   "Workbooks": [
     "Workbooks/TrendMicroApexOne.json"

Solutions/Trend Micro Apex One/Data/system_generated_metadata.json

@@ -0,0 +1,34 @@
+{
+  "Name": "Trend Micro Apex One",
+  "Author": "Microsoft - support@microsoft.com",
+  "Logo": "<img src=\"https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Logos/Trend_Micro_Logo.svg\" width=\"75px\" height=\"75px\">",
+  "Description": "The [Trend Micro Apex One](https://www.trendmicro.com/business/products/user-protection/sps/endpoint.htmlhttps:/www.trendmicro.com/business/products/user-protection/sps/endpoint.html) solution for Microsoft Sentinel enables ingestion of [Trend Micro Apex One events](https://docs.trendmicro.com/enterprise/trend-micro-apex-central-2019-online-help/appendices/syslog-mapping-cef.aspx) into Microsoft Sentinel. Refer to [Trend Micro Apex Central](https://docs.trendmicro.com/enterprise/trend-micro-apex-central-2019-online-help/preface_001.aspx) for more information. \n\r\n1. **Trend Micro Apex One via AMA** - This data connector helps in ingesting Trend Micro Apex One logs into your Log Analytics Workspace using the new Azure Monitor Agent. Learn more about ingesting using the new Azure Monitor Agent [here](https://learn.microsoft.com/azure/sentinel/connect-cef-ama). **Microsoft recommends using this Data Connector**.\n\r\n2. **Trend Micro Apex One via Legacy Agent** - This data connector helps in ingesting Trend Micro Apex One logs into your Log Analytics Workspace using the legacy Log Analytics agent.\n\n**NOTE:** Microsoft recommends installation of Trend Micro Apex One via AMA Connector. Legacy connector uses the Log Analytics agent which is about to be deprecated by **Aug 31, 2024,** and thus should only be installed where AMA is not supported. Using MMA and AMA on same machine can cause log duplication and extra ingestion cost [more details](https://learn.microsoft.com/en-us/azure/sentinel/ama-migrate).",
+  "BasePath": "C:\\GitHub\\Azure-Sentinel\\Solutions\\Trend Micro Apex One",
+  "Metadata": "SolutionMetadata.json",
+  "TemplateSpec": true,
+  "Is1PConnector": false,
+  "Version": "3.0.0",
+  "publisherId": "azuresentinel",
+  "offerId": "azure-sentinel-solution-trendmicroapexone",
+  "providers": [
+    "TrendMicro"
+  ],
+  "categories": {
+    "domains": [
+      "Security - Threat Protection"
+    ]
+  },
+  "firstPublishDate": "2021-07-06",
+  "lastPublishDate": "2022-03-24",
+  "support": {
+    "name": "Microsoft Corporation",
+    "email": "support@microsoft.com",
+    "tier": "Microsoft",
+    "link": "https://support.microsoft.com"
+  },
+  "Data Connectors": "[\n  \"Data Connectors/TrendMicro_ApexOne.json\",\n  \"Data Connectors/template_TrendMicro_ApexOneAMA.json\"\n]",
+  "Parsers": "[\n  \"TMApexOneEvent.txt\"\n]",
+  "Workbooks": "[\n  \"Workbooks/TrendMicroApexOne.json\"\n]",
+  "Analytic Rules": "[\n  \"TMApexOneAttackDiscoveryDetectionRisks.yaml\",\n  \"TMApexOneCommandLineSuspiciousRequests.yaml\",\n  \"TMApexOneCommandsInRequest.yaml\",\n  \"TMApexOneDvcAccessPermissionWasChanged.yaml\",\n  \"TMApexOneInboundRemoteAccess.yaml\",\n  \"TMApexOneMultipleDenyOrTerminateActionOnSingleIp.yaml\",\n  \"TMApexOnePossibleExploitOrExecuteOperation.yaml\",\n  \"TMApexOneRiskCnCEvents.yaml\",\n  \"TMApexOneSpywareWithFailedResponse.yaml\",\n  \"TMApexOneSuspiciousConnections.yaml\"\n]",
+  "Hunting Queries": "[\n  \"TMApexOneBehaviorMonitoringTranslatedAction.yaml\",\n  \"TMApexOneBehaviorMonitoringTranslatedOperation.yaml\",\n  \"TMApexOneBehaviorMonitoringTriggeredPolicy.yaml\",\n  \"TMApexOneBehaviorMonitoringTypesOfEvent.yaml\",\n  \"TMApexOneChannelType.yaml\",\n  \"TMApexOneDataLossPreventionAction.yaml\",\n  \"TMApexOneRareAppProtocolByIP.yaml\",\n  \"TMApexOneSpywareDetection.yaml\",\n  \"TMApexOneSuspiciousFiles.yaml\",\n  \"TMApexOneTopSources.yaml\"\n]"
+}