|
6 | 6 | "config": { |
7 | 7 | "isWizard": false, |
8 | 8 | "basics": { |
9 | | - "description": "<img src=\"https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Solutions/Lookout/Workbooks/Images/Logo/lookout.svg\"width=\"75px\"height=\"75px\">\n\n**Note:** Please refer to the following before installing the solution: \n\n• Review the solution [Release Notes](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/Lookout/ReleaseNotes.md)\n\n • There may be [known issues](https://aka.ms/sentinelsolutionsknownissues) pertaining to this Solution, please refer to them before installing.\n\nThe [Lookout](https://lookout.com) solution provides the capability to ingest [Lookout events](https://enterprise.support.lookout.com/hc/articles/115002741773-Mobile-Risk-API-Guide#commoneventfields) into Microsoft Sentinel through the Mobile Risk API. It can get events which helps to examine potential security risks and more. Refer to [API documentation](https://enterprise.support.lookout.com/hc/articles/115002741773-Mobile-Risk-API-Guide) for more information .\n \n **Underlying Microsoft Technologies used:** \n\n This 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:\n\n a. [Azure Monitor HTTP Data Collector API](https://docs.microsoft.com/azure/azure-monitor/logs/data-collector-api) \n\n b. [Microsoft Sentinel Codeless Connector Platform](https://aka.ms/Sentinel-CCP_Platform)\n\n<p><span style='color:red; font-weight:bold;'>NOTE</span>: Microsoft recommends installation of \"LookoutStreaming_Definition\" (via Codeless Connector Framework). This connector is build on the Codeless Connector Framework (CCF), which uses the Log Ingestion API, which replaces ingestion via the <a href='https://aka.ms/Sentinel-Logs_migration' style='color:#1890F1;'>deprecated HTTP Data Collector API</a>. CCF-based data connectors also support <a href='https://aka.ms/Sentinel-DCR_Overview' style='color:#1890F1;'>Data Collection Rules</a> (DCRs) offering transformations and enrichment.</p>\n\n<p><span style='color:red; font-weight:bold;'>Important</span>: While the updated connector(s) can coexist with their legacy versions, running them together will result in duplicated data ingestion. You can disable the older versions of these connectors to avoid duplication of data..</p>\n\n**Data Connectors:** 2, **Workbooks:** 3\n\n[Learn more about Microsoft Sentinel](https://aka.ms/azuresentinel) | [Learn more about Solutions](https://aka.ms/azuresentinelsolutionsdoc)", |
| 9 | + "description": "<img src=\"https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Solutions/Lookout/Workbooks/Images/Logo/lookout.svg\"width=\"75px\"height=\"75px\">\n\n**Note:** Please refer to the following before installing the solution: \n\n• Review the solution [Release Notes](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/Lookout/ReleaseNotes.md)\n\n • There may be [known issues](https://aka.ms/sentinelsolutionsknownissues) pertaining to this Solution, please refer to them before installing.\n\nThe [Lookout](https://lookout.com) solution provides the capability to ingest [Lookout events](https://enterprise.support.lookout.com/hc/articles/115002741773-Mobile-Risk-API-Guide#commoneventfields) into Microsoft Sentinel through the Mobile Risk API. It can get events which helps to examine potential security risks and more. Refer to [API documentation](https://enterprise.support.lookout.com/hc/articles/115002741773-Mobile-Risk-API-Guide) for more information .\n \n **Underlying Microsoft Technologies used:** \n\n This 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:\n\n a. [Azure Monitor HTTP Data Collector API](https://docs.microsoft.com/azure/azure-monitor/logs/data-collector-api) \n\n b. [Microsoft Sentinel Codeless Connector Platform](https://aka.ms/Sentinel-CCP_Platform)\n\n<p><span style='color:red; font-weight:bold;'>NOTE</span>: Microsoft recommends installation of \"LookoutStreaming_Definition\" (via Codeless Connector Framework). This connector is build on the Codeless Connector Framework (CCF), which uses the Log Ingestion API, which replaces ingestion via the <a href='https://aka.ms/Sentinel-Logs_migration' style='color:#1890F1;'>deprecated HTTP Data Collector API</a>. CCF-based data connectors also support <a href='https://aka.ms/Sentinel-DCR_Overview' style='color:#1890F1;'>Data Collection Rules</a> (DCRs) offering transformations and enrichment.</p>\n\n<p><span style='color:red; font-weight:bold;'>Important</span>: While the updated connector(s) can coexist with their legacy versions, running them together will result in duplicated data ingestion. You can disable the older versions of these connectors to avoid duplication of data..</p>\n\n**Data Connectors:** 2, **Parsers:** 1, **Workbooks:** 5, **Analytic Rules:** 5, **Hunting Queries:** 1\n\n[Learn more about Microsoft Sentinel](https://aka.ms/azuresentinel) | [Learn more about Solutions](https://aka.ms/azuresentinelsolutionsdoc)", |
10 | 10 | "subscription": { |
11 | 11 | "resourceProviders": [ |
12 | 12 | "Microsoft.OperationsManagement/solutions", |
|
67 | 67 | "name": "dataconnectors2-text", |
68 | 68 | "type": "Microsoft.Common.TextBlock", |
69 | 69 | "options": { |
70 | | - "text": "This Solution installs the data connector for Lookout. You can get Lookout data in your Microsoft Sentinel workspace. After installing the solution, configure and enable this data connector by following guidance in Manage solution view." |
| 70 | + "text": "This Solution installs the data connector for Lookout Mobile Threat Detection Connector (via Codeless Connector Framework) (Preview). You can get Lookout Mobile Threat Detection Connector (via Codeless Connector Framework) (Preview) data in your Microsoft Sentinel workspace. After installing the solution, configure and enable this data connector by following guidance in Manage solution view." |
71 | 71 | } |
72 | 72 | }, |
73 | 73 | { |
|
125 | 125 | { |
126 | 126 | "name": "workbook2", |
127 | 127 | "type": "Microsoft.Common.Section", |
128 | | - "label": "Lookout Executive Dashboard", |
| 128 | + "label": "Lookout Enhanced Security Dashboard", |
129 | 129 | "elements": [ |
130 | 130 | { |
131 | 131 | "name": "workbook2-text", |
132 | 132 | "type": "Microsoft.Common.TextBlock", |
133 | 133 | "options": { |
134 | | - "text": "Executive-level overview of mobile security posture" |
| 134 | + "text": "This workbook leverages the enhanced Lookout Mobile Risk API v2 data with comprehensive field extraction and advanced threat intelligence. It depends on the LookoutEvents parser deployed with the Azure Sentinel Solution." |
135 | 135 | } |
136 | 136 | } |
137 | 137 | ] |
138 | 138 | }, |
139 | 139 | { |
140 | 140 | "name": "workbook3", |
141 | 141 | "type": "Microsoft.Common.Section", |
142 | | - "label": "Lookout Comprehensive Dashboard", |
| 142 | + "label": "Lookout Security Investigation Dashboard", |
143 | 143 | "elements": [ |
144 | 144 | { |
145 | 145 | "name": "workbook3-text", |
146 | 146 | "type": "Microsoft.Common.TextBlock", |
147 | 147 | "options": { |
148 | | - "text": "Detailed analysis and metrics for mobile threat detection" |
| 148 | + "text": "Real-time mobile threat investigation and incident response" |
| 149 | + } |
| 150 | + } |
| 151 | + ] |
| 152 | + }, |
| 153 | + { |
| 154 | + "name": "workbook4", |
| 155 | + "type": "Microsoft.Common.Section", |
| 156 | + "label": "Lookout Executive Dashboard", |
| 157 | + "elements": [ |
| 158 | + { |
| 159 | + "name": "workbook4-text", |
| 160 | + "type": "Microsoft.Common.TextBlock", |
| 161 | + "options": { |
| 162 | + "text": "Real-time mobile threat detection and device security monitoring" |
| 163 | + } |
| 164 | + } |
| 165 | + ] |
| 166 | + }, |
| 167 | + { |
| 168 | + "name": "workbook5", |
| 169 | + "type": "Microsoft.Common.Section", |
| 170 | + "label": "Lookout IOA Investigation Dashboard", |
| 171 | + "elements": [ |
| 172 | + { |
| 173 | + "name": "workbook5-text", |
| 174 | + "type": "Microsoft.Common.TextBlock", |
| 175 | + "options": { |
| 176 | + "text": "Comprehensive mobile threat intelligence, device investigation, and security posture monitoring" |
149 | 177 | } |
150 | 178 | } |
151 | 179 | ] |
|
177 | 205 | "uri": "https://docs.microsoft.com/azure/sentinel/tutorial-detect-threats-custom?WT.mc_id=Portal-Microsoft_Azure_CreateUIDef" |
178 | 206 | } |
179 | 207 | } |
| 208 | + }, |
| 209 | + { |
| 210 | + "name": "analytic1", |
| 211 | + "type": "Microsoft.Common.Section", |
| 212 | + "label": "Lookout - New Threat events found.", |
| 213 | + "elements": [ |
| 214 | + { |
| 215 | + "name": "analytic1-text", |
| 216 | + "type": "Microsoft.Common.TextBlock", |
| 217 | + "options": { |
| 218 | + "text": "Created to detect new Threat events from the data which is recently synced by Lookout Solution." |
| 219 | + } |
| 220 | + } |
| 221 | + ] |
| 222 | + }, |
| 223 | + { |
| 224 | + "name": "analytic2", |
| 225 | + "type": "Microsoft.Common.Section", |
| 226 | + "label": "Lookout - High Severity Mobile Threats Detected (v2)", |
| 227 | + "elements": [ |
| 228 | + { |
| 229 | + "name": "analytic2-text", |
| 230 | + "type": "Microsoft.Common.TextBlock", |
| 231 | + "options": { |
| 232 | + "text": "Detects high severity mobile threats from Lookout Mobile Risk API v2 with enhanced threat intelligence and device context. This rule leverages the comprehensive v2 field set to provide detailed threat classification, risk assessment, and device compliance status for improved security monitoring." |
| 233 | + } |
| 234 | + } |
| 235 | + ] |
| 236 | + }, |
| 237 | + { |
| 238 | + "name": "analytic3", |
| 239 | + "type": "Microsoft.Common.Section", |
| 240 | + "label": "Lookout - Device Compliance and Security Status Changes (v2)", |
| 241 | + "elements": [ |
| 242 | + { |
| 243 | + "name": "analytic3-text", |
| 244 | + "type": "Microsoft.Common.TextBlock", |
| 245 | + "options": { |
| 246 | + "text": "Monitors device compliance status changes and security posture degradation using Lookout Mobile Risk API v2 enhanced device fields. Detects devices becoming non-compliant, security status changes, and potential device compromise indicators with detailed device context and MDM integration data." |
| 247 | + } |
| 248 | + } |
| 249 | + ] |
| 250 | + }, |
| 251 | + { |
| 252 | + "name": "analytic4", |
| 253 | + "type": "Microsoft.Common.Section", |
| 254 | + "label": "Lookout - Critical Smishing and Phishing Alerts (v2)", |
| 255 | + "elements": [ |
| 256 | + { |
| 257 | + "name": "analytic4-text", |
| 258 | + "type": "Microsoft.Common.TextBlock", |
| 259 | + "options": { |
| 260 | + "text": "Detects critical smishing (SMS phishing) and phishing alerts from Lookout Mobile Risk API v2. This rule identifies sophisticated social engineering attacks including CEO fraud, credential harvesting, and malicious link campaigns targeting mobile devices. Leverages enhanced v2 smishing detection capabilities for comprehensive mobile threat protection." |
| 261 | + } |
| 262 | + } |
| 263 | + ] |
| 264 | + }, |
| 265 | + { |
| 266 | + "name": "analytic5", |
| 267 | + "type": "Microsoft.Common.Section", |
| 268 | + "label": "Lookout - Critical Audit and Policy Changes (v2)", |
| 269 | + "elements": [ |
| 270 | + { |
| 271 | + "name": "analytic5-text", |
| 272 | + "type": "Microsoft.Common.TextBlock", |
| 273 | + "options": { |
| 274 | + "text": "Monitors critical audit events and policy changes from Lookout Mobile Risk API v2. Detects unauthorized configuration changes, policy modifications, security setting adjustments, and administrative actions that could impact mobile security posture. Provides comprehensive audit trail for compliance and security governance." |
| 275 | + } |
| 276 | + } |
| 277 | + ] |
| 278 | + } |
| 279 | + ] |
| 280 | + }, |
| 281 | + { |
| 282 | + "name": "huntingqueries", |
| 283 | + "label": "Hunting Queries", |
| 284 | + "bladeTitle": "Hunting Queries", |
| 285 | + "elements": [ |
| 286 | + { |
| 287 | + "name": "huntingqueries-text", |
| 288 | + "type": "Microsoft.Common.TextBlock", |
| 289 | + "options": { |
| 290 | + "text": "This solution installs the following hunting queries. After installing the solution, run these hunting queries to hunt for threats in Manage solution view. " |
| 291 | + } |
| 292 | + }, |
| 293 | + { |
| 294 | + "name": "huntingqueries-link", |
| 295 | + "type": "Microsoft.Common.TextBlock", |
| 296 | + "options": { |
| 297 | + "link": { |
| 298 | + "label": "Learn more", |
| 299 | + "uri": "https://docs.microsoft.com/azure/sentinel/hunting" |
| 300 | + } |
| 301 | + } |
| 302 | + }, |
| 303 | + { |
| 304 | + "name": "huntingquery1", |
| 305 | + "type": "Microsoft.Common.Section", |
| 306 | + "label": "Lookout Advanced Threat Hunting - Multi-Vector Attacks", |
| 307 | + "elements": [ |
| 308 | + { |
| 309 | + "name": "huntingquery1-text", |
| 310 | + "type": "Microsoft.Common.TextBlock", |
| 311 | + "options": { |
| 312 | + "text": "Identifies devices experiencing multiple threat types within a short timeframe, indicating coordinated attacks This hunting query depends on LookoutAPI data connector (LookoutEvents Parser or Table)" |
| 313 | + } |
| 314 | + } |
| 315 | + ] |
180 | 316 | } |
181 | 317 | ] |
182 | 318 | } |
183 | 319 | ], |
184 | 320 | "outputs": { |
185 | 321 | "workspace-location": "[first(map(filter(basics('getLAWorkspace').value, (filter) => and(contains(toLower(filter.id), toLower(resourceGroup().name)),equals(filter.name,basics('workspace')))), (item) => item.location))]", |
186 | 322 | "location": "[location()]", |
187 | | - "workspace": "[basics('workspace')]", |
188 | | - "workbook1-name": "Lookout", |
189 | | - "workbook2-name": "LookoutEventsV2", |
190 | | - "workbook3-name": "LookoutSecurityInvestigationDashboard" |
| 323 | + "workspace": "[basics('workspace')]" |
191 | 324 | } |
192 | 325 | } |
193 | 326 | } |
0 commit comments