Makwa Global: Driving Defender Secure Score from 71 to 93
How a tribal enterprise federal contractor reduced exposure across its sovereign Microsoft 365 environment in just three months — raising Defender Secure Score by 22 points, improving its SPRS posture, and turning vulnerability management into an operating discipline.
Headline Outcomes
Four measurable results that defined the engagement — from posture score to federal scoring impact.
A 22-point Defender Secure Score lift in three months across the sovereign environment.
Quantified improvement in Supplier Performance Risk System scoring for federal contracting.
Defender for Endpoint tuned, attack surface reduction enforced, and telemetry centralized.
Vulnerability management turned from a project into a sustained operating cadence.
A Sovereign Environment in Place — and a Posture That Needed to Catch Up
Makwa Global had already established a sovereign Microsoft 365 GCC High enclave aligned to DFARS, NIST 800-171, and CMMC. The environment was compliant by design — but compliance posture and operational security posture are not the same thing. Configurations drift, new threats emerge, endpoint hygiene evolves, and Defender Secure Score is a continuous signal, not a one-time configuration outcome.
When Makwa baselined its Defender Secure Score at 71, the implication was clear: the sovereign foundation was in place, but there was meaningful exposure left on the table — endpoint configurations to tighten, attack surface reduction rules to enforce, identity hygiene to improve, and operational practices to standardize. Each gap individually was small. Compounded across a federal contractor workforce handling CUI, they added up.
Makwa’s leadership also recognized a second-order incentive: improving Defender Secure Score wasn’t just an internal security win — it directly influenced their SPRS (Supplier Performance Risk System) posture, which federal customers actively consider when evaluating contractor risk. Vulnerability reduction at the operating layer was both a defense investment and a federal contracting advantage.
Why Leaving the Score at 71 Wasn’t a Neutral Choice
For a federal contractor handling CUI, an exposed Defender Secure Score and an unaddressed vulnerability surface aren’t documentation gaps — they are active risk. Without the remediation engagement, Makwa faced four concrete consequences:
Compounding Endpoint Exposure
Each untightened endpoint configuration, unenforced attack surface reduction rule, and missed Defender recommendation left part of the estate operationally weaker than the compliance documentation suggested.
SPRS Score Drag
A lower operational posture would continue to pull SPRS scoring downward — directly affecting Makwa’s competitive standing across federal contract evaluations.
Reactive, Not Proactive, Defense
Without a structured cadence, vulnerability management would stay reactive — addressing what shows up rather than driving Secure Score upward as a measurable, intentional outcome.
Gap Between Compliance and Operations
A compliant environment with an unmanaged Secure Score creates a paper-vs.-reality gap — exactly the kind of gap auditors, customers, and adversaries notice for very different reasons.
A Cyber Watchtower-Led Vulnerability Remediation Cadence Inside the Sovereign Enclave
Jadex Strategic Group delivered the engagement through its Cyber Watchtower platform — applying a structured, three-month vulnerability remediation cadence focused on driving Defender Secure Score from 71 to a target above 90, while strengthening Makwa’s broader SPRS posture as a downstream benefit.
Baseline Capture and Prioritization
Captured the baseline Defender Secure Score at 71, inventoried every open Defender recommendation, and prioritized actions by exposure reduction, operational risk, and SPRS impact — building a remediation backlog tied to measurable outcomes.
Endpoint Hardening and Attack Surface Reduction
Tuned Defender for Endpoint across the estate, enforced attack surface reduction rules, hardened endpoint configurations, and closed device-level gaps that were the highest-frequency contributors to Secure Score drag.
Identity and Access Tightening
Tightened identity-layer Secure Score recommendations — privileged account hygiene, Conditional Access posture, sign-in risk policies, and legacy authentication exposure — closing identity-side gaps without disrupting the federal workforce.
Data and Collaboration Posture Improvements
Addressed data and collaboration recommendations across SharePoint, OneDrive, and Teams — sharing posture, sensitivity coverage, and DLP enforcement — pulling forward Secure Score wins that also reinforced CUI handling discipline.
Operating Cadence, Reporting, and SPRS Alignment
Established a sustained operating cadence: monthly Secure Score reviews, prioritized backlog refresh, reporting aligned to leadership and SPRS scoring inputs, and documented improvements supporting federal contracting risk reviews.
22 Points in 90 Days — and a Discipline That Outlasted the Project
The Cyber Watchtower vulnerability remediation engagement delivered a measurable Defender Secure Score lift, a stronger SPRS posture, and — most importantly — turned vulnerability management into a sustained operating discipline rather than a one-time push.
Defender Secure Score: 71 → 93
A documented 22-point Defender Secure Score lift in three months — moving Makwa from a moderate posture into a high-performing one across identity, endpoint, data, and collaboration domains.
Improved SPRS Posture
Strengthened SPRS scoring inputs — directly improving Makwa’s competitive risk profile across federal contract evaluations and supply chain risk reviews.
Endpoint Estate Hardened
Defender for Endpoint tuned, attack surface reduction rules enforced, and endpoint configurations tightened — reducing device-level exposure and improving telemetry visibility across the workforce.
Identity-Layer Risk Reduced
Privileged account hygiene, Conditional Access posture, and sign-in risk handling were all tightened — closing identity-side gaps that quietly suppress Secure Score across most environments.
Collaboration Risk Tightened
Sharing posture, sensitivity coverage, and DLP enforcement across SharePoint, OneDrive, and Teams were sharpened — pulling forward Secure Score wins that also reinforce CUI handling discipline.
A Sustained Operating Discipline
Most importantly, vulnerability management became an ongoing operating discipline — monthly Secure Score reviews, prioritized backlog refresh, and leadership reporting — rather than a one-time project that decays the moment the engagement ends.
Compliance got us the environment. Cyber Watchtower got our posture caught up to it — 22 Secure Score points in 90 days, a stronger SPRS profile for federal evaluations, and a vulnerability management cadence we now run as part of how we operate.
Turn Vulnerability Management Into a Measurable Operating Discipline.
Like Makwa, your Microsoft 365 environment may be compliant by design — but is your Secure Score keeping pace with the threats and the expectations? Cyber Watchtower turns vulnerability management into a structured, sustained discipline with measurable outcomes leadership can defend.