← Back to blog

Microsoft 365 Security Assessment: From Secure Score to CREST

October 12, 2026
Microsoft 365 Security Assessment: From Secure Score to CREST

A Microsoft 365 security assessment identifies tenant misconfigurations across identity, data, apps and endpoints, and returns a prioritised, verifiable remediation plan. Start with a Microsoft Secure Score and Compliance Manager snapshot, then run a targeted expert review of identity and access controls. Where you need external assurance or hands-on fixes, bring in a CREST-accredited assessor to produce evidence you can act on.

Solusec
solusec.co.uk
Validate Your Microsoft 365 Security
Solusec provides CREST-accredited penetration testing and practical, expert-led advice to help identify vulnerabilities and strengthen your security posture.
Explore penetration testing

Key Takeaways

A comprehensive Microsoft 365 security assessment covers all tenant areas, provides prioritized, verifiable fixes, and ensures compliance through expert validation and continuous monitoring.

PointDetails
Identify tenant gapsConduct a thorough review of identity, data, security, endpoints, and operation controls to uncover misconfigurations and vulnerabilities.
Use native signals smartlyPull Microsoft Secure Score, Compliance Manager, and telemetry logs to establish a baseline and track improvements over time.
Automate and manual checkingCombine automated configuration checks with manual reviews of high-risk areas like privileged roles and sharing defaults for accuracy.
Prioritize quick winsImplement fast fixes such as multi-factor authentication enforcement and legacy protocol blocks to reduce immediate risk.
Engage accredited assessorsWork with CREST-accredited professionals for an objective, validated view and to produce audit-ready evidence.

Table of Contents

What a Microsoft 365 security assessment actually covers

A thorough assessment works through five areas of the tenant, not just a single setting or report. Each area has its own checks, and skipping one tends to leave the biggest gaps unaddressed.

  • Identity and access management: Entra ID role assignments, privileged access, conditional access policies and multi-factor authentication coverage across all accounts.
  • Data governance: sensitivity labels, data loss prevention rules and external sharing controls for OneDrive, SharePoint and Teams.
  • Security hardening: tenant-wide settings, Exchange Online protections and service configuration checked against NCSC-aligned baselines and CIS benchmarks.
  • Devices and endpoints: Microsoft Defender for Endpoint posture, patching cadence and compliance policy enforcement.
  • Operations: audit logging coverage, alerting rules and how well Microsoft 365 telemetry feeds into a SIEM or monitoring workflow.

Enterprise tenants add a further layer: service account hygiene, third-party app permissions and app governance review, since over-permissioned OAuth grants are a common blind spot that native dashboards rarely surface clearly.

What Microsoft's own tools measure, and where they fall short

Before any manual review, pull the native signals Microsoft already generates. They are free, always on, and give you a baseline to measure improvement against.

  • Microsoft Secure Score aggregates recommended actions across identity, apps and devices into a single comparative number, with each action weighted by its relative impact.
  • Microsoft Purview Compliance Manager runs pre-built, risk-based assessments against standards such as ISO 27001, GDPR and NIST CSF, calculating an initial score from a Microsoft 365 data protection baseline.
  • Audit logs and Defender for Cloud Apps telemetry fill in the operational picture: sign-in anomalies, app usage patterns and policy violations over time.

Completed Secure Score actions typically take 24 to 48 hours to reflect in the score, so do not expect instant confirmation after a change. Treat the score as a relative measure rather than a risk verdict: a tenant can gain points from cosmetic fixes without meaningfully reducing exposure, so conditional access and privileged role changes need direct verification, not just a score delta.

The assessment process: scope, phases and realistic timelines

A repeatable process starts with a clearly written scope: tenant boundaries, in-scope services, data types covered and a sample of accounts that represents both normal users and administrators.

  1. Discovery and inventory: catalogue licences, connected apps, administrative roles and data repositories.
  2. Automated checks: pull Secure Score, Compliance Manager scores and configuration baselines.
  3. Manual configuration review: examine conditional access logic, privileged role assignments and sharing defaults that automation tends to misread.
  4. Vulnerability checks: test authentication flows, legacy protocol exposure and external attack surface.
  5. Reporting and remediation planning: document findings with evidence and a prioritised action list.

A small organisation with a single tenant and under 50 users can usually complete this in a few working days; a multi-domain enterprise with legacy hybrid identity can take several weeks. Add time afterwards for remediation validation and a short re-assessment once fixes land, since some changes need a full business cycle to confirm they hold.

Turning findings into a remediation plan that sticks

Not every finding deserves the same urgency. Rank issues by business impact, how easily they could be exploited and how many accounts or how much data they expose, then work through the list in that order.

  • Quick wins: enforce multi-factor authentication for all administrative accounts, block legacy authentication protocols and tighten conditional access rules.
  • Medium-term actions: roll out app governance policies, apply data loss prevention rules and sensitivity labels, and restrict default external sharing settings.
  • Long-term: build continuous monitoring, integrate with Microsoft Sentinel, and schedule recurring re-assessments alongside periodic penetration tests.

Pro Tip: Map every remediation item back to a specific Secure Score or Compliance Manager action and capture a configuration snapshot before and after, so you have evidence the fix actually took effect rather than just a changed number.

Our Active Directory security assessment playbook walks through how to apply this same prioritisation logic to hybrid identity environments, where on-premises AD and Entra ID controls need to align.

Active Directory and Entra ID controls aligning

Mapping findings to certification and compliance requirements

Assessment output is only useful if it connects to the frameworks your organisation is actually measured against. Cyber Essentials and the NCSC cloud security principles are the two most common reference points for UK-facing businesses, and most Microsoft 365 findings map cleanly onto one or the other.

  • Multi-factor authentication gaps map directly to Cyber Essentials requirements, where MFA is now a hard requirement rather than a recommendation, as covered in our piece on the Cyber Essentials v3.3 changes.
  • Broad external sharing, new processing activities, or features like Copilot that touch large volumes of organisational data warrant a data protection impact assessment, with privacy teams involved early rather than after deployment.
  • Keep audit evidence organised as you go: exported logs, configuration snapshots and a remediation log with dates, since certification bodies and auditors ask for exactly this.
  • Bring in an external certification body or a CREST-accredited assessor once internal findings need independent verification, particularly for Cyber Essentials, IASME Cyber Assurance or similar formal certifications.

Tools and playbooks that speed up the audit

Community scripts and open-source repositories can accelerate the inventory stage, pulling tenant configuration, role assignments and sharing settings into a reviewable format far faster than clicking through admin portals manually.

  • Bulk inventory and Secure Score snapshots are where automation earns its keep, cutting hours of manual lookups down to minutes.
  • Contextual privilege review is where automation runs out of road. Deciding whether a given admin role assignment is actually justified for that person's job still needs a human who understands the organisation.
  • Our Azure penetration testing guidance covers detection patterns using Microsoft Graph and Azure PowerShell that are directly reusable when reviewing Microsoft 365 tenant activity.

Why an accredited assessor changes the outcome

Our assessment methodology and our certification decisions both sit under independent scrutiny. We also run cloud security assessments for Azure environments and publish technical playbooks covering Active Directory and Azure detection patterns that guide the manual checks automation cannot do alone.

An expert engagement gives you validated findings rather than a raw tool output, a remediation plan ranked by actual business risk, and a retest to confirm fixes hold once applied.

Independent verification matters because an internal team marking its own homework, or an MSP reviewing the environment it manages, has an inherent conflict of interest.

Our piece on why your MSP isn't the best judge of your own security goes into this conflict in more detail.

How we support your Microsoft 365 assessment

Solusec

If your Secure Score review or internal audit has turned up more questions than answers, we offer a direct route to clarity rather than another dashboard to interpret. Our cloud security assessments for Azure pair with penetration testing and Cyber Essentials gap analysis and certification to give you a prioritised remediation plan, verification once fixes are applied, and hands-on remediation support where you need an extra set of hands. Get in touch through our penetration testing services page to scope an assessment for your tenant.

FAQ

How do I know if a Microsoft security alert is real?

Genuine Microsoft security notifications appear inside the Microsoft 365 admin centre or Defender portal, never as unsolicited phone calls or emails asking you to click a link or share credentials. Verify any alert by logging into the admin centre directly rather than following a link, and cross-check it against your Secure Score or Compliance Manager dashboard before acting on it.

What are the security checklists for Microsoft 365?

A practical checklist covers identity and access controls, data sharing and loss prevention settings, tenant hardening, device compliance and audit logging, aligned to the NCSC's cloud security principles. Our own Cyber Essentials checklist breaks these down into certification-ready requirements for the 2026 standard.

What does a security assessment include?

A Microsoft 365 security assessment includes a review of identity and access management, data governance, tenant hardening, endpoint security and monitoring, backed by Secure Score and Compliance Manager data. It ends with a prioritised remediation plan and, where needed, formal evidence suitable for certification or audit purposes.

What are the 5 steps of security risk assessment?

The typical sequence is discovery and inventory, automated configuration checks, manual review of high-risk settings, vulnerability testing and reporting with remediation planning. Each step builds on the last, so skipping the manual review stage is the most common reason automated assessments miss real risk.

How long does remediation validation take after fixes are applied?

Most Secure Score and Compliance Manager updates reflect within 24 to 48 hours of a change being made. A full re-assessment to confirm fixes hold under normal operating conditions is usually scheduled a few weeks later, giving the organisation time to generate real activity against the new settings.

Sources

This article was created with assistance of AI. We never use AI with your data unless given explicit permission.