Safety Chunk: So, what occurred to cross-platform E2EE for RCS messaging?

9to5Mac Safety Chunk is solely delivered to you by Mosyle, the one Apple Unified Platform. Making Apple gadgets work-ready and enterprise-safe is all we do. Our distinctive built-in method to administration and safety combines state-of-the-art Apple-specific safety options for absolutely automated Hardening & Compliance, Subsequent Era EDR, AI-powered Zero Belief, and unique Privilege Administration with essentially the most highly effective and trendy Apple MDM in the marketplace. The result’s a completely automated Apple Unified Platform presently trusted by over 45,000 organizations to make thousands and thousands of Apple gadgets work-ready with no effort and at an reasonably priced price. Request your EXTENDED TRIAL right now and perceive why Mosyle is every thing you might want to work with Apple.

Earlier this 12 months, Apple introduced that it was main the cost on a cross-industry effort to carry end-to-end encryption (E2EE) to the RCS Common Profile, which is printed by the GSMA. Apple advised 9to5Mac in March it might come to the iPhone in a future software program replace. Google quickly after jumped in, stating it too was ‘dedicated to offering a safe messaging expertise.’

I didn’t suppose it was utterly unreasonable to imagine we’d see this showcased at WWDC 2025…that didn’t occur. Then I assumed possibly in one of many iOS 26 betas? Additionally nothing. So, what occurred to cross-platform E2EE for RCS messaging? Is it nonetheless coming?

With this functionality integrated into the usual, all Wealthy Communication Commonplace (RCS) messaging between iPhone and Android customers can be utterly unreadable to backend intermediaries—its contents encrypted, scrambled into gibberish, and solely unlockable with the decryption key saved on the consumer gadgets. Large for consumer privateness.

For the reason that launch of iOS 18 beta 2 in June, Apple has added RCS help, permitting iPhone customers to lastly ship wealthy messages with audio and bigger media information to Android customers who aren’t utilizing iMessage. It was a welcoming transfer for folks with dad and mom who refuse to get an iPhone. Not like the {industry} commonplace SMS, RCS presents acquainted options corresponding to learn receipts and the traditional typing indication animation, nevertheless it additionally provides the power to vastly enhance privateness and safety.

The key phrase is “capacity.”

There’s a standard false impression that RCS comes with end-to-end encryption (E2EE) baked in, however that’s not the case. Google’s Messages app, one of the vital broadly used RCS shoppers, presents E2EE between Android gadgets as an additional layer of safety for these utilizing the service. That is just like how iMessage supplies E2EE solely between Apple gadgets.

When an iPhone communicates with a non-Apple system through RCS, messages are solely encrypted in transit utilizing transport-layer encryption (like TLS). Whereas this protects towards primary interception throughout transmission, it doesn’t assure messages can’t nonetheless be accessible server-side, not like E2EE, the place solely the sender and recipient can learn the content material.

It’s nonetheless a significant enchancment over SMS, which sends messages in unencrypted plaintext, making them much more susceptible to interception. Nonetheless, with out full E2EE, RCS in its present state stays a step beneath platforms like iMessage or Sign.

In a press release to 9to5Mac in March, Apple stated:

Finish-to-end encryption is a strong privateness and safety expertise that iMessage has supported for the reason that starting, and now we’re happy to have helped lead a cross {industry} effort to carry end-to-end encryption to the RCS Common Profile printed by the GSMA. We are going to add help for end-to-end encrypted RCS messages to iOS, iPadOS, macOS, and watchOS in future software program updates.

At this level, it appears like a type of {industry} shifts that simply takes time to play out. Requirements must be finalized, after which Apple, Google, carriers, and everybody else within the chain wants to truly implement them. That sort of cross-company collaboration doesn’t occur in a single day or, on this case, over a 12 months. If something, we will proceed sleeping effectively at night time, on condition that each Apple and Google are publicly on board.

Thanks for studying Safety Chunk is a weekly security-focused column on 9to5Mac. Every week, Arin Waichulis delivers insights on knowledge privateness, uncovers vulnerabilities, and sheds mild on rising threats inside Apple’s huge ecosystem of over 2 billion energetic gadgets.

Follow Arin: Twitter/X, LinkedIn, Threads