Security
One of the main concerns we heard from members as we developed this product was privacy of transaction data as well as protecting the Credit Union's internal network and member data. NOTE: If utilizing pal@net via TCP/IP we recommend placing behind Firewall or DMZ. We Also recommend site authentication via NetworkSolutions utilizing port 443.Explanation to follow:
Member Security
For the member's protection of confidential data, internet desktop Banking employees two forms of security:
1. Dual Pin/Password verification
2. 128 Data Encryption.
The Credit Union has the option to utilize 1 or both although N.C.U.A. would highly recommend implementing both security measures.
Dual Password Protection requires the user to enter a password, in addition to A "PIN" number to ensure account information is not accessed by any unauthorized users. We require this of our membership so to provide another form of defense there by ensuring secure transactions to your accounts.
Data Encryption is a process which transposes account information which is sent from our host server to your browser. The coded data cannot be interpreted or altered without using a defined "key". The "key" deciphers the information from our server which in turn allows you to view your account information securely at your desktop.
Currently there are two levels of RSA data encryption that our server will provide, 40-bit and 128-bit. 40-bit data encryption is the standard method that is used all over the world for electronic commerce and is the least secure. 128-bit encryption is the highest form which is available with Internet Explorer 5.5 SP2 and is the recommend data encryption to secure all your transactions.
Network Security
The second facet of our security is protection of the Credit Union's internal network and member information from access by unauthorized internet users. (Host to server is strictly via a serial connection unless utilizing TCP/IP then a firewall is required as discussed above) Internet transactions are routed to the Credit Union from the client via a T1/FRAME RELAY/ISDN or dial-up connections. When requests reach the C.U. router, the traffic is either sent to the home banking server (a specific, secured port address), or to a proxy server. The proxy server allows us to isolate our local network from the public Internet. The pal@net Banking server is connected via a serial port or TCP/IP to the main computer that houses the account information. Only a valid transaction request from the member via a pin and password can cause information to be downloaded from the C.U. host computer back to the client via the internet. Utilizing these methods will disallow unauthorized access to our network including all member information. The pal@net server stores no Pin, Password or specific account information what so ever, its solely a pass thru via a serial connection from the host server, unless utilizing TCP/IP it then will be defended via a proxy/firewall device.