How an African Manufacturer Closed the Gap Between Device Enrolment and Real Endpoint Security
The Assumption That Almost Cost Them
A large fast-moving consumer goods manufacturer, operating across multiple African markets and running a mobile-first sales force of several thousand devices, believed its endpoint environment was under control.
Their outsourced IT team had enrolled the devices on Microsoft Intune.
IT had a platform.
On paper, that looked like protection.
It wasn’t. Enrolment is a registration event, not a security outcome. And the gap between the two is exactly where breaches happen.
Microsoft’s own research attributes 80–90% of successful ransomware attacks to unmanaged devices, and a 2025 industry survey found 48% of organisations suffered a data breach traced to an unsecured or unmanaged personal device in the past year.
A car can have every safety feature engineered into it, but you still put your seatbelt on before you drive. Enrolling a device on Intune is the car. The policies are the seatbelt.
Organisations taking Endpoint management seriously are proactively managing the risk and the serious penalties and costs relating to such data breaches are a reality in South African IT environment:
- POPIA’s maximum administrative fine is R10 million, and the most serious breaches carry criminal liability of up to 10 years’ imprisonment for the responsible party.
- The Information Regulator has already issued its first fine (R5m, against the Department of Justice) specifically for inadequate technical security measures.
- Breach notifications to the Regulator rose roughly 40% year-on-year into 2025/2026 – enforcement is visibly accelerating, so “eventually” is becoming “soon.”
- IBM’s 2025 Cost of a Data Breach report puts the average breach cost to a South African organisation at R44.1 million.
What the Environment Actually Looked Like
This is a pattern Torch sees repeatedly across large African multinationals: organisations hold the licences, and devices are technically “on” the platform, but the environment was never properly scoped, built and rolled out. The enrolment project happened; the governance detail didn’t.
After an event, the CIO wanted the mobile environment assessed by specialists.
Torch was called, and the findings were inconsistent with that of a fully managed and governed environment:
- The MDM platform was missing the configuration profiles and compliance policies needed to actually enforce a secure environment – no mandatory PIN, no multi-factor authentication, no restriction on copying corporate data into personal apps.
- 15% of the devices were unmanaged. Hundreds of eligible sales users, along with other non-provisioned support staff, were not registered on the right platforms at all – a significant population of unknown, unmanaged and ungoverned devices, carrying corporate data and applications. Corporate email and apps. Unmanaged, is not just a housekeeping gap, typically, that’s where the attack starts.
- No enrolment structure existed to enable the different ways people actually work – Sales, Support, Back-Office, BYOD, VIP and the user groups were all being treated the same or, not treated at all.
None of this would show up as a single dramatic failure. It would show up the way these things always do: as a finding in an IT or security audit, as the entry point for a breach that traces back to a device nobody was managing properly.
Best Practice, Applied to a Real Environment
Torch’s response was not another go at a generic Intune rollout project. It combined Microsoft best practice with a working understanding of this client’s environment – its sales organisation structure, its multi-country footprint, its existing application estate, in order to design a solution that raised security without disrupting the field teams who depend on their devices to work uninterupted.
The engagement followed three phases:
- Audit and gap analysis: a rapid assessment against Microsoft best practice and the client’s actual compliance requirements, delivered in days, not months.
- Blueprint design: a build architecture covering the operational administration model (scope tags, RBAC, groups), enrolment profiles for every user type, a Conditional Access baseline, and application protection policies.
- Phased rollout: pilot, user acceptance testing, wave-based production deployment, VIP transition, hyper-care, and full handover to business-as-usual support, run in parallel across every market the client operates in.
Every configuration profile, compliance policy and Conditional Access rule was purpose-built for this client’s environment, not a template applied and left to drift, but a governed build with clear ownership from day one.
From Exposed to Governed
The client moved from an environment where enrolment created a false sense of security to one where every device is actively governed: enforced PIN and multi-factor authentication, controlled data flow between corporate and personal apps, defined policies for every user population from head office to the sales van, and a clear operational model for keeping it that way as the fleet grows.
The unmanaged sales population, previously invisible to IT and to any audit, was brought onto the platform with the same policy enforcement as every other device in the estate.
The Lesson for Every Enterprise Running Any EMM Platform
This client is not unusual. Torch regularly encounters organisations that hold the licences and have done the hard work of enrolling devices, but have never had the environment properly scoped, built and governed. Under a security audit, that gap is indefensible, and increasingly, it’s the gap attackers are looking for.
IBM’s 2025 data shows third-party and supply-chain compromise is now the single leading breach cause (17% of incidents, R29.6m average cost) — and a distributed sales fleet on personally-influenced devices behaves exactly like that exposure category, even though it’s internal.
Don’t fall into the trap of assuming enrolment equals protection. Investing in the exercise of scoping, building and governing your endpoint environment is far cheaper than the alternative.
If your organisation has enrolled devices on any EMM platform, and you’re not certain the policies behind that enrolment would hold up under audit, that’s exactly the question Torch’s Unified Endpoint Security Management practice exists to answer.
Your audit and gap analysis can be on the table in days. Your build blueprint – the design that actually closes those gaps – within days after that. Then we roll out the policies that turn “enrolled” into “fully protected”, before an attacker, an auditor, or the Information Regulator finds the gap first.
Enrolment is the car. Policy is the seatbelt. Don’t wait for the crash to find out your passengers were never wearing one.
Let’s start with the assessment.
Get in touch with us to set up a quick Teams call to discuss your endpoint security and management goals
Every User. Every Issue. Managed Every Day.
torch.co.za | info@torch.co.za
Sources:
- POPIA Compliance Consequences in South Africa
- Bowmans: Information Regulator issues first R5m POPIA fine
- Braintree: POPIA enforcement sharpening in 2026
- IBM Cost of a Data Breach 2025 — South Africa findings
- Hypori: The Hidden Cost of BYOD (VMI Report, 48% breach stat)
- Guardz: 36 Endpoint Security Statistics 2026

