Coming Soon. The Nessus integration is in active development. Everything on this page describes how it will work when it ships. Want early access? Email us.
Integration · Coming Soon

Nessus findings, side-by-side with your Microsoft 365 scans

Export a Nessus scan, feed the report to Siemserva, and your vulnerability findings land in the same dashboard, HTML report, and MCP graph as your Microsoft 365 and Entra ID findings. One compliance map. One place to triage.

Senserva Trustworthy AI

Vulnerability data, in the same place as the rest of your posture

A Nessus .nessus or CSV export is a big list. Siemserva normalizes it into the same finding shape as a native Microsoft 365 and Entra ID scan, links hosts and CVEs into the graph, and applies the same Senserva Trustworthy AI treatment, same compliance mapping, same MCP tools.

One dashboard, one report

Nessus findings tagged Source=Nessus show up in the same live TUI dashboard and HTML report as native Microsoft 365 checks. No second console. Filter by severity, host, plugin family, or CVE right next to your Entra ID gaps.

siemserva-win-x64.exe --reporter --ai

CVE graph, KEV-aware

Each Nessus plugin lands as a node linked to its host and CVEs. Siemserva enriches from NVD and CIRCL, flags CISA KEV matches, and stitches the result into the same graph your native scans use. Claude can traverse it over MCP.

Node_Cve + Node_Host + Edge_HostCve

Ask Claude across sources

Run Siemserva as an MCP server and ask Claude questions that span everything: "Which Nessus Critical findings touch a host with a privileged Entra user? Show KEV CVEs on internet-facing VMs." Claude reads the same graph Siemserva's native scans populate.

siemserva-win-x64.exe mcp. 28 tools. stdio transport

Three steps to a unified report

Run your Nessus scan the way you always do. Export the result. Hand it to Siemserva alongside your Microsoft 365 scan.

STEP 1

Export from Nessus

From Nessus Professional, Tenable.io, or Tenable.sc, export the completed scan as a .nessus file or CSV. Both formats are supported.

STEP 2

Convert to Siemserva

Use the SDK's ConvertFrom-Nessus.ps1 helper to emit the shared wire format every Siemserva source uses. Source tag: Nessus.

STEP 3

Render anywhere

Pipe to siemserva-win-x64.exe --reporter for HTML, add --dashboard for the live TUI, or add --ai for Senserva Trustworthy AI summaries.

powershell. nessus-import.ps1
# Option 1. Full HTML report
PS> .\ConvertFrom-Nessus.ps1 -Path scan.nessus -Stdout `
| siemserva-win-x64.exe --reporter --out nessus-report.html --ai
# Option 2. Live dashboard alongside a Microsoft 365 scan
PS> .\ConvertFrom-Nessus.ps1 -Path scan.nessus -Stdout `
| siemserva-win-x64.exe --dashboard --tenant yourtenant.onmicrosoft.com

Need the converter or want to wire a different scanner? The SDK covers the wire format, source tagging, and graph writing. See the SDK.

Senserva Trustworthy AI on Nessus data

Every Nessus finding, AI-enriched for reporting and remediation

Add --ai and the same Trustworthy AI that analyzes your Microsoft 365 and Entra ID findings runs across your Nessus vulnerability data. Nothing leaves your machine that you did not consent to, every AI response is validated against the rules engine, and every number in the report traces back to a CVE in the local graph.

Executive narrative

Top risks summarized for leadership: which CVEs are in CISA KEV, which hosts carry the most severe exposure, and how the vulnerability picture overlays your identity and device posture.

Remediation per finding

Every Nessus finding gets a remediation write-up: the fix in plain language, the vendor patch ID when known, and a ready-to-run script when one fits. Validated against the rules engine before it reaches your team.

Ask Claude across sources

With the MCP server running, Claude can answer questions that span Nessus CVEs, Entra ID identities, and Intune devices in one natural-language prompt. "Show me KEV CVEs on hosts owned by a Global Admin" is one question, not three queries.

Claude Desktop + Siemserva + Nessus

Point Claude Desktop at the Siemserva MCP server and get the full power of Claude working over the combined Nessus and Microsoft 365 graph. Natural-language investigation across CVEs, identities, devices, and compliance frameworks in one conversation. A game changer for anyone who has spent a day cross-referencing a vulnerability scanner against an identity portal.

Turn AI off and Siemserva still delivers every Nessus finding and fix. AI is an accelerator, not a dependency. See how Trustworthy AI stays trustworthy in the Claude integration guide.

Nessus + Microsoft 365, in one report

Stop pivoting between a vulnerability console and an identity console. Let Siemserva stitch them together, enrich the CVEs, and hand the result to Claude. This integration ships soon, email us to get early access.

Request early access Get Siemserva See the SDK
From the blog

Reading from the Senserva team.

Latest post

Read the Senserva blog

Microsoft 365 and Entra ID security commentary, research notes, and behind-the-scenes posts from the Senserva team.
Recent

Architecture and check deep-dives

How Siemserva is built, how the graph is modeled, and how Senserva Trustworthy AI turns raw findings into validated answers.
From the team

Research, releases, and customer stories

New posts from the Senserva team. Subscribe on blog.senserva.com or follow along for the latest.
See all posts