Compliance view, generated automatically
One scan produces the Compliance tab below. Each row is a Microsoft 365, Intune, or Entra ID finding with the framework codes it satisfies (or fails) right next to it. Filter by code, jump to the failing finding, export to HTML, or pipe the same data into Claude over MCP.
Compliance tab in the live dashboard. Same data lands in the HTML report and the MCP tool responses.
What lands in the evidence packet
Compliance is not a list of issues. It is a list of issues with proof. Every Siemserva HTML report ships the four things an auditor asks for on the same finding row, so there is no separate document to assemble after the scan.
Named entity, severity, the specific configuration or gap, and which Microsoft 365 / Intune / Entra ID workload it lives in.
Underlying scan data Siemserva used to reach the conclusion: policy assignment, user properties, sign-in trace, audit-log event, group-membership chain. Reproducible, not synthesized.
MCSB v2 and CISA SCuBA codes attached at the row level on every scan. Ask Claude over the Siemserva MCP to bridge to NIST 800-53, NIST 800-171, ISO 27001, SOC 2, HIPAA, PCI-DSS, CIS Controls, MITRE ATT&CK, and Microsoft ZTA.
A validated, step-by-step fix written by Senserva Trustworthy AI. Where possible, an attached PowerShell script ready for review and apply, plus a re-prove pass after the fix lands.
One scan. One self-contained HTML file. Prints to PDF for the audit packet. Try it on the demo →
Frameworks supported out of the box
Siemserva ships with the mappings already done. Nothing to configure, no separate compliance tool to license. Every native check, plus Maester, Microsoft ZTA, and any of your own PowerShell scripts, lands in the same mapped catalog.
Microsoft Cloud Security Benchmark
31 MCSB v2 controls across Identity, Access, Privileged Access, Posture, Data Protection, Logging, and Incident Response. Maps to Azure baselines and the Microsoft Security Score so your posture column moves the same direction as the M365 admin centers.
IM-1, PA-7, LT-3, DS-2CISA SCuBA Baselines
81 SCuBA codes across MS.AAD (Entra ID), MS.EXO (Exchange Online), MS.SHAREPOINT, MS.TEAMS, MS.DEFENDER, MS.POWERPLATFORM, and MS.INTUNE. The federal baseline the auditor on a public-sector engagement is going to ask for first.
MS.AAD.3.1v1, MS.EXO.2.2v2, MS.TEAMS.6.1v1Microsoft Zero Trust Assessment
ZTA test results land as first-class findings. Same severity model, same remediation language, same dashboard tab. Run the official ZTA tool or let Siemserva run it inline; either way it shows up in the same Compliance view.
Three concrete examples
What a Siemserva finding looks like with the compliance mapping attached. These are not mock-ups: this is the same data shape the dashboard, the HTML reports, and the MCP tools all return.
SCuBA scorecard, one keystroke away
Press C in the dashboard for the SCuBA-by-code scorecard. Every required code, pass or fail, with the count of failing findings and a one-click jump to the offending row. Same view exports to HTML for compliance review packets.