Hardening Microsoft 365 to BSI IT-Grundschutz: which modules apply
Key takeaways
- The IT-Grundschutz Compendium (Edition 2023) of the German Federal Office for Information Security (BSI) has no dedicated module for Microsoft 365. Module APP.5.3 explicitly excludes pure cloud solutions such as Microsoft 365 and refers to OPS.2.2 Cloud Usage.
- For a Microsoft 365 tenant you model OPS.2.2 together with ORP.4, CON.1, CON.3, OPS.1.1.5, DER.1 and the client and mobile device modules.
- Most technical requirements are implemented with Conditional Access, Intune, Defender and central logging. For requirement OPS.2.2.A13, Microsoft provides a C5 report.
- Grundschutz++ is gradually replacing the Compendium. According to the BSI milestone plan, certification applications based on Grundschutz++ are possible from 1 January 2027, and certification against the existing IT-Grundschutz ends on 30 November 2031.
Public authorities, municipalities and many critical infrastructure operators in Germany follow the BSI IT-Grundschutz baseline, whether for an ISO 27001 certification based on IT-Grundschutz or as the benchmark for the state of the art. Anyone using Microsoft 365 quickly hits a gap during modelling: there is no module that describes the tenant as a whole. This article shows which modules to use instead, what the central requirements look like in Microsoft 365 and what the new Grundschutz++ changes.
Is there an IT-Grundschutz module for Microsoft 365?
No. The module list of Edition 2023 includes APP.5.2 Microsoft Exchange and Outlook and APP.5.3 General E-Mail Client and Server, but no module for Microsoft 365. In its scope section, APP.5.3 states that pure cloud solutions, such as those that are part of Microsoft 365, are not covered. General requirements for them are found in module OPS.2.2 Cloud Usage.
In practice, OPS.2.2 provides the frame for the service. The concrete protection of identities, devices, logs and data follows from the cross-cutting modules you model anyway.
Which modules apply to Microsoft 365?
The module titles below are English renderings of the German originals (Bausteine).
| Module | Relevance to Microsoft 365 |
|---|---|
| OPS.2.2 Cloud Usage | Strategy, security policy, division of responsibilities, provider selection, contract, contingency plan and exit for the Microsoft 365 service |
| ORP.4 Identity and Access Management | User accounts, administrator roles, multi-factor authentication in Microsoft Entra ID |
| CON.1 Crypto Concept | Encryption of devices, transport and documents |
| CON.3 Backup Concept | Backup of mailboxes, OneDrive and SharePoint |
| OPS.1.1.5 Logging | Unified audit log, Entra logs, central storage |
| DER.1 Detection of Security-Relevant Events | Defender alerts, analysis, central detection |
| DER.2.1 Handling Security Incidents | Incident process based on Defender and Sentinel incidents |
| SYS.2.1 General Client, SYS.2.2.3 Clients under Windows | Managed devices on which Microsoft 365 is used |
| SYS.3.2.1 General Smartphones and Tablets, SYS.3.2.2 Mobile Device Management | Mobile devices and their management with Intune |
| APP.1.1 Office Products | Office apps on the devices |
How do you implement the central requirements in Microsoft 365?
The letter after each requirement shows whether it belongs to basic (B), standard (S) or elevated protection needs (H).
OPS.2.2 Cloud Usage
OPS.2.2.A4 Definition of responsibilities and interfaces (B). Write down what Microsoft is responsible for, what your IT is responsible for and what an external provider covers. In practice this is a role matrix: who holds which Entra administrator role, who approves changes to Conditional Access, who responds to Defender alerts?
OPS.2.2.A13 Evidence of adequate information security in cloud usage (S). The requirement explicitly names the BSI C5 criteria catalogue and ISO/IEC 27001 as possible bases. Microsoft provides a C5 Type 2 report for Microsoft 365 and its ISO 27001 certificates in the Service Trust Portal. Check whether the scope covers the services you use, and file the reports with a date.
OPS.2.2.A14 Orderly termination (S) and OPS.2.2.A16 Performing your own backups (H). Both address the same question: can you get your data out without Microsoft, and can you restore it? Microsoft 365 Backup or a third-party solution answers the second part. CON.3.A15 already requires regular testing of backups at the basic level.
OPS.2.2.A11 Contingency plan for a cloud service (S). Plan for the case that Microsoft 365 or sign-in through Entra ID is unavailable, or that an administrator account has been compromised. This includes at least two emergency access accounts that are excluded from Conditional Access and whose sign-ins are monitored, a contact list outside the tenant and a communication channel that works without Teams and Exchange.
ORP.4 Identity and Access Management
ORP.4.A10 Protection of user IDs with extensive privileges (S) requires multi-factor authentication for privileged accounts. In Entra ID you implement this with a Conditional Access policy for all administrator roles and the “Phishing-resistant MFA” authentication strength. ORP.4.A21 Multi-factor authentication (H) extends this to all accounts. How to roll out Conditional Access without locking anyone out is covered in a separate article.
ORP.4.A4 Task distribution and separation of duties (B) is implemented with restricted Entra roles instead of the Global Administrator role and with separate administrator accounts. Time-limited rights through Privileged Identity Management require Entra ID P2. ORP.4.A24 Four-eyes principle for administrative tasks (H) can be partly reflected through approval requirements for role activation in Privileged Identity Management.
Logging and detection
OPS.1.1.5.A3 Configuration of logging (B) means in Microsoft 365: check that the unified audit log is active and mailbox auditing has not been turned off. OPS.1.1.5.A6 Central logging infrastructure (S) and OPS.1.1.5.A8 Archiving (S) are met by routing Entra and Intune logs to a Log Analytics workspace via diagnostic settings and setting a retention period there. Without this step, Entra sign-in logs are deleted after 30 days with Entra ID P1 or P2, and after seven days with the free tier. OPS.1.1.5.A10 Access protection for log data (S) is handled through permissions on the workspace.
DER.1.A5 Use of built-in system functions for detection (B) is covered in Business Premium by Defender for Business and Defender for Office 365 Plan 1, whose alerts are correlated into incidents in the Defender portal. DER.1.A11 Use of a central logging infrastructure for analysis (S) usually leads to a SIEM such as Microsoft Sentinel.
Devices and cryptography
For SYS.2.2.3, SYS.3.2.2 and CON.1, Intune is the central tool: compliance policies requiring BitLocker and a minimum operating system version, security baselines, and Conditional Access that only admits compliant devices. Sensitivity labels with encryption from Microsoft Purview add protection at document level. If elevated protection needs call for your own keys, you need Customer Key or Double Key Encryption; neither is included in Business Premium.
What changes with Grundschutz++?
The BSI is developing IT-Grundschutz into Grundschutz++. The methodology is described in BSI Standard 300-1; the requirements are in the Grundschutz++ user catalogue in what the BSI calls its state-of-the-art library, which replaces the IT-Grundschutz Compendium. Three changes matter for Microsoft 365 environments:
- The requirements are machine-readable, so checks can be automated, including against configuration data from the tenant.
- The user catalogue only describes solution-neutral requirements. Mapping them to Entra ID, Intune and Defender remains your task.
- According to the BSI, the previous protection levels (basic, standard, elevated) are replaced by flexible performance figures with dynamic thresholds.
On timing, the BSI milestone plan (as of October 2026) states: from 1 January 2027, applications for ISO 27001 certification based on Grundschutz++ can be submitted. An early adopter phase starts in the first quarter of 2027 and runs until the end of 2027. Certification against the existing IT-Grundschutz ends on 30 November 2031. Until then, IT-Grundschutz remains applicable during the transition period.
Our recommendation: if you are preparing a certification today, model against Edition 2023 and keep the mapping from requirement to setting in a separate table. You will carry this mapping over to Grundschutz++ later. The settings in the tenant do not change because the methodology does.
Next step
Our Microsoft 365 hardening implements the technical requirements of ORP.4, OPS.1.1.5 and DER.1 and documents each setting with a reference to the requirement. For public authorities and municipal bodies, our public sector page describes how we approach this.
Frequently asked questions
Is Microsoft 365 compatible with IT-Grundschutz?
Yes, if you model the service via OPS.2.2 and implement the cross-cutting modules. IT-Grundschutz does not prohibit cloud services. It requires a deliberate decision, clear responsibilities and evidence, such as the provider’s C5 report.
Do we have to switch to Grundschutz++ immediately?
No. The existing IT-Grundschutz remains applicable during the multi-year transition and, according to the BSI milestone plan, can be certified until 30 November 2031. Plan the switch anyway, so your documentation does not have to be rebuilt from scratch.
What do B, S and H mean for the requirements?
They mark basic requirements, standard requirements and requirements for elevated protection needs. In the standard protection approach that underlies an ISO 27001 certification based on IT-Grundschutz, you implement basic and standard requirements. For elevated protection needs, the H requirements indicate additional measures for the risk analysis.
Is there a BSI recommendation specifically for Microsoft 365?
There is no dedicated IT-Grundschutz module for Microsoft 365. For assessing the provider, OPS.2.2 refers to recognised evidence such as C5 or ISO/IEC 27001. You derive the configuration decisions in the tenant from the cross-cutting modules.
Book an introductory call