HOW DOES SafeSMS WORK?

Using SafeSMS is not much different to receiving a regular text message. However rather than being able to read the text message immediately, the user must enter their unique PIN to decrypt it and read it.

So, how do you make an application, for example a WEB application, able to send an encrypted SMS? Quite simply in fact - at your WEB application, post (via HTTP or HTTPS) a SOAP/XML request to your u.assure Security Server (SNES), and, well, ...that's it!

The SNES looks up the receiver account details, session keys (AES, 3DES or RSA) from your directory, encrypts the message and submits it to its destination. There.s no need even to specify the receiver number, if you don't want to, just the receiver's username, email-address or a similar identifying information.

So, as you might've already guessed by now, you won't have to amend your existing directory accounts (i.e. Windows Domain accounts). Key management is LDAP based, as in any PKI implementation. No replication of account details or separate (and potentially insecure) key repositories are required.

NEXT STEPS? Try now! Watch a video Free trial Contact us