Skip to content

A vulnerability found is not a vulnerability closed.

We fix the vulnerability with you, then a before-and-after check confirms it is closed.

  1. Detect
  2. Fix
  3. Prove

Who does what

The same chain for the pentest and the SOC. Each plays its part, from finding to proof.

  1. Detect

    Pentest

    Our pentesters look for your vulnerabilities the way an attacker would.

    24/7 SOC

    24/7 monitoring, plus an audit of your Microsoft 365 every 3 months.

  2. Fix

    Pentest

    The report gives the fix for each vulnerability. You apply it, or we do: this is agreed at scoping.

    24/7 SOC

    Fixing included in all three tiers, on Microsoft 365, in the mode you choose.

  3. Prove

    Pentest

    A retest, included within 60 days of the report.

    24/7 SOC

    A before-and-after check of the fix.

And the PSSI? It has no before-and-after check: it sets the rules for the whole and delivers a prioritized action plan.

Two ways to fix, your choice

You choose who applies the fix. Either way, your IT team stays in control.

We apply the fix for you

With the delegated rights you grant us and can revoke at any time. Every fix we apply is validated by an expert.

or

We hand you the fix ready to apply

Your team applies it at its own pace, with the exact setting to change.

What stays on your side

  • Your application code and vendor patches: we specify the fix, your team or your providers apply it.
  • Outside Microsoft 365 (business applications, servers, equipment): fixed by your IT team, or by us on quotation.

On the SOC side: what happens after the alert

The effect of each fix shows up in the Microsoft Secure Score, an indicator computed by Microsoft.

The score doesn’t rise on its own. It rises because a specific action was taken, and you can name it.

Microsoft Secure Score

Illustrative six-month progression

3080
  1. 40Initial state
  2. 50Month 1
  3. 60Month 3
  4. 70Month 6

+30 points from the initial state

Illustrative values, order of magnitude only: a typical progression for a supported full-cloud tenant. Real gains depend on your starting point; no target score or timeline is guaranteed.

An indicator, not a promise

« Microsoft Secure Score isn’t an absolute measurement of how likely your system or data could be breached, and it shouldn’t be interpreted as a guarantee against security breach in any manner. »
Microsoft Learn, Microsoft Secure Score, “Risk awareness” (new tab)

The work, step by step

Following one recommendation, from finding to proof

Block legacy authentication

7points

Recommendation status : 06Recorded in the monthly report
  1. Framing

    At kick-offDMC DEFENSE

    Initial Secure Score audit

  2. At kick-offDMC DEFENSE

    Action prioritization

  3. At kick-offDMC DEFENSE

    Remediation plan

  4. Execution

    OngoingDMC DEFENSE or your IT team

    Applying the fixes

  5. OngoingDMC DEFENSE

    Verification and validation

  6. Proof

    MonthlyDMC DEFENSE

    Progress reporting

Microsoft scoring: enabling the policy that blocks legacy authentication is worth 7 points (Microsoft Learn, Microsoft Secure Score, accessed 29 September 2026).

Where the points come from

The Secure Score spreads its recommendations across four categories: identity, devices, apps and data.

  • Identity and access

    • Enable MFA for all users
    • Block legacy authentication
    • Set up conditional access
  • Devices

    • Turn on real-time antivirus protection
    • Turn on tamper protection
    • Encrypt disks (BitLocker)
  • Apps

    • Configure anti-phishing rules
    • Enable Safe Links and Safe Attachments
    • Block automatic forwarding of email outside the organization
  • Data

    • Encrypt sensitive email
    • Configure DLP policies
    • Classify confidential data

Each recommendation is worth 10 points or less; exact weightings evolve with Microsoft’s recommendation catalog.

Beyond the score

The Secure Score sets the priorities. Alongside it, we maintain the underlying health of your Microsoft 365 tenant.

  • License optimization

    Spotting underused or missing licenses to get the most security out of your subscriptions.

  • Account cleanup

    Removing inactive accounts, old guests and permissions that have become obsolete.

  • Configuration hardening

    Applying Microsoft best practices beyond the Secure Score recommendations alone.

  • Automation

    Scripts and workflows that keep best practices in place; each one is validated by one of our experts before it is deployed.

  • Tenant documentation

    Up-to-date documentation of every security configuration, ready for audits.

Sources

How the Secure Score works and how it is scored is documented by Microsoft.

Where does your Secure Score stand?

We audit your tenant and show you, in numbers, the points to win back first. No commitment.

Discover Offensive Security

After you send it

  1. Reply within 24 business hours

    An expert reads your request and gets back to you to qualify your need.

  2. Free audit

    On Microsoft 365: a one-hour audit of your tenant's posture (Secure Score, identities, Defender) and your priority flaws. Otherwise: we scope your need (pentest, security policy) and set the price. No commitment.

  3. Dedicated contact

    The same DMC expert follows you end-to-end, with no call-center in between.