What’s important in Cloud Hardening & Tenant Hardening

Azure environments, Microsoft 365, and other similar services aren’t secure just by default! We offer you a concise, practical overview of the most important facts about Cloud Hardening, as well as Tenant and Azure Hardening.

The cloud is now essential

Hardly any company today operates its IT infrastructure exclusively with its own servers in the basement or its own hardware in a data center. Microsoft 365, Azure, AWS, SAP S4/HANA, or the Google Cloud Platform: Cloud services are now the norm. This approach can lead to greater efficiency and cost savings. However, it also brings new challenges, for example in the area of cybersecurity.

When you adopt a cloud service “out of the box,” you typically receive a configuration designed for ease of use and rapid productivity – but not for maximum security. This is exactly where Cloud Hardening comes in.

Definition: What is Cloud Hardening?

Cloud Hardening refers to the process of significantly reducing the attack surface of a company’s cloud systems and services through Secure Configuration.

The principle is the same as with any hardening process: Anything that is not explicitly needed is removed, disabled, or configured restrictively. This is because outdated applications, as well as unnecessary programs, account functions, applications, ports, permissions, and access points, can be exploited by hackers. The fewer such vulnerabilities there are, the smaller the overall attack surface becomes.

What are the goals of Cloud Hardening?

Microsoft describes the purpose of hardening in the Azure Well-Architected Framework as follows:

“Security hardening is an intentional self-preservation exercise. The goal is to reduce an attack surface and increase attackers’ costs in other areas, which limits opportunities for malicious actors to exploit vulnerabilities.”

This statement applies equally to both On-Premises and Cloud Hardening. Whether you are hardening individual workstations, Windows Servers, or cloud infrastructures, the primary objective should be to make your systems more resilient against attacks. After all, in today’s landscape, it is no longer a question of *if* your systems will be attacked, but *when*!

In these attempts, hackers look for known vulnerabilities – or, as the BSI (German Federal Office for Information Security) puts it, seek to secure “easy prey.” With the aid of AI malware, this process is now faster than ever. Professional Cloud Hardening typically causes such standard attacks to fail. Furthermore, if “cyber-criminals” do manage to compromise a cloud system, hardening measures can slow them down. This provides the SOC with more time to detect the attacks and initiate appropriate countermeasures.

Another objective of Cloud Hardening is to enhance information security, thereby preventing costly and complex consequences such as production downtime, data theft, or PR disasters. Additionally, it ensures compliance with regulatory requirements. An increasing number of IT laws, regulations, and standards – such as NIS2 and DORA -, mandate the comprehensive hardening of all systems.

Cloud Hardening vs. System Hardening: What’s the difference?

System Hardening serves as the foundational template. It involves creating a sensible, tailored hardening configuration. For instance, by combining various established hardening standards. This process entails removing unnecessary services, ports, protocols, accounts, and software, disabling unused features, and restricting access rights to the absolute minimum required.

Using hardening tools – such as Enforce Administrator – this configuration can then be applied in an automated and scalable manner across large, complex IT environments, complete with continuous monitoring and the automatic remediation of any deviations.

⏬ Download: Enforce Administrator
Product Brochure (PDF)

Cloud Hardening applies this principle to a cloud environment and expands upon it. This is because the target object there is a tenant, which includes subscriptions (or accounts), resource groups, directory services, policies, interfaces, and a multitude of individual services. Consequently, hardening a cloud environment involves working far more at the platform’s configuration and management layers than at the level of individual machines.

Cloud Hardening therefore encompasses areas such as the shared responsibility model, policies, cloud-native controls, Infrastructure as Code, self-service capabilities, and APIs. Nevertheless, it must always be kept in mind that a virtual machine in Azure or an EC2 instance in AWS is still an operating system that requires a “traditional” hardening. Cloud Hardening serves as an additional layer on top of this.

What is Tenant Hardening?

For most companies, Cloud Hardening begins where daily work takes place: within their own SaaS tenant – most notably in Microsoft 365. Tenant Hardening refers to the targeted securing of this tenant through the systematic review and strengthening of all security-relevant settings.

A hardened tenant is configured deliberately to strike a balance between usability and security. This is necessary because self-service features, guest access, and automated app access create vulnerable targets that can quickly become a risk if left unaddressed. A step-by-step approach is therefore advisable: first secure identities, then implement controls for collaboration, applications, and data.

When it comes to Tenant Hardening in particular  – and System Hardening in general – the following holds true: there is no such thing as 100% hardening! While such a state might make the systems secure, it would likely also make them unusable.

What makes Azure Hardening so unique?

Azure Hardening involves the targeted securing of a Microsoft Azure environment through the Secure Configuration of all its constituent layers. While System Hardening focuses on securing individual servers, Azure hardening centers on the platform’s core management and control layers.

In concrete terms, this means: in Entra ID, you secure user access – for example, through multi-factor authentication and conditional access. Privileged administrative rights are granted only on a temporary basis via Privileged Identity Management. Furthermore, Azure Policy ensures that any new resources comply with the organization’s security standards from the very outset.

As such, Azure Hardening is a specific subset of Cloud Hardening, characterized by its own unique features and challenges. Implementing it professionally requires expert knowledge and specialized tools. Without these, the process can become both lengthy and costly.

Conclusion

Cloud Hardening extends the established principles of System Hardening to the new layers inherent in cloud environments. This includes, for example, focusing on tenants rather than individual machines, as well as addressing identities and policies, which serve as the primary attack surface. It is crucial to understand this is not a one-off project! The hardening of both on-premise and cloud environments must be continuously monitored, adjusted, and documented. A requirement often mandated by regulatory standards, cyber insurance policies, and auditors.

Managing the entire lifecycle of professional System Hardening – from conceptualization and implementation to monitoring and optimization- is extremely labor-intensive if done manually. A more efficient approach is to implement Cloud, Tenant, or Azure Hardening using a tool-based solution. One such solution is Enforce Administrator, which enables the hardening of large, complex IT landscapes – ranging from individual workstations to entire server fleets. In the near future, this hardening tool will also offer comprehensive Cloud Hardening capabilities.

Do you have any further questions?

Would you like to learn more about System Hardening in general, or Cloud Hardening in particular? Are you interested in how to professionally execute and implement (automated) System Hardening within your organization? Get in touch with us! Our experts are here to help!

💬 Contact us!

Image: Magnific AI

Leave a Reply