VaikoraVaikora

Vaikora › Blog › Product Updates

How Cyren email security works inside your own Azure subscription, with no MX record change

Product Updates · Nov 22, 2026 · 3 min read

Routing your mail through a third-party filtering service means trusting that service with every message your organization sends and receives. Cyren's Microsoft 365 email security takes a different approach: analysis runs on a virtual machine inside your own Azure subscription, connected through Microsoft Graph, with results reported into your own Sentinel workspace.

What the architecture actually does

The filtering VM lives in your environment. No MX record change is required, which means you are not re-routing mail through external infrastructure to get protection. The integration reads mail via Microsoft Graph API, inspects it, and writes findings back to your Sentinel workspace.

That matters for two reasons. First, your message content never leaves the boundary you control. Second, the Sentinel workspace where alerts land is the same one your SOC already works in, so there is no separate console to watch.

What Cyren is inspecting

Cyren's detection runs on the GlobalView telemetry network, which processes over a billion email, URL, and file transactions a day. That scale matters because phishing infrastructure is frequently visible in that telemetry during the staging window, before a campaign is weaponized against your users.

When a message arrives, Cyren checks the sender, embedded URLs, and attachments against that live telemetry. A URL that was registered two hours ago and matches known malicious infrastructure patterns gets flagged before anyone clicks it.

The specific threat types covered:

How findings reach your SOC

Because the Sentinel integration is native, detections appear as analytic rule alerts in the workspace your analysts already use. Cyren ships through the Microsoft Sentinel Content Hub as a packaged solution: a CCF connector, analytic rules, hunting queries, and workbooks. You are not writing custom parsers or mapping fields by hand.

The workbooks give you a view of volume, verdict distribution, and trend data. The hunting queries let an analyst pivot from a specific indicator into related messages or infrastructure without leaving Sentinel.

Indicators from Cyren also push into CrowdStrike Falcon and SentinelOne, so a URL or file hash identified in email can automatically propagate to endpoint enforcement. A phishing link seen in a message this morning can be blocked at the endpoint layer before a user encounters it through a different channel.

A concrete scenario

An attacker registers a domain and sets up a credential-harvesting page. They send 40 messages to employees over three hours, low enough volume to avoid bulk-sending heuristics. The domain is new, so reputation lists do not flag it yet.

Cyren's GlobalView telemetry has seen the infrastructure during staging. When the first message arrives, the embedded URL resolves to a known-malicious hosting pattern. The analytic rule in Sentinel fires, the alert lands in the queue, and the URL indicator pushes to Falcon and SentinelOne. Employees who have not yet opened the message are protected at the endpoint even if the message itself was delivered.

That detection sequence happens without anyone touching a configuration file and without mail leaving your Azure environment.

What to check before you deploy

A few operational questions worth answering before you install:

The Microsoft Graph connection requires specific application permissions in Entra ID. Scoping those permissions to only what the inspection service needs, rather than broad mail read access, is worth doing at setup time rather than retrofitting later.

Once the VM is deployed and Graph permissions are granted, the Sentinel content hub deployment handles the connector, rules, and workbooks as a single package.

Review the analytic rules after deployment. The defaults are a reasonable starting point, but tuning them to your mail patterns, expected sender domains, and internal relay behavior will reduce noise in the first week.

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

More from the Vaikora blog