The short version
MDM.Plus has urgently released Anti-Bypass Lock 2.0 in response to iOS 27 vulnerabilities being actively exploited against rental fleets. We want to be direct about the trade-off: this may be a short-lived feature, and it does add real friction for merchants and end users. Our position is that until an official system-level fix actually lands, customer device assets cannot be left to "it will probably be patched soon."
Why a defence was needed now
For an ordinary user, a system flaw is one line in a release note. For a rental operator, the same flaw becomes a concrete asset loss once it is weaponised. That gap drove this release. Anti-Bypass Lock 2.0 is not a marketing add-on and not a feature we want to keep forever; it is a line of defence that had to be closed quickly under current risk conditions.
Stricter policies change how devices are used: some operations now need extra management steps, and end users must adapt. Merchants absorb more support and after-sales cost. We do not downplay this. Before shipping, the question we debated most was how far to trade convenience for lower asset risk. Doing nothing would have been the cheapest choice in the short term, but risk does not disappear because it is ignored.
What we can and cannot decide
- Not ours to decide: when Apple ships a fix, when a flaw appears, when an exploit is picked up.
- Ours to decide: whether to act while customer assets are exposed — we chose to act.
Building a feature with a possibly short lifecycle is not economically attractive: it means re-studying attack paths, testing across OS environments, adjusting management policies, and coordinating support and business teams, then handling compatibility issues and feedback after launch. Our measure was not how long the feature would survive, but whether, while it exists, it helps a merchant avoid a real loss.
Boundaries and the way forward
No single control permanently resolves risk. Operating systems change, flaws are found and fixed, and attack methods evolve; today's measure may need adjustment tomorrow. We have never claimed 100% security. Anti-Bypass Lock 2.0 adds one line of defence, not a promise that risk is over.
In fact we hope it becomes unnecessary. If Apple closes the underlying risk at system level, we will reassess and gradually remove restrictions no longer needed. Inconvenience can be solved through product refinement and process changes; an asset loss is far harder to reverse. That is why, at this stage, we put device-asset security first.
The final scope is subject to the confirmed product specification and service agreement. Technical background: http://www.mdm.plus/hangye/397.html and http://www.mdm.plus/hangye/402.html.
