Overview of HyperSSL

HyperSSL is a simple Network channel encryption module which uses SSL/TLS protocol for its channel encryption. It operates in the network level of the OSI stack to offer encryption. HyperSSL has a Server and Client module and they can be configured to use with Smartcard. Network traffics to be protected have to be configured in a configuration file.

A HyperSSL connection is end to end tunnel encrypted traffic. It is capable of handling all TCP/IP protocols encrypted through a virtual network adapter. In order to achieve this, application programs are required to configure their network traffics to this virtual network adapter. The virtual network adapter creates an encrypted tunnel between two machines.

HyperSSL is able to configure and operate under:

• Server to client (See Figure 1 - HyperSSL Server to Client Connection)
• Server to server (See Figure 2 - HyperSSL Server to Server Connection)

HyperSSL uses SSL/TLS technology and is more simple and easy to use compared to IPSec in terms of installation, configuration, and management. HyperSSL’s simplicity does not compromise its effectiveness in providing protection or functionalities.

Unlike other SSL gateway products, HyperSSL keep applications out of Ring 0 that adheres to the secure OS Ring Architecture philosophy of non-interference with kernel space.

Product Features

HyperSSL features are as follow:

• Uses SSL/TLS
  
  
• Encryption :
  • AES-256 bit key in CBC mode;
  • RSA authentication;
  • Diffie-Hellman key agreement;
  • HMAC-SHA1 integrity checks.

Compliance to Open Standards

There are three modules in HyperSSL that support and comply to open standards. They are :

1. Cryptographic Module
   • Symmetric
     • AES 256 bits (FIPS-197)
   • Asymmetric
     • RSA (PKCS#1)
     • DH (RFC 2631)
   • Random Number
   • Hash
     • SHA-1 (RFC 3174)
   • ASN.1 (RFC 3641)
   • X.509 V3 (RFC 2459 & RFC 3280)
   
   
   
2. Smartcard Module (only on Microsoft Operating System)
   • Smartcard Reader : PC/SC
   • Smartcard : PKCS#11
   
   
   
3. Network Module
   • Protocol : SSL/TLS (RFC 2246 & RFC 3546)
   • Virtual Adapter: TUN/TAP virtual devices

System Support Requirements

Below are the minimum requirements your server and computer needs to run HyperSSL.

X.509 Version 3 Certificate

• SecuriCert HyperSSL X.509 Version 3.0 Certificate Generator Program
• Optional : Smartcard Reader / Cryptographic Smartcard

HyperSSL Server Configuration

• Operating Systems :
  • Microsoft 2000/2003 Server
  • Sun Solaris 9 / 10
• Hard Disk Space : 10MB
• RAM : 512 MB
• CPU : Intel Pentium 4 (1.7GHz) Or Sparc Processor for Sun OS
• Optional : Smartcard Reader / Cryptographic Smartcard

HyperSSL Client Configuration

• Operating Systems :
  • Microsoft 2000/2003 Server
  • Sun Solaris 9 / 10
• Hard Disk Space : 10MB
• RAM : 256 MB
• CPU : Intel Pentium 4 (1.7GHz) Or Sparc Processor for Sun OS
• Optional : Smartcard Reader / Cryptographic Smartcard

HyperSSL is currently not available on Windows 95, 98 and ME.

HyperSSL can be configured with or without smartcard.