top of page

How Do I Know Whether My Microsoft 365 Tenant Is Properly Hardened?

Writer: Kyle Cira
Kyle Cira
Nov 5
7 min read

Your organization relies on Microsoft 365 for email, collaboration, file storage, identity management, and potentially much more.


But how confident are you that your Microsoft 365 environment is properly secured?


Maybe your IT team configured security settings when Microsoft 365 was first deployed.

Perhaps your managed service provider (MSP) performed a security hardening project a few years ago. Or maybe you're not entirely sure what security measures are currently in place.


The question isn't simply whether your Microsoft 365 tenant has been hardened. It's whether it has been hardened recently, against a recognized security standard, and in a way that addresses your organization's actual risks.


Let's explore how to determine where your environment stands and what you should do next.


1. Start With a Microsoft 365 Security Assessment


If you're unsure about the security posture of your Microsoft 365 tenant, a comprehensive security assessment is an excellent starting point.


A proper assessment should answer three important questions:


  • What's already secured? Identify which security controls are implemented and operating as intended.

  • What's missing? Determine which recommended security controls are not implemented or only partially implemented.

  • What should we fix first? Prioritize remediation based on risk, potential impact, and current threats.


At Redeemer Cyber, our Microsoft 365 Security Assessment evaluates approximately 180 security controls, including recommendations from the CIS Microsoft 365 Foundations Benchmark and our own security guidance.


The assessment provides an objective view of your environment's alignment with established security best practices, along with a prioritized remediation roadmap.


Rather than simply telling you that your tenant needs improvement, we identify the specific gaps and explain which ones deserve attention first.


An assessment tells you where you stand. Remediation is what improves your security posture.


2. If You've Already Had Hardening Performed, Ask These Questions


Perhaps your organization recently completed a Microsoft 365 security hardening project.


That's great! But how do you know whether the work was comprehensive?


Start by asking your IT team, MSP, or security provider:


  • What security standard was used? Was the work aligned with the CIS Microsoft 365 Foundations Benchmark, Microsoft's recommendations, or another documented security baseline?

  • Which version of the standard was used? Security recommendations evolve, so the version matters.

  • How many controls were evaluated? Did the engagement cover the entire Microsoft 365 environment or focus on a handful of settings?

  • How many controls were fully implemented? Were any controls partially implemented, deferred, or excluded?

  • Were any controls not implemented due to licensing or business requirements? If so, were those decisions documented?

  • When was the last assessment or remediation performed?


Ideally, you should have documentation showing exactly which controls were evaluated, their implementation status, and any exceptions.


If you can't answer these questions, you may not have a clear picture of how comprehensively your Microsoft 365 tenant was hardened.


And even if the work was comprehensive at the time, that doesn't mean your environment remains aligned with today's recommendations.


3. Microsoft 365 Hardening Is Not a One-Time Project


One of the biggest misconceptions about Microsoft 365 security is that hardening only needs to happen once.


Microsoft 365 is constantly evolving.


Microsoft introduces new security features, modifies existing capabilities, and occasionally changes how security settings operate. Meanwhile, attackers continue developing new techniques to compromise identities, steal data, and bypass existing protections.


The CIS Microsoft 365 Foundations Benchmark typically receives updates twice per year, introducing new or revised security recommendations.


Consider what that means for an organization that hardened its tenant two years ago but hasn't revisited its security configuration since.


Several benchmark releases may have occurred during that period. New controls may have been introduced, existing recommendations may have changed, and previously unavailable security capabilities may now be supported.


Over time, an organization can accumulate dozens of security gaps relative to the latest benchmark, even if its original hardening project was successful.


That's why we recommend reviewing new benchmark releases and performing corresponding remediation approximately every six months.


This doesn't necessarily mean repeating an entire security assessment every six months.


If you already have a comprehensive assessment and remediation baseline, subsequent engagements can focus on newly introduced controls, updated recommendations, configuration drift, and emerging threats.


The goal is to maintain the security posture you've already invested in.


4. Security Standards Need to Keep Up With Emerging Threats


Following an established security benchmark is an excellent foundation.


But security standards aren't necessarily updated as quickly as the threat landscape changes.


Attackers continuously develop new techniques, and artificial intelligence is accelerating certain aspects of cybercrime, including phishing, social engineering, and the creation of convincing malicious content.


Waiting for every new security recommendation to appear in a published benchmark may leave organizations exposed to risks that can already be addressed.


That's one reason Redeemer Cyber maintains its own internal Microsoft 365 security benchmark.


Our internal controls supplement established CIS recommendations and allow us to evaluate additional security configurations that we believe deserve attention.


These recommendations are informed by our hands-on experience assessing and remediating Microsoft 365 environments, Microsoft's evolving security capabilities, and developments in the threat landscape.


We also regularly submit our proposed controls and improvements to the Center for Internet Security (CIS) for consideration.


Our goal isn't to keep useful security knowledge proprietary forever.


When we identify a security improvement that could benefit the broader community, we want organizations everywhere to benefit, whether they become Redeemer Cyber customers or not.


We've already had security recommendations adopted into the CIS Microsoft 365 Foundations Benchmark, and we continue contributing to its development.


5. Be Cautious With One-Click Automated Remediation


Automated Microsoft 365 security tools can be incredibly useful.


They can quickly evaluate configuration settings, identify certain security gaps, and sometimes implement recommended changes with minimal effort.


But there's an important distinction between automating a configuration change and safely remediating a production environment.


Imagine an automated tool identifies 40 missing security controls and offers to implement all of them with a single click.


Sounds convenient, right?


Unfortunately, implementing security controls without understanding their operational impact can cause significant problems.


For example, changing Conditional Access policies could inadvertently block legitimate users or administrators. Restricting external sharing could disrupt collaboration with customers and partners. Disabling certain authentication methods could break applications or business processes that still depend on them.


These are legitimate security improvements, but they require planning.


Just because a security control can be implemented automatically doesn't mean it should be implemented without oversight.


We recommend a controlled remediation process that includes:


  1. Reviewing each finding and understanding its purpose.

  2. Evaluating the organization's business requirements and technical dependencies.

  3. Prioritizing controls based on risk and potential impact.

  4. Testing potentially disruptive changes before enforcing them.

  5. Implementing changes in manageable phases.

  6. Validating that the controls work as intended.


Automation can accelerate this process, but expert oversight helps ensure the security improvements don't unnecessarily disrupt business operations.


This is especially important for identity, authentication, privileged access, and Conditional Access controls.


6. Not Every Security Control Can or Should Be Fully Implemented


Here's another important consideration.


A properly hardened Microsoft 365 environment does not necessarily mean 100% of every security benchmark is implemented.


Every organization has different business requirements, licensing, technical dependencies, and risk tolerances.


For example:


  • An organization may require external sharing to collaborate with customers or vendors.

  • A legacy application may temporarily depend on an authentication method that should otherwise be restricted.

  • Certain security capabilities may require Microsoft 365 licensing that the organization doesn't currently have.

  • A recommended control may create operational challenges that outweigh its risk-reduction benefit in a particular environment.


These situations don't automatically mean the organization has failed at security.


They mean the recommendation needs to be evaluated in context.


Sometimes the right decision is to implement a control exactly as recommended. Other times, a compensating control, phased implementation, documented exception, or formal risk acceptance may be more appropriate.


What's important is that these decisions are intentional, informed, and documented.


There's a meaningful difference between a security control being overlooked and an organization deliberately deciding not to implement it after evaluating the risks.


A comprehensive security assessment and remediation process should make that distinction clear.


7. How Often Should You Revisit Microsoft 365 Security?


For most organizations, we recommend establishing a recurring Microsoft 365 security review process rather than relying on occasional, reactive hardening projects.


A practical approach looks like this:


Initial Assessment: Establish a comprehensive baseline against the latest applicable CIS Microsoft 365 Benchmark and other relevant security recommendations.


Initial Remediation: Address identified gaps, prioritizing the controls that provide the greatest risk reduction.


Semiannual Hardening: Review new and updated benchmark controls approximately every six months and implement applicable recommendations.


Annual Reassessment: Perform a security assassessment annually to identify configuration drift, validate existing protections, and reassess the overall security posture.


Ongoing Threat Awareness: Evaluate emerging threats and security capabilities between benchmark releases when meaningful new risks arise.


This approach allows organizations to maintain their Microsoft 365 security posture without repeatedly starting from scratch.


At Redeemer Cyber, this philosophy is reflected in our three-step approach:


Assess. Remediate. Maintain.


So, Is Your Microsoft 365 Tenant Properly Hardened?


If you don't know the answer, that's a good reason to investigate.


And if you believe your environment is already hardened, consider whether you can confidently answer these questions:


  • Which security standard and version is your environment aligned with?

  • How many security controls have been evaluated?

  • Which controls are fully implemented, partially implemented, or not implemented?

  • Which missing controls represent the greatest risk?

  • When was your last security assessment or remediation?

  • What's your plan for addressing new security recommendations as they emerge?


If you can't answer most of these questions, you may not have the visibility needed to confidently assess your Microsoft 365 security posture.


And remember, security hardening isn't a finish line. It's an ongoing process.


Ready to Find Out Where Your Microsoft 365 Security Stands?


Redeemer Cyber specializes in Microsoft 365 Security Assessments, Remediation, and ongoing M365 Assurance services.


Our assessments evaluate approximately 180 security controls and provide a prioritized roadmap to help organizations address their most important security gaps.


Whether your tenant has never been formally assessed, was hardened several years ago, or recently completed a remediation project, we can help you understand where you stand and determine the appropriate next steps.


Don't assume your Microsoft 365 tenant is secure simply because it was configured or hardened in the past.


 
 
 

Comments


bottom of page