The CoreView Zone

Presented for your approval: a US-based global bank migrating to the cloud, preparing to edge out of the safe harbour of their on-premise environment into the ocean of the cloud, due to Microsoft’s sunsetting key services. Rightly cautious, the bank first creates a test tenant, a cloud-based replication of their on-premise environment.

They will soon discover how warranted their caution was, because in the meantime, Microsoft releases an update. In the cloud tenant, the update is applied automatically, and one tiny security setting is changed; a single pebble cast into still waters – but a pebble that creates a massively consequential ripple. Within sixty minutes, the test tenant is breached by an attacker.

It’s a tale as old as time – or at least a tale as old as the cloud. Even more concerningly, consider the fact that this breach was caused by a single configuration change in one isolated tenant – how many ripples would a bigger update create, especially if applied to the whole environment? Regardless of an organisation’s size, a single small misconfiguration can cause massive problems, and it can happen a lot faster than you might think.

When an organisation’s Microsoft 365 environment is based on-premise, the organisation has control over which updates to apply. But when an environment is in the cloud, updates can be rolled out and automatically applied before any review can take place on the part of the organisation’s IT team. These updates can potentially change critical settings and create exploitable gaps in your security.

So, we’re presented with a problem. Maintaining an on-premise M365 environment is becoming increasingly unfeasible and, in cases such as the one described, even impossible. But the prospect of putting your enterprise at the mercy of automatic updates and the subsequent security vulnerabilities is an unacceptable risk. You can’t stay in the harbour, but you also can’t stop someone from throwing a pebble, or even a handful of pebbles (or, stretching the metaphor further, a hulking great boulder) into the ocean. What’s the solution?

While Microsoft will inevitably roll out updates, CoreView puts you back in control; no matter how quickly changes happen. With CoreView’s Configuration Manager, IT teams can instantly roll back unwanted updates with a single click, minimising risk and disruption. More importantly, CoreView provides comprehensive visibility into every configuration change: see who made it, precisely when and why, so you can audit and address issues before they become threats.

Instead of being at the mercy of automatic updates and invisible changes, CoreView empowers your organisation to proactively manage, monitor, and secure your Microsoft 365 environment. This not only protects against breaches caused by misconfigurations, but also supports compliance and operational resilience – no matter how turbulent the cloud “ocean” may become.

Book your demo below:

CoreView – Kite Distribution

Don’t forget to join us soon for the next instalment in our CoreView Zone series, where we’ll be diving headfirst into a subject that we’d all rather not think about: disaster recovery.