Sentinel Integration

Prev Next

The Silent Push for Microsoft Sentinel solution brings Silent Push preemptive cyber defense data into Microsoft Sentinel. Once installed, you can ingest Silent Push Indicators of Future Attack (IOFAs) into Log Analytics and use Silent Push actions in Logic Apps playbooks for enrichment and automation.

The solution installs:

  • 1 data connector that ingests Silent Push IOFA feeds into the SLP_Feeds_CL table

  • 1 custom Azure Logic Apps connector (SilentPush-API) that exposes Silent Push API actions in the playbook designer

  • 4 playbook templates for domain and IP feed enrichment (sample and full versions)

Key Features

  • Daily ingestion of Silent Push Data Export feeds into Log Analytics

  • 49 ready-made Silent Push actions in Logic Apps, including domain/IP enrichment (single and bulk), threat checks, PADNS and Live Scan searches, and feed management

  • Prebuilt playbook templates that export a feed, enrich indicators with Silent Push data, and add them to Sentinel Threat Intelligence with risk scores

  • Support for hunting, analytics rules, and workbooks against ingested Silent Push data

Benefits

  • Automatically enrich Sentinel incidents, alerts, and indicators with high-fidelity Silent Push context

  • Reduce manual pivots by bringing IOFA feeds and enrichment actions directly into your existing Microsoft Sentinel workflows

  • Build custom automations without writing code using drag-and-drop Silent Push action blocks

  • Keep threat intelligence current with daily feed pulls and scheduled playbook enrichment

Requirements

  • An Azure subscription with permission to create resource groups, deployments, and Log Analytics workspaces

  • Access to the Silent Push for Microsoft Sentinel listing in the Microsoft Marketplace

  • A Silent Push API key (sign up at app.silentpush.com)

  • A resource group (created in Step 1) and a Microsoft Sentinel workspace (created in Step 3)

Installation

Installation takes four steps. Deploy the custom connector before installing the solution—the playbooks depend on it.

Step 1: Deploy the Custom Connector

  1. Open the Silent Push for Microsoft Sentinel listing.

  2. Under IMPORTANT, click Deploy Custom Connector.

  3. On the Custom deployment page, select your subscription and the resource group from Step 1, then complete the deployment.

  4. Open the resource group, select Deployments, and confirm the custom connector deployment shows a status of Succeeded.

Important: Deploy the custom connector into the same resource group as the playbooks, and keep its name as SilentPush-API. The playbooks will not connect if the resource group or the name is different.

Step 2: Install the Solution

  1. Return to the Silent Push for Microsoft Sentinel listing and click Get it now.

  2. On the Create Silent Push for Microsoft Sentinel page, select your subscription, resource group, region, and the workspace from Step 3.

  3. Click Review + create, then Create.

  4. Wait for the message Your deployment is complete.

Using the Integration

Open your Microsoft Sentinel workspace. Under Configuration, you will find the Silent Push data connector and automation components.

Ingest IOFA Feeds

The SilentPush Feeds data connector pulls a Silent Push Data Export feed into the Log Analytics table SLP_Feeds_CL.

  1. Under Configuration, select Data connectors. Select SilentPush Feeds and click Open connector page.

  2. In the Silent Push console, open Data Export. On the feed you want to ingest, click Automate Export and select CSV. Note the data source (category in the path) and the feed file name (CSV file at the end of the endpoint).

  3. Back on the connector page, complete the fields and click Connect:    

    Field

    What to enter

    Example

    API key

    Your Silent Push API key

    (hidden)

    Data source

    The feed category exactly as it appears in the Data Export API endpoint

    iofa-exports

    Feed file name

    The CSV file name at the end of the Data Export API endpoint

    loader_offloader_domains.csv

  4. Confirm the connector status shows Connected, then click Go to log analytics.

  5. In Logs, switch to KQL mode if needed and query:    

    SLP_Feeds_CL | take 1000

Note

Indicators can take up to an hour to appear after you connect the feed. The connector then polls every 24 hours and ingests the full export each time, so an indicator can appear once per day.

Enrich Data with Logic Apps Playbooks

Under Configuration, select Automation. You can start from a Silent Push playbook template or build your own playbook with Silent Push actions.

Important: Create playbooks in the same resource group as the Silent Push custom connector, and keep the connector name as SilentPush-API.

Option A: Start from a playbook template

Silent Push provides domain and IP export enrichment templates (Sample and Full). Full templates run every 24 hours: they export a feed, enrich the indicators, and upload them to Microsoft Sentinel Threat Intelligence with Silent Push risk scores.

  1. Select the Playbook templates tab, select a Silent Push template, and click Create playbook.

  2. Select your resource group and click Next.

  3. On the Parameters tab, keep CustomConnectorName as SilentPush-API. For WorkspaceName, enter the name of the workspace where the integration is installed.

  4. Continue through the remaining tabs and click Create playbook.

Before you turn a playbook on:

  1. Add your API key. Open the playbook, go to API connections, select the Silent Push connection, choose Edit API connection, paste your Silent Push API key, and click Save.

  2. Choose the feed. Open the playbook in the Logic app designer, select Export Domains (or Export IP), and fill in export_category and file_name with the Silent Push feed to process. Click Save.

Option B: Build a blank playbook

  1. Click Create, then select Blank playbook.

  2. On the Create Logic App page, select your resource group, enter a name and region, then click Review + create.

  3. When the deployment completes, open the playbook in the Logic Apps designer and add actions from the SilentPush-API connector.

For the latest Silent Push API details or additional feed options, refer to the Silent Push console and API documentation.