Notifications
Clear all
Topic starter
25/06/2026 3:20 pm
TL;DR: Recent Signal-related incidents showed that sensitive conversations can be exposed through mistaken invites and linked-device phishing even when encryption remains intact, according to SSH Communications Security. The real control gap is operational trust: access verification, device governance, and monitoring now matter as much as cryptography.
NHIMG editorial — based on content published by SSH Communications Security: encrypted messaging still fails without access governance and verification
Questions worth separating out
Q: How should security teams govern encrypted messaging apps in sensitive environments?
A: Security teams should treat encrypted messaging as an access-governed system, not a confidentiality-only tool.
Q: Why do encrypted collaboration tools still create leakage risk?
A: They still create leakage risk because encryption protects content, not the human decisions and device approvals that expose it.
Q: What should organisations do when a linked device is suspected to be rogue?
A: They should revoke the device immediately, verify all active session memberships, review message exposure, and document the trust failure as an identity governance issue.
Practitioner guidance
- Treat device linking as privileged access Require explicit approval, visible ownership, and periodic recertification for any linked messaging device used for sensitive conversations.
- Verify chat membership before sensitive exchanges Use membership checks, recipient validation, and classification prompts before any operational or classified discussion begins.
- Add revoke workflows for compromised sessions Make it easy to remove unauthorized participants, unlink rogue devices, and confirm that the revocation took effect across all clients.
What's in the full article
SSH Communications Security's full research covers the operational detail this post intentionally leaves for the source:
- Specific discussion of how secure messaging changes when encryption is paired with access verification and monitoring.
- The vendor's framing of operational-grade messaging security for mission-critical environments.
- Product context for SalaX Secure Messaging and the Element plus Matrix stack used beneath it.
- References to the public incidents and ecosystem details cited by the vendor, including platform and standards context.
👉 Read SSH Communications Security's analysis of Signal exposure and secure messaging trust gaps →
Encrypted messaging: what IAM teams miss about operational trust?
Explore further
25/06/2026 4:48 pm
Encryption without operational trust is an incomplete control model. The article’s central point is that confidentiality technology cannot compensate for weak invitation hygiene, weak device governance, or poor verification of who is entitled to see a conversation. In identity terms, the control failure sits above the crypto layer. The practitioner conclusion is that secure messaging must be governed as an access system, not only as a protected transport channel.
A few things that frame the scale:
- Two-thirds of enterprises have endured a successful cyberattack resulting from compromised non-human identities, with a quarter encountering multiple attacks, according to The 2024 ESG Report: Managing Non-Human Identities.
- 72% of organisations have experienced or suspect they have experienced a breach of non-human identities, with 46% confirmed and 26% suspected.
A question worth separating out:
Q: Who is accountable when sensitive chats are exposed through user error or device phishing?
A: Accountability typically sits with the organisation’s communication governance owners, because the failure is usually in access policy, training, and review rather than encryption itself. Security, IAM, and collaboration platform teams should share responsibility for membership control and device assurance.
👉 Read our full editorial: Encrypted messaging still fails without access governance and verification
