How it's managed

Mideye from the administrator's perspective

Mideye can be implemented to protect virtually any remote access service that requires strong two-factor authentication. Examples include:

• Remote access to corporate LANs
• Extranet services
• Internet banking
• Access to Wireless LANs
• E-business services
• E-government services

To implement Mideye, the service provider (e.g. enterprise, bank, or government authority) installs a Mideye Server in a protected environment within the internal network. The server is integrated with access products such as firewalls, VPN servers, and web servers via standard interfaces and APIs.

No Integration

Since the Mideye Server is a RADIUS server, no integration is needed for most RAS (remote access solutions) products. An easy API is also available for building strong authentication into customized web applications.

No Administration

Since the Mideye Server authenticates using the user's mobile phone and not a hardware token, there is no hardware administration. No OTP tokens to manage, send out or loose. And since the Mideye Server is integrated to LDAP, there is no extra user administration. The connection to GSM networks is provided through a secure Internet connection to a centrally operated Mideye Switch.

No Upfront Investment

Since Mideye is a service, there is no upfront investment and a very low cost of ownership.