Vaikora AI Agent Signals for Microsoft Defender for Cloud
Data443 · Cybersecurity & IT
Certification per Microsoft Marketplace.
Evidence tier Source Confirmed · 7 captures on record
What the publisher says
As described on Microsoft Marketplace.
The Vaikora AI Agent Signals connector for Azure Security Center ingests AI agent behavioral signals from Vaikora into Microsoft Defender for Cloud.
The connector polls the Vaikora API every 6 hours for high-risk agent actions, anomalies, and detected threats. It filters signals where severity is high or critical, an anomaly is flagged, a threat is detected, or the Vaikora policy decision is "block". Qualifying signals are written to a custom Log Analytics table (Vaikora_SecurityAlerts_CL) that Defender for Cloud analytic rules continuously monitor.
Show the rest of the publisher’s description (7 more lines)
Each signal carries behavioral anomaly scores across seven risk dimensions: action type risk, agent profile risk, temporal risk, environmental risk, behavioral risk, compliance risk, and data sensitivity risk. Signals also include the Vaikora policy decision (allow, block, or flag) and a tamper-proof audit hash for log integrity verification.
Included analytic rules:
- Vaikora - High Severity Security Alerts — triggers on any high or critical severity agent action in the last 6 hours (Severity: High)
- Vaikora - Anomaly Detection — triggers on behavioral anomaly or threat detection below the high/critical threshold (Severity: Medium)
- Vaikora - Feed Outage Detection — triggers when no signals are received within the expected polling window (Severity: Low)
Prerequisites: Active Vaikora account with API key, Azure Log Analytics workspace (workspace ID and primary key required), Logic App Managed Identity granted Monitoring Metrics Publisher role on the DCR.
Built by Data443 Risk Mitigation, Inc. — data443.com | vaikora.com
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Compliance
- FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27
Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.
Vendor
External enrichment
Sources
Publisher resources
2 linksLinked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.