Security Basics
RE: Re: Bank Of Montreal Online Security Nov 02 2012 07:07PM
Mikhail A. Utin (mutin commonwealthcare org) (3 replies)
Re: Bank Of Montreal Online Security Nov 04 2012 01:50AM
Davin Enigl (davinenigl comcast net) (1 replies)
RE: Bank Of Montreal Online Security Nov 23 2012 11:45AM
Ken Schaefer (ken adOpenStatic com) (1 replies)
Re: Bank Of Montreal Online Security Nov 24 2012 06:12AM
Nathan V (nathan v gmail com)
Re: Bank Of Montreal Online Security Nov 03 2012 12:40AM
Davin Enigl (davinenigl comcast net)
Re: Bank Of Montreal Online Security Nov 03 2012 12:33AM
Davin Enigl (davinenigl comcast net)
On 11/02/2012 12:07 PM, Mikhail A. Utin wrote:
> Frankly, considering usual number of a bank customers,

which could be up to 10 million, using anything better

than a user name and a password create a technical

problem for IT, meaning finally money.

Wrong. Bank of America uses "SafePass": a one time password card
("liquid paper" window) that generates numbers, 12 (six at a time with a
press of a button), accounting for 10^12 random numbers -- to
authenticate users to their on-line accounts. So far it's been optional,
leaving users to chose it or not. The users pay a small one-time fee. I
think I paid $20USD. They have been doing thins for about five years.

PayPal and eBay have way way more than 10 million users and they do it
too, -- again for about five years so far.

------------------------------------------------------------------------

Securing Apache Web Server with thawte Digital Certificate
In this guide we examine the importance of Apache-SSL and who needs an SSL certificate. We look at how SSL works, how it benefits your company and how your customers can tell if a site is secure. You will find out how to test, purchase, install and use a thawte Digital Certificate on your Apache web server. Throughout, best practices for set-up are highlighted to help you ensure efficient ongoing management of your encryption keys and digital certificates.

http://www.dinclinx.com/Redirect.aspx?36;4175;25;1371;0;5;946;e13b6be442
f727d1
------------------------------------------------------------------------

[ reply ]


 

Privacy Statement
Copyright 2010, SecurityFocus