UNDERSTANDING SSL

The primary goal of the SSL (Secure Sockets Layer) Protocol is to provide security and authentication between two communicating parties. When used properly SSL can provide a level of security that exceeds most other modes of data submission, including paper. SSL has become the standard for commerce over the internet. To date, there has never been a documented case, where SSL was being used, and security was violated (see Netscapes On Security). The only known credit card fraud that has occurred over the internet has been at sites where no security was being used.

The SSL Handshake Protocol allows the client to authenticate the host and to negotiate an encryption algorithm and cryptographic keys before the application protocol transmits or receives a single byte of data. Authentication is necessary to prevent Spoofing, a technique whereas a local user, i.e. the internet service provider of the client, sets up an elaborate system pretending to be the host. If the unsuspecting client signs on without authentication, the spoofer acts as if he is the legitimate host and mediates the data. This is not possible with Authentication. Authentication uses an encrypted token that validates the host with a third party company, without this validation the transaction will not take place. The validation also provides a visual cue to the client, such as the closed key on the clients browser screen; showing the client that he or she is now in a secure transaction.

The connection IS private. Encryption is used after the initial handshake to define a secret key. Symmetric cryptography is used for data encryption (e.g., DES[DES], RC4[RC4], etc.), these are significant levels of encryption that cannot be broken without days of processing time on a given data set with a given encryption key. Because the keys are always changing during the negotiation phase, and because transactions usually only last a few minutes, it is not possible to break the code in the time available.


OTHER SECURITY TECHNIQUES THAT WE USE

Client IP Address Authentication
The InterFrame server tracks the clients IP address (the addressing scheme that the internet uses to uniquely identify a given node), and only responds to this address during a given transaction, assuring that the same user that started the transaction is finishing the transaction.

Dynamic Host Redirect
A technique whereas the user is authenticated and supplied with a set of personalized forms, each containing a unique, random sequence. This sequence is only live on the host for the duration of the transaction. The client can submit only these forms and only for a brief period of time.

Dynamic Port Redirect
A technique whereas the user is authenticated and supplied with a set of personalized forms, containing links to predetermined ports (frequencies on the internet), these ports are valid for only a brief period of time and only for specific authenticated clients. This assures that only one client has access to a given transaction.