CellTrust SecureSMS™




SecureSMS is a secure text messaging solution for enterprises, governments and consumers for transmitting sensitive and confidential information from handset-to-handset, server-to-handset or vice versa.

Using SecureSMS state-of-the-art mobile Micro Client, mobile phones utilize the familiar and user-friendly SMS channel to send and receive healthcare information, financial data or internal communication from others within their Circle of Trust™.

Integrated with CellTrust two-way global SecureSMS Gateway, SecureSMS implementation is similar to using standard SMS gateways. Supported by a set of high-level APIs, you can submit secure text messages from your own application or by using CellTrust's powerful web tools and plug and play scripts without the need for developing any code. On the handset, SecureSMS's full featured editor is used to send secure text messages to other handsets or your application.

CellTrust SecureSMS Benefits


  • Secure end-to-end encryption meeting the highest security standards
  • Optionally, specify your own encryption scheme for your Circle of Trust
  • Unique key for each handset with decryption limited to the designated device
  • Communicates over SMS channel (resilient and supported by all carriers)
  • Delivery and read confirmation
  • Remote data wipe in case of loss or unauthorized access attempts
  • Unlimited message size (limited by handset hardware)
  • Integrated with CellTrust SecureSMS Gateway supporting 218 countries and 700 carriers
  • Optional message archiving for reporting and compliancy
  • Rebrandable to your identity via SecureSMS FAVE icon
  • Certified with major carriers, operating systems and handset manufacturers

Encryption Methodology

Not just an SMS application, the CellTrust SecureSMS offering is a complete secure mobile communication solution incorporating a full featured secure gateway platform with advanced Micro Client technology.

In contrast to mono-key encryption methods, CellTrust SecureSMS utilizes a patent pending vanguard AES technology whereby each mobile phone has a unique encryption key and decryption is limited to the designated device. Encryption keys are dynamically generated, continuously changed and never kept on the mobile phone, meeting the most stringent security requirements. Secure messages are stored in an encrypted database with an expiration option and complete data wipe feature protecting the data against unauthorized access.

What is Advanced Encryption Standard (AES)?

The Advanced Encryption Standard (AES) specifies a FIPS-approved cryptographic algorithm that can be used to protect electronic data. AES was announced by National Institute of Standards and Technology (NIST) as U.S. FIPS PUB 197 (FIPS 197) [PDF, 273K] on November 26, 2001 and is adopted as an encryption standard by the U.S. government.

The AES algorithm is a symmetric block cipher that can encrypt (encipher) and decrypt (decipher) information. Encryption converts data to an unintelligible form called ciphertext; decrypting the ciphertext converts the data back into its original form, called plain text. AES is one of the most popular algorithms used in symmetric key cryptography.

Standard SMS Challenges

Current standard SMS technology is non-secure. It can be intercepted along the transmission path at multiple locations (aggregators, carriers, infrastructure providers, or tower operators) especially when using Internet to submit your messages. The content is transmitted as a plain text making it easy to eavesdrop. Depending on the carrier, messages larger than 160 characters (varies per carrier) are rejected, truncated or broken down into multiple messages that may be delivered out of sequence. Standard SMS is typically assumed delivered as soon as the carrier submits the message over their network without having any confirmed response from the recipient's mobile handset. Hence, there is no definitive way to determine if a message was received by the recipient or whether it was opened or just simply deleted. Standard SMS does not provide timing around any of these events.

To learn more about SecureSMS please see following pages:

- SecureSMS Micro Client
- SecureSMS Gateway
- SecureSMS API & SDK
- Implementation Models