Connecting long-term flexibility with day-to-day resilience
The GSMA’s 2026 eSIM updates provide useful technical context as organisations plan deployments for 2027 and beyond. Remote profile management allows connectivity arrangements to change over time, while SIM-level switching helps devices respond to connectivity failures. These are complementary capabilities: one supports planned changes, while the other responds locally when a connection fails.
For customers, bringing them together supports a more coordinated approach to expanding deployments, adapting operator arrangements and maintaining service resilience.
How CSL brings eSIM management and local resilience together
CSL combines managed IoT connectivity, eSIM orchestration and rSIM® resilience in one managed-service proposition. The CSL IoTM platform coordinates connectivity and profile-management workflows across supported mobile operator portals, connectivity management platforms, remote SIM provisioning systems and eSIM IoT Remote Managers (eIMs).
Customers can use CSL’s managed connectivity, retain existing mobile operator relationships or combine the two. CSL can also provide eIM services or integrate with a customer-selected eIM, offering flexibility in how the solution is delivered.
Alongside this remote management capability, rSIM acts locally within each device. The SIM holds two distinct multi-network roaming profiles, with SIM-resident logic that tests the active connectivity path and can select the alternative profile when the configured failure threshold is reached. This switch does not require an instruction from the eIM or platform, because the profiles and switching policy are already on the SIM.
Read more: How CSL delivers eSIM management together with rSIM resilience.
What the 2026 eSIM updates mean for deployment planning
The updates cover three areas relevant to the technology supporting IoT deployments:
- Remote profile management. The GSMA’s IoT specifications, SGP.31 and SGP.32, reached v1.3 in May 2026 as a maintenance release. They refine existing procedures and clarify requirements for components such as the eSIM IoT Remote Manager (eIM). The accompanying SGP.24 compliance process sets out how relevant products and services demonstrate compliance.
- eUICC security evaluation. The eUICC is the secure SIM hardware and software that stores operator profiles. SGP.27 adds application-isolation requirements covering separation between applications, operator profiles and the underlying eUICC platform. These build on existing security requirements rather than replacing them.
- Profile-delivery infrastructure. SGP.14 v2.3 introduces shorter maximum validity periods for TLS certificates used by SM-DP+ and SM-DS servers. These changes concern certificate lifecycle management within the infrastructure supporting profile delivery.
What v1.3 means for existing and new deployments
Annex C of SGP.24 v2.7 lists both v1.2 and v1.3 as active for compliance, with no expiry date currently specified. Publication of v1.3 does not, by itself, require changes to existing v1.2 deployments. The detailed specification updates are summarised in the table under “Technical reference: GSMA eSIM publications in 2026” towards the end of this article.
Plan connectivity around the life of your IoT estate
Plan for both the changes you expect and the connectivity failures you need to respond to. CSL’s combined approach supports that planning, from initial deployment through ongoing operation.
To discuss connectivity, profile management and resilience for your IoT deployment, contact CSL.
Technical reference: GSMA eSIM publications in 2026
For readers looking for the underlying technical detail, the table summarises the ten specifications and application notes listed by the GSMA from April to October 2026.
| Specification or application-note date (2026) | Document | What changed | Who it concerns |
|---|---|---|---|
| 24 April |
SGP.21 and SGP.22 v2.7
|
New versions in the consumer v2.x line | Makers of consumer v2.x products |
| 19 May | AN‑2026‑05 v1.0 | Clarifies two formatting errors in the SGP.22 v2.7 ASN.1 definitions. | Implementers of SGP.22 v2.7 |
| 22 May | SGP.31 and SGP.32 v1.3 | New versions of the IoT architecture and technical specification | IoT eUICC and device manufacturers, eIM providers and SM‑DP+ service providers |
| 22 May | SGP.14 v2.3 | Shorter maximum validity for newly issued SM-DP+ and SM-DS TLS certificates: 200 days initially, 100 days from 15 March 2027 and 47 days from 15 March 2029 | Operators of SM‑DP+ and SM‑DS servers |
| 17 July | SGP.24 v2.7, with Annex C | The compliance process for consumer v2.x and IoT products, replacing v2.6.1. Introduces SGP.27 into eUICC security evaluation, subject to defined exclusions | Providers declaring consumer v2.x or IoT products compliant |
| 17 July | SGP.27 v1.0 | A new module adding application isolation to the SGP.25 eUICC protection profile | eUICC manufacturers and their security laboratories |
| 26 October | SGP.06 and SGP.07 v2.4 | Consumer and IoT eUICC security assurance updated to include SGP.27 alongside SGP.25 | eUICC manufacturers and their security laboratories |
Source: GSMA eSIM specification listing, accessed 13 November 2026.
Further reading
- GSMA eSIM Consumer and IoT Specifications
- SGP.31 v1.3: eSIM IoT Architecture and Requirements
- SGP.32 v1.3: eSIM IoT Technical Specification
- SGP.24 v2.7: RSP Compliance Process
- Annex C: eSIM Certification Applicability, accompanying SGP.24 v2.7
- SGP.27 v1.0: Application Isolation in the eUICC
- SGP.14 v2.3: eUICC PKI Certificate Policy
