Vaikora AI Agent Signals to CrowdStrike

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

Back to Content Index


This playbook polls Vaikora for AI agent behavioral signals (high or critical risk actions and anomaly detections) and pushes them as Custom IOCs to CrowdStrike Falcon for detection and prevention.

Attribute Value
Type Playbook
Solution Vaikora-CrowdStrike-ThreatIntelligence
Source View on GitHub

Logic App Connectors

This playbook uses 1 Logic App connector / built-in action:

Connector / Action Type Connections Actions
http Built-in 0 3
Action parameters (URLs, paths, function IDs)

http (Built-in)

Action Method Endpoint Other
Get_CrowdStrike_Token POST @{parameters('CrowdStrike_BaseUrl')}/oauth2/token
Get_Vaikora_Actions GET @{parameters('Vaikora_BaseUrl')}/actions?agent_id=@{parameters('VaikoraAgentId')}&per_page=100
Post_IOC_to_CrowdStrike POST @{parameters('CrowdStrike_BaseUrl')}/iocs/entities/indicators/v1?ignore_warnings=true

Additional Documentation

📄 Source: readme.md

Vaikora CrowdStrike Threat Intelligence

Publisher: Data443 Risk Mitigation, Inc. Solution ID: azure-sentinel-solution-vaikora-crowdstrike Version: 3.0.0

What This Does

A Microsoft Sentinel Content Hub solution that polls Vaikora for AI agent behavioral signals and pushes high-risk actions and anomaly detections into CrowdStrike Falcon as Custom IOCs. The Logic App playbook runs on a schedule, filters to actions where risk_level is high or critical, or where is_anomaly is true, then calls the CrowdStrike Custom IOC API to create or update indicators.

Signal Mapping

Vaikora risk_level CrowdStrike severity CrowdStrike action
critical critical prevent
high high detect
medium / low medium detect

Tags applied automatically:

IOC type is resolved from the action fields: ip_address or target_ipipv4, url or target_urlurl, fallback → domain.

Each IOC sets external_id to vaikora-{action_id} for deduplication.

Prerequisites

Files

Playbooks/VaikoraToCrowdStrike_Playbook.json   Standalone ARM template for the Logic App
Playbooks/Images/                              Deployment screenshots
Data/Solution_VaikoraCrowdStrike.json          Solution manifest
Package/mainTemplate.json                      Content Hub deployment template
Package/createUiDefinition.json                Deployment wizard UI definition
SolutionMetadata.json                          Publisher and category metadata
ReleaseNotes.md                                Change history

Deployment

Via Content Hub

Install from Microsoft Sentinel Content Hub. Search for "Vaikora CrowdStrike".

Via ARM template (standalone)

az deployment group create \
  --resource-group <your-rg> \
  --template-file Playbooks/VaikoraToCrowdStrike_Playbook.json \
  --parameters \
      VaikoraApiKey="<your-vaikora-key>" \
      VaikoraAgentId="<your-agent-id>" \
      CrowdStrike_ClientId="<cs-client-id>" \
      CrowdStrike_ClientSecret="<cs-client-secret>" \
      CrowdStrike_BaseUrl="<cs-base-url>"

Post Deployment

  1. Configure the Vaikora API Key and Agent ID parameters
  2. Configure the CrowdStrike Client ID, Client Secret, and Base URL parameters
  3. Enable the Logic App and adjust the recurrence trigger as needed

Test Evidence

Screenshots from a deployment to a test workspace:

Support

Data443 Risk Mitigation, Inc., support@data443.com


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

Back to Playbooks · Back to Vaikora-CrowdStrike-ThreatIntelligence