TL;DR: eSIM adoption is accelerating toward billions of devices, according to Workz Group, but telcos now face profile lifecycle, delegation, and inventory control gaps that manual provisioning cannot absorb at IoT scale. The core risk is governance drift across distributed channels, where profile assignment and ownership must become policy-driven rather than operator-led.
At a glance
What this is: NHI Mgmt Group's analysis, drawing on Workz Group's blog post: eSIM IoT scale turns profile lifecycle management, channel coordination, and delegated provisioning into operational control problems.
Why it matters: It matters to identity and access practitioners because the same governance failure modes seen in IAM, NHI, and privileged delegation appear when telcos hand out and manage eSIM profiles across many parties.
By the numbers:
- More than six billion eSIM-capable devices will be shipped between 2024 and 2028, according to Workz Group.
- Global IoT eSIM connections are expected to rise from 165 million in 2024 to nearly 1.3 billion in 2028, according to Workz Group.
- Seven out of every 10 cellular devices shipped in 2030 will have eSIM, according to Workz Group.
Context
eSIM IoT is the shift from removable SIM logistics to software-managed identity and connectivity provisioning at device scale. The security problem is not simply volume, but the control boundary that appears when many distributors, OEMs, enterprises, and telcos all touch profile issuance, lifecycle management, and inventory.
In practice, this creates a governance gap similar to delegated access in IAM and NHI programmes. If profile ownership, approval, and revocation are distributed across channels without consistent orchestration, the organisation loses clarity over who can provision what, where, and under which policy.
The article argues that telcos can no longer rely on manual fulfilment or narrow profile sets. That starting position is increasingly atypical for a market moving toward automated, multi-channel delivery and bulk management.
Key questions
Q: What breaks when eSIM profile management is still handled manually at IoT scale?
A: Manual profile handling breaks when device volume, device diversity, and channel count rise faster than operators can match profiles, track inventory, and update lifecycle state. The result is delayed delivery, stockouts, and inconsistent fulfilment across distributors, which is why lifecycle orchestration has to replace ad hoc processing.
Q: Why do delegated eSIM channels create governance risk?
A: Delegated channels create risk when partners can provision widely without clear scope, logging, and revocation. The problem is not delegation itself, but standing authority that outlives its business purpose. Telcos need the same discipline they would apply to privileged access in IAM and PAM.
Q: How should telcos prioritise bulk orchestration versus channel expansion?
A: Telcos should prioritise orchestration first when channel growth increases the number of profiles, hand-offs, and inventory decisions. Without automation and real-time state consistency, additional channels only amplify provisioning drift, while a controlled orchestration layer makes expansion operationally sustainable.
Q: What should organisations do when multiple distributors share eSIM management responsibilities?
A: They should define one accountable control plane, require consistent lifecycle state across every distributor, and verify that revocation reaches all downstream systems. Shared responsibility only works when roles, scope, and auditability are explicit enough to prevent duplicate or stale provisioning actions.
Technical breakdown
Why eSIM profile lifecycle becomes the control point
An eSIM profile is the provisioned connectivity identity that lets a device join and remain on a network. In IoT, the challenge is not just initial issuance but matching the right profile to changing device capabilities, regions, and operators over time. When telcos manage only a small catalogue of profiles or rely on manual generation, they create latency, error, and scale limits. Lifecycle control therefore becomes the primary mechanism for availability and governance, because every profile is both a service object and a policy object.
Practical implication: Treat profile issuance, update, and retirement as a governed lifecycle, not a one-time fulfilment task.
Why delegated distribution needs stronger authorisation boundaries
The eSIM distribution chain often includes telcos, OEMs, enterprises, enablers, aggregators, and regional distributors. Each party may operate its own systems, which means provisioning authority can fragment across multiple control planes. Without clear delegation rules, organisations risk uncontrolled profile creation, inconsistent approvals, and weak revocation paths. This is an identity governance problem as much as a connectivity problem, because delegated management only works when permissions, scope, and accountability are explicit across every channel.
Practical implication: Define delegation scopes and revocation authority before allowing partners to provision or manage profiles.
How bulk orchestration changes inventory and fulfilment risk
Bulk management matters because IoT estates are not managed device by device. The article’s point is that profile delivery must support many devices at once, real-time status changes, and automated updates when devices move or change state. That requires orchestration, inventory visibility, and state synchronization across the eSIM platform and all connected distributors. Without those capabilities, stockouts and delayed activation become predictable operational failures rather than occasional exceptions.
Practical implication: Use bulk orchestration and real-time inventory tracking to prevent provisioning bottlenecks and stockouts.
NHI Mgmt Group analysis
Profile lifecycle is now a governance control, not an operations detail. The article shows that eSIM growth turns provisioning into an identity-like lifecycle problem because each profile must be issued, updated, delegated, and retired with policy precision. Traditional manual fulfilment cannot sustain that model once channels, device types, and geographies multiply. Practitioners should treat lifecycle orchestration as part of access governance, not back-office logistics.
Delegation without bounded authority creates the same risk pattern seen in over-permissioned identity programmes. When OEMs, enablers, aggregators, and distributors all have a role in provisioning, the real question becomes who can act, on which devices, and with what revocation path. That is a control design problem, not a partnership problem. Telcos need explicit delegable scopes, auditable approvals, and lifecycle offboarding discipline.
eSIM scale introduces profile sprawl. The article’s core insight is that large eSIM estates will not fail because of a single missing feature, but because profile sets, delivery paths, and inventory states drift apart faster than humans can reconcile them. That is the same structural weakness seen when identity estates outgrow their governance model. Practitioners should design for automated reconciliation before manual exception handling becomes the default.
Multi-channel provisioning should be evaluated as a control plane design issue. A single interface is useful only if it preserves segregation of duties, channel accountability, and state consistency across every provisioning path. Otherwise, it centralises confusion rather than control. Telcos should measure whether the control plane can answer who provisioned what, under which policy, and whether revocation reached every downstream actor.
The eSIM market is heading toward identity governance at scale. The more devices, distributors, and countries enter the model, the more telcos will need IAM-like governance logic for non-human provisioning entities. This does not make eSIM an IAM product, but it does mean the industry is converging on the same governance primitives: delegated authority, lifecycle state, inventory visibility, and revocation certainty. Practitioners should plan accordingly.
What this signals
eSIM profile lifecycle now behaves like a governed identity lifecycle. Telcos that treat provisioning as logistics will struggle once device state, channel distribution, and profile inventory diverge. The programme response is to design for issuance-time policy decisions, state reconciliation, and authoritative revocation before scale makes manual oversight impossible.
Delegation needs tighter control boundaries than most telecom operating models currently provide. The article points to a familiar governance failure pattern: when partners can act but accountability is unclear, the system becomes hard to audit and harder to unwind. That is where telcos should focus their operating model review, especially across enterprise and aggregator channels.
For practitioners
- Map every provisioning role and delegation path Document which telco, OEM, enterprise, enabler, or aggregator can request, approve, issue, update, and retire eSIM profiles, then remove any unowned path that lacks a revocation authority.
- Automate profile selection by device capability Tie profile issuance to real-time device attributes such as capability, region, and network requirements so that manual profile matching does not become the bottleneck.
- Build inventory monitoring into the control plane Track profile stock in real time across all channels and define alerting thresholds before stockouts affect customer fulfilment or activation latency.
- Test multi-channel state consistency Validate that a profile created, updated, or revoked in one channel is reflected across every downstream system that can act on the same device estate.
Key takeaways
- eSIM IoT scale turns profile issuance and retirement into a governance problem, not just a delivery problem.
- Distributed channels increase the chance of profile sprawl, inconsistent state, and delegated authority drift.
- Telcos need automated matching, real-time inventory visibility, and explicit revocation paths to keep control of the lifecycle.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack surface, NIST CSF 2.0 and CIS Controls v8 set the technical controls, and ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | PR.AA-05 — Access Permissions, Entitlements and Authorizations | Delegated profile provisioning depends on bounded permissions and auditable entitlement scope. |
| Recommendation — Apply PR.AA-05 to bound who can provision, update, and revoke eSIM profiles across every channel. | ||
| CIS Controls v8 | CIS-5 — Account Management | Shared provisioning roles and partner access need lifecycle controls and clear ownership. |
| Recommendation — Use CIS-5 to govern provisioning accounts, partner roles, and revocation of eSIM management access. | ||
| ISO/IEC 27001:2022 | A.5.18 — Access Rights | The article centres on delegated authority and the need to control who can act on profile lifecycle tasks. |
| Recommendation — Enforce A.5.18 to review and revoke eSIM management rights as roles and channels change. | ||
| MITRE ATT&CK | TA0006;TA0008 — Credential Access; Lateral Movement | Fragmented provisioning authority can be abused to move from one channel to broader control of eSIM lifecycles. |
| Recommendation — Map delegated provisioning abuse to TA0006 and TA0008 to hunt for overbroad channel access. | ||
Key terms
- eSIM Profile: A digital subscriber profile that replaces the physical SIM card’s stored network identity. It contains the credentials and service settings a device uses to authenticate with a mobile network, which makes it a governed identity object rather than a simple configuration file.
- Direct Provisioning: Direct provisioning means writing accounts, entitlements, or permissions straight into a target application rather than routing every change through an intermediary identity provider. It can reduce friction, but it also concentrates trust, audit, and rollback requirements into the connector itself.
- Profile Sprawl: Profile sprawl is the accumulation of too many profile variants to handle small access differences. It makes governance brittle because access logic gets buried in duplicated base configurations, which increases review effort and makes it harder to understand who can do what.
- Multi-Channel Control Plane: A shared management layer that coordinates provisioning across telcos, OEMs, distributors, and enterprise operators. Its value depends on whether it preserves consistent state and clear responsibility, rather than simply centralising many disconnected workflows in one interface.
Deepen your knowledge
NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, workload identity, secrets management, and identity lifecycle control. It helps practitioners connect delegated access, lifecycle discipline, and policy enforcement across complex programmes.
Published by the NHIMG editorial team on July 14, 2026.
Updated on October 13, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org