Vaikora › Blog › Product Updates
How Vaikora adds a runtime enforcement gate to Microsoft 365 email without an MX record change
Microsoft 365 email security gaps are rarely gaps in Microsoft's filtering. They appear in what happens after a message clears the platform's default checks: credential-harvesting links that look clean at delivery, attachments that detonate later, and policy violations that Microsoft's native controls were never configured to catch. The question for most security teams is where to add an enforcement layer without rebuilding mail routing.
How the architecture works
Vaikora's email security for Microsoft 365 runs on a virtual machine inside the customer's own Azure subscription. It connects to Exchange Online through Microsoft Graph. No MX record change is required, so mail routing stays exactly as it is.
The analysis happens on that VM, inside the customer's tenant boundary. Mail does not leave the customer's environment to reach a third-party scanning cloud. All telemetry and findings report into the customer's own Microsoft Sentinel workspace, not a shared vendor dashboard.
This matters for two reasons. First, data residency stays under the customer's control. Second, the entire detection and enforcement record lands in Sentinel alongside every other signal the SOC already works with, so investigation does not require pivoting between platforms.
What gets inspected
The connection through Microsoft Graph gives Vaikora read access to messages as they arrive. Each message passes through content inspection: URLs are evaluated against threat intelligence, attachments are checked, and content is assessed against the policy rules configured in the Vaikora Control Plane.
The policy decision is deterministic. The same input produces the same output every time, which is what makes the audit record meaningful. Every decision is written into a SHA-256 hash-chained, tamper-evident audit log. If an auditor or investigator needs to reconstruct what happened to a specific message on a specific date, the record is there and cannot be altered after the fact.
For compliance teams working toward SOC 2, HIPAA, GDPR, PCI DSS, or ISO 27001, Vaikora ships presets for all five frameworks. The preset defines which content rules and enforcement thresholds apply. That reduces the configuration work for teams that need demonstrable policy alignment without building rule sets from scratch.
What the SOC sees
When Vaikora identifies a high-severity threat in an email, it promotes that finding into Azure Security Center and Microsoft Defender for Cloud as a native incident. No custom engineering is required. The incident appears in the same queue where analysts handle other Defender and Sentinel alerts.
This is different from a sidecar dashboard or a separate portal. The alert is native, so triage, assignment, and response follow the same workflow the team already uses.
For teams that also run SentinelOne or CrowdStrike Falcon, Vaikora pushes AI agent threats as Threat Intelligence indicators with severity mapping: Critical at 100, High at 75, Medium at 50, Low at 25. That allows automated enforcement at the endpoint layer based on what Vaikora found in the mailbox.
A concrete scenario
An employee receives a message containing a URL that resolved to a clean page at delivery. Two hours later, the destination changes to a credential-harvesting form. This is a standard staging technique: the link is benign at the moment most mail security checks it, then becomes malicious after delivery.
Vaikora's enforcement does not rely solely on point-in-time URL reputation. The finding, once detected, writes to the audit log immediately, and the severity-mapped indicator pushes downstream to Sentinel and connected enforcement platforms. The SOC can see the event, trace the message, and act without waiting for a user to report a suspicious page.
The audit trail captures the full decision sequence: what was inspected, what policy rule applied, what the enforcement outcome was, and when it happened. That chain is tamper-evident from the first entry.
What to check next
If you are evaluating this configuration, two things are worth verifying before you deploy. First, confirm that the Microsoft Graph permissions scoped to the Vaikora VM are as narrow as the integration requires. Graph permissions have a wide blast radius if over-scoped. Second, check that your Sentinel workspace retention settings match your compliance requirements before the first findings land there. Findings written to a workspace with a 30-day retention window are not useful for a SOC 2 audit that looks back 12 months.
The Vaikora-AzureSecurityCenter solution is available in the Azure Sentinel content hub. That is the fastest path to a working configuration if your team is already operating in Azure.
See Vaikora enforce policy on your AI
Open-core AI runtime control. Self-host the MIT gateway free, or run the hosted Control Plane.
Get a demo Self-host the gateway
Vaikora