Every cloud platform you connect gets its own section in the sidebar under Platforms: Azure / Microsoft 365 and Google Workspace each have a security dashboard, the list of framework requirements the platform can evidence, a coverage map, the findings from the last scan and the scan history. The section answers one question for each connected tenant: which of our requirements does this platform prove today, and where is it letting us down?
A tour of the Azure / Microsoft 365 and Google Workspace sections: dashboard, requirements, map and findings. (65 seconds)
The security dashboard
The top bar shows which tenant is connected (for example your onmicrosoft.com domain or your Workspace primary domain), when the last scan finished, and two actions: Connection opens the integration page and Run scan starts a fresh read-only scan. Below the title, six numbers summarise the last scan:
| Number | What it counts |
|---|---|
| Checks passing | Checks that the last scan evaluated and found in order, out of all checks in the catalogue for this platform. |
| Checks failing | Checks with at least one open finding, split by the highest severity found. |
| Not evaluated | Checks the scanner could not judge: no completed scan yet, or the scanner skipped them (for example there are no Conditional Access policies to evaluate). |
| Open findings | Findings behind the failing checks. Click through to the findings list. |
| Requirements met | Framework requirements whose mapped checks all pass. |
| Requirements at risk | Requirements that are failing or only partially met. |
The Security areas panel groups the checks by theme - Identity and access, Conditional Access, Applications and consent, Tenant posture, Data protection and sharing, Email security and Cross-tenant access for Microsoft 365; MFA, admin accounts, account lifecycle and devices for Google Workspace - and shows how many checks in each area pass. The Frameworks table lists every framework you have enabled with the number of requirements this platform can evidence, a coverage bar, and the count of met, partially met and failing requirements. Open jumps to the requirements list filtered to that framework.
How a check is evaluated
Venvera keeps a catalogue of checks per platform. Each check has a plain statement of what a pass means and a list of the framework requirements it evidences. After each scan the platform status engine turns findings into a verdict per check:
| Verdict | When it is given |
|---|---|
| Fail | The check has an open finding that is not informational. The severity shown is the worst open finding. |
| Pass | For failure-only checks (the Microsoft Graph scanner reports problems only) a completed scan with no finding is a pass. For graded checks (the Google Workspace scanner reports every check) an informational result is a pass. A finding you have marked as accepted or false positive also counts as a pass. |
| Not evaluated | No completed scan yet, the scanner reported that it skipped the check, or a graded check was not part of the last scan. |
Requirements
The Requirements tab lists every requirement of your enabled frameworks that this platform can evidence, with the checks that map to it. A requirement's status is derived from those checks:
- Met - every evaluated check passes.
- Partially met - some checks pass and at least one fails.
- Failing - every evaluated check fails.
- Not evaluated - none of its checks has a verdict yet.
Filter by framework or status (the dashboard's numbers link straight to these filters) and open a requirement to see the check statements, the open findings and the remediation guidance from the scanner.
Map
The Map tab draws the checks on the left and the framework requirements on the right, with a ribbon for every mapping. Failing checks are marked in red, so you can see at a glance which single misconfiguration is holding back the most requirements. The decision list under the map ranks failing checks by the number of requirements they affect, with the action to take: fix the setting in your tenant, or enable a check the scanner skipped. The same map is available under Coverage maps.
Findings, scans and resources
Findings opens the integration's findings list, where each finding carries its severity, the affected object, remediation guidance and the controls it maps to, and where you can attach a finding as evidence or mark it accepted. Scans shows the scan history with status and duration. For Microsoft 365 a Resources tab lists the Azure resources discovered through Defender for Cloud.
Running a scan
In the sidebar, under Platforms, open Azure / Microsoft 365 or Google Workspace.
Click Run scan in the top bar. The scan is read-only and usually finishes within a minute or two; the dashboard refreshes with the new verdicts when it completes.
Open the Map tab, fix the checks at the top of the list in your tenant, and run the scan again to confirm the requirements move to Met.
Google Workspace
The Google Workspace section works the same way. Its scanner grades every check, so the dashboard shows an explicit pass for 2-Step Verification enrolment, super-administrator count, dormant accounts and device compliance rather than inferring a pass from silence. Requirements mapped from these checks cover the access-control, MFA and asset-management clauses of your frameworks.