|
|
Login |
 |
 |
|
|
|
|
Did you know? |
 |
 |
Why choose SafeInput?
|
|
|
Random FAQ |
 |
 |
Disable soft-keyboard input.
|
|
 |
 |
|
SafeInput Control Features |

|
|
A secure online
transaction includes three main aspects: 1. Server-side: security is well understood and system administrators
generally guard their server-side security
very well, reducing the risk of hacking attempts on the server. 2.
Transmission: security is also well understood with Secure Sockets Layer
(SSL) providing strong encryption
between the client and server. 3. Client-side: security, although
well understood, is generally neglected by end-users who are not sufficiently motivated to take
action against hacking attempts, or do not have the skills or knowledge to implement proper
security measures or take precautions.
SafeInput Control is focus on Client-side
and Transmission protections.
SafeInput Control can be easily
deployed on any input field (e.g. Login form) of a website.
How does it work?
-
SafeInput Control does not affect the normal use of a website. It will be applied only when visitors
access to a page which is deployed SafeInput Control.
-
Visitors will be asked to install SafeInput Control at the first
time when they access a page which is
deployed SafeInput Control. If a visitor has already installed
SafeInput Control from another
website, they don't need to install it again. That's what we
call "Install once, run everywhere" .
-
If the visitors do not want to use
SafeInput Control they can still use the original method to input.
-
When visitors entering data via
SafeInput Control everything
entered is secured
by SafeInput Control, which can prevent over 99% of keyloggers,
Trojans, Viruses, and Worms from stealing users' critical information.
-
SafeInput Control will then encrypt and
transmit the data to Server-side, on which the data is
decrypted.
Click here to view the main advantages of SafeInput Control. |
Workflow illustration

|
System Requirement |
|
Server |
No limitation |
|
Database |
Not required |
|
Web Browser |
IE 5.0 or
higher (Client side) |
|

|