🚫 [DEPRECATED] Lookout

🚫 Deprecated: This connector has been deprecated and may be removed in future versions.

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

Attribute	Value
Connector ID	`LookoutAPI`
Publisher	Lookout
Used in Solutions	Lookout
Collection Method	Azure Function
Connector Definition Files	Lookout_API_FunctionApp.json
Ingestion API	HTTP Data Collector API — Azure Function code uses SharedKey/HTTP Data Collector API
Custom Log V1 Tables	Yes 🔶 — ingests into tables with type-suffixed columns

The Lookout data connector provides the capability to ingest Lookout events into Microsoft Sentinel through the Mobile Risk API. Refer to API documentation for more information. The Lookout data connector provides ability to get events which helps to examine potential security risks and more.

NOTE: This data connector has been deprecated, consider moving to the CCF data connector available in the solution which replaces ingestion via the deprecated HTTP Data Collector API.

Tables Ingested

This connector ingests data into the following tables:

Table	Transformations	Ingestion API	Lake-Only
`Lookout_CL` 🔶	?	✓	?

💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.

Permissions

Resource Provider Permissions: - Workspace (Workspace): read and write permissions on the workspace are required. - Keys (Workspace): read permissions to shared keys for the workspace are required. See the documentation to learn more about workspace keys.

Custom Permissions: - Microsoft.Web/sites permissions: Read and write permissions to Azure Functions to create a Function App is required. See the documentation to learn more about Azure Functions. - Mobile Risk API Credentials/permissions: EnterpriseName & ApiKey are required for Mobile Risk API. See the documentation to learn more about API. Check all requirements and follow the instructions for obtaining credentials.

Setup Instructions

⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.

NOTE: This Lookout data connector uses Azure Functions to connect to the Mobile Risk API to pull its events into Microsoft Sentinel. This might result in additional data ingestion costs. Check the Azure Functions pricing page for details.

NOTE: This data connector depends on a parser based on a Kusto Function to work as expected LookoutEvents which is deployed with the Microsoft Sentinel Solution.

STEP 1 - Configuration steps for the Mobile Risk API

Follow the instructions to obtain the credentials.

STEP 2 - Follow below mentioned instructions to deploy the Lookout data connector and the associated Azure Function

IMPORTANT: Before starting the deployment of the Lookout data connector, make sure to have the Workspace ID and Workspace Key ready (can be copied from the following). - Workspace ID: WorkspaceId Note: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel. - Workspace Key: PrimaryKey Note: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.

3. Azure Resource Manager (ARM) Template

Follow below steps for automated deployment of the Lookout data connector using an ARM Template.

Click the Deploy to Azure button below.

2. Select the preferred Subscription, Resource Group and Region.

NOTE: Within the same resource group, you can't mix Windows and Linux apps in the same region. Select existing resource group without Windows apps in it or create new resource group. 3. Enter the Function Name, Workspace ID,Workspace Key,Enterprise Name & Api Key and deploy. 4. Click Create to deploy.

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

↑ Back to Connectors Index