Cloud identity hardening
Privileged directory roles, risky configuration, and Conditional Access — including MFA required directly or through an authentication strength. Risky users are read from Identity Protection on tenants licensed for it.
Cloud posture — plus the collaboration layer where data actually leaks.
Cloud posture is more than infrastructure. Most day-to-day data exposure happens in the collaboration layer — a sharing link, a permissive default, a team nobody owns. This module reads cloud identity, cloud resources in Azure and Oracle Cloud, and Microsoft 365 together and shows where the posture is weakest. Each source works on its own, so an organisation on Oracle Cloud or Azure alone is covered without connecting a directory.
Privileged directory roles, risky configuration, and Conditional Access — including MFA required directly or through an authentication strength. Risky users are read from Identity Protection on tenants licensed for it.
Exposure, hardening and compliance of cloud services across subscriptions, with resources that share a name across resource groups kept apart.
For an estate that publishes through one path — DNS, perimeter firewall, web application firewall, application — three checks find what reaches the Internet some other way: an App Service whose own address, or whose deployment site, accepts connections from anywhere; an App Service bound to a domain that isn't one of yours, typically a supplier's; and an Azure public address on a gateway, cluster, virtual machine or load balancer that is neither behind nor published by the perimeter firewall.
Tenancy administrators and who is granted what, multi-factor and sign-in policy, long-lived credentials, security rules that open management ports to the Internet, public storage buckets, logging and monitoring switched off, and load balancers and their listeners. Identity checks cite the CIS Oracle Cloud Infrastructure Foundations Benchmark.
Whether the service backs each database up, and where its listener can be reached from. Each container database lists its pluggable databases, with how each is open and whether a database audit reaches it — and coverage is judged per pluggable database, not only per container. A database audited from the inside by Database Security is linked to the Oracle Cloud database it is.
Sites, drives and teams inventoried across SharePoint Online, OneDrive and Teams, with dedicated explorers alongside the findings they produce.
Where content is shared outside the organization, which links exist and how permissive they are — and tenant-level sharing settings evaluated against best practice, so a permissive default is caught once, at the tenant, rather than one site at a time.
Each with the evidence behind it, not just a severity label.
A built-in explainer on every finding — what it is, why it matters, what to do.
Rolled up from the findings and trended over time.
Findings mapped to the framework controls they evidence.
A check that guesses produces false findings, and false findings teach a team to ignore the real ones. These are the places this module holds back.
Findings from this module evidence the configuration, access-control and cloud-hardening control areas of every activated framework.
Licensed on its own, and on the same platform as every other module. We'll show you the answer — and what it would say it couldn't measure.